Skip to content
NexStaq

Process

Six steps, in order.

From the first conversation to the day the repository moves to your account. This is what happens in each step, and what you have in hand when it ends.

01The steps

What happens, and what you receive.

Nothing is built before you have seen it designed, and nothing is designed before the structure is agreed in writing.

  1. 01

    Discovery

    A conversation about what the business actually needs the site to do: who is arriving, what should happen next, and how you will know it worked. We agree the success measure before anything is designed.

    You receive

    An agreed measure of success, settled before anything is designed.

  2. 02

    Strategy

    Sitemap, page-by-page structure and the technical approach. You see exactly which pages exist and what each one is for, in writing, before design starts.

    You receive

    The sitemap, the page-by-page structure and the technical approach, in writing.

  3. 03

    Design

    High-fidelity layouts for every page, designed mobile-first and checked for contrast and readability. You review and mark up real screens, not a mood board.

    You receive

    High-fidelity layouts for every page, as real screens to review and mark up.

  4. 04

    Engineering

    Custom code in Next.js and TypeScript. Semantic markup, accessible components, and a build with no unused libraries dragged along for the ride.

    You receive

    The site itself, custom-coded in Next.js and TypeScript.

  5. 05

    Optimisation

    Core Web Vitals tuning, structured data, metadata and canonicals, real-device testing, and an accessibility pass before anything goes live.

    You receive

    A site tested on real devices, with structured data, metadata and an accessibility pass complete.

  6. 06

    Launch & handover

    Deployment, DNS, analytics and Search Console. Then the repository moves to your GitHub account and we walk you through it. The site is yours, not rented.

    You receive

    The live site, and the repository in your GitHub account, with a walkthrough.

02Before we start

The clock starts with your content.

Timelines run from the day we have your content and brand assets. That is the step that most often causes delay, so it is the one to prepare first.

What we need from you

  • 01Your logo and brand assets, if you have them
  • 02The text for each page
  • 03Images of your product, premises or team
  • 04Access to your domain

If you do not have some of these, we will tell you what is genuinely required and what can follow later. For an online store, the payment gateway merchant account is applied for by you, since it requires your business documents. We will tell you exactly what to prepare.

Total time, by plan
PlanTimeline
StarterA single page built to convert paid traffic.3–5 days
ProfessionalA complete site for an established business.7–14 days
PremiumE-commerce and larger multi-page systems.21–30 days

Each figure is the total for the whole build, all six steps included.

What each plan includes

03Handover

Then it is yours.

On final payment, ownership of the code and the design transfers to you. This is what changes hands.

  • 01

    The repository

    The complete source code, transferred to your GitHub account. We walk you through it, and any developer can take it forward from there.

  • 02

    The live site

    Deployed, with the DNS configured so that your domain points at it.

  • 03

    Analytics and Search Console

    Google Analytics and Search Console, set up for the site before it goes live.

  • 04

    The performance measurement

    For Professional and Premium builds we commit to a Largest Contentful Paint figure in writing, and show you the measurement at handover.