A website built around your requirements.

Choose code for a reason.

Next.js can fit a team that needs custom website behaviour, a connection to a React product or control over content rendering. A developer-maintained codebase also creates an ongoing responsibility for releases, hosting and dependencies.

If your main need is a visual publishing workflow, we compare that requirement with Framer before committing to a custom stack. The choice should fit your team, not just the design file.

A defined marketing-site build.

• Page structure, custom responsive UI and reusable components.
• Server-rendered or prerendered content where appropriate to the page.
• The agreed forms, interactions and third-party integrations.
• Metadata, canonical URLs, sitemap and redirect requirements.
• Cross-device QA, deployment and source-code handover.

This website is a working example.

been.design itself runs on Next.js. Its service pages, guides and case-study text are delivered in the page HTML. The homepage uses a sticky A/B assignment, while analytics and visual behaviour recording follow the site's consent settings.

Those are features implemented for this website. They are not included in every client quote. Our Framer case studies remain labelled as Framer work; they are not recast as Next.js builds.

Decide how content will change.

A React framework does not provide a finished editorial workflow for your business. We agree whether the project uses files, a CMS or another source, and which changes a content editor can make without a developer.

Hosting, account ownership, source access and maintenance need an owner. We include the required handover detail in the proposal instead of assuming someone else will manage it after launch.

Bring the integration requirements early.

Share the existing stack, content model, required forms and any system the website must connect to. We review what belongs in the website and what belongs in a separate application before setting the scope.

Before you decide.