Meet the minds behind TwinMind.
We are twin brothers in Brisbane. One of us qualified as an economist, the other as a software engineer, and for more than twenty years since, each of us has worked in both trades at the same time: writing the software, and carrying the books that software had to serve. Today we design the systems and run fleets of AI agents that build them, with 18 of them in production.
Twin brothers, and each of us holds both halves of the work
That is the part worth understanding, because it is unusual. Each of us is both at once: a finance professional who has carried a real ledger, and an engineer who has built production systems. Both of us have answered for real accounts, ledgers, month-end, audits and tax, while writing the systems that carried them. Sergii leans further into the finance, Alex further into the engineering, and that is the whole of the difference, so whichever of us you speak to holds both halves of the work.
Every system we ship is therefore designed by someone who has done the job it carries. That is why it survives contact with a real month-end, a real warehouse and a real audit.
And we answer for a date. Both of us came up in jobs where month-end closed on the day it closed and an audit arrived when it arrived, so a date we agree to is a promise. The person you speak to at the beginning is the one still answering for it at the end.
Principles we build by
Not slogans - constraints. They decide what we ship, and what we hand back.
We build what is specific to your company
The approvals, the exceptions, the odd formats, the rollups that exist only here, the systems built decades apart that now have to talk. We start from how the work is actually done, and build that.
Audit-ready by design
Every figure traceable to its source, every action logged. "Why did this change, and who approved it?" is always answerable.
A human approves anything touching money
Automation does the work; a person makes the call. Anything that moves money or reaches a regulator waits for sign-off.
Hosted onshore in Australia
Client systems are hosted in Australia by default, aligned with the Privacy Act. Where a component sends data offshore, we tell you in writing first. Built for local businesses, on local ground.
You own the system
The code, the data and the system are yours, and they keep running on your own ground for as long as they are useful to you.
Scoped and quoted up front
Price, boundary and dates are agreed in writing before the work starts. We map the work in the Audit and hand you a costed, fixed-scope plan before a line is written.
Audit, build, run
A short, costed path from "this is painful" to "this runs itself."
Audit
We study how the company actually works and say plainly which parts are worth building, and in what order. A fixed A$2,000, one to three days, credited in full against your first build, and the written findings are yours to keep either way. They name the work to automate first and what it costs you a year, plus the extra service you could sell and what it would earn.
Build
We build the system around the tools you already run, and prove it on your real data before anything goes live. That usually means building on the Xero API, MYOB, MYOB Acumatica, Cin7, Unleashed or anything else with an API. The first system usually lands in 1-2 weeks, at a fixed price quoted before we start.
Run
It clears the routine itself and surfaces the genuine exceptions for a person. Monthly care and improvement for as long as it is useful to you, and you keep the code, the logs and the control.
The record, in detail
What we built before TwinMind, at what scale, and how we build now. This is the part worth reading if you are deciding whether to hand us something that matters.
The accounting system a packaging group runs in twenty of its plants
Alex spent his career at a large international maker of packaging, where he built the accounting system itself, together with the daily tools of the finance director, the economists, the accountants and the plant managers. His application runs at twenty of the group's factories, in several countries. Production, stock, costing and the ledger are one system rather than three systems arguing with each other, which took learning the accounting to the standard the accountants themselves hold.
Twenty subsidiaries, and 700 people working inside the systems
He spent thirteen years with that group and rose from developer to head of its technology. The systems he built there carried more than 700 users across twenty subsidiaries, put in on site, plant by plant, in four countries. A budgeting module he built for twelve of them brought the group's budget forward to the fifth of the month, from the fifteenth. His warehouse system serves seventy thousand square metres and loads up to seventy-five vans a day.
A bank statement that posts itself, and a finance seat of his own
Afterwards he built automation for logistics and finance businesses. One of those systems reads an incoming bank statement and posts about ninety-five per cent of the payments by itself: 200 lines become accounting documents in three minutes. He has also established a company of his own and carried the finance seat in it, with the payroll of sixty people, and he took a regulator's certification through in four months.
The system an international voice business ran on
Sergii spent more than twenty years with a company in international voice traffic. He wrote the system the whole business ran on, around a hundred people working inside it every day, traders to accountants, while running the finance function he was building it for. Everything between a supplier's price list and a customer's payment was automated: price lists ingested and rated in whatever format each one arrived in, usage records reconciled against what was actually billed in both directions, invoices issued, supplier invoices loaded and compared line by line against our own figures, statements and reminders going out on their own schedule, receivables and payables with automatic chasing of overdue debt, and around 100 contract templates produced from data rather than retyped. Every morning, before anyone arrived, the reports were already waiting on the desk of every manager and every owner, each one able to open the detail behind any figure. The system was afterwards sold and implemented for more than thirty other companies in the same industry.
Seventeen firms, four sets of national rules, two ways of reading the result
About seventeen firms of that group were run inside one system Sergii wrote with his team, under four sets of national rules at once. It also reported along a second dimension they called the business, because one business usually traded through several firms. Statutory reporting came out by firm, for the registers and the auditors. Owner and investor reporting came out by business, each with its own margin, balance and result. Both views came off the same transactions. Every audit file, every statutory set and every report a bank asked for came out of that system and was sent from it, in every jurisdiction they filed in, and every figure in them was assembled by the machinery itself.
Audits the auditors quoted back to us
Over the whole of that time Sergii prepared and filed the audits of a company registered in the United Kingdom, and for about fifteen years those of a Hong Kong company. Several were singled out by the auditors, and by HM Revenue & Customs, as the best they receive from any client. The reporting prepared for the bank was named, more than once, the strongest of any company in their pool. That is what we mean by a system that survives a real audit.
A plant that has run on one system since 2001
A pasta manufacturer in Ukraine, two hundred people and about forty million dollars a year, has run on a system Sergii wrote for that plant twenty-five years ago and has looked after every one of those years. It was built for that factory and runs the whole operation from the same numbers. It covers payroll and bonuses, contracts, receivables and payables. It also covers production planning and shop floors, barcoding, pallets and hand-held terminals, tax planning, profit, the balance sheet and P&L. It still runs the plant today and is still being extended: the layer built on top of it now prices every product from its true cost and shows today's profit instead of last month's. Twenty-five years of daily use is the plainest proof that what we build is meant to be lived in.
USD 800,000 of profit that needed explaining
A migration that went wrong left a group with two accounting systems and a profit figure of USD 800,000 that nobody on either side could account for. In ten days both systems were reverse-engineered, more than thirty reports were rebuilt, and the group had one truthful picture again. Several of the businesses we have built for now run a fully automated accounting cycle: practically every block of financial accounting, covered.
Twenty years of servers, data and recovery, as well as the applications
It is a fair question to ask early, so here is the plain answer. Behind every one of those applications, each of us also ran the machinery underneath it: around twenty years of system administration and of what is now called DevOps. Servers and networks, the environments code is deployed into, monitoring, backup and recovery, and the discipline of keeping something running that other people's work depends on. We understand database design and how databases fail under load. We also understand server and cloud architecture, data structures and the interfaces that connect systems. Each of us works in several programming languages. Each of us spent about fifteen years designing and building ERP systems, where production, stock, costing and the ledger live in one structure, so the architecture of a large system is home ground.
Architects, and a fleet of agents
AI agents write the code now, under our design, our standards and our review, and we work as architects: deciding what gets built and how it is structured, what it has to survive, where its limits are drawn, and answering for the result. Twenty years of building these systems with our own hands is what makes that solid rather than reckless, and it is the reason two people can now deliver what used to take a team. Today we run fleets of agents on one problem, more than a hundred of them across forty machines, in parallel and under review. That review is Alex's own trade: for ten years he built the machinery that checks other people's software on large financial platforms, and he now designs systems where agents plan the checks, run them and judge what came back.
The development environment we built for ourselves
We went as far as building our own development environment rather than buying one, because ours lets us fit a solution to what a particular business needs. Everything we ship is on the web and individual to the person using it: the warehouse sees the warehouse, the finance lead sees the cash, the owner sees the whole company, all reading the same numbers. We first built a knowledge base for ourselves and now build it for others. It genuinely knows an organisation: ask what was agreed in a meeting or quoted last year, and the answer comes with the document it came from.
Six engines, eighteen live systems
Each engine is a block of work we take over whole, wired into the accounting software and the systems you already run. One at a time, at a fixed price agreed before it starts.
| Engine | What it does | What changes |
|---|---|---|
| Close & Consolidate | Company files across different accounting platforms pulled into one position, findings ranked by the money at stake, cash thirteen weeks out. | A consolidated position on demand, rather than at the end of a close. |
| Reconciliation | Invoices and payments matched across ledgers, bank feeds and partner statements, with the evidence attached to every discrepancy. | The matching runs to a schedule, and a person sees only what did not match. |
| Payables | Supplier invoices read out of the inbox and coded from your own purchase history, with exceptions and approvals routed to a person. | The keying moves into the system. Approval stays with a person, on the accounts that matter. |
| Receivables | Escalating reminders at +7, +14 and +21 days, written in your company's own voice. Only genuinely stuck accounts reach a person. | Collections run whether or not anyone had time for them this week. |
| Cost, Margin & Stock | Actual and planned cost traced through every production stage, live stock and ageing across sites, and a quote priced as the bill of materials builds. | Margin risk shows up before the sale rather than after the period closes. |
| Documents & Obligations | Contract terms checked against the rules you set, with judgement calls raised to a person, and statutory forms filled from source data and paused for signature. | Review capacity stops depending on one person's calendar. |
Let's find the work worth automating.
Book the AI Opportunity Audit - a fixed A$2,000, credited in full against your first build. We map your repetitive work and hand you a costed plan that answers two questions in dollars: which block of work to automate first and what it is costing you a year, and which extra service you could offer and what it would earn you.
Book a 60-minute meetingOr reach us right here, right now - talk, type or call, whichever suits you:
Live video & voice calls run 9am-5pm Brisbane; chat, the AI assistant and email are open any time. Calls are transcribed live into your chat, so everything you discuss stays right here in your messages.