⟶ Practice / 04
18anonymised engagements shipped
Senior teams. Real products. No hand-offs.
Web and mobile products shipped end-to-end by senior engineers who own outcomes, not tickets.
Outcomes · Selected proofs
Lighthouse, shipped
Northfold
MVP to first paying user
SoukWave
P1 incidents post-launch
Last 4 releases
What we do
We work like a product team, not an agency — discovery, design, full-stack build, mobile, performance, QA and scale handled by the same senior people from day one to launch. One tech lead is accountable for scope, quality and timeline; the engineers in the pitch are the engineers in the codebase. Web (React, Next.js, TanStack Start), mobile (Swift, Kotlin, React Native, Flutter), API and data — all under one standard.
Capabilities
Discovery & product strategy
Senior-led discovery: problem framing, user interviews, jobs-to-be-done, IA, low-fidelity prototyping and a measurable definition of done. You leave week one with a working clickable prototype, a scoped MVP and the assumptions we're going to invalidate first — not a 40-page deck.
Product & UX design
Interaction design, motion, accessibility (WCAG 2.2 AA) and usability testing shipped alongside engineering — same Figma, same standups, same Slack. Designers think in components and engineers think in flows, so the design-to-dev hand-off chasm simply doesn't exist on our engagements.
Design systems
Tokens, primitives, documented components, Storybook and contribution guidelines — built so your in-house team can extend the system after we leave. We ship Figma libraries and code libraries in lockstep, with semantic versioning and visual regression tests on every PR.
Web applications
Full-stack TypeScript on React, Next.js, TanStack Start and Remix — SSR, edge rendering, streaming, server actions and typed RPC. Backed by Postgres, Drizzle or Prisma, Redis and S3-compatible storage. Built to score 95+ on Lighthouse and stay there as the product grows.
Mobile applications
iOS (Swift, SwiftUI), Android (Kotlin, Jetpack Compose) and cross-platform (React Native, Expo, Flutter) — chosen by what the product actually needs, not what's trending. Native modules, deep links, push, in-app purchase, offline-first sync and App Store / Play Store release pipelines wired in from day one.
Backend, APIs & data
REST, GraphQL and typed RPC services on Node, Bun or Go; Postgres with proper migrations, queues with idempotency, event-driven workers and background jobs. We treat the API as a product surface — versioned, documented, tested and observable, not an afterthought to the screens.
Performance & scale
Core Web Vitals green, INP under 200 ms, p99 API budgets honoured, N+1 queries hunted, images and bundles right-sized. We instrument before we optimise, so improvements are measured against real-user data and held in CI as performance budgets — not regressed in the next sprint.
QA, automation & release
Unit, integration, contract and end-to-end tests on every PR (Vitest, Playwright, Detox), preview environments per branch, feature flags, canary releases and rollback drills. 'It works on my machine' stops being a thing because the pipeline proves it works on the user's.
Learning paradigms
Three paradigms. One unified practice.
We scope to the metric that matters — activation, retention, conversion, time-to-value — and cut features that don't move it. Velocity is measured in user behaviour shifting, not story points burned.
Designers, engineers, QA and tech lead in the same standup, same repo and same definition of done. There is no 'throw it over the wall' moment because there is no wall.
Every codebase is built so your team can own it the day after we leave — readable code, ADRs, runbooks, onboarding docs and a working CI pipeline. No lock-in by obscurity.
AI tech stack
Our AI tech stack — research to production.
Web framework
- React 19
- Next.js
- TanStack Start
- Remix
- Vite
- Astro
Mobile
- Swift / SwiftUI
- Kotlin / Jetpack Compose
- React Native + Expo
- Flutter
- Native modules
- App Store / Play Store CI
Language & runtime
- TypeScript (strict)
- Node 20
- Bun
- Go
- Python (services)
- Zod / Valibot
Data & APIs
- PostgreSQL
- Drizzle · Prisma
- tRPC · GraphQL
- Redis · BullMQ
- S3-compatible storage
- Kafka / NATS
Design & systems
- Figma libraries
- Storybook
- Tailwind · CSS variables
- Radix · shadcn/ui
- Framer Motion
- Chromatic visual regression
Quality & testing
- Vitest
- Playwright
- Detox (mobile)
- Pact (contracts)
- MSW
- Lighthouse CI
DevOps & delivery
- GitHub Actions
- Vercel · Cloudflare
- AWS · Fly.io
- Docker
- Preview environments
- Feature flags (Statsig · Flagsmith)
Observability & growth
- Sentry
- OpenTelemetry
- PostHog · Amplitude
- Grafana / Datadog
- Real-user monitoring
- Server-side analytics
Approach
How we run engagements. Predictable rhythm, senior owners.
A short cadence, demos every two weeks, one accountable lead — no theatre, no surprises.
- 01
Discover
Problem framing, user interviews, a working clickable prototype and a one-page scope by end of sprint one. We agree the success metric — activation, time-to-value, conversion, retention — and design the build to move that number, not just to ship features.
- 02
Design
Design and engineering work in the same room and the same repo. Interaction, motion, accessibility and component design happen against real code in Storybook, so what you sign off in Figma is what ships to production — pixel-, motion- and behaviour-accurate.
- 03
Build
Two-week sprints, demo every Friday, working software in your hands continuously. Trunk-based development, preview deploys per PR, automated tests on every change and a release every sprint by default — so feedback compounds instead of stacking up behind a big-bang launch.
- 04
Scale
Performance budgets, observability (Sentry, OpenTelemetry, Grafana), on-call runbooks, capacity tests and a documented handover to your team. We design the exit before we design the architecture — so your engineers own the product the day after we leave.
What you receive
Concrete artifacts. Nothing hand-wavy.
Signed off at go-live. Yours to own — source, runbooks and rights, no lock-in by obscurity.
Industry plays
AI by industry — where it pays off.
Consumer
React Native apps with offline-first sync, push and in-app purchase, wired into a typed Node API and Postgres
Faster onboarding, higher D7 retention
B2B SaaS
Multi-tenant Next.js app with RBAC, SSO/SAML, audit logs and a typed tRPC API on Postgres
Enterprise-ready from MVP
Retail & eCommerce
Headless storefronts on Next.js with edge personalisation, search and CMS-driven content
Higher conversion, lower bounce
Fintech
Hardened web + native mobile with KYC, transaction signing, audit trails and PCI-aware architecture
Audit-ready release one
Healthtech
HIPAA-aware patient & clinician apps with role-based access, audit logs and offline capture
Compliant, usable in clinic
Media
Editorial CMS, paywall, video pipeline and personalised feeds on edge-rendered Next.js
Sub-second TTFB at scale
Automotive
Dealer portals, connected-car companion apps and service-booking flows backed by typed APIs
Lower no-shows, higher attach
Marketplaces
Two-sided web + mobile apps with search, ranking, payments split, disputes and notifications
Liquidity unlocked sooner
Engagement models
Three ways to work with us. One standard.
Project-based for fixed scope. Time & material for evolving work. Dedicated developers when you need senior capacity embedded with your team. Every engagement is shaped to your goals — we’ll recommend the right fit on the first call.
Engagement model
Project-Based
Fixed scope, fixed outcome. We define the work, agree the milestones, and own delivery end-to-end.
- Timeline
- Fixed scope
- Best for
- Well-defined builds, migrations and one-off implementations.
- ▸Senior-led discovery & sign-off
- ▸Defined milestones with demos
- ▸UAT, training & handover
- ▸Post-launch warranty
Engagement model
Time & Material — Agile
A senior squad billed by sprint. Scope flexes as you learn; cadence and quality stay constant.
- Timeline
- Sprint cadence
- Best for
- Evolving scope, continuous product work and discovery-led builds.
- ▸Dedicated senior squad
- ▸Two-week sprints with demos
- ▸Transparent burn-up reporting
- ▸Rolling roadmap
Engagement model
Dedicated Developers
Hire named senior engineers full-time, embedded with your team. You set priorities; we own quality.
- Timeline
- Ongoing
- Best for
- In-house teams that need senior capacity without the hiring lift.
- ▸Named senior engineers
- ▸Embedded in your stand-ups & tools
- ▸Tech-lead oversight included
- ▸Monthly performance review
Guardrails & governance
AI governance & guardrails — built so legal signs.
Trunk-based delivery
Small PRs, preview deploys per branch, mandatory review and automated tests on every change. Production is always one merge away — without anyone holding their breath.
Performance budgets in CI
Lighthouse, bundle-size and API p99 budgets enforced on every PR. Regressions block merge instead of slipping into a 'we'll fix it later' backlog that never gets fixed.
Accessibility as default
WCAG 2.2 AA baked into the component library, axe checks in CI and manual screen-reader passes on critical flows. Accessibility is not a retrofit; it's a definition of done.
Architecture decision records
Every meaningful choice — framework, data model, vendor — is captured as an ADR with context, alternatives considered and reversal path. Future you (and your team) will know why, not just what.
Observability & on-call
Sentry, OpenTelemetry traces, SLOs and runbooks shipped with the product. When something breaks, you see it before your users tweet about it — and you know what to do.
Why us
Why senior buyers pick us — and stay.
Seniors only, on the work
The people you meet in the pitch are the people who write the code. No bait-and-switch to juniors after kickoff.
One accountable lead
Every engagement has a single tech lead who owns scope, timeline and quality — and answers their own emails.
Built to be left
We ship documentation, runbooks and training so your team can take it forward without us. No lock-in by obscurity.
AI across the practice
We do AI alongside everything else we ship.
AI isn't a separate department here. It's the layer that compounds every other discipline — ERP, product, infrastructure and growth.
Related work
Where it shipped.
Industries shipped in: Packaging · HVAC & Field Service · SaaS
Cratewell Packaging Works →
A high-volume custom-box manufacturer replaced HubSpot, Xero and a scattering of spreadsheets with one Odoo backbone — quoting, manufacturing, sales channels and finance now move together.
Northvent HVAC Marketplace →
We designed and shipped Northvent's entire digital stack — storefront, service-management portal, CRM, vendor portal, inventory, plus brand identity, SEO and AI-search programme.
Lumen Copilot →
We took Lumen from a Notion-doc idea to a paid B2B AI copilot — multi-tenant SaaS, evaluation harness, agentic workflow engine and a brand that gets the sales meeting.
Lighthouse score (avg)
Products shipped
Years senior engineering experience
Questions