SAP to open-stack ERP migration
Manufacturer, 500+ employees. Phased migration off SAP ERP onto an open stack with custom modules — run in stages while the plant kept working.
- 0 downtime
- 8 mo migration
- −40% on licences
Next.js development for products where the first screen is a business metric
Next.js is what you pick when search traffic and first-load speed decide revenue — and what you regret picking when a static site would have done the job for a tenth of the running cost.
What we can show you
Overview
Why teams reach for Next.js
React renders in the browser; Next.js decides where and when rendering happens — which is exactly what search engines and slow phones care about.
What Next.js is actually for, and what it costs to run
A plain React application ships an empty page and fills it in with JavaScript. That is fine behind a login and expensive in front of one: crawlers see less, and a mid-range phone spends a second or two on script execution before anything appears.
Next.js moves that work to build time or to the server, adds routing, image handling and a caching model. The price is operational: you now have a server-side runtime to host, monitor and pay for. That trade is worth making when organic traffic or first-load speed carries revenue, and not otherwise.
When Next.js is the right call
When SEO matters, when the first screen has to be fast on a cheap phone, or when public pages and a logged-in product share one codebase. For a purely internal application, plain React or Vite is simpler and cheaper to run.
Signals a project belongs on Next.js
- organic search is a real acquisition channel, not an afterthought;
- the public part of the product must be indexable;
- Core Web Vitals are being watched by someone in marketing;
- the same team maintains both the site and the application;
- content changes often and cannot wait for a full rebuild.
Price
From $7,990
Timeline
3 weeks to first release
Payment
50/50 by milestone
Comparison
Next.js, a static site generator, or a React SPA
Three answers to «how does this page reach the user», with different bills attached.
Criterion
Static siteNext.js
Next.jsStatic generation
Search visibility
Excellent
Excellent
Content that changes hourly
Rebuild the whole site
Regenerate the page that changed
Personalised or logged-in views
Not really
Native
Hosting cost
Pennies on a CDN
A runtime you pay for and monitor
Operational complexity
Almost none
Real: caching, cold starts, revalidation
When it wins
Brochure and docs sites, rarely changing content
Catalogues, marketplaces, products with a public and a private side
Scope
What we build with it
Where this stack earns its place in a project, and what we would use instead if it did not.
Marketing and content surfaces that convert
Pages that rank and load fast, with the CMS your marketing team already uses behind them.
Storefronts and catalogues
Product pages rendered on the server, filters that survive the back button, and image handling that does not eat the budget.
Product apps with a public side
A logged-in application and a public, indexable surface in one codebase, without two teams and two deployments.
Migrations from a React SPA
Route by route, keeping the app running, usually driven by a search-visibility problem.
Fit
When it is the right call — and when it is not
The best stack is usually the one your team can maintain after we leave.
Right for
Products where organic traffic matters, where the first screen has to be fast on a mid-range phone, or where public pages and an application share a codebase.
Not right for
A purely internal tool behind a login, or a brochure site: the first needs no SSR, the second is cheaper and calmer as static generation — and we will say so.
Rates
$28–55/hour by role
Fixed builds
From $7,990
Discounts
Dedicated −10% · partners −15%
How we work
Rendering strategy is a product decision, not a technical preference
The part that is specific to this stack rather than true of every project.
Why us
Why teams bring us in for this stack
Four things we can prove, not four adjectives.
Rendering decided per route, in writing
Each route gets a documented choice — static, incremental, server or client — with the reason. That document is what keeps the hosting bill explainable a year later.
Performance budget enforced in CI
Bundle size and Core Web Vitals measured on a mid-range Android, not on our laptops, with the build failing when a regression lands.
No vendor lock-in by default
We deploy to Vercel when you want it and to your own cloud when you do not. The infrastructure is code either way.
Your repository from commit one
Code, CI and content model live in your accounts, with IP assigned at delivery and a documented chain of title.
Industries
What we buildfor your industry
Next.js earns its keep where public pages carry revenue: property listings, marketplaces, e-commerce catalogues and content-heavy SaaS.
- IT companies and digital agencies
- Insurers and brokers
- Lenders and microfinance
- E-commerce
- Wholesale and distribution
- Manufacturing
- Freight and forwarding
- Clinics and medical centres
- Dental
- Car dealers and service centres
- EdTech
- Legal and consulting firms
- Equipment rental
- Real estate agencies
- Property developers
- Travel and events
- Beauty and wellness
- Construction and renovation
FAQ
Questions we get about this stack
Answered by the people who would do the work, not by a sales team.
Why Next.js if we already have React?
For anything the public has to find and load fast. Next.js adds server rendering, static generation and routing; behind a login, plain React remains simpler and cheaper to run.
SSR or static generation?
Per route, not per project. Prices that change hourly need server rendering or incremental regeneration; a docs page does not. We write the decision and the reason down.
What does it cost to host?
More than static, less than a full application platform. We model the running cost during scoping, because server-rendering everything by default is the classic Next.js budget mistake.
Do we have to use Vercel?
No. Vercel is convenient and we deploy there when you want it, but your own cloud with containers works fine and keeps the bill predictable.
Can you migrate our existing React app?
Yes, route by route while the app keeps running. These migrations are usually driven by a search-visibility problem, so we start with the pages that need to rank.
How do you measure Core Web Vitals?
Lab measurements in CI on a throttled mid-range device profile, plus field data once the site is live. A regression fails the build rather than waiting for a complaint.
2–4×
faster on the code-writing share
in 3 weeks
from idea to MVP
230+
projects delivered
17 years
of engineering experience
Work
Work we can show you
SMARTWILL
Digital inheritance service (Web3)
AIRDEVELOPPA
Indoor air quality finder driven by sensor data
CAR5
Car-sharing app
APP.DENTAL
Cloud CRM for dental clinics
NEXORA
Warehouse and logistics management platform
As-built docs
Digital as-built documentation
EX211
Telegram Mini App for currency exchange
SMARTWILL
Digital inheritance service (Web3)
Need this stack with a senior review included?
Tell us what exists today — a green field, a legacy codebase, or a team that needs two more pairs of hands. We answer with a scope, a price and a date.
We do not take work on a stack we cannot review internally at senior level.