For accounting practices
QuickBooks conversions, inherited messes, clients whose payouts never tie out. Work that isn't bookkeeping and isn't billable, but lands on your team anyway. I take it off your plate, one client file at a time.
Starting point
Not with a formal arrangement. With one project, for one client.
You send over whatever's in front of you — the Desktop conversion nobody wants, the client whose books came over wrong, the Stripe file that eats four hours every month. I scope it in writing, do the work, hand it back with the reconciliation attached.
If it's useful, we talk about what a standing arrangement looks like. If it isn't, you've spent what a one-off was going to cost you anyway.
Capabilities
Support for Desktop 2023 ended in May. Desktop 2024 is the last version there will ever be, and it goes in September 2027. Intuit's own tool moves the data, then quietly reroutes entries through suspense, converts paychecks into ordinary checks, and gives you no way to fix one thing without overwriting the file. I do the cleanup first, map the chart of accounts, migrate, and hand back a reconciled opening balance you can sign off on.
Every client you win costs your team a week or two before a single billable hour is logged. Records chased, accounts mapped, historical reconciliation, bank feeds connected. I run that end to end, per file, on a process that stays the same whether it's your next client or your fiftieth.
The inherited ones. Four hundred lines in the chart of accounts, six versions of the same vendor, accounts that haven't reconciled since the previous bookkeeper left. Fixed-price per file, with a written record of what changed and why.
Every firm has three or four clients on Stripe, Shopify or PayPal where the payouts never match the ledger. I automate the match at the transaction level — fees, refunds and FX split out to the right accounts, exceptions surfaced for someone to decide on. Built once, runs every month after that.
Domain background
Five years in accounting practice and a full professional accounting qualification programme before I moved into engineering. Ten years building software since.
That's the whole difference. Most engineers treat a ledger as a data problem, get the rows across, and leave you to find out in February that the opening balance was never right. I know what a cut-off is, why a clearing account has to net to zero, and what your reviewer is going to check first.
Clean boundaries: I don't do the accounting work. No bookkeeping, no filing, no advisory, and I'm never in front of your client. Your relationship with them stays yours.
Case studies
Payment Infrastructure & Accounting Automation
Payouts, fees and refunds never matched the ledger. Automated at balance-transaction level: payouts tie to the cent, revenue available same-day.
AI & Accounting Automation · Live Beta
Built for bookkeepers doing this by hand every week. AI coding with confidence thresholds, exceptions routed to a human queue. Categorisation time down about 80%.
ERP Architecture & Migration
Full migration with payroll and statutory e-invoicing. Python migration scripts with dry-run validation before anything was committed.
Ongoing relationship
Reply with the client file, the system it's stuck in, and what you need it to look like when it's done. I'll come back with a scope and a price, in writing, before anything starts.
Prefer to talk it through? Book 30 minutes.