How a project runs
Five stages, each with something you can see and react to. You hear what changed, what is next and what it costs, without the jargon.
-
Discover
We learn your goals, users and limits, then agree scope and timeline in writing.
- What you do
- Share your goals, examples and any limits on budget or time.
- What you get
- A written scope, timeline and quote.
-
Design
Wireframes and clickable prototypes you can react to before building starts.
- What you do
- Look at the prototypes and tell us what works and what doesn't.
- What you get
- Designs you have approved before any building begins.
-
Build
Short iterations, with a working preview to review along the way.
- What you do
- Try the previews and give feedback while changes are still cheap.
- What you get
- Working software you can see and use as it grows.
-
Launch
Testing, security checks and a planned release with a way back if needed.
- What you do
- Sign off the release once you are happy.
- What you get
- A live product, with documentation for your team.
-
Support
Monitoring, fixes and improvements after go-live, on a plan that suits you.
- What you do
- Tell us what you want improved, and choose how much support you need.
- What you get
- Ongoing care, so the product keeps working and keeps improving.
What a written scope contains
The first stage ends with a short document you can read in one sitting and approve. It covers:
- The goal, and who the product is for
- What is included, and what is deliberately left out
- The stages, with a timeline for each
- The price, and what could change it
- Assumptions, and what we need from you
Get in touch
You can email us at [email protected].