FAQ
Process & timeline:
“How long does a typical project take?” Depends on shape. An Answer is often measured in days to a couple of weeks. A System is typically a few weeks. An Engine is ongoing by design, with clear scope and review cadence — not an open-ended retainer.
“What’s your process from the free audit to delivery?” Free Operations Audit → Fit and shape (Answer, System, Engine, or no fit) → Fixed-scope proposal → Kickoff → Build → Handoff. Details are on the Services and Audit pages.
“Do you work on retainer, or is it project-by-project?” Most work starts as a fixed-scope Answer or System. Ongoing Engine support is available when the decision is recurring — scoped and asynchronous, not open-ended access.
“Can you start immediately, or do you have a waitlist?” Bandwidth is intentionally limited. If there is room and the problem fits, Answers can start quickly. Larger Systems and Engines depend on current client load.
Data & logistics:
“What if my data is messy / in different systems / not well-organized?” That is normal. Cleaning and joining existing data (Excel, EHR, practice management, claims, CRM, accounting tools) is part of scoping — we work with what you already have.
“Do you need to visit in person, or can we work remotely?” Most work is remote. On-site meetings are available when stakeholder alignment or process context needs it.
“How do you handle sensitive data / confidentiality?” Career work has always fallen under HIPAA, IRB, and banking supervisory expectations where relevant. Additional documentation and security arrangements can be scoped when needed.
“What tools/software do I need to have?” CSVs and spreadsheets are enough for many Answers. If we need API or system access, that gets scoped upfront so there are no surprises. The goal is a lightweight system you can run — not a software purchase.
Scope & expectations:
“How do I know if this is the right fit for my budget?” Work has to have a believable path to lower waste, better cash conversion, tighter pricing, or clearer performance decisions. If we cannot explain the ROI in plain English, we should not do the project.
“What industries can you work with?” Primary focus is operational efficiency and margin recovery for healthcare operators. Secondary is pricing and margin analytics for clinics and similar owner-led operators. Opportunistic work outside those wedges happens when the problem maps cleanly — we do not market as a generalist analytics shop.
“What happens after the project? Is it a black box, or do you explain what you built?” You get the logic, documentation, and a walkthrough so your team can maintain it. No black boxes. Client-owned output is the default.
Pricing:
“Seriously, what is this actually going to cost?” Fixed scope, fixed price. After the free audit, you’ll get a range that reflects the decision at stake and the complexity of the build — not an open-ended hourly burn. The return should exceed the investment.