All roads to one place.
Kamino exists because operators keep being handed pictures of their finances and asked to act on them. A picture is not an instrument. The systems that hold the truth about a business already run in a dozen directions; the useful thing is not another one, it is the junction where they meet, and a way to open the record behind any number.
How this started
I have spent 20 years in finance, and a good part of that implementing systems: ERPs, and the operational platforms that grow up around them. Long enough to watch two of the three back-office functions get properly solved, and one get left behind.
Finance is the harder one, and not for want of trying. Its data is more entangled than HR's or IT's, and it carries the things a company most needs to keep safe. Complexity and security are good reasons to move carefully. They are not good reasons for a company of thirty people to have no operating picture at all.
That left two roads to one. Replace the stack, and an ERP will join the data by owning it. Or live with the silos, and join them by hand, monthly, in a spreadsheet. A services company can afford neither.
Neither road is a mistake at the top of the market. A large organisation can carry the licence, the implementation and the people to keep it alive, and often it should. A thirty-person company has neither the budget nor, reasonably, the appetite, and at the end of it would still be looking at silos, because the operational systems it actually runs on were never in scope.
So Kamino does not ask you to replace anything. It reads the systems you already run, stitches them into one set of records, and lets you open the invoice behind any figure. That is why the drawing on this site is a junction and not a tower.
Marc-Andre Chartrand (LinkedIn profile, opens in a new tab), Founder & CEO
HR got streamlined. IT got streamlined. Finance is still waiting.
Three roads to one picture
Replace the stack
An ERP joins the data by owning it. It works, and at the top of the market it is often the right call. It also arrives with a licence, an implementation, and a change process that makes the next question expensive too.
Live with the silos
Every operational platform is right about its own domain and blind to all the others. The join still happens: in a spreadsheet, monthly, done by somebody who could be doing something else.
Read what already runs
What Kamino does
Connect the systems you have, stitch the records into one set, and leave every source exactly where it is. No migration, and nothing new appointed as the system of record.
What we are building
One product that reads the books a company already keeps, starting with QuickBooks Online and with more accounting platforms opening, and answers the questions its operators actually ask: which project made money, which client is expensive, where the hours went, and what the number is right now. It has to be traceable, with every figure openable down to the invoice, and it has to be deterministic, which is a stronger promise than governed.
Shipped today: Insights, meaning ask, report, dashboards and the data fabric underneath, with 41 reports and 108 KPIs in the catalogue, over eight connected data domains, QuickBooks Online and HubSpot by direct API and the rest by spreadsheet import. Being built: AR & Collections and Bank, more accounting platforms, Projects and Planning. We do not publish delivery dates.
What we will not claim
- We have no customer logos to show you, because we are early. There is no wall of them here and no space reserved for one.
- The demo company, One Step Ahead, is fictional: an experiential agency invented so you can see the product work on real-looking books. It is labelled illustrative everywhere it appears.
- We publish the whole plan catalogue, four tiers compared row by row, rather than a teaser and a call. Where a number is genuinely quoted rather than listed, as the add-ons are, we say so instead of inventing one.
- We name our competitors and say where they win. If one of them is the right buy for you, this site says so.
- A line on our diagram is drawn dashed until it is genuinely open. AR & Collections and Bank are not available at launch, coming soon after. Neither is ever written up as if it were running.
How to reach us
Email info@kamino.app. A person reads it. If you have a chart of accounts we would struggle with, that is the most useful message you can send us.
Diagram conventions used here
- Line
- A system feeding the picture. It runs at 0, 45 or 90 degrees, never a curve.
- Terminus
- A figure, drawn as the end of a line. Click one and its records open.
- Interchange
- The one node every line touches. That node is the product.
- Under construction
- Drawn dashed, never described as running. Above, that is Projects and Planning; on the domain diagram are AR & Collections and Bank.
- Service note
- The exception you must not miss, in magenta, with what to do about it.
Corrected on every sync with your accounting platform.
Architecture · ten domains in, one interchange, two dashed branches