Header image

The Platform That Processed $100M (And Why You've Never Heard of It)

Most people assume:

“If a platform processes $100M, everybody must know about it.”

Nope.

Conductor quietly moved tens of millions to roughly the $100M mark in annual flow through state programs, healthcare workflows, and related operations.

Not as credit card swipes on a website.
As authorizations, assessments, and decisions that determined where money went in the real world.

You’ve never heard of it. That’s not a bug. It’s how a lot of real infrastructure works.

1. What the “$100M” Actually Represents

This isn’t:

A Stripe account exporting clean graphs
Or an e-commerce checkout funnel

Conductor sat in the middle of:

State-funded healthcare programs
Assessment and eligibility workflows
Care coordination and related services

The $100M figure (directionally) represents:

Annualized value of programs and services whose approval, routing, or validation flowed through the platform:
- assessments processed
- services authorized
- care delivered and billed against those decisions

The platform wasn’t “holding” the money.
It was the decisioning and workflow engine that determined:

Who qualified for what
Which providers got which cases
How state dollars got allocated

No clean “GMV” slide.
But the economic footprint was very real.

2. The Invisibility Problem

Why have you never heard of Conductor?

Because:

It was B2B in a non-flashy vertical (state healthcare).
It wasn’t a brand consumers touched.
It sat behind:
- agencies
- providers
- internal portals and tools

And this is normal.

Most real-world infrastructure:

Doesn’t have a logo on billboards.
Doesn’t sponsor conferences.
Doesn’t trend on Hacker News.

It just runs.

3. Scale Without Traditional Marketing

Growth came from:

State contracts and RFPs
- win one state
- execute well
- become the reference for the next state
Performance and word of mouth within the ecosystem
- People talk:
  - “They hit their SLAs.”
  - “Their system doesn’t fall over.”
  - “They actually fix things when we raise issues.”
Long-term retention
- Zero state contract losses over a long stretch meant:
  - revenue stacked
  - volume stacked
  - more money flowed through the same platform year after year

There were no:

Growth hacks
Paid acquisition channels
Ad funnels

The “growth loop” was:

Do good work on a critical problem
→ become the safe choice
→ win/keep more contracts
→ volume increases.

4. Why Healthcare Tech Isn’t Glamorous

For consumer startups, “scale” means:

Downloads
Daily actives
Social buzz

For healthcare tech:

Scale means:
- more people getting evaluated
- more services authorized
- more compliance risk
It comes with:
- regulation
- oversight
- auditors
- lawyers

It’s not glamorous because:

No one outside the system understands what you do.
You don’t get press for “we met our obligations for another year.”
You can’t just “move fast and break things” without hurting people.

You get:

Respect from the people who actually rely on you
Silence from everyone else

5. The Unglamorous Day-to-Day Reality

A typical day in enterprise healthcare software looks like:

Fixing edge-case bugs triggered by weird real-world data
Building state-mandated reports nobody will praise you for, but everyone will crucify you over if they’re wrong
Handling integration failures between:
- legacy systems
- flat files
- mismatched schemas
Dealing with:
- time zones
- licensing rules
- policy changes written in lawyer-speak

You spend more time on:

audits
data correctness
workflows

…than on “cool features” anyone will tweet about.

6. Compared to “Sexy Tech”

Pick a typical “sexy” startup:

Funded by VCs
PR hits for launch, round, and pivot
Talking about:
- virality
- engagement
- user growth

Conductor’s world:

No VC round announcements
No launch party
No TechCrunch write-ups
Just:
- RFPs
- renewals
- program changes
- and another Monday with thousands of cases flowing through the system

Differences:

Culture:
- Sexy startup: hype, speed, growth slides
- Conductor: reliability, compliance, quiet execution
Attention:
- Sexy startup: lots of noise early, questionable survival
- Conductor: little noise, long survival

One gets noticed.
One gets used.

7. Lessons About B2B Invisibility

Things people don’t understand about B2B software:

Visibility ≠ Value
- Some of the most valuable systems are invisible by design.
Brand awareness doesn’t always matter
- If your “customers” are a handful of states and agencies, your reputation in that circle matters more than your Twitter following.
Quiet competence can be a moat
- Being the vendor that “just works” in a messy industry is a massive advantage.

Would more visibility have helped? Maybe.
But for this business, execution > noise.

8. How I Felt About Being Invisible

Did I want public recognition?

At times, yes:
- When I watched flashy, fragile companies get praise while we were quietly doing real work.
Most of the time, though:
- I cared more about:
  - renewals
  - uptime
  - outcomes for people on the ground

Quiet success was enough for the business.

Where invisibility did hurt:

Later positioning:
- When you pivot into consulting / advisory, having a public brand helps.
- “I built Conductor” doesn’t mean much if nobody outside the niche has heard of it.

That’s one reason you’re seeing these posts now.

9. Is This Just Healthcare, or All B2B?

This isn’t unique to healthcare.

There are:

Logistics platforms
Manufacturing systems
Energy grid tools
Back-office banking software

…that move:

billions of dollars
goods worldwide
critical data

…and you’ve never heard of them.

The pattern:

Horizontal B2B brands (Salesforce, Stripe) break into public consciousness.
Deep vertical platforms often stay known only to insiders.

Healthcare adds:

extra compliance
extra risk
even stronger bias toward “don’t talk, just deliver.”

10. Repositioning: Talking About Conductor Now

As a consultant / fractional CTO, I talk about Conductor differently:

Not as:

“Here’s a brand you know.”
But as:
“Here’s a real, long-lived system that:
- processed ~$100M+ in annual flow,
- survived 20 years,
- and never needed a ground-up rewrite.”

Would I have liked more visibility earlier?

From a branding standpoint: yes.
From a risk/compliance standpoint: staying under the radar wasn’t the worst thing.

Now, the story isn’t:

“Look at this famous logo.”

It’s:

“I built invisible infrastructure that handled real money, real people, and real risk for decades. That’s what I bring to your architecture and operations.”

Sometimes the platforms that matter most are the ones nobody outside the room ever hears about.

Context → Decision → Outcome → Metric

Context: Built a B2B healthcare platform processing $100M+ annually in state-funded program flow. No VC, no PR, no TechCrunch. Just state contracts, RFPs, and execution.
Decision: Prioritized reliability and contract retention over visibility. Let the work speak through renewals and word-of-mouth within the healthcare vertical.
Outcome: Platform ran for 20 years without major rewrites. Zero state contract losses over a 12-year stretch. Became the "safe choice" in RFP evaluations.
Metric: $100M+ annual processing. Zero contract losses. 99.9% uptime. Sale valuation included a "stability premium" reflecting the $20-35M replacement cost.

Anecdote: The Competitor With the Better Pitch Deck

In 2016, we went up against a competitor in a state RFP. They had a beautiful pitch deck. Modern stack. Slick demo. Cloud-native architecture. All the buzzwords.

We had: a 15-year-old system, ASP.NET, SQL Server, and a track record.

During the evaluation, the state asked both of us the same question: "What happens when you have an outage during open enrollment?"

The competitor talked about their auto-scaling infrastructure and disaster recovery plans. We showed them our actual incident log from the previous three years. Two incidents. Both resolved in under an hour. Total customer impact: minimal.

We won the contract. Three years later, we heard the competitor had pivoted to a different market. They couldn't get traction because their system kept having issues during high-volume periods.

Sometimes "boring and proven" beats "modern and theoretical."

Anecdote: The Day Nobody Noticed

One of my proudest moments was a day that nobody noticed.

In 2019, we had a major database migration. Moved from one SQL Server version to another. Schema changes. Index optimizations. The kind of work that could easily cause downtime.

We did it on a Saturday. Ran the migration. Verified everything. Switched over. Monday morning, nobody said a word.

No tickets. No complaints. No "what happened over the weekend?" emails.

That's the goal of invisible infrastructure. When it works, nobody knows. When it doesn't, everybody knows. The measure of success is silence.

Mini Checklist: Building Invisible Infrastructure That Matters

[ ] Prioritized reliability over features; system stays up when it matters most
[ ] Built reputation through execution, not marketing; let renewals speak
[ ] Measured success by contract retention and customer trust, not press mentions
[ ] Accepted that "invisible" is the correct state for critical B2B infrastructure
[ ] Documented the real metrics (uptime, processing volume, retention) for when visibility matters later
[ ] Prepared to translate "invisible but essential" into compelling narrative for repositioning
[ ] Understood that the absence of complaints is the highest compliment in enterprise software