3Pillars is excited to announce we are officially Certified in the Claude Partner Network! Our people hold Claude certifications, and we are building from here.

Proof, one engagement
at a time.

Healthcare · PE portfolio company · +$75M ARR · payer contracting

PE-backed multi-state behavioral health provider

In production 3 weeks Claude Cowork + Claude Code
$7M+
in contract revenue identified
avoided additional FTE hiring

The operator

The problem we took

Three merged entities, hundreds of payer contracts, and no formal contract system or negotiation engine. A two-person team ran the payer lifecycle on PDFs and spreadsheets, with revenue leaking through missed negotiation windows, passed renewals, and reimbursement schedules the team could not reconcile against each contract.

Clients' people

What was already in the client's environment

The payer book they already had: 1,000+ agreements across drives, boxes, and laptops. Revenue cycle, operations, and finance set the operational priorities, with SharePoint as the primary repository. The client keeps the repository, the renewal matrix, and the final say at every checkpoint.

The build team

What shipped, what it returned

Live in three weeks: Claude Cowork extraction agents read 1,000+ documents into 82 contract records on a 42-field schema; Claude Code analysis agents query them over MCP and wrote seven briefs. Renewal visibility went from none to 12+ months.

$7M
opportunity identified
40+ → 8 hrs
contract ops per month
82 / 1,201
contracts, CPT-level rate rows
Healthcare · supply chain, logistics and security data company · two new lines of business

Supply chain and logistics data company: an agentic PMO on Claude Cowork

In production since May 2026 6 workflows, 2 product lines Claude Cowork
2 FTEs
replaced by the agentic PMO, about $300K a year in loaded cost
board and customer materials 8-10 hrs/wk to 1-2

The operator

The problem we took

Two healthcare lines of business standing up at once: surgical asset tracking with a large device maker and three of its agencies, and a state emergency-preparedness supply platform. About 12 recorded meetings a week with health systems, device companies and state and federal agencies, and teams that had never run a program this size. A traditional PMO would add 1 to 3 staff per workstream and still miss the cross-functional risk.

Clients' people

What was already in the client's environment

Six workflows stood up on the tools the team already ran: recorded meetings in Granola, Notion for tasks, decisions and risks, and the Claude desktop app. The PMO lead owns exceptions and the risk register. Every human correction is written back into the prompts.

The build team

What shipped, what it returned

An agentic PMO on Claude Cowork scheduled tasks: it preps every meeting, turns each call into tracked tasks, decisions and risks, and drafts the decks and the customer, agency and state updates. 3Pillars reviews and sends. Three workflows at the market, three at the company.

2 FTEs
replaced, ~$300K a year
8-10 → 1-2 hrs
senior time a week on materials
62 runs
152 meetings, 358 tasks logged (May-Sep 2026)
Healthcare · PE portfolio company · +$225M ARR · digital health marketplace

National digital health marketplace

In production 12 weeks to deployment Locally-hosted + frontier models
$3-7M
projected annual revenue from matching accuracy
90% of current bookings affected by this initiative

The operator

The problem we took

Up to 40% of users picked the wrong insurance plan and 7% could not find theirs, driving cancellations, provider churn, and missed revenue. Underneath, a decade-old database of ~12,000 plan records patched by manual research, offshore teams, and outside vendors.

Clients' people

What was already in the client's environment

The data-operations team moved from manual maintenance to high-judgment review. Product, operations, engineering, and data took the handoff with taxonomy, SOPs, and training, on the systems they already ran: their internal proprietary database and data lake, and the Microsoft suite. The growth came from data the business already owned.

The build team

What shipped, what it returned

A five-tier payer hierarchy rebuilt under the live marketplace with zero record loss, wired to the Aequalis Payer Insights Platform and a national claims clearinghouse.

$3-7M
projected annual revenue
~4,000
plans added, 2,000+ removed
90%+
of bookings covered
Public sector · state health agency · $7.5M annual license

Statewide readiness platform, via a national logistics data company

In production Ongoing fractional AI leadership Locally-hosted models
$15M
state contract secured for statewide deployment

The operator

The problem we took

A proven logistics, inventory, and supply-chain platform, redesigned and deployed for healthcare: statewide emergency preparedness and readiness across 8 regional coalitions, 8 health systems, and 2 state departments. Federal expansion is the long-term goal.

Clients' people

What was already in the client's environment

The client's existing platform carried the work, adapted rather than rebuilt. State health and technology departments, coalitions, and health systems align on one operating picture. We stayed on as the fractional AI arm, applying AI principles and practices to the system they already run.

The build team

What shipped, what it returned

The commercial case, ROI model, and pricing for a $15M state contract, then an AI-native deployment across every coalition and both departments.

