Best Fit
When Discovery is the right starting point
- the process lives too much in tribal knowledge
- handoffs and ownership are unclear
- the future state is still being debated
- one workflow slice needs clearer shape before broader work begins
Discovery → Future-State Process Pack
The starting offer for workflow areas where the process is fuzzy and the future state is not yet agreed.
Discovery turns confusion into a practical future-state design and next-step roadmap for one named workflow or functional slice. It clarifies how the work should run before more detailed delivery support is added.
Use Discovery when the work is slowed by misalignment, tribal knowledge, fuzzy process, or an unclear future state. It is meant for one named workflow family or functional slice that needs a clearer operating shape, not a giant enterprise transformation.
Misalignment around how the work should run
Tribal knowledge carrying too much of the process
A process that feels fuzzy in practice
An unclear future state that needs agreement
What You Get
Every Discovery engagement starts with this shared foundation before additional operational detail or enablement support is attached.
Current-state map
Makes visible how the work actually moves today, including key handoffs, friction points, and hidden dependencies.
Future-state map
Gives the group an agreed target shape for how the workflow should operate once the ambiguity is removed.
Role clarity
Clarifies who decides, who contributes, and where ownership is currently blurred or contested.
Decision / open-questions log
Separates the decisions already made from the questions that still need leadership attention or boundary-setting.
1-page roadmap
Summarizes the next 30 days in practical terms so the design can move into action without becoming a long document shelf.
What The Work Looks Like
A practical engagement shape
Most Discovery engagements are structured to move within 2 weeks to 2 months, depending on decision pace, scheduling realities, and whether priority add-ons are attached.
01
Discovery workshops and artifact review
02
Current-state mapping and pain-point validation
03
Future-state design and boundary decisions
04
Recommendations and next-step roadmap
Pricing
Engagement shapes and pricing
This pack is fixed-fee and tiered by scope depth, artifact detail, and bounded follow-through. It is not priced as hourly coverage.
Core
Best when the future-state answer needs a clearer structure.
$11,750
- Future-state definition and decision path
- Current-state and future-state maps
- Role clarity, open questions, and next-step roadmap
Plus
Best when the priority workflow needs more operating detail.
$13,750
- Everything in Core
- Priority SOPs or job aids
- More operational detail and leadership readout
Premium
Best when the work needs bounded first-cycle enablement.
$16,000
- Everything in Plus
- First-cycle enablement plan and walkthrough
- Light process-to-system notes and bounded Q&A
Each engagement is scoped to a defined problem, a bounded artifact set, and one consolidated review cycle. Additional scope is handled as an add-on, change order, or follow-on phase.
Common Add-Ons
Process-to-System Alignment Review
Connects the future-state design to the systems and constraints it will need to work within when fit and sequencing need a clearer read.
Pilot Readiness Pack
Prepares the first live cycle so the priority workflow, handoffs, and ownership are ready to be tested in practice.
Rollout Enablement Pack
Adds the materials and enablement support needed to put the agreed future-state into use without turning Discovery into ongoing ownership.
What This Is Not
Clear boundaries keep the pack useful and focused
- Not hands-on system build
- Not broad enterprise transformation
- Not full backlog writing unless separately sold
- Not ongoing implementation ownership unless separately sold
Next Step
If you know there is a fuzzy workflow problem but want help confirming whether Discovery is the right starting point, start with a Fit Call.
The call is there to confirm fit, define the named workflow or functional slice, and keep the starting scope disciplined.