Performance as contract.
Headless platforms, design systems, performance budgets. Next.js, Tailwind stack. Web Vitals as mandatory KPI. no delivery that violates Core Web Vitals.
Headless platforms with Web Vitals as KPI.
Slow portals cost money. Every 100ms of extra latency reduces conversion. The Caporal Web Development programme treats performance as a contractual requirement, not a nice-to-have. LCP, CLS and INP are defined before the first line of code and monitored in production throughout the contract.
What we deliver
Architecture & tokenized design system
Component library documented in Storybook, design tokens mapped to CSS variables, usage guidelines and versioning. Built to grow without refactoring.
Enterprise Next.js development
App Router, strict TypeScript, internationalization with next-intl, image and font optimization, built-in technical SEO including metadata, schema.org and sitemap. Performance guaranteed in contract.
Headless CMS integration
Setup and integration with Sanity, Contentful, Strapi or headless WordPress. Preview mode configuration, approval workflows and editorial team training.
CI/CD with Lighthouse budgets
Deployment pipeline with automated performance tests. Any commit that violates Core Web Vitals budgets is blocked before production.
Documentation & handover
Complete architecture documentation, code standards, operations runbook and internal team training. Delivered in editable format, with no lock-in.
How we operate
Technical discovery (weeks 1-2)
Audit of the existing platform, integration mapping, current performance analysis and technical and business requirements gathering. Deliverable: approved technical spec.
Design system & components (weeks 3-6)
Tokenization of the existing design, component library construction and documentation of variants and states. Approval with client design and product teams.
Core development (weeks 5-14)
Development of prioritized pages and features in 2-week sprints. Incremental client review and approval. CI with Lighthouse budgets active from the first sprint.
Integration & testing (weeks 13-16)
Integration with CMS, CRM and analytics tools. Load tests, accessibility tests (WCAG AA), final performance review and technical SEO review.
Deploy & monitoring (week 17)
Production deployment with rollback ready. Uptime monitoring, performance alerts and error tracking configured. 2-week stabilization period.
Handover & support (weeks 18-20)
CMS training for the editorial team, architecture training for the technical team and final documentation delivery. 90 days of post-launch support included.
Frequently asked questions
What is the typical stack?
Next.js 15 (App Router), TypeScript, Tailwind CSS v4, Vercel or Cloudflare deployment. CMS varies by project: Payload, Sanity, Shopify Headless or WordPress headless.
How are Web Vitals guaranteed?
Performance budgets are contractualised before the project starts: LCP < 2.5s, CLS < 0.1, INP < 200ms. CI/CD with Lighthouse checks blocks deploy if budgets are violated.
Do you deliver design or just development?
Both. We have a senior design team for tokenised design systems. For clients with existing design teams, we collaborate on design system implementation and handover.
What happens after delivery?
Full documentation for internal team handover. Monitoring period with Caporal for 90 days after launch. Optional ongoing optimisation contract.
What is the typical timeline for an enterprise replatforming?
For mid-sized portals with 50-200 pages and 2-3 integrations, the typical timeline is 16 to 20 weeks. For larger portals or projects with more integrations, it is 24 to 32 weeks. Migration planning includes a parallel operation period for the old and new platforms to ensure zero downtime and safe rollback.