A 90-day execution engagement sits between a vague retainer and a fixed one-off project. It gives enough time to diagnose, implement, review, and adjust without drifting into undefined consulting.
Scope starts with outputs
The first question is not “how many days per week?” It is “what must be true at the end of the 90 days?” That could mean a visible sales pipeline, an approved systems architecture, a working automation flow, or an implementation roadmap with real evidence behind it.
Inputs and exclusions need to be explicit
The sprint should identify what information, access, and stakeholder availability are required. It should also name what is outside scope. That keeps the work sharp and reduces later conflict.
Weekly rhythm matters
Short engagements fail when review only happens at the end. Weekly check-ins surface blockers, decisions, missing data, and next actions early enough to keep momentum.
KPIs create accountability
Not every engagement needs a complex KPI set, but there should be visible markers of progress: pipeline visibility, system readiness, adoption, response time, handoff quality, or another measurable signal tied to the problem being solved.
Commercial clarity protects both sides
Fixed pricing against written scope keeps the engagement disciplined. If major scope changes appear, they should be priced and agreed separately rather than smuggled in under the original fee.