Exploring a similar greenfield build?
The Hello ICP is $2M+ practices, but the solo exception applies where LTV and willingness-to-pay hold. Every engagement starts with an audit, operational review of current stack, call flow, and staffing model.
Greenfield Build
A solo cash-pay telehealth practice built from zero in eight weeks,
with enterprise-grade compliance from day one
Board-certified anesthesiologist launching a cash-pay functional medicine telehealth practice in Colorado. A greenfield build from zero: site, CRM, EHR, scribe, supplements, payments, and Hello Voice, with Mercury on every AI data path from day one. Included on this page as a capability showcase: it proves end-to-end greenfield delivery, not that solo cash-pay is Hello's primary market.
Practice
- Practice
- Functional Medicine (Telehealth)
- Location
- Colorado (cash-pay telehealth)
- Practice shape
- Solo provider, zero support staff
- Deployment motion
- Greenfield Build
- Existing systems
- AI systems deployed
The problem
Solo economics, enterprise compliance posture
A physician launching a cash-pay functional medicine telehealth practice from zero. No administrative staff. No legacy systems to retrofit. Two constraints had to hold simultaneously: the monthly stack had to stay inside solo-practitioner unit economics, and the compliance posture had to match what a multi-provider clinic would carry from day one.
Most tooling that prices for solo practices does not meet HIPAA-grade compliance. Most HIPAA-grade stacks price for organizations with administrative teams. A solo cash-pay clinician falls in the gap: high willingness to pay for outcomes, no IT function, no operations staff, and real compliance exposure the clinician-founder cannot self-govern. Hello's mandate was to build the bridge.
The solution
Eight weeks from audit to live practice, one accountable team
Hello sequenced legal and BAAs, CRM and form middleware, clinical stack and revenue capture, Hello Voice, and Mercury across eight weeks. The six-layer architecture enforced the PHI and non-PHI boundary by design, not clinician discipline. No systems to replace. Compliance was part of the architecture from day one, not retrofitted after launch.
What was deployed
Six layers live, full BAA-backed stack
Capabilities drawn from the same Done-for-you AI Implementation taxonomy as every Hello engagement. Services below map the greenfield manifest into the case-study console pattern.
AI audit, operating model, and BAA execution
8 wks
Audit to live practice
Before
No website, no CRM, no EHR, no vendor BAAs, no compliance architecture. Every vendor needed selection, contracting, BAA execution, and configuration from scratch.
After
Discovery produced a six-layer stack architecture with explicit contracts between layers. Week one ran BAAs across Practice Better, Zoho in HIPAA mode, Google Workspace, Freed, Stripe, and Hello Voice. Solo-clinician operating model with clear AI and human boundaries.
Hello Voice
Week 6
Voice go-live in sequence
Before
No inbound voice coverage, no after-hours path. The physician was the only intake surface.
After
Hello Voice for inbound calls, booking, and after-hours coverage, with Mercury on the voice data path as integrations came online.
Lead qualification
Before
No lead capture, no CRM, no routing from web to clinical intake.
After
Zoho CRM Plus in HIPAA-appropriate mode, consented lead capture, web form routing, and pre-qualification into the CRM. Marketing and identity data kept upstream of PHI wherever possible.
Workflow automation
30–40%
Administrative burden automated
Before
No intake automation, scheduling, payment capture, or protocol delivery. Everything manual.
After
Practice Better for EHR, programs, and intake; Freed as AI scribe; Fullscript and Stripe wired into the operating model. Intake, payments, supplement dispensing, and follow-up automated end to end.
Data foundation and integrations
Before
No integration layer, no source-of-truth alignment, no enforced PHI boundary.
After
Cloudflare Worker form endpoints, Zapier middleware, and explicit workflow automation between non-PHI and PHI boundaries. Alignment across site, CRM, EHR, payments, labs, and supplements.
Mercury compliance layer
Day 1
Controls at launch
Before
No audit-ready evidence, retention policy, or access controls on AI-mediated data paths.
After
Mercury instrumented every integration as it came online: retention, audit evidence, role-based access, and model and data control flows across every AI-mediated step.
The outcome
Solo-clinician unit economics, enterprise-grade controls
The practice launched with the operational backbone of a multi-provider clinic inside the cost envelope of a solo practice. Every PHI-touching vendor is BAA-backed. Marketing and identity data flows through a lighter-weight CRM layer, kept upstream of PHI wherever possible. The compliance posture was not retrofitted; it was part of the architecture from day one.
One accountable delivery team owned audit, architecture, ship, and ongoing operations. The clinician operates the stack daily with no administrative staff, no IT function, and no vendor coordination overhead.
8 wks
Greenfield implementation, end to end
30–40%
Administrative burden automated
6 layers
Architectural compliance enforcement
Day 1
Full compliance posture at launch
0
Administrative staff required
100%
BAA coverage across PHI-touching vendors
Mercury
On every AI data path, from go-live
$400–600K
Year-1 revenue target, achievable solo
Revenue target is a planning figure, not a guarantee. Outcomes depend on specialty, patient acquisition mix, and agreed scope.
In their words
What Dr. Lepczyk says about the engagement
I am one physician with no staff. Hello built me the operational backbone of a multi-provider clinic and kept it inside the cost envelope of a solo practice. The compliance posture is the thing I would have spent six months building wrong on my own.
Is this your motion?
When this pattern fits, and when it does not
Use this as a readiness check before booking a consultation.
Strong fit
- Solo or small-group practice launching from zero with no existing stack to retrofit
- Cash-pay, DPC, or concierge model with high willingness-to-pay for done-for-you implementation
- Clinician-founder with no IT function and no operations staff to manage vendor coordination
- Leadership ready for enterprise-grade compliance posture from day one, not bolted on later
Not the right motion
- The practice relies on insurance-heavy payer mix requiring complex billing integrations from launch
- Multi-location operations are needed from day one (scale retrofit may be the better motion)
- The practice already has operational staff and existing systems that work (see the scale or existing stack case study)
- Scope is limited to a single-function AI add-on rather than end-to-end greenfield build
Next step
Be the next case study
An audit if you need diagnostic clarity before commitment. A consultation if scope is already clear and you want a written statement of work.
Either path lands you with the same accountable team and the same SOW.
HIPAA + BAA-backed
Live in 10 days
Done-for-you implementation