01Discover & Architect02Design & Prototype03Build & Verify04Launch & Hand over
Clear gatesTwo-week sprintsWeekly reportingYour repository from day oneQuality built inFull ownershipClear gatesTwo-week sprintsWeekly reportingYour repository from day oneQuality built inFull ownershipClear gatesTwo-week sprintsWeekly reportingYour repository from day oneQuality built inFull ownership
The journey
Four phases, one clear path.
Scroll to follow a typical 12-week project from first workshop to handover.
Weeks 1–2
Strategy
Discover & Architect
Agree what we are building, why, and how, before any code is written.
Exit gate: Blueprint sign-off
Weeks 2–4
Experience
Design & Prototype
Turn the blueprint into an interface people understand at first glance.
Exit gate: Design freeze
Weeks 4–10
Engineering
Build & Verify
Ship working software every two weeks, tested and secured as we go.
Typical timeline. Phases overlap slightly, and the exact plan is confirmed at the end of Phase 1.
Phase by phase
What happens, and what you get.
Select a phase to see activities, deliverables, your role and the exit gate.
Strategy · Weeks 1–2
Discover & Architect
Agree what we are building, why, and how, before any code is written.
What we do
Stakeholder workshops to capture goals, users and constraints
Domain-driven design: map the business into clear bounded contexts
Threat modelling and compliance scoping
Milestone plan with a fixed scope, budget and timeline
What you receive
System architecture blueprint
Domain and data-flow diagrams
Security and risk register
Milestone roadmap
What we need from you
Name one decision-maker, share existing systems and documents, and join two workshops.
Gate: Blueprint sign-offAn architecture decision record (ADR) is reviewed and approved by you.
Experience · Weeks 2–4
Design & Prototype
Turn the blueprint into an interface people understand at first glance.
What we do
Design tokens: type, colour, spacing, radius and elevation
Responsive and mobile-first interaction design
Accessibility checks against WCAG 2.2 AA, including keyboard use
Clickable prototype tested with real users
What you receive
Figma design system
Token export (JSON and CSS variables)
Interactive prototype
Component inventory
What we need from you
Review prototypes within two working days and give consolidated feedback.
Gate: Design freezeScreens and flows are approved so engineering builds against a stable target.
Engineering · Weeks 4–10
Build & Verify
Ship working software every two weeks, tested and secured as we go.
What we do
Type-safe front-end and back-end implementation
Automated unit, API and end-to-end tests in CI
Static analysis, dependency and secrets scanning on every commit
Staging demo and sprint report every two weeks
What you receive
Production source code in your repository
Passing automated test suite
Staging environment
Sprint reports and burn-down charts
What we need from you
Attend the bi-weekly demo and answer questions within one working day.
Gate: Release candidateAll agreed scope is complete, tests pass and the security checklist is clear.
Delivery · Weeks 10–12+
Launch & Hand over
Go live safely, then leave you fully in control.
What we do
Blue/green or canary release with rollback triggers
Monitoring dashboards, alerts and runbooks
Performance, security and accessibility sign-off
Code, cloud and documentation handed to your team
What you receive
Live production platform
Runbooks and architecture documentation
Monitoring and alerting
Full code and infrastructure ownership
What we need from you
Confirm the go-live window and nominate who receives the handover.
Gate: Go-live & handoverThe platform is live, monitored and documented, and your team holds every key.
Sprint rhythm
Every two weeks, working software.
During Phase 3, the same five-step cycle repeats. Select a step to see what happens.
Day 1
Plan
Confirm the sprint goal, scope and acceptance criteria together.
Governance
Four gates. Your approval at each one.
We never move to the next phase without your explicit sign-off.
01
Blueprint sign-off
Phase 1
You approve the architecture, scope and plan in writing.
02
Design freeze
Phase 2
Screens and flows are locked, so builds do not chase a moving target.
03
Release candidate
Phase 3
Scope is complete, tests pass and security checks are clear.
04
Go-live & handover
Phase 4
The platform is live, monitored and fully transferred to you.
Communication
Always know where things stand.
A predictable rhythm of updates, so you are never chasing us for news.
Daily
Async update
A short written progress note in your shared channel.
Weekly
Status call
30 minutes: progress, risks and decisions needed.
Every 2 weeks
Sprint demo
Working software on staging, with the sprint report.
Monthly
Steering review
Budget, roadmap and outcomes with your leadership.
Shared repositoryEvery commit lives in your own Git account from day one.
Live task boardSee what is planned, in progress and done, any time.
Staging environmentTry the real product at every sprint, not just at the end.
Reports & dashboardsBurn-down, test results and quality metrics in plain language.
Sprint 3 reportIllustrative
24Tasks done
0Open blockers
PassTest suite
Who does what
A true partnership.
Clear roles keep decisions fast and projects on track.
Set goals, priorities and success measuresYou
Name a decision-maker and approve gatesYou
Provide access, content and domain knowledgeYou
Architecture, design and engineeringNorthwind
Testing, security and release managementNorthwind
Weekly reporting and risk escalationNorthwind
Change requests and scope trade-offsBoth
Launch readiness and handoverBoth
Quality built in
Not a phase at the end. A habit throughout.
Our definition of done applies to every piece of work.
Code reviewEvery change is reviewed by a second engineer.
Automated testsUnit, API and end-to-end tests run on every commit.
Security scanningStatic analysis, dependency and secrets checks in CI.
AccessibilityWCAG 2.2 AA checks on every key flow.
Performance budgetsSpeed targets agreed up front and measured.
DocumentationArchitecture notes and runbooks updated as we build.
Please note: targets such as uptime, test coverage and performance budgets are agreed per project in Phase 1 and written into the plan.
Ways to work together
Pick the model that fits.
The process is the same. Only the commercial wrapper changes. See the pricing page for ranges.
Fixed-scope delivery
A defined outcome for a fixed price and timeline, paid by milestone.
Best for products with clear requirements.
Dedicated pod
A cross-functional team working only on your roadmap, billed monthly.
Best for long-running, evolving products.
Retainer & support
Reserved engineering hours for upgrades, fixes and growth.
Best after launch.
Managing change
Requirements will change. We plan for it.
A simple three-step path keeps scope, cost and timeline under control.
1
Raise itAnyone can log a change request on the shared board.
2
We assess itWe estimate the effect on scope, cost, timeline and risk within two working days.
3
You decideApprove, defer or swap it for something of equal size. Nothing changes without your yes.
Handover
You leave with the keys.
Nothing is held back and nothing is locked in.
Source code in your repository
Cloud accounts owned by you
Infrastructure as code
Architecture and API documentation
Runbooks and on-call guide
Credentials rotated and transferred
Recorded walkthrough sessions
Post-launch support window
In plain English
What is a software delivery process?
A software delivery process is the agreed way a team takes an idea to a live, working product. A good one makes progress visible, decisions explicit and risks early, so there are no surprises on launch day.
Northwind Studio uses four phases (discover, design, build and launch), each ending in an approval gate. Inside the build phase, we work in two-week sprints with a live demo each time, so you can steer as we go.
Quality, security and documentation are part of the daily work, and you own the code, accounts and infrastructure from the start.
FAQ
How we work, answered.
How long does a typical project take?
A typical build runs about 12 weeks across four phases. Smaller projects can be shorter, and larger platforms run in several releases. We confirm the timeline at the end of Phase 1.
Will I know what is happening each week?
Yes. You receive a short written update every day, a weekly status call, a demo every two weeks and a monthly steering review.
What if requirements change mid-project?
Change is normal. Every change request is assessed for scope, cost and timeline, and nothing is added until you approve it. You can also swap work of equal size without changing the budget.
Who owns the code and the infrastructure?
You do. Code lives in your repository from the first commit, cloud accounts are yours, and we hand over documentation and credentials at the end.
How do you handle quality and security?
Code review, automated tests, security scanning and accessibility checks run throughout, not only at the end. Each phase finishes with a gate that you approve.
Can you work with our in-house team?
Yes. We can run the whole project, or embed with your engineers and follow your tools, branching rules and release process.
What happens after launch?
We include a post-launch support window to resolve issues. After that you can run the product yourselves, or keep us on a retainer or dedicated pod.
Ready to begin?
Ready to kick off Phase 01?
Book a discovery call. We will reply within one business day with a plan for the first two weeks.