Project Scoping & Estimate-Readiness Tool
Answer 5 questions about your project to get a complexity signal and a personalized checklist for what to prepare before requesting a cost estimate.
The three complexity signals, explained
The tool above scores your five answers and matches them to one of these three signals. Here's what each one means and recommends, regardless of which one applies to you.
Your project looks relatively well-bounded
Based on your answers, the scope, integration surface, compliance needs, and duration all point toward a project that's easier to estimate with confidence. That doesn't remove the need for a scoping conversation, but it usually means a shorter one.
- You can likely move to requesting a written proposal with a scope breakdown fairly directly.
- Still ask any prospective partner to state the assumptions behind their estimate explicitly.
- Confirm there's genuinely no compliance requirement hiding in the data you'll handle — this is the most common thing teams underestimate even on "simple" projects.
Your project has real complexity worth scoping deliberately
Your answers point to a project with enough scope ambiguity, integration surface, or compliance overhead that a short discovery or scoping phase before a firm quote will likely save cost and rework later, not add delay.
- Ask a prospective partner to run a discovery or scoping phase before quoting a fixed figure.
- Ask directly how team seniority would be matched to the complexity you've described.
- Identify your compliance and integration requirements as early as possible — they shape architecture decisions that are expensive to unwind later.
Your project carries meaningful scope, integration, or compliance risk
Multiple factors in your answers — ambiguous scope, several integrations, real compliance requirements, or a long engagement horizon — compound together. A confident-sounding number from a short call, without a scoping phase, is a signal worth questioning rather than reassurance.
- Insist on a structured discovery or scoping phase before accepting any firm number.
- Ask specifically how integration risk with legacy or poorly documented systems was factored into the estimate.
- Expect — and ask for — a range grounded in stated assumptions, not a single precise-sounding figure.
- Ask how the delivery model (fixed-price, time-and-materials, outcome-based) allocates risk for a project shaped like yours.