Skip to content
Cinistine

Process

A short, predictable path.

Four stages, each ending in something you can read and approve. No work begins before scope is agreed in writing.

  1. 01

    Discover

    This is a working conversation, not a pitch. We look at the current site and analytics if they exist, ask what happens after an enquiry, and write down what we heard so it can be checked.

    • Conversation with the people who own the outcome
    • Review of the current site, tracking and enquiry handling
    • Written summary of goals and constraints

    You end this stage with: A written summary of the business, the constraints, and what success will be measured against.

  2. 02

    Define

    Ambiguity is expensive later. We agree what is included, what is not, in what order it ships and how it will be judged — so a change later is a decision, not a surprise.

    • Scope and deliverable list
    • Priority order and dependencies
    • Success criteria and measurement plan

    You end this stage with: An agreed scope document: deliverables, exclusions, priority order and how the work will be judged.

  3. 03

    Build

    Work is reviewed in stages rather than revealed at the end. Content, design and implementation are checked against the agreed criteria, including performance, keyboard access and mobile behaviour.

    • Design and build in reviewable increments
    • Quality checks: performance, accessibility, responsive behaviour
    • Staged review and sign-off

    You end this stage with: Staged deliverables you have reviewed, and a build that passes the checks agreed in Define.

  4. 04

    Launch and improve

    Launch includes verification: forms deliver, tracking records, redirects resolve and the site behaves under real conditions. What happens afterwards is a separate, honest conversation.

    • Deployment and post-launch verification
    • Handover documentation and access
    • Optional maintenance or improvement plan

    You end this stage with: A verified deployment, handover documentation, and a short list of what is worth improving next — if anything.

Every project is scoped individually — timelines follow the agreed scope rather than a fixed promise.

One point of contact

You speak with the people doing the work. No account layer between you and the build.

Written updates

Progress, decisions and blockers are recorded so there is a shared reference, not just a call.

Decisions, not drift

When scope or priorities change, it is written down and agreed before the work moves.

Next step

Discovery starts with a conversation.

Send a short note about the business and what you want to change. We will tell you what we would do first, and whether we are the right fit.