Your stack is the problem. Not your bookkeeping.
Your books are fine. The trouble is that the answer to “did that project make money” is spread across eight systems that have never met: the ledger, the CRM, the bills, the resourcing plan, the HR record, payroll, the card spend and the timesheets. One picture out of those eight is normally a data-warehouse project. Kamino does the stitching itself, and there is no data engineer in the room.
Eight of ten domains connect today: QuickBooks Online and HubSpot by direct API, the rest by spreadsheet import. AR & Collections and Bank are not available at launch, coming soon after.
Ten lines, one interchange
Every domain is a line. They all terminate at the same place, the Unified Data Fabric, Kamino’s own stitching engine, and one trunk leaves it carrying the operating picture. Eight run: QuickBooks Online and HubSpot by direct API, the rest by spreadsheet import. Two are drawn dashed, with hollow nodes: AR & Collections and Bank, which are not available at launch. We leave them on the drawing, in their real state, because you should be able to see exactly where the picture stands.
Kamino is camino, Spanish for road: all roads to one place. That is why the drawing looks like a junction rather than a logo wall.
- Accounting
- Direct API · connected
- Invoices, bills, journals, the chart of accounts
- CRM
- Direct API for HubSpot, spreadsheet import otherwise · connected
- What has been won and what is quoted
- Accounts Payable
- Spreadsheet import · connected
- Vendor bills and what you have committed to pay
- Resourcing
- Spreadsheet import · connected
- Who is committed, and to what
- HR
- Spreadsheet import · connected
- Headcount, departments, joiners and leavers
- Payroll
- Spreadsheet import · connected
- What the people on the job actually cost
- Expenses
- Spreadsheet import · connected
- Card spend and recharges tagged to a job
- Time Tracking
- Spreadsheet import · connected
- Approved hours, billable and not
- AR & Collections
- Direct API or spreadsheet import · coming soon
- Dunning status, promises to pay, collections effort
- Bank
- Direct API · coming soon
- Cleared balances and the money that actually moved
- Connected: by direct API or spreadsheet import
- Coming soon: not available at launch, no date published
The ten domains
Column two lists the systems each domain draws from. None of them is a partner and none of them is a logo. They are the shape of the domain, written out so you can tell whether your stack is in it. Column three is the route: a domain connects either by direct API or by the spreadsheet import. Eight read connected. AR & Collections and Bank read coming soon.
Systems, route, and what each domain opens
| Domain | Systems in this domain | Route | What connecting it unlocks |
|---|---|---|---|
| Accounting | QuickBooks Online | Direct API · connected | Ledger, invoices, project P&Lnamed by 24 of 41 reports |
| CRM | HubSpot · Salesforce · Pipedrive | Direct API for HubSpot, spreadsheet import otherwise · connected | Pipeline forecast, win rate, client concentrationnamed by 4 of 41 reports |
| Accounts Payable | Bill.com · Ramp | Spreadsheet import · connected | Vendor spend, commitmentsnamed by 2 of 41 reports |
| Resourcing | Float · Runn · Forecast | Spreadsheet import · connected | Capacity, bench, over-allocationnamed by 4 of 41 reports |
| HR | BambooHR · HiBob · Rippling | Spreadsheet import · connectedHR systems rarely expose a usable external API, so spreadsheet import is the right route here rather than a fallback. | Headcount, attritionnamed by 2 of 41 reports |
| Payroll | Gusto · ADP · Paychex | Spreadsheet import · connected | True cost rate, burdennamed by 3 of 41 reports |
| Expenses | Expensify · Brex | Spreadsheet import · connected | Recharges, card spendnamed by 1 of 41 reports |
| Time Tracking | Harvest · Toggl | Spreadsheet import · connected | Utilisation, realisationnamed by 7 of 41 reports |
| AR & Collections | Invoiced.com · and others in that category | Direct API or spreadsheet import · coming soonNot available at launch. Coming soon after, and it carries no date. AR ageing and collections risk already run on the Accounting domain, because invoices live in the ledger; this domain adds the dedicated collections layer on top of them: the workflow, not the balance. | Collections workflow and receivables risk: dunning status, promise-to-pay, collections effectivenessNo report or KPI count is published for this domain until it runs. |
| Bank | Plaid · and others in that category | Direct API · coming soonNot available at launch. Coming soon after, and it carries no date. Cash movement already appears through the Accounting domain, because the ledger records what it was told; this domain adds the bank's own record of what actually cleared, which is what makes a reconciliation possible rather than an assertion. | Cash position and movement: cleared balances, bank transactions, reconciliationNo report or KPI count is published for this domain until it runs. |
Report counts in the last column are counted from the catalogue, not asserted, and they sum higher than 41 on purpose, because 6 reports need two domains and are named by both. A domain that is not available carries no count until it runs, and no date is published for them here or on the roadmap.
Pick your domains. See your reports.
This is the real catalogue: 41 reports, each mapped to the domains it needs, so what you see below is what you would actually get. On accounting alone, 19 of 41 answer. The rest need a second source, which is the point: value compounds across domains rather than adding up.
19 of 41
reports answerable on these domains
19 of 41 reports answerable, 0 of them cross-domain, on 1 selected domain.
0 of these need more than one domain, marked two sources below. Those are the reports a single-source tool can never produce, whatever it charges: the answer does not exist in any one system. That is the whole argument for a fabric.
Profitability · 4 of 6
- Project P&L
- Client profitability
- Gross margin by service line
- Margin waterfall
Cash & Working Capital · 4 of 6
- Cash flow statement
- AR ageing
- Collections risk
- 13-week cash forecast
Revenue & Pipeline · 3 of 7
- Revenue by client
- Revenue recognition schedule
- Backlog & booked revenue
People & Cost · 3 of 7
- Headcount roster
- Contractor spend
- 1099 readiness
Delivery · 2 of 5
- Budget vs actual by project
- Change orders & scope creep
Compliance & Audit · 3 of 4
- Chart of accounts mapping
- Journal entry audit
- Access & permission review
Add the remaining domains and the catalogue opens to all 41 reports, including 6 that need two domains at once.
A domain doesn’t need a finished API to be usable
This is the mechanism behind eight connected domains, and it is the reason coverage is a fact rather than a promise. Two systems connect by direct API today, QuickBooks Online and HubSpot. Every other connected domain arrives by spreadsheet import: you export what you already export, on the shape we publish, and the fabric treats it as a source like any other, with the same entity stitching, the same lineage, and the same drill back to the record.
HR is the clearest case. HR systems ship thin external APIs out of the box, so for most teams the spreadsheet route is not a fallback. It is the route that actually works. An import is a file, so when the source changes you import again; nothing runs in the background pretending to be a live connection.
This is why HR connects at all, and it is why a domain is never held open waiting on somebody else’s API.
Two routes, one fabric
Direct API or spreadsheet, a source is a source. Nothing downstream, not reports, KPIs, dashboards or drill-to-record, knows or cares which route the rows arrived by.
Never blocked on a vendor
Every integrations page in this category is a race to list more logos, and every one of them leaves you out if your system is not on the list. A spreadsheet route means a domain is never blocked on a vendor's API, on a vendor's partner programme, or on our position in a roadmap queue.
Never blocked on us either
If the API for your particular system is not written, you are not waiting for us to write it before you get the domain. That is the difference between coverage you can rely on and a list of intentions.
The shape is published
The columns each domain needs are documented, so a spreadsheet route is a specification you can meet, not a support ticket. Same review queue for anything ambiguous, same match rate you can inspect.
How far one domain gets you
Every figure here is counted from the report catalogue rather than claimed. We publish them because a report that needs a domain you have not connected should say so and name the domain, rather than quietly returning a worse number. That is the same determinism the rest of the product runs on, applied to coverage.
- domains connected
- 8 of 10
- reports on accounting alone
- 19 of 41
- reports that need two domains
- 6 of 41
Connect the rest and the whole catalogue opens: all 41 reports and 108 KPIs. The KPI figure is a catalogue total rather than a per-domain split. There is no honest per-domain mapping behind it, so we do not publish one.
The stitching is the product
Joining eight systems is not a matter of eight connectors. It is deciding that the client in the CRM, the customer on the invoice and the job on the timesheet are the same piece of work. That is the part people hire out.
It is also the part that has no halfway state. Either two records are the same client or they are not, and something has to decide: with a rate you can inspect and a queue for the ambiguous ones, or silently, to make a number look tidy.
Entity stitching across sources
Clients, projects, people and vendors are matched across systems, with a match rate you can inspect and a review queue for anything ambiguous. Nothing gets silently merged to make a number look tidy.
Nothing to stand up
No warehouse, no pipeline to keep alive, no semantic layer to build and then own. You connect a source; the model on the other side is already written.
What it replaces
Generic BI or a warehouse needs a connector, a modelling layer and somebody to keep both alive: months, six figures, and a standing dependency. Kamino starts at $49 a month with nobody to hire and nothing to keep alive, and how many sources you may connect is a published plan cap rather than a project.
Connecting a domain does more than open reports
Insights is the product: the fabric plus ask, report and dashboards. Projects and Planning are paid modules that sit on top of it, and both are being built. Each domain you connect is not only reports and KPIs. It is what those modules will be able to do, because a module is only as good as the data feeding it.
CRM
Pipeline-weighted revenue forecasting. With real deal records behind it, a forecast starts from what is actually in play rather than a number you typed into an empty box.
Resourcing and Payroll
True project margin and capacity planning. Hours at their real burdened cost, against who is committed where: the only honest way to say whether a job made money.
Accounts Payable
Committed-spend forecasting. Cash you have already promised is the half of a cash forecast that the ledger alone never sees.
These are what the data makes possible, not features you can switch on today. Projects and Planning are being built, priced as add-ons on top of the base subscription, and carry no dates.
Why the other tiers don’t do this
Report packs
Never leave the general ledger. A beautiful pack of the same 19 of 41 the ledger can answer.
FP&A platforms
Assume you employ an analyst. The model is yours to build and yours to keep true.
Generic BI and warehouses
Can absolutely do it. That is precisely where the consultant and the data engineer live.