Engagement Process
How a typical engagement starts, what the Paid Scoping deliverables look like, and what walking away looks like.
Overview
A good process protects you before money is committed and keeps scope honest after. DevStudio starts with a free discovery call, then a Paid Scoping engagement that produces four written artifacts useful to any builder. This page explains how an engagement starts, what the deliverables are, what walking away looks like, and how change requests are handled without silent scope creep.
Key things to know about the process
Discovery, then Paid Scoping
A free 30-45 minute discovery call leads into a $700-$2,800 Paid Scoping engagement with a written go/no-go and four deliverables before any build commitment.
Four artifacts you keep
Business Alignment memo, Data Readiness Scorecard, Architecture and Eval Plan, and a Cost Model with risk register — designed to be useful regardless of who ends up building.
Change requests are explicit
Work runs in two-week increments. Anything inside the next increment is in scope; anything bigger is a written, priced change request, so scope changes never get absorbed silently.