Processes - New Product Contracted Development β Onboarding & Delivery Process
A precise breakdown of what happens from first call through to launch. Built for founders and product leads who want clarity, velocity, and outcome-led development.
Overview
This guide outlines how we deliver new software products under our New Product Contracted Development service.
Broken into:
- Pre-Engagement: Discovery & offer (pre-payment)
- Onboarding, Planning, and Setup: Once we agree to proceed
- Execution: Task-driven build cycles
- Handoff or Scale: Launch and next steps
NOTE - The 'payment' referred to here is the upfront cost of Β£1,000 or more for the 'Onboarding, Planning, and Setup' step.
It's the planning that's required for any development, packaged and done upfront - not an additional cost but a structured approach.
Curious about our our methodology behind the madness here
Pre-Engagement (pre- initial payment)
1 β Introduction & Discovery
- We listen to your needs
- We convey our offering options
- We determine which which of our offers suit your needs (if any)
2 β Offer & Agreement
- We established commination channels
- We provide an offer breakdown - with documents including:
Onboarding, Planning, and Setup (post- initial payment)
3 β Specification & Prioritisation
- Feature requirements are collaboratively expanded into actionable tasks.
- Areas of technical uncertainty are flagged.
- Fix MAX prices are established for features and task.
- You choose which features and tasks to prioritise - like selecting from a menu.
4 β Setup & Expectation alignment
- We agree on a rolling budget and parameters for adhoc tasks - adhoc consultation, planing, R&D, etc.
- We establish timelines based on your budget and the task breakdowns.
- We establish and communicate the some of the 'Ongoing Processes and Systems' - our ways of work, so that it's clear how we'll proceed.
- Backlog refinement sessions
- Service quality assurance reviews & check-ins
Ongoing Execution
5 β Task-Based Delivery
- We execute on signed off tasks.
- We communicate progress.
6 β Service Management
- We host recurring backlog refinement sessions
- We host recurring service quality check-ins on velocity, communication, and alignment
Handoff or Scale
7 β Project Close or Next Phase
At any stage you can:
- Pause: We wrap the project with clean handoff documentation, versioned code, and source access.
Note: All completed and in-progress work must be fully compensated prior to offboarding. - Scale: Continue building features, increase capacity, or launch a new planning cycle.
All our builds include:
- Deployment to your infrastructure
- Handoff-ready documentation
- Access to all design and dev sources
- High-level system overview (to support internal or external continuation)
Summary
This is not just development. It's structured product delivery β with:
- CTO-level planning & guidance
- Outcome-based pricing
- Production-quality code
- Fast, flexible delivery
- Clarity from day one to handoff (or scale)