Tech · Next.js

A Next.js developer
with no agency in between.

Next.js is the stack I work in every day. Not because it is popular, but because it combines the two things you normally have to choose between: a site Google can simply read, and an application that feels like nothing is loading. You talk to the person who builds it, not to an account manager.

Sound familiar

When people call me for this.

01

Your site is slow and it costs you rankings

Core Web Vitals in the red, a homepage that spins for seconds. Usually it is too much client-side JavaScript for something that should have run on the server.

02

WordPress has outgrown itself

Every feature is a plugin, every plugin an update, and nobody dares update anymore. At some point rebuilding is cheaper than gluing.

03

Your React app cannot be found

A single-page app without server rendering is, to a search engine, largely an empty page with a loading spinner.

04

The previous developer is gone

A half-finished project, no documentation, and a repository nobody dares go into. Taking that over is a job in itself.

05

You need capacity temporarily

A team stuck on a migration, an App Router move or a deadline. A few weeks extra, then gone again.

06

Site and application are two separate worlds

Marketing site here, portal there, two styles, two logins. That can be one codebase with one design.

How it works

How a track like this runs.

01

Look first, quote after

You send the site or the repository. Within two working days I try to tell you what is going on and whether building on beats starting over. That opinion costs you nothing.

02

Fixed price, no hourly billing

You know up front what it costs and what you get. If the scope changes along the way, you hear it before it is built, not on the invoice.

03

Building in the open

A preview environment every week that you click through yourself. Changes through pull requests, so you see exactly what changes and why.

04

Delivered in your name

Repository, hosting and domain sit on your account. I am replaceable, and that is how it should be.

What you end up with
  • ✓Next.js with App Router and server components
  • ✓TypeScript, so mistakes surface before the deploy
  • ✓Meta text, sitemap and structured data built in
  • ✓Deployed on Vercel or your own server
  • ✓Repository and hosting in your name

The first opinion costs you nothing: send me the repository or a link and I will tell you honestly whether building on beats starting over.

Reviews

Clients rate me
5 stars on average.

“I am extremely happy with the result of my new website for DoubleStreet Australian Cobberdogs, made by Webframer. From first contact, Webframer radiated expertise and creativity.”
Ben VorsteveldDoubleStreet Australian Cobberdogs
“Webframer helped me enormously with the Veldvisuals website. It is not only good to spar with Bas about building the site, but also in the aftercare and whenever changes have to be made. Recommended!”
Nick in 't VeldVeldvisuals
“Great to work with. Listens carefully to what we want. When we ask for changes, they are made expertly.”
Marieke van 't WoutVan Der Linde Mode & Lingerie
“Really pleasant to work with and short lines of communication!”
Hugo BrandwagtGoogle review
“The website looks great!! Definitely recommended!”
Jayden BresserGoogle review
“Excellent! Fast service and good contact!”
Devin de WaardGoogle review

Translated from the Dutch originals on Google.

Bas Voets, founder of Webframer
Who builds it

I am Bas Voets. Since 2021 I have been building websites, client portals and business software for small and mid-sized companies, from Hazerswoude-Dorp in the Netherlands. From first call to launch you talk to me, not to an account manager.

CoC 70168741 · since 2021 · Hazerswoude-DorpMore about me
Frequently asked questions
What does hiring a Next.js developer cost?
I work per project, not per hour. You get one fixed number for an agreed scope, so no reckoning afterwards and no surprise on the invoice. If you do not know what you need yet, we work that out in the first call.
Can you take over an existing project?
Often yes. I read through the codebase first and tell you honestly whether building on is sensible. Sometimes the answer is that part can be saved and part cannot; you hear that too.
Do you also work inside an existing team temporarily?
Yes, for defined blocks of a few weeks. In your repository, with pull requests, so the team follows along and takes it over the moment I leave.
Why Next.js and not WordPress?
For a brochure site that never changes, WordPress is fine. As soon as data, logins or custom work come into it, you are done faster with Next.js and you have less maintenance and fewer security updates afterwards.
Let's build

Tell me what you
want to build.

A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.

Free · no obligation

Have your current site or tool scanned

You do not have to want to buy anything yet. Send what you have and I will tell you honestly what I would keep, what I would replace and whether that is worth the investment. Including when the answer is that you are better off doing nothing.

The scan is a first impression, not a security audit.

WhatsApp
0:00 / 0:00
  1. 01Send a link to your site, your tool or your repository
  2. 02I look at speed, structure, data and security
  3. 03Usually within two working days you hear what I would replace and what that costs
Bas Voets · Webframer
0:00 / 0:00
Hire a Next.js developer · Webframer