We rebuilt an entire finance function with zero extra headcount. AP, AR and vendor onboarding are where we start in yours.
Corporate back offices grow by adding people to queues. We look at your four worst queues, automate the mechanical parts, and leave your team the exceptions.
Two weeks, fixed price. You keep the savings map either way.
- 40%
- operating costs cut, no new hiresWinnit
- 0
- extra headcount — finance rebuilt end to endWinnit
- 0 diffs
- against the human-led filing deliverableCase study
A two-week audit names your worst four
Invoice against purchase order against ledger
Approvals and escalations on rules you set
Mismatches arrive with the discrepancy already named
Every error found once becomes a recurring check
GATEFlag, never guess. An unverifiable value never enters a statutory filing, a payment run or a board pack — it stops and waits for a person.
Accounts payable
Invoices arrive as PDFs in a shared inbox. Someone reads them, matches them to a purchase order, routes them for approval, chases the approver, then keys them into the ledger. We automate the read, the match, the routing and the chase. Mismatches come to a human with the discrepancy already named.
Accounts receivable and collections
Dunning is the most reliably neglected process in a growing company, because it is awkward and repetitive. Automated, it is neither: reminders go out on schedule, escalate on rules you set, and stop the moment payment lands.
Vendor and procurement admin
New vendor onboarding — documents, tax details, bank verification, approval trail — is a form-filling exercise pretending to be a control. We keep the control and remove the form-filling.
Marketing and reporting operations
Not strictly finance, but the same shape of problem, and the numbers are the sharpest we have. Reporting, campaign assembly and routine content production are mechanical work that agencies bill as creative work.
The objections we actually get
“Our data is too sensitive to hand to a third party.”
You don't have to. The work runs inside your own accounts — your ledger, your document store, your bank feeds. Nothing is copied out to a platform we own, because there is no platform we own. Only code crosses the boundary.
“We bought AI tools before and nobody used them.”
So did we, before we started building instead. A tool arriving beside an unchanged process gets abandoned. We rebuild the process, run it ourselves for a while, and hand it over only once it has been working long enough to trust.
“We don't have the engineering capacity to support this.”
You don't need it. We supply the engineer, and they work in your systems for the length of the engagement. At handover you get the code, the documentation and the training — and if you would rather never touch it, we keep running it.
What this looked like the last time we did it
Each one is a documented rebuild — the situation, what we built, and what came out of it.
Vendor invoices reconciled auditor-style
4 group entities on one process; 4 previously manual errors now encoded as automated checks
FinanceFiling prep, re-derived independently
0 cell differences against the human-led deliverable; 4 real issues caught
FinancePricing decisions run on margin math
Every quote backed by real customer volumes and modelled margin scenarios
SalesAn SEO agent with publishing authority
46 stale posts found; publishes at most 2 posts per run, behind 5 hard gates
MarketingA paid daily newsletter
8 verified runs; 4–6 stories now fit in a single day, with a human holding the send button
MarketingCMS hygiene sweep
137 junk entries archived; a pricing update stranded 27 days pushed live and verified
MarketingWebsite audit, traced to root cause
~100K daily impressions against 29 clicks, traced to 3 code defects and 178 MB of assets
MarketingLifecycle emails that check the database first
Live since 30 June with 0 manual steps; exits silently if the account has already funded
MarketingQuestions people ask before booking
How is this priced?
Discover is a fixed price for a two-week audit. Build & run is monthly, per scoped workflow, so you can start with one queue. Transfer is included at exit rather than sold as a tier.
Who owns the code afterwards?
You do. At handover you receive the code, the documentation and the training. That is the point of the Transfer step and it is not an upsell.
What happens when the underlying models change?
The gates do not move. A model change can alter a draft; it cannot alter what is allowed to send, pay or file without a human. That boundary is structural, not a setting.
How long before we see anything?
Two weeks to a savings map. First workflow live is usually measured in weeks, not quarters, because we start with one queue rather than a transformation programme.
Start with one queue. If the first one does not pay for itself, there is no reason to do the second.