Project scoping

Scope the work before the work starts.

I do not force every technical problem into the same package. The useful question is what needs to change, what is already known, and how much uncertainty has to be removed before implementation can be scoped responsibly.

01

Bounded implementation

Best when the problem is already clear: a feature, production bug, integration, migration step or focused improvement with a definable finish line.

  • Problem and desired outcome are already understandable
  • Scope can be written without a long discovery phase
  • Timeline and investment are agreed before implementation
  • New requirements are discussed before they expand the scope
02

Discovery-led work

Best when the system has more uncertainty: multiple flows, unclear technical constraints, architecture decisions or dependencies that need investigation before a responsible build plan exists.

  • Current system and constraints are reviewed first
  • Important unknowns are reduced before committing to a build
  • A sensible implementation path is defined from the evidence
  • Scope, timeline and investment follow the discovery outcome

What shapes the quote

Price follows scope and responsibility, not a generic menu.

  1. 01How much of the product or system is changing
  2. 02Technical complexity and existing system condition
  3. 03Integrations, data, authentication and deployment requirements
  4. 04How much uncertainty needs to be resolved before implementation
  5. 05Timeline constraints and the level of delivery responsibility involved

Start with context

Send the problem first. We can decide the right engagement shape from there.

A useful first message includes what exists today, what is not working or needs to change, and what a good outcome looks like. Budget and timeline can stay open if they are not clear yet.

Start a project