Engagement model
A narrow commercial ladder for products that need better judgment before more motion.
Morrow Works is designed to stay legible. Most teams should not buy a vague retainer first. They should begin with the smallest paid step that creates real decision quality, then move into bounded rescue or ongoing partner support only if the product actually needs it.
The 3-step ladder
Morrow Works gets stronger when each engagement has a clear reason to exist.
- Assessment first when the situation still needs diagnosis, tradeoff clarity, and a recommendation the team can trust.
- Rescue second when one concentrated risk zone is already visible and should be stabilized directly.
- Build Partner third when the product is important enough to justify ongoing senior continuity after the shape of the work is already understood.
Default sales rule
Sell the smallest paid step that creates real decision quality.
That usually means assessment first, rescue when scope is already defensible, and Build Partner only after the system and operating need are clear enough to support an ongoing premium relationship.
When each offer is right
Choose the motion that matches the product reality, not the client’s initial guess
Best when the product matters, the stakes are rising, and the right next move is still fuzzy.
- Fixed fee: $2,500
- Typical shape: ~1 week
- Outcome: written decision memo + preserve / stabilize / replace recommendation
Best when one subsystem or milestone is already the obvious problem and the work can stay bounded.
- Starting band: $6,000–$12,000+
- Typical shape: 1–3 weeks
- Outcome: one dangerous path made calmer, more trustworthy, and easier to own
Best when the company needs ongoing senior product/engineering judgment, not just another implementation vendor.
- Typical bands: $4,000–$6,000, $7,500–$12,000, $12,000+/mo
- Typical shape: monthly ongoing
- Outcome: steadier sequencing, technical decisions, and selective direct execution over time
See Build Partner details · Review example Build Partner scope
Start with assessment when
- The team still needs a calm read on what is actually wrong
- Multiple systems or stakeholders are involved
- The product is too important for vague pre-sale advice
- The buyer wants senior judgment, not free diagnosis theater
- You need a real recommendation before code changes start
Skip to rescue when
- The dangerous path is already visible
- Access is ready now
- Scope can be bounded in writing
- The client accepts that only one concentrated risk zone gets addressed first
- The work is clearly smaller than a rebuild and more concrete than advisory
Good Build Partner fit
- The product is strategically important to the company
- Leadership needs recurring senior judgment, not commodity dev capacity
- There is a real next milestone or operating stretch ahead
- The team can use ongoing review, prioritization, and selective hands-on work
- Budget supports premium monthly continuity
Not a good Build Partner fit
- The real need is generic staff augmentation
- The product is still too blurry to justify monthly continuity
- Nobody can provide access, ownership, or decision speed
- The team wants unlimited hours under a nicer label
- The client is trying to outsource accountability instead of buy leverage
Representative pricing logic
The fixed fee stays simple because the value is decision quality, not time spent sounding thoughtful.
Price increases when the risky subsystem touches billing, auth, permissions, data integrity, compressed timelines, or multiple vendors/environments.
Monthly price depends on how much of the product surface needs active involvement, how often decisions need senior review, and how much direct execution is required.
What Morrow Works is trying to prevent
When a buyer wants free consulting disguised as “just one more conversation.”
When bounded implementation starts turning into a backlog-clearing service.
When Build Partner starts sounding like rented dev hours instead of senior operating leverage.
When every unusual lead becomes an excuse to invent a fourth or fifth core service.
Anti-sprawl rule
One lead should map to one primary motion: assessment, rescue, or Build Partner. If the lead still needs clarity, sell clarity. If the scope is already bounded, sell bounded work. If continuity is truly needed after trust exists, sell partner support.
Start with the Morrow Assessment.
See whether Morrow Rescue can be scoped directly.
Review Build Partner, but expect the engagement to stay grounded in an assessment or prior rescue truth.
Practical next step
If the product matters but the right engagement shape is still unclear, begin with the assessment.
That keeps the conversation honest. It creates a real recommendation, a real next-step choice, and a cleaner path into rescue or Build Partner only when the product earns it.
Need to gather context first? Use the prep checklist. Want to see the first step more concretely? Review the assessment deliverables.