$15M
state contract secured
5,000+
SKUs visible statewide
8 · 8 · 2
coalitions, systems, state depts
Healthcare · PE portfolio company · +$250M ARR · clinical data intelligence

Clinical data intelligence company entering risk adjustment

Board delivered 8 weeks to the target list Claude Cowork + Claude Code
$60M+
projected annual uplift for a new line of business

The operator

The problem we took

Provider-market dominance, and a board mandate to take a risk adjustment product into payer segments the commercial team had never sold to. Started from no payer value proposition and no target list, in a crowded and maturing market.

Clients' people

What was already in the client's environment

Built around the client's own product, growth, and sales teams, with 15 voice-of-customer interviews reached through the 3Pillars network, VP to board level. The sales team kept and shaped the growth enablement kit; the board approved the roadmap.

The build team

What shipped, what it returned

Claude Sonnet matched about 4,000 client relationships against public MA, ACO, Medicaid and ACA plan data and kept the risk-bearing ones: 52 named targets, 24 top priority, in 8 weeks. Buyer maps, PMPM ROI models, a board-level recommendation, then Phase II dashboards and KPI reporting built on Claude Cowork beside the customer success team.

52
named targets, 24 top priority
2 vs 6-8
people on the engagement
4-6 → 2 wks
sales-to-CS handoff
Public sector · state government

Statewide police force, every district

In production Ongoing fractional AI leadership Locally-hosted models
80% less
senior-officer time per case review, measured in production
30-45 min down to 5-10 · 10,000+ hours returned

The operator

The problem we took

Senior officers spent 30 to 45 minutes on every case review, and situational awareness was assembled by hand, district by district, hours late. Modernization had to happen inside the government's own environment.

Clients' people

What was already in the client's environment

The state's existing infrastructure and camera estate, kept: video intelligence runs above installed CCTV without replacing it. Officers' corrections retrain the models, and command reviews every flag.

The build team

What shipped, what it returned

Seven interconnected production systems on locally-hosted models: grievance processing, digital evidence, investigative data fusion, document digitization, video intelligence.

5-10 min
case review, was 30-45
10,000+
man-hours returned
40%
faster incident response
MedTech · AI aortic imaging · pre-revenue portfolio company

Pre-revenue AI imaging company: five revenue pathways, one lead path, a back office on Claude

Fractional commercial ops, ongoing 5 pathways scored Claude + Claude Code + Agent Skills
$300K/yr
commercial hire avoided: a two-person fractional team on Claude runs sales and business operations
5 pathways → 1 lead path · $50K-$200K per site

The operator

The problem we took

AI that reads aortic hemodynamics from the CT and MR scans hospitals already take: a 1,700+ patient study in Radiology, four pilot academic medical centers, an FDA 510(k) pathway confirmed, and no commercial function or budget to hire one before a seed raise. The unknowns were the economic buyer, the price, the implementation burden and the defensibility.

Clients' people

What was already in the client's environment

Founders with clinical standing, warm relationships at the pilot sites, and the published evidence. 3Pillars runs sales and business operations as a fractional team; company leadership keeps every decision.

The build team

What shipped, what it returned

The same top-down and bottom-up assessment 3Pillars ran for a clinical data company entering the payer market: five revenue pathways scored, health systems segmented, 169 provider-sponsored plans profiled and tiered (15 in Tier 1), buyer maps per pathway. Then the weekly Claude-generated intelligence brief, the investor newsletter skill, a 60-month financial model and the website prototype.

169 / 15
PSPs profiled / Tier 1 targets
4
pilot AMCs as first commercial targets
9
weekly intelligence briefs by Claude
Public sector · nonprofit public health institute · price transparency

Nonprofit public health institute: a statewide rate platform built with Claude Code

In production since Q4 2025 Client on the MCP server today Claude Code + Claude API + MCP
~1 month
to build the platform with Claude Code, against about six for a team build
up to 4 FTEs replaced, $600K-$800K a year

The operator

The problem we took

A large corpus of Medicaid, Medicare and state public health data with no utilization or pricing layer: what the state's residents actually use and what it costs. The plans publish their negotiated rates, but the files run 5 to 200 GB each and 100 million+ raw rows statewide.

Clients' people

What was already in the client's environment

The corpus, the public health mission and a business plan with seven customer types from public good to paid. The client paid for the initial specification; 3Pillars delivered beyond it, and the client needed no software of its own.

The build team

What shipped, what it returned

Aequalis, built by one developer with Claude Code: every published BCBS Michigan and HAP rate loaded, a behavioral health and substance use rate assessment run through the Aequalis AI Assistant, then an MCP server (again built with Claude Code) so the client queries the live data inside Claude with no SQL and no exports.

