Marketing sites
Fast, indexable pages with structured content, clean metadata and a CMS your team can actually edit.
Web development
Next.js and React builds with a performance budget, structured content and metadata generated from one source — so speed and search visibility are maintained, not audited once and forgotten.
Written scope and a fixed estimate within two business days. NDA on request.
Performance budget
These are targets for the pages that carry traffic and revenue. We measure them on a deployed build, on a mid-range device — not on a developer laptop.
LCP
under 2.5s
Largest contentful paint on a mid-range phone over 4G.
CLS
under 0.1
No layout jumps from late-loading images or injected banners.
INP
under 200ms
Interaction response, measured on the pages that do real work.
Payload
budgeted
A JS budget per route, checked in CI rather than after launch.
Capabilities
Marketing pages, product surfaces and content platforms — with the same standard applied to each.
Fast, indexable pages with structured content, clean metadata and a CMS your team can actually edit.
Authenticated product surfaces with real state, permissions and the loading and error states people forget.
Catalogue, cart, checkout and payment flows with the edge cases — refunds, failed payments, tax — handled.
Sanity, Contentful or a custom admin, wired so content changes do not require a deploy.
Auditing and fixing an existing site: bundle size, images, fonts, third-party scripts and rendering strategy.
Moving off an ageing stack without losing rankings, URLs or the content that earns the traffic.
Process
What each page is for, which queries it answers, and how the navigation connects them.
Build the real components early so typography, spacing and responsive behaviour are settled in code, not in a static mock.
Server rendering where it helps, code splitting, image discipline and a JS budget per route.
Performance, accessibility, metadata and crawlability checked on the deployed build.
Launch checklist
Stack
FAQ
Both, and they are different jobs. A marketing site is judged on speed, clarity and search visibility; a web app is judged on whether the workflow holds up under real use. The scope and the estimate reflect which one you are asking for.
Often yes, and it is usually cheaper. We audit performance, accessibility, metadata and structure first, then propose the smallest set of changes that moves the numbers. A rebuild is recommended only when the foundation blocks the fixes.
Yes. Pages are built against a CMS model, so your team edits copy and images without a developer or a deploy. We include a walkthrough of the editing flow at handover.
URLs are mapped one-to-one with redirects for anything that changes, metadata is preserved or improved, and the sitemap is regenerated. We check the crawl after launch rather than assuming it carried over.
We deploy to Vercel, AWS or Cloudflare depending on the requirement, and hand over with the pipeline documented. Ongoing maintenance is optional and covers dependency updates, monitoring and small changes.
Request a quote
Send the current URL, the pages that matter and the problem you are trying to fix. We will come back with a scoped plan and a fixed estimate.
No obligation. We will tell you if we are not the right team for the job.
Tell us the goal, platforms and must-have features.
We reply within two business days with scope, approach and a fixed estimate.
Sign an NDA first if you prefer — nothing about your idea is public.