A project moves well when the next decision is visible. We connect the commercial brief, creative direction and technical work through written milestones and reviewable outputs.

From first brief to client control

1. Clarify the outcome

Describe the business, buyer, current tools and the outcome that matters. We identify whether the work is brand, web, marketing, software or a connected engagement.

2. Confirm scope and dependencies

Agree deliverables, exclusions, roles, content, integrations, costs, acceptance rules and start conditions. Unknowns that affect price are resolved or explicitly scoped.

3. Review the content and design

Approve the hierarchy, identity direction and critical user flows. Feedback is consolidated against the agreed rounds, not spread across conflicting channels.

4. Review working behavior

Test the defined interactions, records, exceptions and permissions on staging. AI assistance, if included, is assessed with its human-review and failure boundaries.

5. Accept the agreed scope

Review the stated checks and report reproducible deviations within the agreed window. New features follow a change request with cost and schedule impact.

6. Receive the handover

Receive the agreed source, design files, access, deployment notes and operating guidance after the corresponding payment. Optional care is a separate explicit choice.

What we need from your team

A decision-maker, a consolidated reviewer, approved business information, content and brand assets where relevant, authorised system access and timely feedback. Sensitive information uses an agreed secure route rather than the public enquiry form.

Scope-specific target windows

Conversion Sprint: 5–7 working days. Growth Website: 10–15 working days. Bounded Portal/System: 15–25 working days. Integrated System: estimate after scope. All windows depend on complete inputs, confirmed access and the booked start, not simply the date of the first message.

A clear launch and support boundary

The accepted scope includes a 30-day reproducible-defect warranty. Hosting and external service failures, new functionality and changes made outside the agreed process are addressed according to the agreement. Optional care has a shared monthly time allowance and separate infrastructure costs.

After the agreed payment, you receive the project-specific code and design deliverables. Disclosed reusable foundations come with a perpetual licence to use, host, modify and maintain them within your system. Third-party and open-source licences remain in force. Hosting, external usage and optional care are listed separately.

What if our requirements change?

We document the change, price and schedule effect before doing the additional work. A clear change process protects the result and the relationship.

Can you start without all content?

Only if the missing content and its effect are explicitly agreed. A target build window begins under the written start conditions.

Can a different provider maintain the result?

The handover and reusable-foundation licence support maintenance by an authorised replacement provider, subject to the third-party licences and the agreement.