~2 TB
payer files into 11.9M enriched rates
2 plans
every published rate reviewed
June 2026
MCP server live; the client has its own seat
Industrials · wholesale diamonds · $15M+ of consigned inventory

$40M B2B wholesaler: a memo risk and sales intelligence layer on a legacy ERP

In production since April 2026 16 reps on ranked queues Claude API + MCP + Agent Skills
~1,500
follow-ups sent from reps' own mailboxes, each approved by a person
$15M+ consigned risk-scored every 15 minutes · first workflow live in 5 weeks

The operator

The problem we took

About 2,130 open memos and $15M+ of consigned inventory in a vendor-hosted ERP with no API, ~$2M past due across 234 accounts, customer data split across the ERP, the CRM and the inbox, follow-ups written one at a time, and a CRM nobody trusted: fewer than 1 in 2,000 records had a valid owner.

Clients' people

What was already in the client's environment

The data, locked in the ERP, and 16 outbound reps across the US and India who knew their accounts. A person approves every follow-up before it sends; the client keeps the final say.

The build team

What shipped, what it returned

An embedded CAIO and production engineering team; 5 production workflows. A 28-endpoint API over the ERP, a risk score on every memo every 15 minutes, a follow-up engine with human approval, a ranked daily list per rep, a nightly sync of the ERP, the CRM and email, a Claude assistant over live data, and a read-only MCP server so staff query the ERP from their own claude.ai accounts. First cycles: 290 follow-up drafts; 138 sends, 31 replies, 18 balances cleared. 6-10 staff hours a week returned.

5 weeks
to the first live workflow
516 → 0
account ownership mismatches
34,000+
actions queued on reps' daily lists
Private equity · ~$1.7B committed capital · 9 portfolio companies

Mid-market industrial private equity firm: a fractional Chief AI Officer

In production since June 2026 All 22 employees Claude API + Claude Code + MCP
10-15 hrs
a week returned across deal, BD and fundraising
fixed-cost build vs $250K+ vendor quotes

The operator

The problem we took

No AI capability anywhere in the firm. Data rooms read by hand too late in the deal window, about 750 proprietary targets sitting unworked in a stale CRM, 200+ limited partners tracked in spreadsheets, and partners who disagreed on what AI was worth.

Clients' people

What was already in the client's environment

The deal CRM with 35,000+ interaction records, placement-agent and Outlook history, and the data rooms. The investment committee ratified the AI charter; the partners now build their own Claude skills.

The build team

What shipped, what it returned

About 20 interviews and a two-by-two produced the charter. Then three production tools on Claude: a sourcing desk that ranks daily outreach, a fundraising desk with generated meeting briefs, and diligence triage that flags every finding, behind per-user keys, passkey login and audit logs, with an accuracy battery on every release.

~750
targets with ranked outreach
200+
LP profiles with generated briefs
~$100
API cost per data-room screening

The thinking behind the work, by industry.

All insights →
Health plans

Three levers for AI in a health plan

Most plans point AI at the smallest lever. The bigger returns sit in the other two.

4 min read
Health plans

The office that actually pulls the levers

Naming the levers is easy. Pulling them is a question of structure.

4 min read
Cross-industry

Consolidate first, then deploy

A hundred workflow variants collapse into a handful, in the right order.

4 min read
Health plans

Health plans already ran this experiment

VBC taught plans what happens when silos own the roadmap.

3 min read
Investors

The $600K math

A credible AI hire costs $600K. The roadmap problem survives the hire.

3 min read
Investors

You need a ledger, not a metric

Activity dashboards don't answer the board. A benefits ledger does.

3 min read
Health plans

The speed trap

Two versions of prior auth: one runs faster, one changes the work.

4 min read
Investors

The moat inversion

When every buyer has the same models, your context becomes the moat.

3 min read
Cross-industry

Own the layer that stays

Route workloads across models. The context layer, locally hosted, is yours.

3 min read
Health plans

The layer tax

Payer data arrives in layers. Each one caps what AI can return.

3 min read
Health plans

Every AI roadmap is secretly a data roadmap

The AI roadmap slips when the data roadmap under it was never written.

3 min read
Health plans

The talent auction

Regional plans cannot win the $600K talent auction. They do not need to.

3 min read
Investors

The office agents report to

Agents that cross silos need an office that owns them.

3 min read
Health plans

The forward-deployed health plan

Sort the org chart into volume and judgment, then staff to the second.

3 min read
How we AI

Most regional MA exits are not exits

Most "exits" are sales. Contract-level tracing tells them apart.

4 min read
How we AI

Reading the Cityblock-Homeward deal

The read the headlines missed, built from public CMS data in an afternoon.

4 min read