Skip to main content
Prolink Digital Network

Our process

A structured approach, from first call to launch

Five stages, applied consistently to every project. You always know which one you are in, what is happening, and what you get at the end of it.

How we work

Most projects that go wrong do so for the same two reasons: nobody agreed exactly what was being built, and nobody found out it was going wrong until it was expensive to fix. Our process is built to close both gaps.

We scope in writing before anything is built, design before we develop, and give you access to work in progress rather than a reveal at the end. None of it is complicated — it is just applied consistently, which is the part that tends to be missing.

  1. 01

    Discover

    Understand the business, goals, and challenges.

  2. 02

    Plan

    Create a strategic plan tailored to requirements.

  3. 03

    Design

    Design interfaces users actually enjoy using.

  4. 04

    Develop

    Build scalable, secure, high-performance solutions.

  5. 05

    Deliver

    Test, deploy, and support ongoing growth.

In detail

The five stages

What happens at each stage, and what you can expect to have in your hands when it ends. 5 stages, every project, no variation.

  1. Stage 01

    Discover

    Understand your organization before proposing anything. We want to know how you actually operate, who you serve, and what is genuinely getting in the way — not just what the project brief says.

    What happens

    • A structured conversation about your goals, constraints, and timeline
    • Review of your existing website, systems, and content
    • Identifying who the site or system has to work for, and what they need from it
    • Agreeing what success looks like in terms you would actually use

    What you get

    A written summary of what we heard and what we recommend, so you can confirm we understood the problem before any work starts.

  2. Stage 02

    Plan

    Turn the discovery findings into a concrete scope. This is where the project stops being an idea and becomes a defined set of deliverables, sequence, and cost.

    What happens

    • Defining scope, feature list, and what is deliberately out of scope
    • Mapping site structure or system architecture
    • Setting the delivery sequence and realistic milestones
    • Confirming the quote against the agreed scope

    What you get

    A clear proposal covering scope, milestones, and cost — with the assumptions written down, so there are no surprises later.

  3. Stage 03

    Design

    Design the experience before building it. Changing a layout at this stage costs a conversation; changing it after development costs real time and money.

    What happens

    • Wireframes covering the key screens and user journeys
    • Visual design applied to your brand, or a new identity if branding is in scope
    • Interactive prototypes for anything with non-obvious behaviour
    • Accessibility and mobile behaviour considered as part of design, not retrofitted

    What you get

    Designs you can click through and give feedback on, with revision rounds agreed upfront rather than open-ended.

  4. Stage 04

    Develop

    Build the approved design properly — structured so it performs well, holds up under real use, and can be maintained by someone other than the person who wrote it.

    What happens

    • Front-end and back-end development against the agreed scope
    • Integrations with the systems and services you already use
    • Content management set up so your team can make routine changes
    • Code review, security checks, and testing across devices and browsers

    What you get

    Access to a staging environment where you can see real progress and raise issues while they are still cheap to fix.

  5. Stage 05

    Deliver

    Get it live safely, make sure your team can run it, and stay available afterwards. Launch is a milestone in the project, not the end of it.

    What happens

    • Final testing, performance checks, and accessibility review
    • Deployment, domain and SSL configuration, analytics setup
    • A walkthrough with your team, plus documentation for routine tasks
    • Ongoing maintenance and support, if you want it

    What you get

    A live, tested product, a team that knows how to use it, and a direct line to us if something needs attention.

Working together

How you stay informed

No client portal or ticketing system — we do not have one, so we are not going to claim one. What we do have is a direct line and a predictable rhythm.

  • A direct line, not a queue

    You deal with the people doing the work. There is no account manager relaying messages between you and the team.

  • Scheduled check-ins

    We agree a review rhythm at the start of the project — usually a short call at each milestone — so progress is visible without you having to chase it.

  • Written decisions

    Scope changes, approvals, and decisions get confirmed in writing. It protects both sides and keeps the project honest about what was agreed.

  • Work you can see in progress

    You get access to a staging environment during development rather than waiting for a reveal at the end.

Questions

Common questions about our process

Five stages: Discover, Plan, Design, Develop, Deliver. We understand your requirements, agree a written scope and cost, design before building, develop against the approved design, then test, launch, and support it. The process page sets out what happens at each stage.

It depends on scope, and we give you a realistic timeline in the proposal rather than a number before we understand the work. In our experience approval cycles, not development, are usually what stretches a schedule.

Most heavily during discovery and design review. Once development starts your involvement drops to milestone check-ins and feedback on the staging site. We agree the rhythm upfront so it is predictable.

Small adjustments within scope are part of the work. Anything that changes scope gets a written variation setting out the impact on cost and timeline, approved before we do it.

Yes. You get access to a staging environment during development, so issues surface while they are still cheap to fix rather than at handover.

Ready to start at stage one?

Discovery costs you nothing but a conversation. Book a consultation and we will work out together whether there is a project worth doing.

Request a QuoteBook Consultation