Discuss a project

Start with a scope call about the product and the next release that matters.

What to include in your first message

Describe the product, who uses it, and the next meaningful release. Include known dependencies, deadlines, and the skills already available on your team.

What happens next

The scope call determines whether the work calls for a focused build, a dedicated team, or added capacity inside your team. If there is a fit, you receive a written release plan before anything starts.

How a project runs

  1. Scope call

    Walk through the product, its users, and the next release that matters. Bring known dependencies and the skills already on your team.

  2. Release plan

    You get a written plan with the smallest useful release, acceptance examples, the people and roles proposed for the work, and what is explicitly out of scope.

  3. Build in the open

    Work ships in small increments with regular demos of real workflows, including failure cases, rather than percent-complete reports.

  4. Handoff you can operate

    The release includes tests, diagnostics, a rollback procedure, and a runbook, and your team has run it before the engagement closes.