React Development Services with Rendering Done Right
Billion Game
Book a strategy call

{{ col.title }}

{{ feature.tag }}

{{ feature.title }}

{{ feature.copy }}

{{ feature.cta }} {{ feature.cta }}
Next.js · rendering · performance

React development services

We build React applications and websites: Next.js and React Router projects, component architecture and design systems, rendering strategy, performance work, API and headless CMS integration, and migrations from legacy frontends. Where the product needs to be found, we get rendering right, which is where most React projects quietly fail.

React is the default choice, which means it gets chosen without a decision being made. The consequence shows up in two places: rendering, where a content product ships as a client-rendered SPA because that is what the starter template did, and bundle weight, which nobody owns. Both are architectural decisions made by default rather than on purpose.

Bundle analysis, rendering strategy per route, real-user performance, and what crawlers actually receive · five business days

Scope it roughly estimating
Engagement
Codebase state
Typical band
{{ scopePrice }}
End to end
{{ scopeTime }}
What decides the number

{{ scopeNote }}

Fixed price on defined scope. For genuinely uncertain application work we scope a paid discovery phase rather than quoting a number that will move.

Before you enquire

What you are actually looking for

Four things nearly every enquiry turns out to be about, in the words people actually use.

{{ askTyped }}
The honest answer

{{ ask.title }}

What you mean

{{ ask.mean }}

What we do about it

{{ ask.doing }}

What you end up with

{{ ask.get }}

In practice

What the work looks like

Screens from live engagements, with client details removed.

The main view

{{ gTitle }}

{{ gr.label }} {{ gr.hits }} {{ gr.chip }} {{ gr.pct }}
{{ gStatLabel }} {{ gStat }}

{{ gNote }}

{{ gListTitle }} {{ gListCount }}

{{ gListNote }}

{{ gStackTitle }} {{ gStackTotal }}
{{ gw.label }} {{ gw.value }}

{{ gStackNote }}

Scope

What we build

Thirteen kinds of work, including the authenticated products where SEO is irrelevant and we will not pretend otherwise.

{{ r.num }}

{{ r.a }}

{{ r.b }}
Try it · interactive

Where React projects go wrong

Six architectural causes. React makes it easy to build quickly and provides no opinion about architecture, which is a strength at the start and a liability at scale. Tick what you recognise.

The pattern: React makes it easy to build quickly and provides no opinion about architecture. That is a strength at the start and a liability at scale, and the gap is filled by whoever is disciplined enough to make explicit decisions.

{{ problemCount }} of 6 recognised
{{ verdictTag }}

{{ verdictTitle }}

{{ verdictBody }}

What each one costs you
• {{ c }}
Nothing ticked yet. Pick whichever ones sound like your codebase and the cost of each appears here.
Architecture

Rendering strategy

The decision that matters most, and the one most projects skip.

Strategy How it works Right for
{{ r.a }} {{ r.b }} {{ r.c }}
Interactive · per route, not per project

Pick a route. Get the strategy.

The mistake is treating this as one decision for the whole application. Your marketing pages and your dashboard have opposite requirements, and modern React frameworks let you choose per route.

{{ d.label }}

Change frequency does not affect the answer behind a login. Nothing there needs to be in the initial HTML, so the question becomes bundle weight instead.
{{ pickTag }}

{{ pickTitle }}

{{ pickBody }}

The trade-off

{{ pickTrade }}

In the initial HTML

{{ pickHtml }}

△

The crawler point, stated once: search engines execute JavaScript with delays and constraints. Most AI crawlers do not execute it at all. If a page needs to be found or cited, its content must exist in the initial HTML response. That is a rendering decision, not an SEO task to add later.

Stack

What we actually use

Being specific, because a technical buyer will ask.

Layer What we typically reach for
{{ r.a }} {{ r.b }}
⇄

We adapt to your stack rather than imposing ours. If you are on a different combination and it works, we work in it. The above is what we choose when the choice is genuinely open.

Incremental by default

Migrations

{{ m.glyph }}

{{ m.title }}

{{ m.body }}
⚠

On rewrites generally: we recommend incremental migration in almost every case. Full rewrites have a poor track record, and the version of this project that ships is usually the one that never had a hard cutover.

Deliverables

What you receive

The actual documents, not a sample deck built for the pitch.

Engineering spec

React performance and architecture review

22 routes · 74 dependencies · 1 bundle

01Bundle composition per route 02Dependency keep or replace 03Rendering and memoisation 04State management boundaries 05Testing and CI additions
B Written as PRs, not as advice
Report
Codebase health at handover
Bundle size310 KB
Time to interactive1.4s
Component reuseGood
Test coverage44%

Test coverage is the lowest bar and the one your team should own from here.

Priorities
Per-route report
Route Was Now
/dashboard11.2s1.6s /reports9.4s1.9s /settings8.1s1.1s /onboarding7.6s1.0s /billing8.8s1.3s

Time to interactive per route on a mid-range device.

Handover
Pricing

React development pricing

Fixed price on defined scope. Paid discovery where the scope is genuinely uncertain.

01 · What do you need
02 · How big {{ estSizeLabel }}
Small Very large
03 · Anything else
Estimate {{ estUnit }}
{{ estLow }} to {{ estHigh }}

{{ estNote }}

{{ eb.label }} {{ eb.value }}
Get this scoped properly

An estimate, not a quote. Fixed price follows a scoping call, and where requirements are genuinely uncertain we run a paid discovery phase first.
Process

How we work

Five commitments, all of them checkable.

{{ m.glyph }}

{{ m.title }}

{{ m.body }}
Fit

Who we work with

{{ f.glyph }}

{{ f.title }}

{{ f.body }}
∅

Probably not us if you need a simple brochure site. React is the wrong tool and we will point you at Webflow or WordPress instead.

Free · five business days

Get a free React app review

Including a crawlability and extractability check: what search engines and AI crawlers actually receive from your key pages.

  1. {{ a.n }} {{ a.text }}
Build walkthrough Screen share · {{ gLoomTime }}
{{ gc.label }}

Requires repository read access, or a deployed URL for the non-code portions. If the codebase is sound and the answer is three dependency changes, we will tell you that.

{{ whyNote }}

Rough is fine. It tells us which parts of the review will be substantial before we open anything.

No sales sequence. A developer reads the code and writes the review, and you will be able to tell.
✓

Request received.

{{ sentNote }}
Evidence

Before and after

The same view, before the work and after it.

Before
{{ gf.label }} {{ gf.pct }}

Most users waited through a blank screen and a spinner before anything responded.

After
{{ gf.label }} {{ gf.pct }}

Same app, same features, delivered in the order people need them.

Our stack

Billion Game runs your work through the same instruments the best in-house teams use.

Licences are on us, and every export we pull from them is yours to keep.

{{ s.alt }}
✎

Be wary of any agency whose reporting is a tool dashboard with their logo on it. Tools measure; they do not decide what matters, and every one of these will happily generate a hundred findings that change nothing. What you are paying for is the judgement about which three of those hundred are worth your developers’ time.

FAQ

React development FAQs

Anything not answered here, ask us directly.

The short version

Use a framework. Choose rendering per route, not per project. Give the bundle an owner and a budget. One state solution per category. Profile before optimising. And build assuming somebody else maintains it.

{{ f.a }}

Rendering is an architecture decision, not an SEO task.

Free app review covering bundle, rendering, performance, architecture, and what crawlers actually receive. Five business days.