A Series A SaaS company raised its Series B with a board pack built on live data.

The company sells practice-management software to physiotherapy and rehabilitation clinics in Germany, Austria and Switzerland. It had raised a Series A eighteen months earlier, reached about €6M in ARR, and was preparing to raise a Series B. The finance team was three people: a head of finance, an accountant and a working student.

Every quarter, the board pack took four working days. ARR came from Stripe, pipeline from HubSpot, product usage from the Postgres database behind the application, and costs from Xero, all pasted into a slide template. Definitions drifted between quarters: one deck counted annual prepayments as ARR the day they were invoiced, the next spread them, and a board member noticed. Investors also increasingly asked for efficiency metrics such as the burn multiple — net burn divided by net new ARR, a ratio popularized by David Sacks — and net revenue retention, which SaaS Capital’s 2025 survey put at a 102% median for private SaaS companies in one ACV band (see references).

The product database was the hardest part. It held clinic and patient-scheduling data, and the company’s contracts with clinics required that it stay in its own German hosting. Copying it into another vendor’s cloud was not an option, so usage metrics had always been pulled by an engineer, by hand, the week before the board meeting.

The team installed Kimo Bridge as a container next to a read replica of the product database. The bridge opens an outbound-only, mutually authenticated tunnel to Kimo; queries for aggregated usage metrics run through it, credentials never leave the company’s servers, and no rows are stored on Kimo’s side. Stripe, HubSpot and Xero sync into Kimo Cloud as usual.

Finance then defined the board metrics once in the semantic layer: ARR and its movements (new, expansion, contraction, churn), net and gross revenue retention, CAC payback, burn multiple, runway and active clinics. Each definition carries a description and an owner, and the board saw the metric dictionary before it saw the first chart.

Kimo’s deck builder turned the model into three outputs that update together: a quarterly board deck, a one-page monthly investor update and a data-room workspace. When the Series B process began, each prospective investor received read-only access to the data room, and follow-up questions were answered with a link to a filtered view instead of a new spreadsheet.