Most MSPs don't have a tooling problem. They have a synthesis problem.
Catalyst Shift exists in the layer between data and decision. Five workflows MSPs structurally can't make time for — QBR prep, churn watch, proposal variants, pipeline forecasting, content. Each too small to hire for, too important to skip. Catalyst OS does them anyway.
Built where the gap is.
Catalyst Shift was founded around one observed pattern across mid-market MSPs: every shop has the data; almost none have time for the synthesis. The stack works. The reports run. And the moves that would actually compound — the QBR opening that lands the renewal, the churn signal caught at day 60, the proposal variant priced to the margin you wanted — sit upstream of the one person who has to do them, who is running ten days behind.
The team brings a Microsoft architecture background, USAF intelligence, and direct MSP operations experience as VP of Professional Services on the build side; fifteen years of cybersecurity sales leadership across RSA, Microsoft, Mandiant, and Palo Alto Networks on the revenue side; and operator credibility from a founder who built and sold a $3–5M services business on the delivery side. Same pattern in all three careers: the technical operations were excellent, while the business layer on top got left to spreadsheets and willpower.
QBRs prepped the night before. Churn signals noticed in retrospect. Proposals written from a template that hasn’t been touched in two years. Not because the team didn’t care — because the work that would have mattered most was the work nobody had time for.
Catalyst OS is those five workflows, productized. Multi-tenant by design, portable by default. Bundled like a hire, sold like infrastructure. The Early Adopter Program is how the first cohort comes in — meaningful discounts, locked rates, and deliverables committed in writing. The public catalog ships at GA pricing as the program produces case studies.
The honest numbers, May 2026.
Five principles. The ones we’d want from a vendor running on our own data.
Synthesis, not dashboards.
A dashboard tells you what already happened. We're not building another one. We exist in the layer between data and decision — surfacing the next move, with the rationale attached.
The QBR is the renewal.
In owner conversations and industry research, the QBR keeps surfacing as the moment relationships are won or lost. Every module ladders back to: does this make the next QBR better, or doesn't it?
Honest about the model.
Predictive analysis gets things wrong sometimes. We publish our false-positive rate, our lead times, and the features driving each rank. No black box. The vCIO is still the operator.
Concierge before code.
Our early adopters are hand-onboarded — two-week setup, every model tuned per-MSP. We'll productize the onboarding when we know what's worth productizing. Not before.
Customer data is customer data.
We never use one MSP's data to train models that serve another. Tuning is per-MSP. SOC 2 Type II in progress. US-only infrastructure. Purged on offboard. No exceptions.
From observation to operating layer.
Pattern crystallized.
Across years of MSP and CMMC work, the same five workflows kept surfacing as the bottleneck — too small to hire for, too important to skip. The decision to productize was made.
Strategy v4.4 locked.
Vertical-first MSPs ($500K–$3M primary, $3M–$10M extended). Five-module catalog. Three published bundle tiers. Bundled like a hire, sold like infrastructure.
Early Adopter Program open.
Recruiting the first cohort across three tiers — Founding Architect (3 spots), Cohort Partner (8 spots), and Community Adopter (open). Two-week concierge onboarding each. Every model tuned per-MSP. Modules ship over the next two quarters.