I build management accounting systems — and I write the code myself. Cash flow and P&L that reconcile with your bank to the penny, not “approximately”. When the project ends, the system is yours, source code included.
Remote work, any time zone · Russian and English
Three situations after which an owner stops trusting their own numbers.
The P&L shows a good month, and two weeks later there's nothing to pay contractors with. Balance is not profit — and without a cash flow statement you can't see the difference.
Bank, inventory, CRM. Each is right on its own, none of them agree, and reconciling them is somebody's full-time job.
Books close by the middle of the next month. The decision was needed yesterday, and the data is from the day before that.
Errors aren't the danger. Invisible errors are: the report looks clean, the totals add up, and the decision is made on wrong data.
Closing cash in the report, the balance on your accounts and the bank statement must all show the same number. If they don't, the system names the account, the period and the difference in money.
Real double-entry bookkeeping, the same as your accountant uses. The balance sheet either closes at zero or shows the gap. There is no third option.
Uncategorized transactions, import duplicates, transfers missing their other half — all of it is listed with amounts, instead of surfacing in a report a month later.
For example: an expense category flagged as income; a transfer between your own accounts that lost its other half; a cash account gone negative. Each check compares two independent sources and shows the difference in money — before the report reaches the owner.
The rule this is built on: if a calculation can quietly lose money, there must be a check standing next to it that says so.
What's left for a human: confirm the unclear ones and read the reports.
Bank statements and APIs, inventory system, CRM, cash and expense claims from a phone. Everything lands in one place, duplicates are filtered out.
Rules by description, counterparty, amount and account; what rules miss is picked up by a model that learns from your corrections.
Cash flow, P&L, balance sheet, receivables — by project, entity and period. Today's data, not last month's.
Built on double-entry bookkeeping — the same method your accountant uses, turned to face the owner instead of the tax office.
Operating, investing and financing flows, with control blocks so the closing balance always ties out.
Revenue, variable and fixed costs, gross and contribution margin, EBITDA. By project and by entity.
Assets equal liabilities plus result — or the system tells you they don't.
Who owes you and whom you owe, with history and ageing.
FIFO costing by lot, so gross margin is calculated, not guessed.
Every movement in one list with filters and bulk actions. You can see how each line was categorized and why.
PDF, Excel, CSV. Duplicates are caught by content, not by file name.
Cash handlers and staff enter operations from a phone browser and see their own balance.
Owner, finance, staff. Everyone sees only what they should.
Subscription tools stop showing your numbers the day you stop paying. Here the build is paid once and the system is yours — support is convenience, not a leash.
Paid by stage, not upfront. Exact figure after a free review — it depends on how many accounts and sources you have and how deep the accounting needs to go.
Not everyone needs a full accounting build right away. Often the sharper pain is people doing by hand what should happen by itself.
Take a task someone repeats every month. Count the hours and the cost of an hour. That's the price — and it repeats every month for as long as the task is manual.
Automation typically pays for itself in 3–6 months and works for free after that. The person freed up goes back to what you hired them for.
A one-off project with a clear beginning and end. Start with a single task and judge by the result.
Usually this job is split between two people — and the numbers fall through the gap between them.
A consultant writes the methodology. A developer writes the code. The developer builds what he understood, the consultant sees the result a month later.
One person owns both. “The cash flow doesn't match the bank” stops being a two-week email thread and becomes an evening of work.
15 years in finance for small and mid-sized business. Double-entry bookkeeping, IFRS-based revenue recognition, FIFO costing. TypeScript, Next.js, PostgreSQL, Python.
Forty minutes: how your accounting works today, where data gets lost and what can be closed quickly. No obligations — you leave with a plan even if we don't work together.