The platform underneath.
Every company runs on the same three things: data, workflows and people. In most companies all three are fragmented — data in dashboards nobody trusts, workflows buried in spreadsheets and SaaS sprawl, teams in silos.
Heartbeat is one base under all of it. We call it a Business OS.
Ready on day one, hardened with every engagement, and priced as an annual subscription banded by users and data scope.
- Identity
- Permissions
- Hierarchy
- Metric layer
- Dashboards
- Discussion
- Planning
- Connectors
- Audit
A rack for everything you build
Forward-deployed people and AI services produce a lot: metric definitions, dashboards, integrations, planning models, internal apps. The only question that matters afterwards is what holds them.
Off the rack, work becomes junk
Every build sits on the floor. It works the week it ships; a year later nobody can find it, nobody owns it, and the only way to keep it running is to keep paying for labour. That is the treadmill every services relationship ends up on.
On the rack, work becomes inventory
Each build slots into the same rails — one identity, one permission model, one hierarchy, one metric layer, one audit trail. It is findable, maintained and reusable, and the next build starts from what the last one proved.
The rails are the product
What you subscribe to is the rack, not the modules on it. It is deliberately boring, and it is the reason the second year costs less than the first instead of more.
Why we call it an operating system
A computer's OS hands every program the same identity, permissions, storage and drivers, so no program has to invent them. A Business OS does that for the systems a company runs on — which is why the word is operating system rather than platform.
The platform is what turns work you paid for into an asset you own — rather than a bill that comes back every year.
Three organs, one system
Most tools give you one of these and leave you to wire the rest. A business operating system needs all three, on one set of definitions.
It senses
Real-time numbers from every function, on definitions the whole company has agreed — so what you feel in the business is what the system shows.
It decides
Discussion, share-outs and planning sit on the numbers themselves, so the argument and the decision live where the evidence is.
It acts
The workflows and internal apps your teams work in, built on the same base — so a decision becomes an action item, not a follow-up email.
Modern enterprises don't lack data. They lack execution coherence — and that isn't a tooling problem.
The metric layer
A single, governed catalogue of what your company measures and what each measure means. Not a glossary in a wiki — the layer your dashboards, plans and agents all compute from.
One definition
Each metric has one formula, written down and enforced in code. When the answer changes, it ships to every chart at the same moment.
One owner
Every metric carries a name. Definitions with owners get maintained; definitions without owners drift back into five versions.
Full lineage
Every number traces back to the source system and the rows it came from. “Where did this figure come from?” gets an answer, not a shrug.
Versioned
Definitions change as the business changes. History stays — so last quarter's board pack still means what it meant when it was presented.
Composable
Metrics are equations, so they build on each other: a branch number rolls into an area number, a funnel step into a conversion rate, a cost line into unit economics. Small systems become the big one.
Define a metric once, then compose it. That is the whole trick — every layer above this one inherits the agreement.
Three views, one truth
The trend at a glance
Key metric trends against prior periods and against plan. What leadership opens Monday morning.
The numbers in full
Time-series tables by day, week, month, quarter and year — the working surface for reviews, replacing the hand-built deck.
The last mile
Every figure opens downward through your hierarchy, with ranked lists at each level, so the outlier surfaces itself.
Your org chart is in the platform
The hierarchy is a first-class object, not a filter someone remembers to apply. Every metric drills through it and every permission follows it, so each level sees its own truth and nothing it shouldn't.
- National
- Zone
- Region
- Area
- Branch
- Field
Every function, one base
Each function gets its own view — its metrics, its drill-downs, its cadence — computed from the same definitions. The CXO summary, the functional deep-dive and the investor update are the same numbers at different altitudes, not three reconciliations.
- CXOs
- Product
- Engineering
- Sales
- Marketing
- Operations
- People
- Finance & FP&A
- Legal
- Investors
Where the argument happens
A chart in a BI tool ends the conversation by starting it somewhere else — in Slack, in email, in a meeting nobody minuted. Heartbeat keeps the discussion attached to the number.
Discussion on the metric
Comment on a figure, tag a colleague, reference another metric inline. The thread lives with the number, so next quarter you can read why it moved and who said so.
Share-outs
Reviews and updates published from the live numbers instead of re-typed into a deck — the same figures, on your cadence, without an analyst in the loop.
Action items with owners
A decision becomes a to-do attached to the metric it was about, with a name and a date. Follow-up stops depending on someone's memory.
A dashboard can't argue back. An operating system can hold the argument, the decision and the follow-up in one place.
Planning on the same definitions
Forecasting usually happens in a spreadsheet that has quietly redefined half the metrics. Here the plan is built on the layer the actuals come from, so plan-versus-actual is arithmetic rather than argument.
Business model
The company's operating model as a live object — drivers, assumptions and unit economics, not a static workbook.
P&L
Current and projected, shareable as a summary without anyone re-keying figures.
Cashflows
Liquidity and runway, tracked against the same actuals leadership reviews.
Projections
Forecasts that move as performance moves, instead of ageing from the day they were built.
Scenarios
Model the what-ifs — a slower funnel, a faster hiring plan, a collections shock — and compare them side by side.
Apps that reuse the foundations
The internal tools every company ends up building — operating reviews, ticketing, work-logs, OKRs, hiring pipelines, sales-ops trackers — are normally four separate projects that each rebuild the same plumbing.
Nothing gets rebuilt
Identity, permissions, hierarchy, integrations and analytics already exist on the base. A new internal tool inherits them instead of re-implementing them badly.
Extensible
The system grows as the business does — a new function, a new geography, a new line of business is configuration, not a replatform.
Composable
Modules can be recombined without rebuilding: the same metric layer feeds a review, a dashboard and an app, so the tools your teams use and the numbers leadership reads never drift apart.
Automation over the repetitive
Scheduled reports, alerts on thresholds, and the mundane follow-ups a person shouldn't be doing by hand.
Instead of assembling a company out of fragmented SaaS, you run it on one base you can extend.
The apps companies ask for first — each built on the base, in a phase, not bought as a separate product:
- Operating reviews
- Ticket management
- Worklog
- OKRs & goals
- Headcount & hiring
- ESOP tracker
- NPS
- SaaS tool manager
AI that answers from your definitions
Ask in plain language — what moved, where, why, what to do next — and get an answer computed from the governed metric layer, with the lineage to check it. Defined use cases, defined guardrails.
An AI is only as good as the definitions underneath it. Point one at five versions of the truth and it will confidently pick the wrong one.
Reads from what you already run
Heartbeat sits on top of your systems of record; it doesn't replace them. Pipes are built and verified per engagement against your actual schemas — not claimed by the hundred.
- Core systems
- ERP
- CRM
- HRMS
- Ticketing
- Databases
- Spreadsheets
Role-based access
Permissions follow the hierarchy, so a branch manager, a zonal head and the board each see their own scope of the same governed numbers.
Audited
Access and changes are logged — who saw what, who changed a definition, and when.
Inside your constraints
We work with your IT and security teams on access and where data sits, rather than around them. Lending stacks are where we've gone deepest so far.
What companies switch on first
Nobody buys a platform. They buy the first thing it fixes — and then the second, on the same base.
Real-time visibility
One current view across the organisation, drillable to the last unit, instead of a month-old deck.
Operations tracker
Progress across every team on shared definitions, so nobody grades their own homework.
Employee pulse
Engagement and satisfaction measured on a cadence, next to the performance numbers they explain.
Scenario planning
Model and compare possibilities on live actuals — before the quarter decides for you.
OKR & goal tracking
Objectives wired to the metrics that move them, so progress is read, not reported.
KPI benchmarking
Compare like with like — branch against branch, region against region — and find the gap that's worth closing.
Headcount planning
Roles and hiring planned against the plan, with attrition and vacancies in the same picture.
Investor updates
Structured updates generated from the numbers leadership already trusts.
Fundraise readiness
Diligence-ready at any moment, because the data room reads from the live layer.
Ready on day one, shaped per company
Worth being exact about, because most platform pages aren't: the base is what every company shares, and the last mile is always yours.
The base platform
Identity and permissions, hierarchy, the metric layer, summaries, scorecards and drill-downs, discussion and action items, connector framework, audit. This is the annual subscription.
Your layer on top
Your metric definitions, your hierarchy, your integrations, your planning models, your agent use cases, and the internal apps above — built with AI Services on this base, never from scratch.
Which is why the platform gets better for everyone: what one engagement proves is common hardens back into the base.
See it on your numbers
Bring one metric your teams disagree on — we'll show you what settling it looks like, live in the platform.