Web Analytics Made Easy - Statcounter

Start Small.
Keep It Predictable

Clear pricing. Clean scope. No surprises. You’ll know the range before we leave the first call.

Healthcare automation pricing

Clear line items.
No hidden fees.

Every quote follows the same simple structure. You know what you’re paying for before signing anything.

One-time · Per workflow

Pilot Build

Everything needed to take one workflow from zero to production-ready in your environment.

$3k–$7k

per workflow · one-time build cost

End-to-end workflow build

Integrations to your stack

Go-live with monitoring

CraftOps foundation included — every subsequent lane ships 30–60% faster

Ongoing · Per lane · Annual plan

Lane Ops

Operational responsibility for keeping your lane running reliably — not just the cloud bill.

~$250

per lane / month on annual plan

Lane Ops — monitoring & uptime

Fine-tuning as your workflows evolve

Compatibility patches & security updates

Scales linearly — each new lane adds ~$250/mo

Ongoing · Pass-through

Hosting

Raw cloud infrastructure, invoiced at cost. No margin added. No surprises. Scales exactly with usage.

At cost

pass-through · no markup · separate line item

No markup, no surprises

Scales with your usage

Separate line item on every invoice

Typically low for most home health agencies at steady-state volume

Get your pricing range in one call

We’ll map the simplest integration path.

FAQs

What is a “lane”?

A lane is one complete workflow running in production. Example: Orders & Signatures, EVV Exceptions, or Claim Follow-ups. Each lane has clear steps, owners, exceptions, and reporting. You start with one and expand at your own pace.

How many lanes do we need?

Most teams start with 1 lane. Once it’s stable and saving time, you add the next. There’s no minimum. You grow at your own pace without pressure to expand until you’re ready.

What is Lane Ops?

Lane Ops is the ongoing care for the lane’s running environment. It covers monitoring, updates, security patches, backups, and recovery so the lane stays reliable over time. It’s the operational responsibility, not just the cloud bill.

Why is Lane Ops separate from hosting?

Hosting is the cloud bill—the raw infrastructure cost. Lane Ops is the responsibility to keep the lane running: catching issues early, patching compatibility, monitoring uptime, and recovering from failures. Both are transparent line items on your invoice.

How is pricing structured?

Simple line items: one-time build per workflow ($3k–$7k intro), monthly support (~$250/month per lane on annual plan), and hosting pass-through at cost. You’ll have a real number before we finish the plan call.

What’s included vs not included?

Support includes stability, compatibility, and tuning for existing workflows. Net-new workflows, major expansions, and big new integrations are quoted separately. We’re explicit about this on every quote.

How fast can we start?

Fast. We start with one workflow. Many agencies begin with Orders & Signatures because it blocks care and cash. We launch a pilot first, then expand. Typical go-live is Weeks 2–6 after the planning call.

What does the pilot look like?

We map your current steps, set the approval points, go live in a safe mode, and tune weekly. You’ll see a scorecard for cycle time and exceptions. The pilot is a live workflow, not a demo or prototype.

What’s the best first workflow to automate?

Usually the loop that causes the most delays. For many agencies: Orders & Signatures, EVV Exceptions, or Claim Status follow-ups. We help you pick the safest first win on the plan call based on your specific volume and pain points.

Explore More

Go deeper
on the platform.