Something to See at Every Phase
You don't wait until the end to see anything. Every phase closes with something you can open and click: design files, a staging site, performance numbers.
Three promises, up front
These three run through all six stages below.
Stop After Any Phase
You can stop when a phase ends. Design files, source code and documentation are handed over, so another vendor can pick it up without getting stuck.
Demo Every Two Weeks
A progress demo every two weeks, scheduled in advance. You never have to wait for us to report in, or guess where the project stands.
The Six Phases
These ranges come from what past projects actually took, not from the best case. The scope document sets the binding dates.
01
Consultation and Scoping
We work out what problem you're solving, what assets you already have, and what's realistic within your budget and timeline.
- Deliverables: recommended approach, budget range, draft schedule
- Time: 15–30 minutes per session, usually one or two sessions
- What we need from you: your current site, reference examples, or any files you already have
02
Quote and Scope Document
Everything we discussed goes into writing. Each deliverable is stated as a criterion you can check on the spot, so neither side has to rely on a feeling about what "done" means. This document becomes the basis for acceptance.
- Deliverables: quote with an itemized delivery specification
- Time: 3–5 business days
- What we need from you: sign-off on scope, and one contact who can make decisions
03
Design
Information architecture is settled before any visual work starts. Development begins only after the designs are approved — changes here cost far less than changes during build.
- Deliverables: information architecture, wireframes, visual designs, interaction specs
- Time: 4–8 weeks depending on scale
- What we need from you: copy, brand identity files, and time for each round of feedback
04
Development
A working staging build lands every two weeks. On 3D projects we optimize the models and run performance tests first, confirming it runs well before stacking features on top.
- Deliverables: a working staging build every two weeks
- Time: 4–12 weeks depending on scale
- What we need from you: assets delivered on the agreed dates — the single most common cause of delay
05
Testing and Acceptance
We check the scope document item by item. Functional adjustments, interface refinements and bug fixes during the QC period carry no extra charge.
- Deliverables: test report, performance data
- Time: 1–2 weeks
- What we need from you: a full pass through the site, with all issues sent to us in one list
06
Launch and Maintenance
We deploy to your domain, hand over accounts and documentation, and run a training session.
- Deliverables: production deployment, training session, operations manual
- Time: first-year maintenance after launch is agreed separately
- What we need from you: access to the domain and the hosting or cloud accounts
What's Hard to Change Once Set
- The 3D coordinate system and object naming conventions — every piece of interaction logic afterwards is built on them
- The content throughline and scene order — changing the path through the experience means rebuilding it
- The extension points reserved in each phase — adding anything where none was reserved means touching the structure
None of these are impossible to change; they simply cost far more to change than anything else, which is why we confirm them explicitly at the relevant phase.
The Biggest Variable in the Schedule
How fast assets arrive. We've had whole projects pushed back by late 3D models, scanning schedules, and domain registration on the client side.
That's why phase 02 puts what you need to supply, and by when, into the document — so both sides have something to point to.
Next steps
If you want a sense of cost first, start with the price ranges. If your scope is already clear, a conversation gets there faster.