Back to blog

What 'Zero Contract Losses in 12 Years' Actually Required

The systems, decisions, and discipline behind maintaining perfect client retention for over a decade.

retentionreliabilityoperationsclient-success

Header image

What "Zero Contract Losses in 12 Years" Actually Required

“Zero contract losses in 12 years” sounds like marketing fluff.

In reality, it was:

  • Stress
  • Discipline
  • Boring, unsexy work
  • And a system + team wired around not dropping the ball for state clients who absolutely will replace you if you screw up.

This is what it actually took.

1. The Claim: Zero State Contract Losses in 12 Years

Directionally:

  • We held a portfolio of state-level contracts in healthcare over more than a decade.
  • During that 12-year run:
    • We did not lose a state contract in open competition due to performance.
    • Contracts ended when:
      • programs changed,
      • scopes shifted dramatically,
      • or larger structural changes happened — not because we failed to deliver.

It wasn’t luck.

It was deliberate.

2. State Healthcare Contracts: Why They’re Hard to Keep

State contracts in healthcare are:

  • Political
  • Bureaucratic
  • High-stakes

You’re dealing with:

  • Medicaid programs
  • Assessment services
  • Eligibility determinations
  • Vulnerable populations

Why retention is tough:

  • Leadership changes:
    • New administration, new priorities, new vendors.
  • Procurement cycles:
    • RFPs that favor lowest bidder or “new” solutions.
  • Compliance landmines:
    • HIPAA, state regs, data security, reporting obligations.
  • Performance expectations:
    • Turnaround times
    • Accuracy
    • Coverage across large geographies

Industry churn is common because:

  • Vendors overpromise.
  • Underinvest in operations and compliance.
  • Treat contracts like generic SaaS, not as critical state infrastructure.

3. The Retention Threats We Lived With

Major threats we had to manage constantly:

  1. Operational failure

    • Missed SLAs
    • Large backlogs
    • Data quality issues

  2. Compliance failure

    • Security incidents
    • Privacy issues
    • Mishandled PHI
    • Incomplete or incorrect reporting to the state

  3. Perception and politics

    • A single highly visible failure can overshadow years of good performance.
    • Changes in state leadership can trigger “let’s re-bid everything” sentiment.

  4. Price pressure

    • New vendors underbidding with unrealistic promises.
    • States looking for “savings” on paper.

  5. Scope creep without structure

    • Being asked to do more and more “as a favor.”
    • Burning out the team.
    • Introducing risk by doing custom one-off work without proper integration.

Keeping contracts meant treating all of these as ongoing risk, not one-time events.

4. Why Competitors Lost When We Didn’t

Patterns we saw when other vendors got replaced:

  1. Underestimating operational reality

    • Fancy proposal, then:
      • slow rollouts
      • missed deadlines
      • inability to keep up with volume

  2. Weak compliance culture

    • Security theater on paper
    • Sloppy practices in reality
    • States notice when:
      • reports are late or wrong
      • audit questions get vague answers

  3. Ignoring local context

    • Trying to run a one-size-fits-all approach across states.
    • Not respecting specific state quirks, policies, and stakeholders.

  4. Bad communication

    • Hiding bad news.
    • Overpromising fixes.
    • Making the state feel blindsided when issues finally surface.

We weren’t “perfect competitors.”
We just consistently did the unsexy things well.

5. Our Retention Strategy (Not Just Lip Service)

The real strategy:

a) Never surprise the state

  • If something broke:
    • they heard it from us first, with:
      • impact
      • mitigation plan
      • timeline
  • That builds trust over years.

b) Treat compliance as a product feature

  • Not:

    “We’ll bolt HIPAA on later.”

  • But:

    • Audit trails everywhere
    • Secure handling of PHI baked in
    • Documentation ready for scrutiny
    • Processes that could stand up to external review

c) Deep operational partnerships

  • Regular check-ins with:

    • program leads
    • contract managers
    • local stakeholders

  • Asking:

    • “Where are we making your life harder?”
    • Then actually fixing those things.

d) Reliability over flash

  • Conductor wasn’t flashy, but it:
    • stayed up
    • delivered
    • produced the reports they needed
    • gave them confidence in hearings and oversight settings

e) Relentless follow-through

  • If we committed to:
    • a bug fix
    • a new report
    • a process change
  • We treated that commitment like a mini contract inside the contract.

This is not mystical. It’s discipline.

6. Staggered Renewals: Reducing Strategic Risk

One tactic that mattered a lot:

Staggering contract renewals instead of letting everything align to the same cycle.

Why this matters:

  • If all your major state contracts are up for renewal in the same 12–18 month window:
    • You’re one bad year away from existential risk.
  • Staggered renewals mean:
    • You never have your entire book at the mercy of one political or budget cycle.

Operationally:

  • We negotiated terms so:
    • initial contracts and renewals had different end dates
    • extensions and amendments were timed thoughtfully
  • This let us:
    • smooth out risk
    • avoid “all hands on deck for five RFPs at once” scenarios
    • maintain focus and quality while still competing to defend the business

It’s not glamorous.
But in a state-contract world, it’s the difference between volatility and survivability.

7. The Unsexy Work Behind 100% Retention

