We're a small team. Are we too small for you?
No — small is where we start. Foundation is built specifically for 3-10 person clinical operations. Reference Stack engagements scale up from there. You have the same regulatory and audit obligations as a larger organization with a fraction of the staff and budget.
How is this different from a regular MSP?
A regular MSP sells managed services. We sell the deployment of a documented reference architecture that is currently running inside a licensed clinical operation the founder co-owns and operates. After the build, an optional co-management retainer keeps the stack maintained. The work is sold as an architecture engagement, not a per-seat MSP contract — because the value is in the architecture, not the helpdesk.
Are you "HIPAA-compliant" yourselves?
We don't claim HIPAA compliance as a marketing label — compliance is a legal status that belongs to covered entities and their business associates, not to a vendor's marketing page. What we can say is that NH Care Center, the licensed home health agency the founder co-owns and operates, runs under the HIPAA Security Rule, He-P 809, and RSA 151 — and the infrastructure stack at NHCC is the same one we deploy for you. We sell infrastructure that meets the Security Rule's technical safeguards. We don't sell compliance programs, policy templates, or attestations. That's a different practice and a different liability.
How do you keep costs predictable?
We're vendor-neutral and budget-honest. Where an open-source or self-hosted platform meets the requirement, we use it and skip the per-seat licensing tax. Where commercial or enterprise tooling is genuinely better for your case, we specify that and tell you why. No pass-through vendor markups, no hidden rebates, no pressure to buy what you don't need. Hardware is at cost. You pay for our expertise and the hardware — not a middleman.
Can we use the tools we already have, or do you force a specific stack?
We meet you where you are. If your team already runs specific firewalls, hypervisors, EDR, or cloud providers, we work with them — and we'll tell you candidly whether they fit or should be migrated. The only thing we require is something defensible under audit and something we can document and hand back to you if you ever leave.
What's the contract like?
Reference Stack and Foundation are fixed-fee engagements with scope locked before signature. Optional co-management retainers after deployment carry a written SLA and a 30-day cancellation clause from either side. No multi-year lock-in, no auto-renewing traps, no early-termination fees. If we stop delivering value, you should be able to leave. So that's how we wrote it.
Do you work with non-healthcare clients?
Yes. Clinical healthcare is our deepest specialty — the Reference Stack and the Blueprint case study are built specifically for clinical operators under HIPAA and He-P 809. But the same infrastructure discipline serves law firms, accounting practices, financial advisors, nonprofits, education, and other regulated SMBs with real audit, insurance, or PII obligations. Those engagements are scoped individually rather than fitting the three published tiers above — reach out and we'll tell you straight whether the fit is right.
What's the difference between Foundation and the Reference Stack?
Foundation is a productized HIPAA baseline for 3-10 person clinical operators who need defensible posture but not full architecture — flat fee, fixed scope, 2-3 week build. The Reference Stack is an architect-tier engagement for production clinical operations of 10+ employees or multi-site footprints, with full HIPAA Security Rule and He-P 809 mapping. Foundation is the on-ramp; the Reference Stack is the destination. A Foundation client who grows into multi-site operations can graduate.
Why no rate card beyond what's published?
The Reference Stack tiers and Foundation are published above. Hardware is pass-through at cost. The architecture review for custom engagements is priced after scope is defined. The pricing is firm — there is no haggling tier, no negotiated discount, no bundle pricing. The work is anchored to a documented reference architecture, not a service catalog, and discounting the work would discount the architecture.