Skip to main content
LYKOS

Next.js development: sites that load before you notice

We are two developers. We build web sites and applications in Next.js, measure the result and publish the numbers. Projects from US$1,000, typical delivery in two weeks.

You probably got here for one of these reasons

  • Your site is slow and you can see people leaving before anything shows up.
  • You are on WordPress and it keeps breaking: one plugin updates, another stops working, or the whole thing goes down.
  • Google does not find you, or finds you on page four.
  • Every small change — a price, a photo, a paragraph — depends on someone having time.
  • You pay for expensive hosting every month for a site that almost never changes.

What you get

HTML built before anyone shows up

Next.js generates the pages at build time and serves them as static files from Cloudflare's network, which caches them in hundreds of cities. There is no PHP booting up and no database query on every visit: the server closest to your visitor hands over something that was already finished.

No server to go down

The site does not live on a machine someone has to patch, monitor and restart: it lives on Cloudflare's edge. There is no server to saturate under a traffic spike and no WordPress install to get compromised. Our own site runs this way and answers in 7 milliseconds.

Nothing that accumulates

No plugins each adding their own stylesheet and their own JavaScript until the page weighs five megabytes. The CSS that ships is only the CSS the site actually uses.

Core Web Vitals measured, not promised

We measure before and after with Lighthouse and hand you the numbers. If something did not improve, you will see that in the report too.

Automated deploys from day one

CI/CD set up from the start: every change passes tests and a typecheck before it ships. No FTP uploads, no file someone overwrote by accident.

A backend and database that were designed

If the project needs data, authentication or integrations, they are designed as part of the system. Not a form glued on with a plugin.

The code is yours

Your own repository, on a standard open stack. If you want to continue with another team tomorrow, nothing proprietary stops you.

How we work

Four steps, no mystery and no invented phases to make the proposal look bigger.

  1. 01

    Understand what you want to achieve

    A site built for traction is not the same as one built to present a brand or one built to sell. Everything else follows from that, including how much design investment makes sense.

  2. 02

    Design

    We do not do graphic design: we bring in a designer or work with the one you already have. We would rather say so upfront than pretend to be a full studio.

  3. 03

    Build with continuous delivery

    We do not disappear for a month and come back with a finished site. Every time a piece is done it gets deployed and you see it working. Course corrections are cheap when they happen early.

  4. 04

    Deploy, adjustments and maintenance

    We ship, and you get two weeks to request changes and fixes on what was delivered. After that, three months of maintenance and warranty are included.

What it costs

From US$1,000

We charge per project, not per hour: you know the number before we start. A corporate site in Next.js typically lands between US$1,000 and US$3,000, delivered in two weeks.

What moves the price

  • Scope: how many pages, how many sections, how much real logic sits behind them.
  • Technical SEO work: metadata, structured data, hreflang if there is more than one language, sitemap, measurement.
  • Integrations: payments, CRM, bookings, inventory — whatever the system has to talk to.
  • Design: whether it has to be commissioned from scratch or there is an existing identity to apply.

What is included

  • CI/CD and deploys configured.
  • Performance measured before and after, with the report.
  • Two weeks of adjustments on what was delivered.
  • Three months of maintenance and warranty.
  • The repository, in your name.

If your budget is US$300, you will find someone who takes it. We lost a job that way once: what they delivered was a single giant image pasted onto a page. It loaded slowly, Google could not read anything because there was no text to read, and changing a price meant exporting the image again. It was cheap once, and then it had to be done over.

One case, measured

Finca Flichman called us because their WordPress site kept going down: the installation was compromised and every fix held for a while and then failed again. We rebuilt it in Next.js. A year later we restored the original WordPress in Docker and measured it against the new site with Lighthouse, median of three runs: first contentful paint went from 3,003 ms to 1,351 ms, CSS from 93 KB across sixteen files to 13 KB across six, and third-party requests from ten to zero.

Read the full measurement, with the methodology

Frequently asked questions

How much does a Next.js site cost?
From US$1,000. A typical corporate site lands between US$1,000 and US$3,000. We charge per project, so you know the number before we start and it does not change if the work takes us longer than expected.
How long does it take?
Two weeks is typical for a Next.js site, counted from the point where the goal and the design are settled. What usually causes delay is not the development: it is getting clarity on the goal and having the design resolved.
What will hosting cost me?
Almost certainly much less than today. A static site on Cloudflare Workers does not need a server running 24 hours a day waiting for visitors, so the monthly cost is a fraction of traditional hosting and in many cases fits inside the free tier. You also do not pay for traffic spikes: the network absorbs them without anything falling over.
Someone offered me the same site for much less. What is the difference?
Almost always the difference is in what you cannot see on day one: whether the content is text Google can read or an image, whether changing a price means editing a field or remaking a file, whether the site keeps working when something updates. Ask to see the Lighthouse score of the site they are going to hand you. It is free and it takes a minute to answer.
Why Next.js instead of WordPress?
WordPress assembles the page on every visit by running PHP and querying the database, and every plugin adds weight and maintenance surface. Next.js generates the pages once and serves them statically. For a site whose content does not change hourly, that is faster, cheaper to host and far less fragile.
Do you do the design?
No. We commission it separately or work from the design you already have. We are developers: what we do well is the build, the performance and the infrastructure.
Can I edit the content myself?
It depends on how much you will edit, and we settle that before starting. If you will change text and photos often, we connect a content panel; if the content is stable, keeping it in the repository is cheaper and faster. We quote the option that fits your case, not the one that suits us.
Am I locked in to you?
No. The repository is in your name and the stack is standard and open: Next.js, React, TypeScript. Any team that works with those tools can continue it. There is nothing proprietary of ours in the way.
Can you migrate my current site?
Yes, it is one of the things we do most. We measure the current site before touching anything, rebuild it, and measure again so the improvement is a number rather than an impression. Redirects for the old URLs are part of the migration, so you do not lose the ranking you already have.
Are you a big team?
We are two. That means you talk directly to the person writing the code and there are no coordination layers — and it also means we do not take projects that need ten people. When a project is too big for us, we say so.

When we are not the right fit

  • If you need brand identity and design from scratch as part of the same contract. We subcontract that, and there are studios that do it better end to end.
  • If the project needs a team of ten. We are two, and we would rather say no than deliver late.
  • If you want a hero with a fifty-megabyte video because someone told you it helps SEO. It does the opposite, and we will not build it.
  • If the deciding factor is the lowest price. We will not win that, and we probably should not.

Tell us what you need

Write to us with what you have today and what you want to achieve. If we can help, we will tell you how and how much; if we cannot, we will tell you that too.

Let's talk about your project

We use analytics cookies (PostHog) to understand how the site is used and improve it. We don't sell your data or share it with third parties.