Why Centralyse Exists: Deals Go Dark

Before Marta and I wrote any Centralyse code, we had each spent years encountering the same problem. It appeared in different settings, industries, and company sizes, but the pattern stayed constant: a deal looked healthy on paper, then went dark after an untracked relationship shift.

I want to share what we saw, because most sales tools still handle this poorly.

The sales problem I kept seeing

I spent several years in B2B sales and sales operations, running deals and building processes at different companies. My work centered on complex deals with multiple contacts, many stakeholders, long cycles, and six-figure contracts.

After enough of these deals, a pattern emerges. The CRM does not show what is happening inside an account. It records what has happened: notes, meeting results, and email status. It shows your activity, not the account's internal reality.

That internal reality keeps shifting. A champion is reorganized. A budget cycle moves. A new VP resets priorities. An evaluator who looked peripheral turns out to control budget sign-off. These changes happen between calls, while the CRM knows none of them.

I built workarounds: org-chart spreadsheets, manual contact scores, and reminders to check when I last spoke with each key contact, flagging anything over two weeks. They helped, but took several hours each week and relied on me to update them correctly.

What Marta saw in infrastructure

Marta spent years building real-time data sync and integration infrastructure at enterprise software companies. She saw the same issue from another angle: CRM data kept going stale. The systems were not necessarily bad; their data was fundamentally batch-oriented. Sync ran once a day or once a week. Contact records showed what a rep logged, not what was happening in the relationship.

She kept asking why the data was always three days old. Why did the key signal, whether a contact was truly engaged, depend on manual entry by someone who might not remember to make it?

The answer was always that this was simply how CRMs worked. Yet the infrastructure for a different approach existed. Technical capability was not the issue. No one had treated relationship-signal tracking as a first-class data problem.

Comparing what we had seen

When Marta and I discussed it, the overlap was clear. I understood the domain issue: reps could not see account relationship changes. She saw the technical one: relationship signals belong to real-time data, not logging.

We also knew what not to build. We did not want another manual data-entry layer or a more elaborate dashboard for reviewing the past. That had been attempted many times. Existing revenue intelligence platforms are powerful, but designed for mature RevOps teams with dedicated admins and weeks of setup.

We were thinking about smaller teams: two to fifteen reps handling complex deals without the support needed to run Gong or Clari at full capacity. They needed something usable on day one, without a full-time admin keeping it current.

What we chose to build

We began with three constraints. Relationship signals had to be tracked automatically, rather than through rep logging. The output had to point to a next action, not just provide a report. And it had to be accurate enough for reps to trust its nudges.

The relationship graph came first because manual workarounds could not scale there. Centralyse takes contact interaction data from CRM, email metadata, and calendar activity, then creates a weighted map showing who engages, how often, and whether engagement is rising or falling. Champions stand out, quiet contacts are flagged, and missing relationships appear as gaps.

The nudge system followed. The graph helps a rep understand an account; the nudge makes that understanding actionable: one specific thing to do today, based on the signals.

Current status

Centralyse was founded in 2024. We raised a small angel round in late 2025 from people who understand B2B sales software. We are now working with design partners, sales teams using the product in active deals and helping us see where signal quality matters most and where more work remains.

We bootstrapped the early build ourselves, so we had to choose our focus carefully. We are not replacing a CRM or trying to match every function of revenue intelligence platforms. Our focus is one job: show a rep what is happening in their accounts and what to do before it is too late.

The problem behind Centralyse is real and remains mostly unsolved for teams without enterprise tooling budgets. We built this because we kept encountering it, and because the pieces needed to address it now exist in a way they did not a few years ago.