Web Development

"Web development" covers a wide range of things, from a single landing page to a full product with logins and a database. What ties every project at Nordbüro together isn't the size — it's that one person handles the whole thing, from the first wireframe to the deployed, working site.

What that actually changes

Most web development happens through a chain of handoffs: a project manager takes the brief, a designer produces mockups, a developer builds from those mockups, and a QA step catches what doesn't match. Each handoff is a place where intent gets lost — a layout that looks fine in a static mockup turns out to be awkward once it's actually built and someone tries to use it on a phone, and by the time that's discovered, it's a change request going back through the same chain.

When the same person designs and builds, that entire chain of handoffs collapses into one continuous loop. A layout decision that doesn't work in code gets caught and fixed the same day, not flagged three weeks later in a review meeting. That's not a lifestyle preference — it's a specific, measurable reason the fixed timelines below are realistic instead of optimistic.

What you actually get

Every project ships with three things, regardless of size:

• A fast, working site, not just a design file. Every page is real, deployed, and responsive before it's called done.
• A clear structure aimed at one outcome per page — a contact form, a booking flow, a pricing table people can actually read. A page that looks good but doesn't ask the visitor to do anything specific isn't finished.
• A technical foundation that can grow. Next.js and TypeScript aren't chosen for hype — they're what lets a five-page marketing site become a full dashboard later without a rewrite, and what one developer can maintain long-term without things quietly breaking. More on why that specific stack, if you want the technical case.

What "done" actually means before launch

A checklist runs before any project is called finished, not just "does it look right": every page tested on real mobile devices, not just a resized browser window; every form actually submitted end-to-end to confirm it reaches the right inbox or database; every link checked for a real destination instead of a placeholder #; analytics installed and verified to be firing correctly, not just pasted into the code and assumed to work; and a final pass against the original scope to confirm nothing agreed upfront quietly got dropped along the way. None of that is exciting to describe, which is exactly why it's worth naming explicitly — it's the difference between a site that looks finished in a demo and one that actually works the first time a real visitor uses it under real conditions.

The three ways to work together

Landing Page — €799, 5 business days. A single page, all sections, your brand and copy, mobile-first responsive design, smooth scroll animations, deployed to Vercel with your domain connected. One round of revisions. This is the right fit for a product launch, an event, or a business that needs a credible web presence fast without five separate pages to maintain.

Business Site — €1,499, 10 business days. Up to 5 pages, a custom design system so every page feels like the same brand instead of five different templates stitched together, an optional blog or lightweight CMS, a contact form wired to analytics, two rounds of revisions, and 30 days of post-launch support included. This is the most common choice — it's what most small and medium businesses actually need: a real site, not a placeholder.

Custom — scope-dependent, quoted after a conversation. SaaS MVPs, web apps with logins and a database, dashboards, booking systems, anything where "how many pages" isn't the right question to ask. The full breakdown of all three tiers is here.

Why the stack matters even if you never look at the code

Most business owners commissioning a website will never open the codebase, and that's fine — but the technology choice still affects things you'll notice directly. A site built on Next.js and TypeScript starts fast and tends to stay fast as pages get added, because the rendering strategy and type safety were part of the foundation from the first commit rather than bolted on. A site built by stacking WordPress plugins tends to get slower with every feature added, because each plugin brings its own JavaScript, its own database queries, and its own way of doing things that doesn't necessarily play well with the others. You feel that difference two ways: as a visitor, in how fast pages load, and as the business owner, eighteen months later, when "can we add one more feature" is either a straightforward addition or the moment where the whole site's performance quietly falls off a cliff.

What "AI-assisted" means here, specifically

AI-assisted workflows handle the repetitive parts — boilerplate code, first-draft component structure, test scaffolding — which frees up time for the decisions that actually matter: how the data is modeled, what happens at the edge cases, and where the performance budget goes. It does not mean shipping unreviewed generated code; every line that ends up in a client project has been read, tested, and understood by the person delivering it. The speed comes from not re-typing patterns that have already been solved a hundred times before, not from skipping the parts that require judgment.

What the first conversation actually covers

Before any pricing tier gets picked, the first conversation is about the project, not the invoice: what the site needs to do, who it needs to convince, and what happens after someone lands on it. Concretely, that means going through what pages actually need to exist (not just "how many," but what job each one does), whether there's a form, a booking flow, or a payment step involved, whether multiple languages matter, and what's already built — an existing site to migrate from, a Figma file, a logo and brand colors, or genuinely nothing yet. That scoping conversation is what turns "I need a website" into an actual fixed price instead of a guess.

Who writes the words

Copy is one of the most commonly underestimated parts of a website project, and one of the most common reasons a timeline slips — not because the build is slow, but because the words aren't ready yet. The default assumption is that you provide the core content (what the business does, pricing, key selling points) and it gets structured, edited for clarity, and fitted to the page — turning a paragraph you'd write in an email into copy that's actually structured to convert. Full copywriting from a blank page, in the voice of a brand that doesn't have one yet, is a different and larger scope, and gets discussed upfront rather than assumed.

Different kinds of businesses, same underlying approach

The 22 live demos on this site span categories that map to most of what "web development" actually means for a small or medium business: SaaS & Tech, Health & Beauty, Food & Hospitality, Trades & Retail, Legal & Finance, Community & Government, and Tourism & Culture. A dental clinic and a construction company need very different content and tone, but the same underlying questions apply to both — what's the one action this page needs a visitor to take, and what does the page need to show, in what order, to get them there. That's the actual throughline across all 22, more than any shared visual style.

Where this fits, and where it doesn't

This setup is built for small and medium businesses, solo founders, and startups that need a real, fast, well-built site without an agency-sized budget or an agency-sized timeline. The tradeoff being made explicitly: one developer means no 24/7 support desk and no team of ten to throw at an emergency — what you get instead is direct access to the person who actually wrote the code, a fixed price agreed before work starts, and a process with no handoffs to lose things in.

For a large organization that needs a formal procurement process, a dedicated account manager, or a team large enough to work in parallel on a dozen pages at once, a bigger agency is probably the better fit — and that's a fair thing to say upfront rather than stretch a one-person studio somewhere it doesn't belong.

Different kinds of sites, same foundation

The 22 live demos on this site span very different business types — restaurants, dental clinics, law firms, construction companies, SaaS dashboards, e-commerce — built on the same Next.js, React, and TypeScript foundation each time. That's not a coincidence; it's the reason a landing page for a bakery and a multilingual job platform like HorecaJob.md can both start from the same technical base and diverge only where the actual business needs differ.

If a specific part of the stack matters most to your project — the framework choice, the interactive frontend work, the design, or the SEO foundation — there are deeper breakdowns of each: Next.js development, React development, frontend development, UI/UX design, and technical SEO.

---

Not sure which tier fits, or whether your project is even web-development-shaped yet? Get in touch — a first read on your situation is free, and if a smaller (or bigger) scope than you expected is the honest answer, that's what I'll say.