01 / 09
Frontend development
Fast, accessible interfaces built from one design system, so every page uses the same tested components.
- A component library in code
- Typed and tested components
- Accessible to WCAG 2.2 AA
Web development that feels instant
Websites, web apps and business software built in React and Next.js, accessible and passing Core Web Vitals.
Websites and web apps we build
Fourteen kinds of project, from a landing page to the software a whole company runs on.
Websites
The sites people find you by: fast, found in search and easy for your team to edit.
- Marketing websites
- Landing pages
- Company websites
- Blogs and content hubs
- E-commerce stores
Web applications
Products people sign in to and work in every day, built for real data and real use.
- SaaS products
- Dashboards and analytics
- Customer and partner portals
- Booking and marketplaces
- AI-powered apps
Business software
The systems a business runs on, from managing its content to running its operations.
- Content management systems
- Admin panels and back office
- Management and internal tools
- Enterprise platforms
Web development services
Everything a website or web app needs, from the first screen to the audit, the redesign and the care after launch.
02 / 09Website development
Marketing sites, landing pages, blogs and online stores, designed and built to load fast and be found.
- Marketing and company websites
- Landing pages
- Blogs and content hubs
03 / 09Web app development
SaaS products, dashboards, portals and business software, from the first screen to launch and beyond.
- SaaS products
- Dashboards and admin panels
- Booking and marketplaces
04 / 09E-commerce development
Online stores with checkout and payments, built to load fast and be found.
- Storefront and checkout
- Payments
- Catalogue and orders
05 / 09Web portal development
Portals where customers, partners or suppliers sign in to see their orders, documents and invoices, and act on them.
- Customer and partner portals
- Sign-in, roles and permissions
- Connected to your systems
06 / 09CMS development
Content your team edits without a developer, in a CMS that feeds the site and the app.
- Headless or classic CMS
- Previews before publishing
- Roles for your editors
07 / 09Website redesign and migration
A dated site rebuilt on a modern stack, its content, addresses and search rankings carried across.
- Redesign on a modern stack
- Content and pages moved over
- Redirects for every old address
08 / 09Website audit and optimisation
A review of your site or app — speed, accessibility, SEO and code — and a clear list of what to fix first.
- Speed and Core Web Vitals
- Accessibility and SEO
- Then the fixes, in order
09 / 09Website maintenance and support
Updates, security patches, monitoring and small changes, so the site stays fast and safe after launch.
- Updates and security patches
- Uptime monitoring
- Small changes when you need them
Frontend problems we fix
The problems teams bring us most, each with a fix that lasts longer than a patch.
Slow-loading pages
Speed budgets for every page, checked before each release.
Code nobody wants to touch
Typed and refactored in place, so changes get easier, not riskier.
Builds that don't match the design
One team and one set of design tokens, so what ships is what was designed.
Every edit needs a developer
A CMS your team edits and publishes in, without waiting for anyone.
A site not everyone can use
Built and tested to WCAG 2.2 AA from the very first component.
Search and AI optimisation
Server-rendered pages with metadata search engines and AI assistants can read.
Our web development process
Five steps, one team: the same people scope, plan and build it, so nothing is lost between the idea and the code.
01Scope
Goals, audience, content and integrations settled, with a sitemap of every page.
02Plan
Wireframes, the design system and every page agreed with you, with an estimate that names the dates.
03Build
Built in milestones on a live preview URL, each page tested as it lands.
04Launch
Content moved, redirects set and checks passed, then live with monitoring.
05Maintain
Hosting, updates and improvements, or a clean handover to your own team.
01Scope
Goals, audience, content and integrations settled, with a sitemap of every page.
02Plan
Wireframes, the design system and every page agreed with you, with an estimate that names the dates.
03Build
Built in milestones on a live preview URL, each page tested as it lands.
04Launch
Content moved, redirects set and checks passed, then live with monitoring.
05Maintain
Hosting, updates and improvements, or a clean handover to your own team.
Fast, accessible and maintainable websites
Built into every website and web app we make, whatever its size.
Design systems
Tokens, components and documentation, so the hundredth screen matches the first.
Responsive on every screen
Laid out for the phone, the laptop and every width between.
Accessible by default
Keyboard, screen reader and contrast, tested to WCAG 2.2 AA.
Quality built in
Typed, tested and reviewed on every change, so what ships keeps working.
Ways to start
Starting something new, or working with software you already have.
Something new
Build a first version
An MVP with the features that matter most, to launch and learn.
Build the whole product
Designed, built and launched in full, by one team.
Extend your team
Engineers join your team, or a dedicated team runs the work.
Software you already have
Audit what you have
A review of your code, setup and costs, and a plain list of what to fix first.
Modernise it
New features or a modern stack, one part at a time, without stopping the business.
Take a prototype to production
A prototype, demo or stalled project made reliable, secure and ready for real users.
Hosting, maintenance & support
Hosting, monitoring, updates and fixes for software in production, agreed with you.
Industries we build software for
Custom software development across industries: web, mobile and AI applications, built and security-audited by one team.
We also build software for insurance (insurtech), government (govtech), energy and media. If your industry is not listed, we can still build for it.
Technologies and tools for web development
A few of the tools we build with. Every project gets the stack it needs, so these are examples, not a limit.
TypeScriptJavaScriptHTMLCSSReactNext.jsNode.jsViteGraphQLTailwind CSS
FigmaRadix UIshadcn/uiFramer MotionLottieLighthouseSentryVercelCloudflareGitHub Actions
Frontend we run in production
Three products of our own, designed, built and kept running by the same team.
Retail · SaaS
A point-of-sale system that keeps sales, stock and receipts together on till, tablet and phone.
Screen capture, 1908 × 944Travel
A travel booking app whose AI assistant finds flights, hotels and trip ideas, through to a confirmed booking.
AI
Silvia AI
An AI assistant for customer support and sales that answers questions and guides buyers.
Screen capture, 1908 × 944
Questions about web development
The ones teams ask before they start, answered plainly.
How much does web development cost?
It depends on what is being built: a landing page and a platform a company runs on are different projects. After a first call we send a written estimate with the scope, the timeline and the price, so you know the cost before any work starts.
How long does it take to build a website or web app?
A landing page or a small website takes weeks; a web app or business system takes months, depending on its scope. The estimate sets out the timeline before any work starts.
Can you take over an existing website or web app?
Yes. We start by reading it — the codebase, its dependencies, its performance and its accessibility — so the plan is built on what is there, not on a rewrite by default.
Do you work from our designs, or design as well?
Either. We build from Figma files your designers own, or design it with you ourselves. Both ways, the components go into a design system the next screen can reuse.
Which framework will you use?
React and Next.js for most products, because they cover server rendering, static pages and rich interfaces in one codebase. If your team is on another framework, or something lighter fits better, we say so before we start rather than after.
How do you keep it fast?
Every route has a budget for loading, response and layout stability, checked before each release. A change that breaks a budget is fixed before it ships, not logged for later.
Is accessibility included, or an extra?
Included. WCAG 2.2 AA is the baseline: semantic HTML, full keyboard support, visible focus, sufficient contrast, and screen-reader testing on the flows that matter.
What happens after launch?
We can keep running it — monitoring, fixes and new features — or hand it over with documentation and a component library your team can build on.