A short, scoped engagement that turns 'we know we need something' into a written plan: who it's for, what it does, what it costs, and how it phases.
What you get when this service is part of a Yab engagement. Scoped per project.
Structured sessions with leadership, operations, IT, and the people doing the day-to-day work. We surface the gaps no single person sees on their own.
What content exists, what it should be, how it's structured, who owns it, and how editors will work with it. The bones of a CMS that doesn't fight you.
End-to-end journeys for each audience — customer, patient, admin, partner — with the systems, screens, and decisions mapped out in writing.
Audit of existing stack, integrations, hosting, security, and compliance posture. What's load-bearing, what's a liability, what should be replaced.
A 6–18 month plan broken into shippable phases with realistic budgets and timelines. You leave with a path you can fund and a way to defend it.
Honest input on what to build, what to buy, and what to keep. We have no resellers and no vendor commissions — the recommendation matches the situation.
Operating numbers and posture you can quote back to us. These are commitments, not aspirations.
Real engagements where this service was load-bearing. Click through for full case studies.
EHR-integrated patient intake, referral coordination, and clinical document handling across six clinics.
NetSuite-integrated B2B commerce with account pricing, quote workflows, and a customer portal that handles 80% of orders.
Member portal, supply-chain integration, certification program, and public impact reporting on one platform.
The shape of a typical engagement. Phases overlap on larger projects, but the sequence is the same.
Half-day session with the leadership team to align on the question we're actually answering. Scope of the discovery confirmed in writing.
5–15 conversations across the org, plus technical audit of the systems and content already in place.
Findings written up. Options weighed. We narrow to a recommended path and the alternatives we considered.
Final readout: the written plan, the phased roadmap, the budget ranges, the risks. Yours to take into the next budget cycle.
Sectors where we’ve done this service often enough to know the patterns — and the patterns that don’t work.
The things people ask before they reach out. If yours isn’t here, send it over — we’ll add it.
If the project is small and the path is obvious, no — we'll say so. If you're staring at a 12–24 month roadmap, an unclear vendor landscape, or a legacy system that nobody wants to touch, then yes, a few weeks of discovery is worth more than the cost.
Discovery engagements start at $12k for a focused 2-week sprint and most land between $15k and $35k depending on the breadth of stakeholders and the depth of technical audit. Quoted in writing before we start.
A written plan (not a slide deck): the recommended path, the alternatives we ruled out and why, the phased roadmap, budget ranges, integration map, content architecture, and the risks. Everything you need to defend the project in your next budget meeting.
No. We'll happily help you go to RFP with the plan, including the parts you should ask other firms about. We bill discovery as discovery — the plan is the deliverable, not a sales tool.
Yes. Discovery often runs alongside an incumbent. If they're doing good work we say so; if they're not, we say that too. Either way the goal is to leave you with a real plan, not a coup.
One reply within a business day. No sales pipeline. We’ll either propose a path or point you somewhere better.