Everything you need to know about how it works, what it costs, and what to expect.
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.
Will this replace my staff?
No. It removes repetitive admin steps. Your team keeps control. They spend less time chasing paperwork and more time on care coordination and exceptions.
What access do you need?
We keep access minimal. We use least-privilege design. In many cases we can start with sample data, a workflow owner, and a controlled integration path. We document all access and make it revocable.
Is this secure and audit-friendly?
Yes. We design for role-based access, human approvals, and traceable logs. We can support BAA needs where applicable. The audit trail is built in by default—not added as an afterthought.
Do we lose control?
No. We design key steps with human review. Your team approves sensitive actions before they run. You can also choose which steps are always manual—that's a configuration decision, not an automation one.
Do we have to change how our team works?
No major change. We fit into your existing process. We simply remove manual steps and make handoffs clearer. The team's job changes from doing repetitive work to reviewing and approving it.
What does "human review" mean in practice?
The system prepares the work and suggests the next action. A human clicks approve for actions like submitting, updating, or closing a critical item. Nothing "important" runs blindly. The approval is logged with timestamp and actor.
How do we know what the system did?
Everything is logged. You can see what happened, when it happened, and why. That includes every automated action, every human approval, every exception, and every change. The audit trail is always available.
Do you work with our current tools?
Yes. We connect to what you already use. We avoid "rip-and-replace." We integrate with fax workflows, portals, and your EMR where appropriate. Bring your system list to the call and we'll map the path.
What if our process changes later?
That's normal. We tune workflows over time. Changes are staged and traceable, so updates don't break production unexpectedly. Process evolution is part of what ongoing support covers.
What happens if a vendor changes their system or portal?
We monitor for breakages and fix compatibility as part of support, within scope. We also design fallbacks so work does not silently fail when portals shift. You'll get an alert before it affects production.