Service 01 of 10Technology & Intelligence

Websites, shops and apps that stay fast on your customers’ phones.

Websites, online shops and apps that load fast, are easy to use and stay secure. We build for new and growing businesses and enterprises. We check speed on every change, before and after launch.

Illustration: the same “Your platform” product page on a desktop, a tablet and a phone. Each is laid out for its screen. Speed from real visits is good on all three. Desktop: main content in 1.2 seconds, taps answered in 60 milliseconds, layout shift 0.01. Tablet: 1.7 seconds, 110 milliseconds, 0.02. Mid-range Android phone on 4G: 1.9 seconds, 140 milliseconds, 0.04. Values are illustrative.

Typical first launch
8–16 weeks to first launch
Works on
Web · iPhone · Android
Built to
Google’s speed targets

01 · After launchPhone load time · 3 in 4 visits · first 90 days

Speed after launch depends on checking every change.

A site can score 98/100 on a fast laptop. Then tracking tags, videos and chat tools slow it down. We judge it on real visits, daily.

RUM · Your platform · /product/* · mobile Illustrative

p75 LCPMain content load time, seconds, per day

Line chart, illustrative, of phone load time for 3 in 4 visits. In the 90 days after launch, an unmanaged site rises from 2.2 to 5.1 seconds. It steps up at each event below and ends in the poor band. A speed-checked site stays between 2.1 and 2.5 seconds, in the good band.

Unmanaged5.1 sPoor

Speed-checked2.1 sGood

  1. 1Day 12

    Marketing tags added

    Unmanaged +0.5 s

    Loaded after consent · +0.1 s

  2. 2Day 34

    Big autoplay video

    Unmanaged +0.9 s

    Blocked by the budget · still image shown

  3. 3Day 58

    A/B test script in the browser

    Unmanaged +0.5 s

    Run on the server · no browser script

  4. 4Day 77

    Chat widget on every page

    Unmanaged +0.5 s

    Loads when first used

A woman outdoors among trees, reading something on her phone
Phone in handMid-range Android · 4G, 2 bars
A man walking a dog along a wet cobbled street while checking his phone
On the moveOne hand, rain, the network switching

Real visits

Judged on 3 in 4 visits

Google’s speed targets (Core Web Vitals) pass when 3 in 4 visits are good, over 28 days of Chrome data. We also track each page type, device and release.

Response to taps

Google now times every tap

On 12 March 2024, Google began timing every tap and click in a visit (INP). Heavy code now shows up. Good is 200 ms or less.

Speed budget

Slow changes are blocked before release

Automatic speed tests (Lighthouse CI) run on every proposed change. A change over budget cannot go in until it is shrunk, delayed or removed. Alerts watch live speed after each release.

02 · What we make6 kinds of build · one set of checks

6 things we build, each measured after launch.

Each starts with the same base: a shared kit of buttons and styles, speed budgets, accessibility checks and live monitoring.

  • 01

    Company & marketing websites

    Fast sites with a website editor (CMS) your team can use, with previews before you publish. They stay fast as you add pages.

    Next.js · Astro · website editor
  • 02

    Web apps & portals

    Customer portals, dashboards and subscription software. Each user sees only their own data, and it works on a weak signal.

    React · Vue · TypeScript
  • 03

    iPhone and Android apps

    Separate iPhone and Android apps, or one shared app. We choose by device features, offline use and team skills.

    Flutter · React Native · Swift · Kotlin
  • 04

    Online shops

    Shopify or custom shops, with search, product pages and checkout that stay fast on cheap phones.

    Shopify · custom · payments
  • 05

    Web apps that work offline

    Web apps that install like an app and save work offline, so field teams keep working.

    Service workers · IndexedDB
  • 06

    Shared design kits

    One kit of buttons, screens and styles for web and mobile, tested for accessibility on every change.

    Storybook · styles · Figma

03 · Speed demoTry it · illustrative model

6 speed fixes to try on the device you choose.

Pick a device and a connection. Then switch on the fixes we use in every build. Watch the page load, its scores against Google’s targets and what each fix saves.

field-test · Your platform · /shop/stoneware Your settings Illustrative model

Device type

Network

Speed fixes6 of 6 on

Filmstrip · one frame every 0.6 s

LCPLargest Contentful Paint

2.1 sGood

INPInteraction to Next Paint

160 msGood

CLSCumulative Layout Shift

0.03Good

Page weight0.93 MB

  • Images 430 KB
  • JavaScript 250 KB
  • Outside tools 0 KB
  • Fonts 70 KB
  • CSS 120 KB
  • HTML 60 KB

Server wait (TTFB)590 ms

First Contentful Paint1.2 s

Est. gCO2e per view0.20 g

Google speed check · real-visit spread

Passedall three at p75 must be good

  • LCP 86%12%2%
  • INP 85%14%1%
  • CLS 99%1%0%

What changednewest first

  1. Delayed outside tools onLCP 2.2 → 2.1 s · INP 240 → 160 ms · CLS 0.08 → 0.03 · 1.23 → 0.93 MB
  2. Nearby copies (CDN) onLCP 2.7 → 2.2 s
  3. Less code sent to the phone onLCP 3.9 → 2.7 s · INP 400 → 240 ms · 2.08 → 1.23 MB
  4. Pages built on the server onLCP 4.9 → 3.9 s · INP 420 → 400 ms · CLS 0.09 → 0.08
  5. Trimmed fonts, instant text onLCP 5.2 → 4.9 s · CLS 0.14 → 0.09 · 2.33 → 2.08 MB
  6. Smaller images for each screen onLCP 5.8 → 5.2 s · CLS 0.27 → 0.14 · 4.10 → 2.33 MB
  7. Start · Low-end Android · Slow 4GLCP 5.8 s · INP 420 ms · CLS 0.27 · 4.10 MB

An illustrative model, not a measurement of any site. Limits are Google’s targets (Core Web Vitals) for 3 in 4 visits. Good is LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1. Poor is above 4 s, 500 ms and 0.25. A page passes when all 3 are good. We assume loads spread log-normally around each value. Emissions use the Sustainable Web Design method for a first, uncached view. It assumes 0.494 kWh per gigabyte and a global-average 442 gCO2e per kilowatt-hour. That is about 218 gCO2e per gigabyte (1 GB = 1,000,000 KB). Section 08 uses the same 2 numbers.

04 · Our toolsOne page load · phone · 4G · time limit per step

The tools we use at each step of loading a page.

Each tool does one step of loading a page, within a time limit. Pick a step to see why we chose it. The timeline below follows one page from tap to screen.

Diagram, illustrative: the path of one page request. It goes from the device to a nearby server, the main server, links to other systems (APIs) and the database. Each step reports to monitoring. Limits in milliseconds: device 150, nearby server 30, main server 180 and APIs 120 for 19 in 20 requests. The database gets 40 per lookup and monitoring 5.

01≤ 150 ms to be usable

Device · Load, show, respond

We send the least code that does the job. Astro or Next.js, by how much a page must do. Flutter or React Native when one app serves both stores. Swift and Kotlin for apps that lean on the camera or sensors.

How we keep to the limitCode-size limit per page · code only where people tap · tap speed checked on live visits

Tools we use at this step

  • React
  • Vue.js
  • Flutter
  • React Native
  • Swift
  • Kotlin
  • TypeScript
  • Tailwind CSS

02≤ 30 ms nearby

Nearby server · Copy served near the user

Copies of pages and files sit close to your users, so most visits never reach your main server. Each release refreshes only what changed. We use Cloudflare or Vercel, or Fastly or Akamai if you already pay for one.

How we keep to the limitShare of visits served nearby · old copy shown while refreshing · new name per file version

Tools we use at this step

  • Cloudflare
  • Vercel
  • Fastly
  • Akamai

03≤ 180 ms to start sending

Server · Page built and sent in parts

The page arrives ready to show. Its frame is sent before the data, so fonts and the main image load while the product details are fetched. We use Next.js for full apps and Astro for simple content sites.

How we keep to the limitBuild time per page type, 19 in 20 · sent in parts by default · no call chains in the browser

Tools we use at this step

  • Next.js
  • Astro
  • Node.js
  • TypeScript
  • Tailwind CSS

04≤ 120 ms for 19 in 20

APIs · Checked, cached, in parallel

APIs link the screens to every system behind them, in one agreed format (GraphQL or OpenAPI). Calls are combined and briefly saved, so a busy product page needs one round trip. Your site editor or Shopify uses the same links.

How we keep to the limitFormat tested per change · repeat queries blocked · calls combined

Tools we use at this step

  • GraphQL
  • OpenAPI Initiative
  • Contentful
  • Sanity
  • Strapi
  • Shopify
  • Algolia

05≤ 40 ms a lookup, 19 in 20

Data · Fast lookups, saved answers

PostgreSQL, set up for the lookups your app makes, with Redis for log-ins, baskets and popular data. Every lookup has a time limit and an alert. A table that grows tenfold is caught before customers notice.

How we keep to the limitSlow lookups reviewed every cycle · data changes tested on a copy of live data

Tools we use at this step

  • PostgreSQL
  • Redis
  • Supabase
  • Firebase

06≤ 5 ms extra

Monitoring · Traces, errors, speed

OpenTelemetry tags every step with one ID, so we can follow a slow page from tap to database. Sentry links each error to the release that caused it. Datadog records speed on live visits. Sampling keeps the cost under 5 milliseconds.

How we keep to the limitOne ID across all steps · release named on every error · alerts per page type for 3 in 4 visits

Tools we use at this step

  • OpenTelemetry
  • Sentry
  • Datadog
  • Grafana

One request, tracedfirst visit · mid-range Android · 4G · trace-id 7f3a…c21e

First byte 120 msHTML complete 212 msLCP 1.9 sIllustrative

Timeline of one page request, illustrative. Connecting takes the first 38 milliseconds. The nearby server has no copy yet at 52. The page frame is sent by 120 milliseconds. Three API calls run side by side until 165, and the database answers by 96. The page is complete at 212 milliseconds. The main content shows at 1.9 seconds. The timeline is saved in the background.

Before release

Built, tested and speed-checked automatically, so only code that passes every check goes live.

  • GitHub Actions
  • Playwright
  • Storybook
  • Lighthouse
  • GitHub

05 · Everyday use4 places · 4 needs

4 places people use your product, and what each one needs.

Your users are rarely at a desk on fast Wi-Fi. We design and test for 4 everyday places, and set what each needs before we write code.

Two workers walking a warehouse aisle, one in a hi-vis vest holding a handheld scanner

Place 01 · Warehouse floor

Gloves, glare and signal that drops behind the shelves.

What it needs

Works offline, with big buttons

  • Work saved on the device, then synced in order, with no duplicates
  • Buttons of 44 px or more, above the WCAG 2.2 minimum of 24 × 24 px (2.5.8)
  • Contrast 7:1, readable under harsh lights
  • Barcode scan by camera, or type the code by hand

Web appOffline modeSyncs later

An operations analyst working across two wide monitors

Place 03 · Operations desk

2 monitors, dense tables and a keyboard that rarely leaves the hand.

What it needs

Big tables and keyboard shortcuts

  • Tables that stay smooth at 100,000 rows
  • Compact view, fixed headers and columns you can reorder
  • Shortcuts for search, moving around and bulk actions, with a visible list
  • Exports that match the on-screen filter

Smooth scrollingShortcutsBulk actions

A commuter reading her phone on an underground train

Place 02 · Commute

One hand, one thumb and a network that comes and goes between stations.

What it needs

One-thumb use and taps answered in 200 ms

  • Main buttons in the lower two-thirds of the screen, in reach of one thumb
  • Taps answered in 200 ms or less for 3 in 4 live visits (INP)
  • Screen updates at once and retries if the signal drops
  • Nothing jumps when the signal returns

INP ≤ 200 msInstant updatesAuto retry

An older man at a bus stop reading his phone with the text enlarged

Place 04 · Bus stop

Bifocals, cold hands and the text zoomed to 200%.

What it needs

Text at 200% with nothing cut off

  • Content fits a 320 px screen with no sideways scrolling (WCAG 2.2 1.4.10)
  • Text grows to 200% with nothing lost (1.4.4), and custom spacing still works (1.4.12)
  • Visible keyboard focus, and no need for hover or a steady hand
  • Plain language, one action per screen

WCAG 2.2 AAFits 320 pxZoom 200%

06 · Quality checks7 checks · set as numbers · run on every change

7 checks every change must pass before it goes live.

Each check is a written limit kept with your code: kilobytes, seconds or number of failures. Each change is tested with the latest code. Pick a change to see how it did.

Illustrative changes

Illustration of a queue holding three proposed changes against seven written limits. Change 412, gallery zoom and AVIF hero images, is first in line and meets every limit. Change 414, filters on the listing page, sends 318 kilobytes of JavaScript against a 250 kilobyte limit. The queue stops there. Change 415, a library update, passes every check but waits third. The other six limits: zero accessibility failures, zero unreviewed screen changes and zero failing or flaky tests of 1,380. Also zero critical or high security warnings and zero broken redirects of 1,240 rules. The app must start in 1.8 seconds for 3 in 4 launches on a Pixel 6a. AI suggests loading the filter panel only when opened. That brings 414 down to 226 kilobytes and frees the queue. A person commits it.

Change queue · your-platform / web held at #414

The queue tests each change on top of the ones ahead of it. So two changes that each pass alone cannot break the live code together.

#412Engineer · 3 commits · +412 −96

feat(product): gallery zoom and AVIF hero images

A code owner approved it at 14:02. The queue adds the latest code and reruns every check, so it goes in exactly as tested.

  1. Speed budget Google Lighthouse runs on each preview, and code size is checked at build time. JavaScript sent to this page 248 KBof 250 KB allowed Within budget
  2. Accessibility axe-core tests every screen, plus manual checks against WCAG 2.2 AA, the accessibility standard. Failures, automatic and manual 0of 0 allowed Within budget
  3. Visual changes Playwright compares screenshots of every part on 4 devices. Unchecked screen changes, of 312 parts 0of 0 allowed Within budget
  4. Code and journey tests Vitest for code pieces, Playwright for customer journeys. Failing or unreliable, of 1,380 tests 0of 0 allowed Within budget
  5. Security OWASP ASVS Level 2 checks, plus scans for risky libraries and leaked keys. Critical or high warnings 0of 0 allowed Within budget
  6. Mobile Tests on real phones, iOS 17–18 and Android 12–15, timed on a mid-range model. App start time, 3 in 4 launches, Pixel 6a 1.4 sof 1.8 s allowed Within budget
  7. Search listings Redirects, titles and search labels checked against the live site. Broken redirects, of 1,240 rules 0of 0 allowed Within budget

Cleared · waiting its turn

14:02 · approved by a code owner

A code owner reviews every change, including those AI opens. The queue can stop a change. Only a person can approve it.

Next to go in

#414Engineer · 7 commits · +1,204 −212

feat(search): faceted filters on the listing page

The listing page sends 318 KB of code against a 250 KB limit. Nothing behind it goes in until it meets the limit or is dropped.

  1. Speed budget Google Lighthouse runs on each preview, and code size is checked at build time. JavaScript sent to this page 318 KBof 250 KB allowed Over by 68 KB
  2. Accessibility axe-core tests every screen, plus manual checks against WCAG 2.2 AA, the accessibility standard. Failures, automatic and manual 0of 0 allowed Within budget
  3. Visual changes Playwright compares screenshots of every part on 4 devices. Unchecked screen changes, of 312 parts 0of 0 allowed Within budget
  4. Code and journey tests Vitest for code pieces, Playwright for customer journeys. Failing or unreliable, of 1,380 tests 0of 0 allowed Within budget
  5. Security OWASP ASVS Level 2 checks, plus scans for risky libraries and leaked keys. Critical or high warnings 0of 0 allowed Within budget
  6. Mobile Tests on real phones, iOS 17–18 and Android 12–15, timed on a mid-range model. App start time, 3 in 4 launches, Pixel 6a 1.5 sof 1.8 s allowed Within budget
  7. Search listings Redirects, titles and search labels checked against the live site. Broken redirects, of 1,240 rules 0of 0 allowed Within budget

AI has drafted a fix

9c8d7e6 · fix(search): lazy-load the facet panel, −92 KB

Suggested by AI · an engineer commits it. It is held until a code owner approves.

#415Opened by AI · 1 commit · +18 −18

chore(deps): weekly dependency bump

Every check passes, but it waits its turn. It goes in once #414 clears or an engineer takes #414 out.

  1. Speed budget Google Lighthouse runs on each preview, and code size is checked at build time. JavaScript sent to this page 244 KBof 250 KB allowed Within budget
  2. Accessibility axe-core tests every screen, plus manual checks against WCAG 2.2 AA, the accessibility standard. Failures, automatic and manual 0of 0 allowed Within budget
  3. Visual changes Playwright compares screenshots of every part on 4 devices. Unchecked screen changes, of 312 parts 0of 0 allowed Within budget
  4. Code and journey tests Vitest for code pieces, Playwright for customer journeys. Failing or unreliable, of 1,380 tests 0of 0 allowed Within budget
  5. Security OWASP ASVS Level 2 checks, plus scans for risky libraries and leaked keys. Critical or high warnings 0of 0 allowed Within budget
  6. Mobile Tests on real phones, iOS 17–18 and Android 12–15, timed on a mid-range model. App start time, 3 in 4 launches, Pixel 6a 1.4 sof 1.8 s allowed Within budget
  7. Search listings Redirects, titles and search labels checked against the live site. Broken redirects, of 1,240 rules 0of 0 allowed Within budget

Passed, and still waiting

#415 · opened by AI, reviewed by an engineer

A library update that passes alone is retested with the changes ahead of it. 2 passing changes cannot break the live code together.

Waits behind #414

What WCAG 2.2 adds to the accessibility check

The 6 new A and AA rules in WCAG 2.2, the level of each and what each means for you
RuleLevelWhat it means in practice
2.4.11Focus Not Obscured (Minimum)AAFixed headers and cookie bars never hide the selected item.
2.5.7Dragging MovementsAAEvery drag has a click or keyboard alternative.
2.5.8Target Size (Minimum)AAButtons at least 24 × 24 px. We build to 44 px on touch.
3.2.6Consistent HelpAHelp and contact sit in the same place on every screen.
3.3.7Redundant EntryANothing already entered is asked for twice in a flow.
3.3.8Accessible Authentication (Minimum)AASign-in never relies on memory or copying.

Where the limits come from

  • WCAG 2.2 AAWeb Content Accessibility Guidelines
  • Core Web VitalsLoading, interactivity and visual stability
  • OWASP ASVSApplication Security Verification Standard
  • OWASP Top 10Web application security risks
  • DORA metricsSoftware delivery performance

Each limit comes from a published standard. Size and time limits follow Google’s targets for 3 in 4 visits. Accessibility follows WCAG 2.2 AA. Security follows OWASP ASVS Level 2 and the OWASP Top 10, the standard list of website security risks. Release measures follow Google’s DORA research. Mobile builds also follow OWASP MASVS, and we report quality against ISO/IEC 25010. The badges are our own marks, not certificates.

07 · How we use AIAI drafts · engineers approve · we watch each release

AI drafts code and tests; a named engineer approves every change.

AI drafts screen parts from your design kit, tests and a note on each visual change. Engineers edit and review all of it. After release, data from your real visitors decides whether a change stays.

Illustration of one change moving through the release lane in a day. At 09:10 a designer approves the design. At 09:38 AI drafts the screen part from the design kit; at 10:05 an engineer edits it. At 10:40 AI drafts fourteen Playwright tests, which the engineer reviews. At 11:12 a preview is live and every check passes. At 14:30 a person checks the AI summary of the visual changes. At 15:02 a person approves it; AI cannot approve. On Thursday the release goes out while we watch real visits. It is undone automatically if tap response for 3 in 4 visits slows by more than 20 percent. Times and values are illustrative.

#418 · feat(checkout): saved addresses

Thu 10:0010% → 50% → 100% of visitors, watched live

Approved design → preview link
2 h 02 m
Preview → approved by a person
3 h 50 m
How often we release
Weekly or faster
Undo a bad release
Under 1 minute
A09:38 → 10:05

Design to screen part

Drafted by AI

Tokens the draft used, and what they resolve to

  • space.416 pxCard padding, both axes
  • radius.md10 pxCorner radius on the card
  • text.label13 px / 1.3The address name line
  • tone.neutralink-2 on paper-2The default badge

AddressCard.tsx · 3 files drafted+1 −5 by an engineerA raw value fails review

AI drafts an AddressCard component from the design kit’s named values in the Figma frame. It uses space.4 for padding, radius.md for the corner, text.label for the name and the neutral badge tone. An engineer then edits the empty view to add a hint and an action. A raw number in place of a named value fails review.

B10:40

Journey tests written by AI

Drafted by AI

saved-address.spec.ts · drafted by AI2 assertions tightened by an engineerNo test counts until a person has read it

AI drafts fourteen Playwright tests. They cover keyboard use, a 320 pixel screen, screen-reader announcements, visible focus and target size. Others check 200 percent zoom, reduced motion, form errors and a dropped connection. Each test runs on four devices: Chromium and WebKit on desktop, Pixel 7 on Android and iPhone 15 on iOS. That makes fifty-six passing runs. An engineer reviews each test before it counts.

C11:12 → 14:30

Visual changes, summarised

Person approves

AI summary · 3 visual changes · 0 unexpected

  1. 1Saved addresses listed above the formexpected · in the ticket
  2. 2Continue button 40 → 48 px tallexpected · design kit v4
  3. 3Delivery estimate moved under the totalflagged for a person · approved

Engineer checked it against the code · 14:30

DThu 10:00

Released, then watched

Automatic watch

Tap response · mobile · release 43Illustrative

  1. +0 mRelease 43 to 10% of traffic
  2. +22 mTap response 205 ms · guard 180 ms (+20% on 150 ms)
  3. +22 mUndone: back to release 42 · automatic · 48 s
  4. +30 mTap response back to 150 ms · incident note drafted by AI
  5. +31 mEngineer owns the fix · next release waits for a person

Tap guard · 10% of visitors firstAutomatic undo in 48 sIncident note drafted by AI, owned by a person

Chart of tap response for 3 in 4 visits in the hour after release 43 reaches 10 percent of traffic. It holds near the 150 millisecond baseline, then rises to 205 milliseconds at 22 minutes, past the 180 millisecond guard. The release is undone automatically, back to 42, in 48 seconds. It is back at 150 milliseconds by 30 minutes; an engineer owns the fix.

  • AI never approves code

    Every change needs a code owner’s approval. AI accounts can propose changes and comment, but cannot approve or add them.

  • Every AI step is logged

    Every prompt, tool use and edit stays attached to the change, so the reviewer sees what the AI saw.

  • No training on your code

    We use business AI tools set to keep no data. Your code never goes into a tool that learns from it.

  • Automatic undo, human fixes

    A slow or failing release is undone in under a minute. A person decides what goes out next, and when.

Release tools · technologies we work with

  • Figma
  • GitHub Copilot
  • Cursor
  • GitHub
  • GitHub Actions
  • Playwright
  • Storybook
  • Vercel
  • Sentry
  • Datadog

08 · Lighter pagesOne product page · 6 limits · estimated

Page-weight limits that cut load time, cost and carbon.

A heavy page is slower, costs more to host and uses more energy. So we set a weight limit that every build must meet. Pick a limit to see what it takes and what it blocks.

Illustrative model

A model of one product page under six weight limits. With no limit it weighs 4.10 megabytes. Images are 2,180 kilobytes, JavaScript 1,120, outside scripts 480, fonts 260, CSS 92 and the page itself 66. Under a 2.00 megabyte limit it weighs 2.00. Under 1.50 it weighs 1.49. Under 1.00 it weighs 0.90 with no feature lost; this is the limit we usually set. Under 0.75 it weighs 0.64, and the gallery loads only when opened. Under 0.50 it weighs 0.42, with no browser framework and no outside scripts. Over 100,000 views, the 4.10 megabyte page sends 420 gigabytes and emits an estimated 92 kilograms of carbon emissions. At 0.90 megabytes it sends 92 gigabytes and emits 20 kilograms. That is about 0.92 grams per view against 0.20. The figures are modelled with the Sustainable Web Design method, not measured. The table below lists every limit.

Limit 1.00 MB0.90 MB−78% on no limit

The limit we usually set. Every feature stays and the page is 78% lighter than at the start.The build blocks: Any image over 200 KB. Any page’s code over 250 KB.

Weight of each part of the page with no limit and at the chosen limit, and how we trim it
Page partNo limit1.00 MBWhat it takes
Images 2,180 KB 402 KB AVIF sized for each screen; the top image first, the rest on scroll
JavaScript 1,120 KB 214 KB Built on the server; only the cart and gallery run code
Outside scripts 480 KB 148 KB Analytics and consent only, on your server
Fonts 260 KB 62 KB One trimmed font file; text shows before the font loads
CSS 92 KB 54 KB First-screen styles sent first; the rest later
Page itself 66 KB 42 KB Streamed, with no data holding up the page
Total4.10 MB0.90 MBEvery view, for as long as the page lives
Data sent per 100k views
420 GB92 GB
Estimated CO₂e per 100k views
92 kg20 kg
Estimated CO₂e per view
0.92 g0.20 g
Page weight
4.10 MB0.90 MB

How the estimate is made

Data sent is page weight times views, in decimal gigabytes. Emissions follow the Sustainable Web Design method. It has 2 inputs: 0.494 kWh per gigabyte transferred and 442 gCO₂e per kilowatt-hour (a global-average grid). That is about 218 gCO₂e per gigabyte. The speed demo in section 03 uses the same inputs. The result is an estimate. A cached page from a low-carbon region emits far less. A first load on an old device emits more. We show the model and its inputs with every estimate. And we track what we control: bytes.

SCI = ((E × I) + M) per REnergy times grid carbon intensity, plus the carbon of making hardware, per unit of work. The Green Software Foundation’s Software Carbon Intensity standard, ISO/IEC 21031:2024.

  • SCI · ISO/IEC 21031:2024Software Carbon IntensityThe carbon software causes per user or other unit, counting energy use and the making of hardware.
  • Core Web VitalsLoading, interactivity and visual stabilityFor 3 in 4 visits, pages show in 2.5 s, respond in 0.2 s and do not jump around.

We follow these standards, and the W3C Web Sustainability Guidelines shape the practices below.

All 6 limits · one product page

  1. No limit 4.10 MB 0.92 g per view Nothing. Any working code goes live.
  2. 2.00 MB 2.00 MB 0.45 g per view A 1.2 MB banner image. One huge code file.
  3. 1.50 MB 1.49 MB 0.33 g per view A second font family. A tag with no named owner.
  4. 1.00 MB 0.90 MB 0.20 g per view Any image over 200 KB. Any page’s code over 250 KB.
  5. 0.75 MB 0.64 MB 0.14 g per view A JavaScript slideshow. Any outside script in the browser.
  6. 0.50 MB 0.42 MB 0.09 g per view A browser router. A web font for body text.
  • Smallest images that look right

    AVIF or WebP sized for each screen, with fixed sizes so nothing jumps. Lower images load on scroll. Images are usually over half the weight.

  • Only the JavaScript needed

    Server-built pages and code split by page, run only where needed. The build fails if code grows past its limit.

  • One font file, or none

    Fonts on your server, trimmed to the letters you use. Text shows before the font loads. Device fonts where the brand allows.

  • Regular checks on outside tools

    Every tag has an owner and a review date. Tags with no clear purpose are removed. The rest load after the visitor taps or scrolls.

  • Copies kept close to visitors

    Files are kept for a long time, refreshed in the background and served from a server near your visitors.

  • Less work for the device

    No autoplay video on phones, dark mode where visitors choose it and less motion when they ask. Less work on the device means less battery used.

The build enforces the limit. Image, script and font limits are kept with your code. The speed budget check in section 06 tests them on every change. A change that pushes the page over its limit fails. So a year of small additions cannot add the weight back.

09 · How it works5 stages · each ends with a file you keep

5 stages, from first research to day 90.

Stages 1 to 4 get your product live. Stage 5 uses 90 days of real visits to fix what has slowed. Each stage ends with a file you can open and a person’s sign-off.

Typical timings · sample files

01Discover · Wk 01–02

Who uses your product, on which devices and networks?

We study your visitor data, support tickets and the devices and networks your customers use. That sets the speed budget, the oldest browser we support and the first release.

Our team
A senior engineer, a product designer and a project lead, part-time for 2 weeks
Your team
A product owner and whoever holds the analytics

Before we move on

  • You agree the budget and it is saved with your code
  • The device and network mix comes from your analytics
  • The first release fits inside 4 weeks
A researcher writing notes beside a laptop mirroring the phone screen a participant is using

The file you receive

performance-budget.jsonJSON · committed to the repository

What you get

  • Product plan and first-release scope
  • System sketch, with trade-offs written down
  • Speed budget set for your slowest quarter of visits
  • Release plan and measurement plan

Signed off byYour product owner and our project lead

02Design · Wk 02–05

Do the screens work for your users before we build?

We design with your content and the design kit, then test a clickable draft with 5 to 8 users. Contrast, button size and keyboard order are designed in.

Our team
A product designer, a content designer and a front-end engineer
Your team
A product owner and 5 to 8 of your users for testing

Before we move on

  • Every journey is tested on a real device
  • Contrast, button size, keyboard order and 320 px layout are noted before build
  • Each decision records its cost as well as its benefit

The file you receive

adr-012-native-or-web.mdMarkdown · architecture decision record

What you get

  • Clickable draft on real devices
  • Shared styles for web and mobile
  • User-test findings and the changes made
  • Accessibility notes on every screen

Signed off byYour product owner, our design lead and our senior engineer

03Build · Wk 04–11

Does every 2-week cycle end with something your team can use?

AI drafts code and tests; engineers review and approve. Each change gets its own preview link, and each cycle ends with a demo.

Our team
2 to 4 engineers, a part-time designer and a project lead
Your team
A product owner at every demo, and one technical reviewer

Before we move on

  • Each change has a preview link and passes section 06’s 7 checks
  • Your team has used each new piece
  • Monitoring goes live with each feature

The file you receive

sprint-06-demo.mdMarkdown · sent the day before the demo

What you get

  • Working features you can use, every cycle
  • Automatic tests for parts and full journeys
  • A preview link for every change
  • Monitoring and dashboards added with each feature

Signed off byYour product owner, at the demo

04Launch · Wk 11–12

How do we launch in stages, and undo it fast?

We release to a share of visitors first and watch speed and errors. If either crosses its limit, the release is undone automatically.

Our team
The build team, plus a reliability engineer for the rollout
Your team
A product owner, marketing and your domain owner

Before we move on

  • Redirects and search listings checked against the live site
  • App store submissions accepted, with current listings and screenshots
  • Dashboards live and alerting a named person before visitors move

The file you receive

release-1.0-plan.mdMarkdown · agreed before traffic moves

What you get

  • Live release, rolled out in stages
  • App store submissions and listings
  • Redirects and search listings report
  • Dashboards: speed, errors, time online

Signed off byYour product owner and our project lead

05Improve · Wk 12+

What do 90 days of real visits show?

At day 90, real visits show which pages slowed and where people stall. We review it with you, fix the 3 worst slowdowns and reset the budgets.

Our team
A performance engineer and the project lead, 2 to 3 days
Your team
A product owner, plus marketing if the tags changed

Before we move on

  • Data read for 3 in 4 real visits, by page type and device
  • The 3 worst slowdowns are fixed and released
  • Budgets are reset for the next quarter and written down

The file you receive

day-90-field-review.mdMarkdown · reviewed with you, then acted on

What you get

  • Real-visit data for 3 in 4 visits, by page type and device
  • The 3 worst slowdowns fixed and released
  • Budgets reset for the next quarter
  • Next work, ranked by measured impact

Signed off byYour product owner and our project lead, at the review

01 / 05 · Discover

10 · What you get6 folders · your code · your accounts

Working code and notes your team can run without us.

Your engineers can copy it on day one. It holds the code, tests, speed budgets, how-to guides and the reasons behind each technical choice.

your-platform main Open a folder to see what is in it
    • app/ Pages and how the server builds them TypeScript
    • components/ Screen parts built from the shared design kit TypeScript
    • tests/e2e/ Full journey tests on 4 kinds of device Playwright
    • lighthouserc.json Speed budgets checked on every change JSON
    • README.md Set-up steps, house rules and who to call Markdown
    • ios/ · android/ Signed app builds, with the keys in your vault IPA · AAB
    • fastlane/ Store uploads by script, from any computer Ruby
    • store/ Listings, screenshots, privacy labels and release notes Markdown · PNG
    • crash/ Crash reports set up to show the cause Config
    • tokens.json Colours, fonts and spacing for web, iOS and Android JSON
    • components/ Every screen part, with notes on how to use it TypeScript · Storybook
    • a11y/ Automatic accessibility checks and the WCAG 2.2 AA checklist Playwright · axe
    • CHANGELOG.md Versioned releases, so you choose when to upgrade Markdown
    • schema/ Content types, input rules and editor previews TypeScript
    • migrations/ Content moves you can undo, tested on a copy first TypeScript
    • roles.md Who can edit, review and publish Markdown
    • architecture/adr/ What we chose, what we rejected and why Markdown
    • runbooks/ Step-by-step guides: release, undo and outages Markdown
    • accessibility-statement.md Accessibility statement, known issues and the fix plan Markdown
    • performance-budget.md The budget, how it was set and how to change it Markdown
    • handover/ Recorded tours of the code and the release steps Video · Markdown
    • ci.yml Tests, plus speed, accessibility, visual and library checks YAML
    • preview.yml A preview link for every change YAML
    • release.yml Release in stages, live checks and automatic undo YAML
    • schedule.yml Nightly speed data and a report on broken budgets YAML

What we make for you is yours once it is paid for.

11 · What we measureTargets we design to · 3 in 4 visits

Speed, stability and recovery, measured on real visits.

We write 3 targets into the plan and check each against your real visits, using its own data source. They guide design and budget. They are not promised results.

Targets with sample readings · Illustrative
  1. 01

    Fast on your visitors’ devices

    Speed budgets are checked on every change and measured on the devices and networks your visitors use.

    Measured from
    Google’s Chrome UX Report (28 days), beside your own visit data
    Read at
    3 in 4 visits, by page type and device type
    Reviewed
    On every release, and formally at the day-90 review

    Google’s 3 speed targets met for 3 in 4 visits

    Sample spread of page loads across Google’s speed bands. Each value is for 3 in 4 visits. Main content shown (LCP): 78 percent good, 15 needs improvement, 7 poor; 2.1 seconds against 2.5. Tap response (INP): 84 percent good, 11 needs improvement, 5 poor; 164 milliseconds against 200. Layout shift (CLS): 91 percent good, 6 needs improvement, 3 poor; 0.04 against 0.1. All three clear the 75 percent line, so the page passes.

    Targetat least 75%

    Google passes a page when 3 in 4 visits are good. Good means main content within 2.5 s (LCP) and taps answered within 200 ms (INP). Layout shift must be 0.1 or less (CLS). We hold that on every key page type.

  2. 02

    Stable on your customers’ phones

    Crash reports are set up before the first release, with clear error details and an owner for every alert. Our release guard catches problems before app-store reviews do.

    Measured from
    Crash reporting, set up before the first build
    Read at
    Per session, over the last 7 days
    Reviewed
    Daily during a rollout, then weekly

    Sessions without a crash, mobile, last 7 days

    Sample week of mobile sessions without a crash, against a 99.5 percent floor. Monday 99.72, Tuesday 99.68, Wednesday 99.81, Thursday 99.42, Friday 99.63, Saturday 99.78, Sunday 99.74. Thursday is the only day below the floor. A release caused crashes, the guard undid it and the line recovered the next day.

    Targetat least 99.5%

    The floor is 99.5%. For a busy app, the gap from 99.0% is thousands of broken sessions a month. A release caused Thursday’s dip. Our release guard undid it within a day.

  3. 03

    Frequent releases, fast recovery

    Small releases that can be switched off, a preview for every change and automatic undo based on real-visit data.

    Measured from
    Release and incident records, kept automatically
    Read at
    Every unplanned fix, typical and worst case
    Reviewed
    At every incident review, with the fix owner named

    Time to restore service after a bad release

    Sample chart: time to fix the last eighteen unplanned outages. Nine took under five minutes and six took five to fifteen. Two took fifteen to thirty, one took thirty to sixty and none took over an hour. Fifteen of the eighteen are inside the fifteen-minute target.

    Targetunder 15 minutes

    Time to restore is 1 of the 4 DORA release measures. We report all 4. DORA’s top band is under an hour. We plan for 15 minutes because undo is automatic.

We measure business results before work starts. We track sales, enquiries, finished tasks and drop-off the same way before and after launch, for a fair comparison. We agree each target with you at the start and review it at day 90.

Offers & plans

From a company website to a full online shop or app.

Pick what you need built. Each offer shows what is included, the tools we usually use and a typical timeline.

Categories
05
Offers
26
Plans
05
Not sure what you need? Tell us the problem

How to buy

  1. 01Pick offers. Ask about one, or add several to one enquiry.
  2. 02Choose a plan. A small job, a fixed project or ongoing help.
  3. 03Send your enquiry. We reply within one working day.

Browse by category

Timelines are typical. We write the scope before we quote.

01Websites

6 offers
Typical timeline: 6–12 weeks

Company website

Your main company site: who you are, what you offer and how to reach you. Fast on any device and easy for your team to update.

What’s included

  • Site map, content plan and templates
  • Website editor, roles and previews
  • Search set-up and labels for Google
  • Speed and accessibility checks
  • Stats and cookie consent
  • WordPress or custom
  • WCAG 2.2 AA
  • Google speed targets

Best forCompanies replacing an outdated site or launching a new brand.

Typical timeline: 2–5 weeks

Marketing & campaign sites

A focused site for a product launch, event or campaign. It turns visitors into enquiries and is ready on launch day.

What’s included

  • Landing pages built from reusable blocks
  • Forms linked to sales tools
  • Split tests and enquiry tracking
  • Tested for launch rush
  • Landing pages
  • Enquiry tracking
  • Fast turnaround

Best forMarketing teams with a launch date and a target to hit.

Typical timeline: 6–14 weeks

Online shop

An online shop where customers browse, pay and track orders. Built on Shopify or WooCommerce, or custom-built for speed and control.

What’s included

  • Catalogue, cart, checkout and order emails
  • Payments through Razorpay, Stripe or PayPal
  • Stock, shipping and tax set-up
  • Product feeds and sales tracking
  • Custom-built shop front, if needed
  • Shopify
  • WooCommerce
  • Custom shop front

Best forBrands selling direct online, from a first shop to a rebuild.

Typical timeline: 8–16 weeks

Multilingual, multi-country website

One website that serves several languages or countries, showing each market the right content, currency and search listing.

What’s included

  • Web addresses set up per country
  • Translations managed in the editor
  • Language labels for Google
  • Right-to-left text and local formats
  • Languages
  • Country sites
  • Localised editor

Best forOrganisations selling or operating in more than one country or language.

Typical timeline: 4–10 weeks

Website editors (CMS)

A website editor your team runs without a developer: WordPress, Contentful, Sanity or Strapi. Pages are built apart from it, so they stay fast.

What’s included

  • Content plan made with your editors
  • Approval steps, roles and scheduled posts
  • Live preview and reusable content blocks
  • Existing content moved over
  • Editor training
  • Feeds site & app
  • Reusable content
  • Editor-friendly

Best forTeams that publish often and feel held back by their editor.

Typical timeline: 8–14 weeks

Portals & intranets

A signed-in website for employees, members or partners, showing each person the documents, news and tools they are allowed to see.

What’s included

  • One log-in (SSO) with your staff accounts
  • Content and access set by role
  • Search across pages and documents
  • Notifications and activity feeds
  • SSO
  • Access by role
  • Search

Best forOrganisations sharing information with staff, members or partners behind a login.

02Web apps

6 offers
Typical timeline: 10–16 weeks

SaaS MVP

Your first working subscription product, ready for paying customers fast and built to grow without a rewrite.

What’s included

  • Workshop to cut scope to essentials
  • Sign-up, accounts, roles and subscription billing
  • Main features and an admin area
  • Usage stats and error tracking
  • One system for many customer accounts
  • Startups
  • Subscription billing
  • Multi-customer

Best forFounders and teams testing a new product idea.

Typical timeline: 10–18 weeks

Customer & partner portals

A secure place where customers or partners log in to place orders, track requests, download documents or manage their account.

What’s included

  • Accounts, roles and one log-in
  • Tied to your business systems
  • Self-service requests with status tracking
  • Record of key actions
  • Self-service
  • SSO
  • Linked systems
  • Salesforce

Best forBusinesses that want fewer emails and calls about routine requests.

Typical timeline: 6–12 weeks

Dashboards & admin panels

Screens that show your team what is happening and let them act on it: approve, edit, assign and export, without touching the database.

What’s included

  • Admin screens by role
  • Charts and tables on live data
  • Bulk actions, filters and exports
  • Activity log of every change
  • Admin screens
  • Live data
  • Access by role

Best forOperations teams working from spreadsheets or raw database tools.

Typical timeline: 6–12 weeks

Installable web apps (PWA)

A website that installs like an app, works on poor connections and sends notifications, with no app store needed.

What’s included

  • Home-screen install and icons
  • Works offline and syncs later
  • Push notifications
  • Speed and install checks in Lighthouse
  • Works offline
  • Installable
  • Push notifications

Best forProducts that need app-like use without the cost of 2 native apps.

Typical timeline: 12–20 weeks

Booking & marketplace platforms

Platforms where customers book time, services or products from you or many sellers, with payments, schedules and payouts handled.

What’s included

  • Listings, search and filters
  • Availability, booking and reminders
  • Payments, refunds and seller payouts
  • Reviews and dispute handling
  • Seller and admin dashboards
  • Bookings
  • Split payments
  • Many sellers

Best forService businesses and marketplaces connecting buyers with providers.

Typical timeline: 6–10 weeks

Shared design kit (design system)

A shared library of buttons, forms and page parts in code, so every screen looks consistent and new features are quicker to build.

What’s included

  • Colours, fonts and spacing saved as code
  • Coded parts, documented in Storybook
  • Accessibility tests on every part
  • Figma-to-code steps for both teams
  • Styles
  • Reusable parts
  • Storybook

Best forCompanies with several products or teams building the same screens twice.

03Choose your technology

6 offers
Typical timeline: 8–16 weeks

Laravel (PHP)

A mature PHP framework with log-in, background jobs and admin built in. Good for business apps, portals and APIs, especially if you already use PHP.

What’s included

  • Laravel app with automatic tests
  • Background tasks and caching
  • Documented API for other tools
  • Automatic release to your cloud
  • PHP
  • Laravel
  • REST API

Best forBusiness apps, portals and teams already using PHP.

Typical timeline: 8–16 weeks

MERN (MongoDB, Express, React, Node.js)

JavaScript from database to browser, with a flexible database. Choose it when your data changes shape often and one JavaScript team runs the product.

What’s included

  • React screens and Node.js/Express API
  • MongoDB data design for speed
  • Log-in and access by role
  • Tests run on every change
  • JavaScript
  • MongoDB
  • Express

Best forFast-moving products with changing data and a JavaScript team.

Typical timeline: 10–18 weeks

MEAN (MongoDB, Express, Angular, Node.js)

JavaScript throughout, with Angular giving big forms and data-heavy screens a firm structure. Choose it for complex staff tools and large-company apps.

What’s included

  • Angular screens in TypeScript
  • Node.js/Express API
  • MongoDB data model
  • Code and journey tests
  • Angular
  • TypeScript
  • Business screens

Best forLarge companies using Angular or building form-heavy tools.

Typical timeline: 8–16 weeks

Next.js & Node.js

React with pages built on the server: fast to load and easy for search engines to read. Choose it for public pages plus a signed-in app.

What’s included

  • Next.js app with fast, pre-built pages
  • Node.js or NestJS API layer
  • Nearby copies and lighter images
  • A preview link for every change
  • React
  • Server-built pages
  • TypeScript

Best forSites that need speed, search rankings and a log-in.

Typical timeline: 8–16 weeks

Django & FastAPI (Python)

Python behind the scenes: Django for data-heavy apps with a built-in admin, FastAPI for fast, documented APIs. Choose it when your product depends on data or AI.

What’s included

  • Django or FastAPI service
  • Admin screens and background tasks
  • Developer guide made from the code
  • Links to your data and AI systems
  • Python
  • Django
  • FastAPI

Best forData- and AI-heavy products, and teams that work in Python.

Typical timeline: 10–20 weeks

Spring Boot (Java) & .NET

Mature large-company tools with long support. Choose them to fit your existing Java or Microsoft systems and their security rules.

What’s included

  • Spring Boot or ASP.NET Core services
  • Links to your staff log-in and messaging
  • Automatic code and security scans
  • Packaged for any server
  • Java
  • .NET
  • Enterprise
  • Microsoft Azure

Best forEnterprises with Java or Microsoft standards to meet.

04Mobile apps

5 offers
Typical timeline: 10–18 weeks

Native iOS app (Swift & SwiftUI)

An iPhone and iPad app built with Apple’s own tools, making full use of features such as the camera, payments, health data and widgets.

What’s included

  • SwiftUI screens to Apple’s design rules
  • Offline storage and sync
  • Push alerts and app links
  • App Store set-up and test builds
  • Swift
  • SwiftUI
  • App Store

Best forProducts where iPhone users matter most or deep device features are needed.

Typical timeline: 10–18 weeks

Native Android app (Kotlin & Jetpack Compose)

An Android app built with Google’s recommended tools, tuned for the wide range of phones and tablets your customers use.

What’s included

  • Compose screens to Google’s design rules
  • Offline storage and background work
  • Push alerts and app links
  • Google Play set-up and staged releases
  • Kotlin
  • Jetpack Compose
  • Google Play

Best forMarkets where Android leads, such as India, or apps that use device hardware.

Typical timeline: 10–16 weeks

iOS + Android app (Flutter)

One set of code for iOS and Android, with one branded look. Usually quicker and cheaper than 2 separate apps.

What’s included

  • One Flutter code base for both
  • Links to native phone features
  • Works offline, with push alerts
  • Submission to both stores
  • Flutter
  • Dart
  • iOS + Android

Best forTeams that want both platforms from one budget and a custom interface.

Typical timeline: 10–16 weeks

iOS + Android app (React Native & Expo)

One JavaScript code base for iOS and Android, sharing code and skills with your React website. Many updates reach phones without a new store release.

What’s included

  • React Native app built with Expo
  • Code shared with your web app
  • Updates without a store release
  • Store builds and submission
  • React Native
  • Expo
  • TypeScript
  • React Native

Best forCompanies with a React web team that want to reuse skills and code.

Typical timeline: 4–10 weeks

App upgrade & store relaunch

Rescue, upgrade or relaunch an existing app: fix crashes, update ageing libraries, move to current frameworks and take it through store review.

What’s included

  • Code and crash review with a fix plan
  • OS and library upgrades
  • Crash reports and speed monitoring
  • Store listing, review and release management
  • Upgrade
  • Fewer crashes
  • Store review
  • React Native

Best forApps with falling ratings, rising crashes or old code.

05Speed, accessibility & care

3 offers
Typical timeline: 2–6 weeks

Speed (Core Web Vitals)

Make your site measurably faster and keep it there, judged against Google’s “good” speed targets for 3 in 4 visits.

What’s included

  • Starting speed from real-visit data
  • Fixes to images, fonts and code
  • Speed budgets that block slow changes
  • Before-and-after report
  • Loads ≤ 2.5 s
  • Reacts ≤ 200 ms
  • Jumps ≤ 0.1

Best forSites losing visitors or rankings to slow pages.

Typical timeline: 3–8 weeks

Accessibility to WCAG 2.2 AA

Make your site usable by people with disabilities, including screen-reader and keyboard users, and reduce legal risk. Built and tested to WCAG 2.2 Level AA.

What’s included

  • Tests with screen readers and tools
  • Fixes to code, content and parts
  • Accessible parts in your design kit
  • Accessibility statement and automatic re-checks
  • WCAG 2.2 AA
  • Screen readers
  • Keyboard access
  • Playwright

Best forPublic-facing services, regulated sectors and teams with accessibility obligations.

Typical timeline: Ongoing, monthly

Website & app maintenance

Keep your site or app secure, updated and working after launch, with a set number of hours each month for fixes and small improvements.

What’s included

  • Security fixes and library updates
  • Downtime and error alerts
  • Backups with regular restore checks
  • Agreed monthly hours for changes
  • Monthly report
  • Monthly plan
  • Monitoring
  • Security updates

Best forBusinesses without an in-house web team.

Your enquiry

Tick “Add to enquiry” on any offer, choose a plan, then continue. Or enquire about one offer.

How we work with you

Ways to start, from a question to a quote.

Ask a quick question, send your project details or request a quote. The person who will lead the work reads each one in full. Services in your enquiry go with it.

Or book a 30-minute call

What are you sending?

  1. 01

    About 2 minutes3 short answers

    For a first chat, a press request or anything not ready to plan yet.

    You get A reply from a named lead

  2. 02Recommended

    About 8 minutes5 short steps

    Goals, who it is for, budget and timing, so our first reply can outline the work.

    You get Options and prices after one call

  3. 03

    About 15 minutesYour documents attached

    Your documents, deadlines and the purchasing and security rules to meet.

    You get Confirmation and a named lead

How it is priced

Each plan shows how it is priced. Work starts once we agree a written scope and price.

  • Typical length
    1–3 weeks
    Pricing
    Fixed fee
  • Typical length
    4–12 weeks
    Pricing
    Fixed price
  • Typical length
    3–9 months
    Pricing
    Fixed price per stage
  • Typical length
    Ongoing · 6-month minimum
    Pricing
    Monthly fee
  • Typical length
    Ongoing · 3-month minimum
    Pricing
    Paid by time used
Compare what each plan includes
What each plan includes and who it suits
PlanWhat you getBest for
SprintA short, fixed job that answers one clear question.
  • Scope and result agreed before we start
  • A senior lead and the right specialists
  • A weekly review with you
  • A clear answer or a test version
An audit, a brand check or a test version of an app
ProjectOne clear job for one fixed price.
  • A written scope: what you get and how we agree it is done
  • A named project lead and a fixed team
  • A shared plan with checkpoint dates
  • Source files, yours once paid for
A brand identity, a website, a simple app or a set of tools
MilestoneA bigger build in stages you approve and pay for one at a time.
  • Stages, each with its own scope and approval
  • A go or stop review at each stage
  • Re-plan between stages as you learn
  • Pay for each stage you approve
Work too big for one contract, such as a large app
RetainerA monthly team that runs and improves what we built.
  • Team time set aside for you every month
  • Agreed response times for requests and fixes
  • A monthly review and a to-do list
  • Planned improvements, not only fixes
Monthly social media and ads, or care for live sites and apps
SquadOur specialists join your team and work in your tools.
  • Named specialists matched to your plan
  • Works in your own tools and meetings
  • Grow or shrink the team each month
  • We teach your team from week one
Teams with a clear plan that need senior people fast

12 · Questions7 questions buyers ask

Websites & Apps questions, answered.

What buyers ask first: app type, website editor, code ownership, AI, support, search rankings and speed.

  • We recommend one early, based on what the app must do. Heavy use of the camera or sensors suits separate iPhone and Android apps. One shared app (Flutter or React Native) costs less. Many products only need a fast web app.

  • The one your team finds easy to use. We work with WordPress, Contentful, Sanity and Strapi. We choose by your content, your publishing steps, languages and cost.

  • What we make for you is yours once it is paid for. Tools we already had stay ours, and you get a free, permanent licence to use them. The code lives in your own accounts from day one.

  • AI drafts code and tests; an engineer approves every change. AI also gives each change a first review. Your code never goes into tools that learn from it.

  • We support you for a set time after launch. Then your team takes over, or we stay on through Integration & Support with agreed response times.

  • Yes, if we plan the move first. We list every page that earns visits or links and test every redirect. After launch we check Google’s search reports daily for a month. Rankings may shift, but no page is lost by accident.

  • We make page weight a rule every change must pass. A change over its image, script or font budget cannot go in. Any release that slows taps is undone automatically. At day 90 we fix the 3 worst slowdowns with you.

Tell us what you need built.

You will talk to the lead who would run your work.

Book a call

Three ways to start

We always agree a written scope and price before work begins.

Choose one of the three ways above