The part nobody sees in the tagline:

  • Custom reporting

    • Built to match:
      • state formats
      • federal requirements
      • auditor expectations
    • Often boring, but mission-critical.

  • Late-night and weekend work

    • Cutovers
    • Data conversions
    • Upgrades timed around low-impact windows

  • On-site visits and relationship work

    • Sitting in state offices
    • Hearing about issues face-to-face
    • Seeing how our output actually got used downstream

  • Manual QA on top of automation

    • Double-checking critical numbers
    • Sanity-checking reports before they left the building

  • Adapting to policy changes

    • Laws and regulations change.
    • We didn’t treat those as “annoying scope creep.”
    • We treated them as:
      • part of the job
      • part of the value proposition

The state sees:

  • “We didn’t have to fire them.”

They rarely see:

  • The volume of grind that made that true.

8. Close Calls (There Are Always Close Calls)

Were there contracts we almost lost?
Yes.

Typical “near miss” scenario:

  • New administration or leadership comes in.
  • They want:
    • “fresh eyes”
    • “competitive bids”
    • “modernization”
  • RFP goes out, and suddenly:
    • you’re defending years of work against:
      • slick decks
      • aggressive pricing from new vendors

How we survived those moments:

  • Leaned hard on performance history:

    • SLAs met
    • uptime
    • compliance record
    • referenceable success stories

  • Brought:

    • program knowledge
    • understanding of their edge cases
    • a realistic path forward

  • Often:

    • the shiny proposal looked great
    • but ours looked:
      • slightly less “wow”
      • much more plausible

The turning point is almost always:

“Do we trust these people to keep us out of trouble
more than we trust whoever wrote the prettiest RFP response?”

We earned “yes” enough times to keep the record intact.

Retention vs churn

9. Business Value of Zero Contract Losses

The value of zero losses over 12 years:

  1. Revenue stability

    • Multi-year deals stacked on top of each other.
    • Predictable cash flows.
    • Easier planning and hiring.

  2. Compounding growth

    • Keep your base.
    • Add new contracts on top.
    • Churn kills compounding; we avoided that.

  3. Valuation uplift

    • When you go to sell or raise:
      • 12-year retention record with state systems
      • is a giant green flag for buyers/investors.
    • It signals:
      • execution
      • reliability
      • non-trivial moat

For contrast:

  • At a hypothetical 10% annual contract loss:
    • After 5 years, you’d only retain ~59% of your base (0.9^5).
    • At 12 years, you’re down near 28% of where you started.
  • With zero losses:
    • Every new win truly stacks.
    • You build, instead of constantly backfilling.

That difference is enormous in dollars.

10. Lessons for Other B2B Founders

A few takeaways:

  1. Retention is a design choice, not an accident.

    • You either architect your product + ops around retention
    • Or you drift into churn and blame “the market.”

  2. In critical B2B (especially gov/healthcare), “flashy” loses to “boring + reliable” over time.

    • You still have to improve.
    • But reliability is the baseline.

  3. Your client’s risk is your risk.

    • If they choose you and you fail publicly, they take political damage.
    • If you understand that, your behavior changes.

  4. Trust buys you time when (not if) something goes wrong.

    • Own problems early.
    • Bring credible fixes.
    • The goal isn’t perfection. It’s recoverability.

  5. 100% retention is rare, but high retention is achievable if you’re willing to do unsexy work.

    • Documentation
    • Compliance
    • Manual verification
    • Over-communication

If all you want is a shiny logo slide and short-term MRR, this is overkill.

If you want:

  • durable contracts,
  • compounding value,
  • and a system you can actually sell someday,

then “zero losses in 12 years” isn’t just a brag line.

It’s the result of a hundred unexciting decisions made correctly, over and over, when nobody was watching.

Context → Decision → Outcome → Metric

  • Context: Credentialing platform running 12+ years, government and healthcare contracts, high switching costs but high scrutiny.
  • Decision: Design for renewals: over-communicate during incidents, keep ops boring and auditable, invest in compliance and adapter-driven integrations, and proactively run “close call” drills before RFP cycles.
  • Outcome: Zero contract losses across a dozen years; renewals became almost default because trust and evidence were compounding assets.
  • Metric: Renewal rate ~100%; RFP win rate on re-bids stayed high despite underbids; uptime 99.9%+ and zero security breaches.

Anecdote: The RFP We Almost Lost

A new administration issued an RFP with flashy modernization asks. Competitors pitched greenfield rebuilds and aggressive pricing. We countered with evidence: 12-year uptime, audit logs, adapter flexibility for new requirements, and a 90-day modernization plan that didn’t risk operations. The deciding factor wasn’t features; it was risk posture. They chose “boring + proven” over “shiny + risky.” That pattern repeated.

Mini Checklist: Designing for Renewal

  • Treat renewal as a feature: build a customer-facing reliability packet (uptime, incidents, mitigations, DR tests).
  • Rehearse RFP responses with evidence, not adjectives—diagram the current state and the upgrade path.
  • Maintain adapter contracts so new requirements land in one seam, not a codebase rewrite.
  • Over-communicate during outages with timelines, next updates, and owner names; trust is the renewal currency.
Back to blog