Scope before production
The deliverables, boundaries and responsibilities are written down before project work begins.
Our process
A clear path from first conversation to handover.
Four stages, written approvals and direct access to the senior people doing the work. You always know what is happening, what we need from you and what comes next.
One clear approval route
A named contact and approver keep feedback decisive, consolidated and easy to act on.
Working progress, not surprises
You review the real work at agreed stages instead of seeing everything for the first time at launch.
Step by step
How a project moves
The depth changes with the project, but the checkpoints remain the same.
-
01
Understand and scope
We clarify the problem, audience, required outcome and constraints before recommending a solution.
The first conversation can be a short call or a focused email exchange. We ask what needs to change, who will use the result, what already exists, which systems are involved and whether a deadline is fixed. For custom software or complicated automation, this may lead to a separate discovery phase before a build can be quoted responsibly.
What we do
- Ask the questions that affect scope
- Review the current website, workflow or tools
- Recommend the simplest sensible route
What we need from you
- Explain the business goal and current problem
- Share useful examples, constraints and access details
- Name the person who can make decisions
Stage resultA shared understanding of the problem and enough information to prepare the right next step.
-
02
Proposal and kickoff
The scope, responsibilities, stages and timeline are agreed in writing before production begins.
The proposal explains what will be delivered, what is outside the scope, how feedback and revisions work, the launch assumptions and the fixed project terms. Once it is accepted, onboarding gathers the content, brand files, domain and platform access needed for an efficient start.
What we do
- Write the deliverables and boundaries clearly
- Send one organised onboarding checklist
- Confirm milestones, review points and launch dependencies
What we need from you
- Approve the written scope
- Provide content, brand assets and named-user access
- Confirm one day-to-day contact and one approver
Stage resultA signed scope, complete kickoff checklist and project schedule with no hidden assumptions.
-
03
Design, build and review
Work is delivered in visible stages, with consolidated feedback and approval before the next stage closes.
Website work normally moves from structure to visual design, content placement and development. Apps and automations move through agreed functional milestones. You see the work in Figma, on a staging site or in a safe test environment, and receive plain-language progress updates rather than waiting for a final reveal.
What we do
- Build and test the agreed stage
- Share working progress and known decisions
- Record approvals and flag risks early
What we need from you
- Review against the agreed scope
- Return one consolidated set of feedback
- Approve the stage or identify a specific correction
Stage resultApproved, tested work that progresses without reopening decisions from earlier stages.
-
04
Launch and handover
We run the launch checklist, move the work into production and leave your team with access and documentation.
Before launch, we test the agreed browsers and screen sizes, forms, content, redirects, analytics and integrations. We coordinate domain and DNS changes carefully so existing email is not disturbed. After launch, we verify the live result, hand over the files and accounts, and explain how routine editing or operation works.
What we do
- Complete pre-launch and live-site checks
- Provide documentation, credentials and training
- Resolve covered post-launch defects
What we need from you
- Give final content and launch approval
- Confirm forms, analytics and business details
- Choose self-management or an optional care plan
Stage resultA live, owned and documented result, with a clear route for support after handover.
Approvals and changes
Clear decisions protect the timeline.
A review stage closes when the named approver confirms it. That gives the next stage a stable foundation.
Review against the brief
Check the work against the agreed audience, outcome and deliverables.
Consolidate feedback
Resolve internal opinions first, then send one clear list from the approver.
Approve or correct
Approve the stage or identify the specific items that must change within scope.
Quote new scope first
If a new request changes the agreed work, we price and schedule it before starting.
Process FAQ
Practical questions before we begin
The proposal remains the final contract for your project. These answers explain how our normal workflow operates.
When does the project timeline begin?
The timeline begins when the proposal is accepted and the kickoff checklist is complete. Missing content, access or approvals can pause the schedule because the next stage may depend on them.
How do we give feedback?
One approver sends a consolidated set of comments at each review stage. Feedback should identify the business or user problem to solve, not arrive as separate and conflicting messages from several people.
What if we need something outside the agreed scope?
We explain the effect on the work and provide a separate fixed change quote before proceeding. You can approve it, defer it to a later phase or keep the original scope unchanged.
How do you handle passwords and account access?
We ask to be added as a named user wherever possible. If temporary credentials are necessary, they should be revocable and sent through the agreed secure route rather than ordinary chat.
Will we be able to manage the finished work?
Yes. The handover includes the relevant files, accounts and documentation. Website scopes with content editing include the agreed CMS setup and training; custom systems include operational notes for the delivered features.
What happens after launch?
Covered defects are handled during the post-launch support period stated in the proposal. Ongoing hosting, updates, monitoring and planned changes can be covered by a care plan, or handed to your own team.
Ready when you are
Start a conversation Tell us what needs to change.
We will recommend the simplest sensible next step and put the scope in writing.