Cogny Cloud · Fortnox

Stop guessing which marketing actually makes money.

Cogny reads Fortnox (read-only), joins your invoiced revenue and repeat-customer LTV to ad spend across Google, Meta, GA4 and Search Console, and creates a ticket per profitable optimization. Approve in tickets — your bookkeeping stays untouched.

❯ book a Cloud demo see how it replaces the manual flow →

❯

cogny --replaces

FLOW

Same outcome. Two very different processes.

How you do it today

Export invoices and customers from Fortnox.
Pull ad spend from Google, Meta and GA4 — separately.
Try to match paying customers back to campaigns in a spreadsheet.
Guess which segments are actually profitable. Repeat next month.

How Cogny Cloud does it

Cogny connects to Fortnox + your ad platforms via MCP — one-time, read-only on Fortnox.
Pulls invoices, customers and articles daily — no login, no export.
Joins invoiced revenue and repeat-customer LTV to ad spend and segments.
Finds insights: campaigns winning paying customers (not just leads), high-margin segments, spend that never turns into revenue.
Creates a ticket per proposed optimization.
You approve in tickets — Cogny executes through your ad-platform MCPs (Fortnox stays read-only).
Tracks which optimizations actually lifted profit. Smarter every period.

❯

cogny --tickets

read-only

Cogny creates tickets. Execution flows to your team or Cogny Code. Each insight becomes one ticket — here are the kinds Cogny creates from Fortnox:

Profit-campaign ticketA campaign winning high-LTV paying customers in Fortnox — proposes scaling the spend.

Burn-alert ticketSpend climbing on a campaign that is not converting to invoiced revenue — proposes a pause.

High-margin segment ticketThe customer segment with the best margin in Fortnox — proposes doubling down on it.

ExecutionFortnox is strictly read-only — Cogny reads invoices, customers and articles but never creates, edits or posts anything. Your bookkeeping stays untouched. Approved tickets execute through your ad-platform MCPs (pause/resume, budget shifts) or become an email-digest checklist. Cogny does not write copy or creative.

LearnsCogny learns which campaigns and segments actually turn into invoiced revenue and repeat customers for your business — so over time the tickets point at the spend that pays back, not just the channels that look busy.

❯

cogny --reads

DATA

The reports Cogny pulls on schedule for Fortnox insights

FortnoxInvoices, Customers, Articles — read-only

Ad platformsGoogle + Meta — spend signals

GA4Site usage + conversions

Cogny memoryOrg context across periods

❯

cogny --book

DEMO

Tell us your use case. Then book a 15-min Cloud demo.

❯

cogny --faq

ASK

The questions we usually get on the demo call

Does Cogny change anything in my Fortnox bookkeeping?

No. The Fortnox connection is strictly read-only — Cogny reads invoices, customers and articles to join your revenue to your marketing. Cogny never creates, edits or posts anything in Fortnox. Your bookkeeping stays exactly as your accountant left it.

Does Cogny replace Fortnox?

No. Cogny connects to Fortnox and adds an AI analyst on top — you keep using Fortnox for everything you do today.

Does Cogny make changes automatically?

No — Cogny creates a ticket for every proposed action, you approve in tickets, then it becomes an email-digest checklist your team executes. Fortnox is read-only via the MCP. Site or code changes can be shipped automatically through Cogny Code (PRs against your GitHub).

Does Cogny write copy or creative?

No. Cogny does not write ad copy, email bodies, post content, image creative or rewrite existing copy. Cogny’s execution is limited to structural changes — segments, tags, metadata, internal links, redirects, scheduling assets you’ve already drafted, status changes (pause/resume/archive), and code-level PRs via Cogny Code.

Does Cogny actually get smarter over time?

Yes. Every approval and rejection is a signal. Cogny tracks the outcome of each executed ticket (did the deal close, did the ranking recover, did the segment lift revenue) and tunes its proposals to your business — so noisy or irrelevant tickets fall off and the high-signal ones become the default.

❯