Architecture document
How the app fits together, why it's shaped this way, what changes when you scale. The thing your next engineer reads on day one.
// next.js development
Next.js, built to last.
Production Next.js work for teams who've outgrown no-code and need something that won't rot in twelve months. App Router, RSC, edge-aware. We ship few projects and we ship them well.
// where teams get stuck
You're past no-code. The next vendor wants a retainer.
- Your prototype outgrew its tools and the rebuild keeps slipping.
- Every agency you've talked to wants to staff a team and bill monthly.
- Your codebase is one developer's idea of "done" and nobody else can touch it.
- The handoff plan is a Notion page and a six-month dependency on the vendor.
// what's included
What you get when we ship.
Production CI/CD
GitHub Actions or equivalent. Preview deploys per PR. Type-checked, linted, tested before merge. No ambiguity at the boundary.
Component library
Built with the design tokens you use. Storybook or equivalent. Visual regression where it matters.
Test coverage where it pays
We don't chase 100%. We test the boundaries — payments, auth, data integrity, anything that wakes someone up.
Post-launch support window
Bugs we shipped, we fix. Questions while your team gets oriented, we answer. Then we hand the keys over.
// how we work
Three phases. Built to last.
01 · Calibrate
30-min call, then a written scope with milestones, costs, and what could go wrong. You sign, or you don't.
02 · Build
Weekly demo on a real staging URL. Decisions documented. No hidden state, no surprise invoices.
03 · Hand off
Your team owns the codebase on launch day. Architecture doc, CI green, support window starts.
// common questions
What teams ask before signing.
A typical Next.js engagement at webkoi covers product architecture, full-stack implementation in TypeScript, App Router with React Server Components, design-system integration, production CI/CD, and a post-launch support window. Every project ships with an architecture document explaining how the app is shaped and where it changes as you scale, so the next engineer joining your team can read it on day one and understand the system without us in the room.
Scoped per project — we don't publish a fixed range, because the honest answer depends on integration depth, auth complexity, and how cleanly the requirements come in. The shape is the same across our work: discovery, design with prototypes, build with weekly demos, launch with a support window. The first written scope (with timeline) arrives within 48 hours of the discovery call. If the scope hasn't been written down yet, we'd rather have that conversation at the start than at week six.
Yes. Every webkoi project ships with a post-launch support window included — bug fixes we shipped, plus questions while your team gets oriented. After that, we offer optional ongoing care plans that cover bug fixes, dependency upgrades, small feature work, and performance monitoring, sized to your team and pause-able month to month. We bias toward fixed-scope projects with milestone-based billing — your team owns the codebase from day one in your own GitHub org — but we'd rather stay around as a quiet partner than disappear at launch.
App Router for any new project, unless there's a specific reason otherwise. New Next.js projects in 2026 should default to App Router because it unlocks Server Components, streaming, and the metadata API — capabilities that materially change how fast your app feels and how much JavaScript ships to the browser. We've also done Pages Router → App Router migrations on existing codebases, so the choice isn't either-or.
Yes. The repository lives in your GitHub organization from day one — not in a webkoi-controlled space we hand over later. There are no license clauses, no proprietary frameworks you can't replicate, and no vendor lock-in. If you decide to take the project in-house or move to another studio after we ship, the handoff is a permission change, not a migration.
Scoped per project. We send a written proposal with the full breakdown after the discovery call — pricing depends on integration depth, auth complexity, and CMS scope. We never quote a number without a written scope first — anyone who does is either guessing or padding. Budget conversations happen on the discovery call, before either side has committed to anything.
Murcia, Spain. About 70% of our clients are outside Spain — across the EU, UK, and North America — and we work with them remotely with weekly video demos on real staging URLs. For projects that warrant it, we travel for on-site reviews to Madrid, Barcelona, Lisbon, or London. Languages: English and Castilian Spanish, daily, in writing and on calls.