CFOpro.

The problem

CFOpro is a CFO-as-a-Service firm for Polish SMEs — an outsourced finance director for companies that don't have one on staff. A business like that has to do two hard things at once: reach owners who are only just starting to look for financial help, and run its clients' finance operations flawlessly. The first needs a steady stream of content it has no spare hands for. The second — until now — ran on scattered Excel files, invoices buried in inboxes, and amounts retyped by hand.

What I built

Two AI systems: one that brings clients in, and one that runs their finances.

A content engine that brings clients in. A new cfopro.pl (Next.js, no CMS) and the agentic content engine behind it: a multi-agent system that researches a topic on its own, writes an article in the brand's voice and gets it ready to publish. I mapped 24 topic clusters onto the real questions owners ask; the system has written 200+ articles from them, released one a day. Sensitive pieces — on tax or KSeF — pass through an editorial gate where a person confirms the numbers before the post goes live. An engine that builds search authority without a standing content team.

A finance operating system that replaced the spreadsheets. I moved the firm's operational core out of scattered Excel files into a single Coda doc:

• A counterparty registry — one base of clients and vendors, filled in automatically with every new invoice.
• An income-and-expense ledger — fed straight from the documents, not from manual retyping.
• A hub for the finance manager — what's overdue, who needs paying and how much, where the deadlines are — in one place.

Under it, four automations pull documents into the system with no one in the loop:

• KSeF, daily — at dawn the system pulls invoices from Poland's National e-Invoice System for every entity, renders a readable PDF, archives it and creates the invoice row in Coda, skipping anything it has already ingested.
• Invoices by email — cost invoices arriving by email are read by OCR, with an AI model normalizing the data when the read is uncertain; the finished record lands in Coda and on Drive.
• Receipts — the same machinery for receipts, so small costs don't slip through.
• Month-end pack — on demand, the system validates the amounts, builds the folder structure for the month and assembles the documents to hand to accounting — with correctness checks and cleanup on error.

The outcome

A CFO-as-a-Service firm now has both a demand engine and a delivery engine. Content builds itself, one article a day, with editors watching only what needs an expert's eye. Clients' finances no longer live in spreadsheets: invoices fall into a single system on their own, and instead of retyping amounts the finance manager looks at a finished picture of what to pay and when. Less manual work, fewer places to go wrong, and operations that scale with the number of clients rather than the number of hours.