Our process

A process built to ship, improve and ship again

Every project we run, whether it's a four-page website or a platform for 17 dealerships, moves through the same cycle. We investigate before we design, design before we build, and keep improving after launch. When a cycle ends, the lessons feed the next one.

Start your project

The cycle behind every project

Two colleagues working side by side with laptops and notebooks.
Illustrative photography · Christina @ wocintechchat.com M / Unsplash
  1. Investigate and discover. We learn how your business works, who the users are, what the competition does and what success looks like. Most expensive mistakes are made by skipping this step.
  2. MVP, design and mock-up. We define the smallest version that delivers real value and design it in Figma, so you can see and approve it before anything is built.
  3. Develop. The main event. We build it properly: clean code in version control, editable content and tested features.
  4. Integrate with production. We connect the work to the systems it depends on, such as CRMs, stock feeds, payment providers and finance platforms, and test it against real data and real failure cases.
  5. Deploy. We put it live on the right hosting, check it again and hand over access and documentation.
  6. Improve and maintain. Updates, backups, monitoring and support, plus improvements driven by what the analytics and your team tell us.
  7. Recycle. What we learn becomes the starting point for the next cycle: the next feature, the next campaign or the next version.

How a website project runs

For websites, the cycle breaks down into ten practical steps:

  1. Call. What the site must achieve and what you already have.
  2. Market research. Competitors, customers and how people search.
  3. Sitemap. The pages and the job of each one.
  4. Figma design. Real page designs on desktop and mobile.
  5. Copywriting. Words and layout designed together.
  6. Image sourcing. Photography and imagery prepared for the web.
  7. Development. The main focus, done properly.
  8. Content implementation. Every page populated and checked.
  9. Feature development. Forms, integrations, stock feeds, bookings and whatever else the site needs to do.
  10. Launch. Live, checked and supported from day one.

A focused business site with a home page, about page, services page and contact page typically takes about a week to build once content and images are ready.

How a software project runs

Software and integration projects follow a more detailed path:

  1. Discovery. We map the process, the users and the systems involved.
  2. Feature list. Every feature is written down and agreed in plain language.
  3. MVP. We separate what the first release needs from what can follow.
  4. Costing. Each feature is costed by unit and expected hours, so you can see where the budget goes and choose what to defer.
  5. Build, integrate and release in stages you can test.

The tools we use

  • Clienthub, our own project, client and billing platform, refined over 13 years, where every request, decision and invoice is tracked.
  • Figma for design and prototypes you can review before development.
  • GitHub for version control, so every change is recorded.
  • Google Analytics 4, Google Tag Manager and Umami for measurement.
  • AWS, DigitalOcean and Vultr, managed with HestiaCP, for hosting, or your own infrastructure.

What keeps a project moving

The biggest delays rarely come from design or development. They come from inputs. You can keep your project moving by:

  • responding quickly to questions and reviews;
  • having content ready: your services, history and the facts we need to write from;
  • settling pricing structures early, if the site shows prices or packages;
  • deciding on images early: your own photography, a shoot or stock.

How we price the work

Most projects are fixed-price once the scope is agreed, so you know the cost before we start. Software is costed feature by feature, which keeps the price transparent and lets you trade features in or out. After launch, hosting, support and content plans continue on agreed terms. For an early view of budget, try our pricing estimators.

Process questions

A few useful answers before you decide.

Do you start without a detailed brief?
Yes. Investigation is the first stage of every project. Bring the problem, what you have today and any deadline, and we’ll help shape the brief.
Will we see the design before it's built?
Yes. Every project includes Figma designs for your review before development starts.
What happens after launch?
We host, update, back up and support the work, with a 24-hour response time, and keep improving it based on real usage. The lessons become the start of the next cycle.

Ready to start?

Tell us what you want to build or improve. We’ll come back quickly with how the process would apply to your project.

Start your project.

Let’s move things forward

Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

Start your project