B2B and B2C sites, webshops, customer portals and internal web apps on a Next.js + React + TypeScript stack. Static HU/EN/DE multilingual support, measurable sub-1.8s LCP on mobile. WordPress or WooCommerce when the project justifies it.
Business context
Typical situations where it's worth talking to us. If more than one rings a bell, we can probably help.
4–5s mobile load, Lighthouse below 50. That's SEO loss and conversion loss together. Next.js with static generation typically gets mobile LCP under 1.8s.
Desktop looks fine, but the site falls apart on phones — where 60–70% of traffic comes from. Mobile-first redesign, Tailwind-based responsive system, documented design tokens.
Every text change needs a pull request and deploy. Marketing can't move independently. Headless CMS (Sanity, Strapi) or WordPress backend hooked to the frontend so editing is no longer a dev task.
Google can't find the site; visitors don't convert. Technical SEO audit, schema.org markup, OpenGraph, sitemap, robots.txt, and A/B testable landing variants in PostHog or GrowthBook.
Deliverables
Concrete deliverables, not abstract capabilities. Documentation and handover included with every shipment.
B2B SaaS landings, B2C webshops, customer portals or internal admin. App Router, RSC + Client Components, TypeScript strict. Vercel preview on every PR, Lighthouse 90+ minimum.
Sanity or Strapi backend with a Next.js frontend. Real-time preview for editors, multilingual content, automatic image optimization.
Custom Tailwind themes, WooCommerce webshops, payment gateway integration (Stripe, Barion, OTP). Plugin development, secure hosting, WP-CLI deploy.
Auth (NextAuth, Clerk or Supabase Auth), RBAC, audit log. Next.js + Tailwind admin UIs against REST or GraphQL APIs. Flows shipped with handover protocols.
next-intl based, locale-aware routing, organized translation keys, static generation per locale. Each language separately indexable with hreflang tags.
Output
Go-live is not the end, it's a handover. You receive every artifact below, and your team can work with all of them.
Next.js app in TypeScript strict mode, ESLint + Prettier config, lint-staged + Husky pre-commit hooks. Repo under your GitHub or GitLab org.
Colors, spacing, typography as a Tailwind config, component inventory with screenshots. Storybook is optional but available.
Vercel project setup, preview deploy on every PR, custom domain config, environment variable documentation.
Sitemap.xml, robots.txt, schema.org markup (Organization, FAQPage where relevant), Vercel Analytics or Plausible enabled.
Beyond on-page technical SEO (markup, sitemap, Core Web Vitals), we write SEO copy and can build an AI-assisted blog content pipeline if you need one.
Desktop + mobile Lighthouse + Core Web Vitals, 90+ across every category. Regression checks in CI.
Content editing guide (CMS usage), list of reusable components, developer onboarding doc.
Conversion, performance and error trends from the first 3 months, plus a recommendation list for the next quarter.
Process
Six steps from discovery to support. The domain-specific content is tailored per project type.
Business goals, target audience, competitor audit, SEO analysis, information architecture.
Wireframe, Figma high-fidelity, mobile + desktop UI, design system.
Next.js + TypeScript, agile sprints, code review, Vercel preview deploy on every PR.
Unit + integration test (Vitest), E2E (Playwright), accessibility audit, cross-browser.
Lighthouse audit, SEO indexing, monitoring (Sentry), error tracking, analytics setup.
90-day post-launch loop, content updates, A/B test, fine-tuning.
Architecture
Modern Jamstack architecture: the frontend is statically generated and served from a CDN, dynamic content runs through serverless APIs. Scalable and fast.
Client
Edge
App
Backend
The user's browser gets static HTML and assets from the edge CDN — this is the secret to sub-second LCP. Dynamic content (form submit, customer portal, payments) runs via Next.js Server Actions or serverless API routes.
The backend can be a coupled CMS (Sanity, WordPress), your own REST/GraphQL API, or a 3rd-party service (Stripe, HubSpot). Frontend and backend aren't tightly coupled — if a backend needs to be swapped, the frontend stays on the contract.
Stack
Proven, documented tools. When the project justifies it we deviate — but we always explain why.
Integrations
Typical 3rd-party integrations we wire into Next.js projects.
Timeline
A medium-complexity Next.js project runs 10–12 weeks. A small landing site 4–6 weeks; a complex webapp with customer portal 14–20 weeks.
Business goal, audience, competition, IA, scope finalization.
Wireframe, hi-fi Figma, design system, mobile + desktop.
Next.js development in agile sprints, Vercel preview deploy on every PR.
Cross-browser, accessibility audit (axe), Lighthouse, content review.
Domain cutover, monitoring on, SEO indexing, analytics validation.
Limits
It's more honest to clarify upfront. Some kinds of work we intentionally don't take on — either it's not our profile, or we can't ship it at the quality we'd put our name on.
If you need a finished site plus hosting and minor maintenance, a dedicated hosting partner is more appropriate. We work in the build + 90-day post-launch combination.
Game development is its own craft — others do it better. And we don't quote on illegal or ethically problematic projects, regardless of budget.
First week
A one-page landing is live in 1-3 days. The schedule below applies to complex — multi-page, integration-heavy — projects.
Monday
60 minutes — business goal, stakeholders, success metric. Onboarding pack handed over.
Tuesday
Brand assets, existing content, voice, baseline SEO keyword research.
Wednesday
Domain, DNS, current platform, analytics access, integration partners.
Thursday
Information architecture, main user flows, initial wireframe sketch.
Friday
A 10–12 week outline, milestones, decision points, scope refinement.
Pricing
Three engagement models. Each one comes with a precise scope after discovery — concrete numbers follow once we've seen the project.
After discovery, fixed price and fixed deadline. Clear scope document, change request process, milestone-based delivery. Go-live date pinned in advance.
Ideal when
Marketing site, brochure site, webshop with core features, B2B SaaS landing.
Weekly or bi-weekly sprints, transparent time logging, priority-driven backlog. Scalable team size, flexible scope.
Ideal when
Customer portals, internal admin, B2B SaaS products where scope is evolutionary.
Monthly fixed capacity (e.g. 40–80 hours), SLA-like ticket handling, minor feature work and bug fixes. Predictable monthly cost.
Ideal when
Post-launch maintenance, smaller feature work, content site upkeep.
Calculator
5 questions, 60 seconds — an indicative price range for your own project.
Case studies
Anonymized cases that fit this pillar. Detailed write-ups are prepared from our project logs.
FAQ
Next step
Concrete scope, transparent pricing, documented delivery. The first 30-minute call is free, and after NDA we share concrete numbers.