Skip to content
How we work

Our web development process

Here is what happens during a project, what we need from you and how decisions are agreed. We review progress every two weeks during the build.

Start a project Book a call
  1. 1
    Discover
    1–2 weeks

    We discuss your current website, users and data. You provide access to the relevant systems and name someone who can approve the scope. We agree priorities and give you a written plan and estimate.

  2. 2
    Design
    1–3 weeks

    We create a prototype for your team to try. You gather feedback and approve the main screens and steps before we build them.

  3. 3
    Build
    Releases every two weeks

    You try each release on a test website. We review progress together, record feedback and explain any proposed changes to cost or timing before you approve them.

  4. 4
    Launch & support
    Ongoing

    We test the agreed features, rehearse any data move and agree the launch date with you. Support hours, response targets and ongoing work are set out in a separate support plan.

Pricing

How we estimate and charge

You get a written estimate at the end of discovery.

DiscoveryFixed priceQuoted upfront

Know what to build and what it costs before you commit.

  • Workshops and user interviews
  • Clickable prototype
  • Written estimate and plan
Discuss discovery
Most commonProjectWritten estimateTailored to scope

A defined build with releases every two weeks and a launch date.

  • Senior developer throughout
  • Staging site from week one
  • Documentation and handover
Start a project
SupportMonthlyTailored to your system

Keep your system secure, fast and improving.

  • Named contact
  • Agreed response times
  • Security updates and small changes
Ask about support

Questions about our process

Do we own the code?

Yes. You own the code, the repository and the hosting accounts from day one, and everything is documented so any competent team could pick it up.

What if scope changes?

We talk it through with you first. We explain in writing what the change means for cost and timing, and nothing changes until you agree.

How long does a typical project take?

It depends on the scope. A focused first version can be ready in a matter of weeks, and larger platforms take several months. You get a timeline with your written estimate.

What happens after launch?

We stay with you. Support plans include a named contact, agreed response times, security updates and small improvements, and we plan the handover so your team is never stuck.

How much of our time will the project need?

Usually a short weekly check-in and a review of each release every two weeks. It helps to name one person who can make decisions quickly.

Start a project

Ready to start with discovery?

Send a short brief and you’ll hear back from Khaled within two working days, with a clear next step.

Start a project Book a call