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
React development that a second team can pick up
Most React problems are not React problems. They are state kept in three places, a component library nobody documented, and a bundle that grew until the phone gave up.
What we can show you
Overview
The cost of owning a front end
Most React problems are not React problems: state in three places, an undocumented component library and a bundle that grew until the phone gave up.
What a React front end costs to own, not just to build
React is a rendering library, not an architecture. What decides the cost of ownership is what you put around it: a component library with documentation, one place per concern for state, tests on flows and a bundle budget that a build can enforce.
That is why we quote a React project by interface complexity and permission rules rather than by screen count — screens are cheap once the system underneath is right.
When React is the right call
Interactive products, dashboards and anything that will keep being built on. A content site that needs SEO and not a single-page app is cheaper and faster as static generation — and we will say so.
Signals React fits your front end
- the interface is stateful: filters, tables, multi-step flows;
- several screens share components and rules;
- more than one developer will touch it;
- you need accessibility and performance to be measurable, not assumed;
- the same team or the next one will keep extending it.
Price
From $7,990
Timeline
3 weeks to first release
Payment
50/50 by milestone
Comparison
React SPA or server-rendered pages
The decision that most affects SEO, first load and the size of the team you will need.
Criterion
Server-renderedReact application
React appServer-rendered site
Search visibility
Best by default
Needs SSR or prerendering
First load on a mid-range phone
Fast
Depends on the bundle budget
Rich interactivity
Awkward past a point
What it is for
Team skills required
Lower
Front-end specialists
When it wins
Content, marketing, catalogue pages
Dashboards, editors, multi-step flows
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.
Product interfaces
The screens your users live in, built on a component library rather than copy-paste, so the tenth screen costs less than the first.
Dashboards and admin
Data-dense interfaces with tables, filters and permissions that behave the same on every screen.
Design systems
Tokens, components and documentation — the thing that stops two developers inventing two buttons.
Front-end migrations
From jQuery, Angular 1 or an abandoned SPA, done page by page rather than in one heroic rewrite.
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
Interactive products, teams that will keep building on it, and anything needing a shared component library across several screens or apps.
Not right for
A content site that needs SEO and does not need a single-page app — static generation or server rendering is cheaper and faster there, and we will say so.
Rates
$28–55/hour by role
Fixed builds
From $7,990
Discounts
Dedicated −10% · partners −15%
How we work
What we consider a finished front end
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.
Accessibility as a delivery criterion
WCAG AA on the flows that matter, checked with keyboard and screen reader — not with an automated score alone.
Performance budget in CI
Bundle size and Core Web Vitals enforced by the build, measured on a mid-range Android rather than our laptops.
Documented component library
Handover includes the docs, so the next team is not archaeology-first.
State in one place per concern
The single decision that separates a maintainable React app from the one everybody is afraid to touch.
Industries
What we buildfor your industry
React front ends sit on top of our logistics, property and SaaS back ends.
- 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.
Next.js or plain React?
Next.js when you need SEO, server rendering or file-based routing; plain React inside an existing app shell. We pick by requirement, not by what is trending.
How do you handle accessibility?
WCAG AA on key flows as a delivery criterion, checked with keyboard and screen-reader passes rather than an automated score alone.
Will you take over someone else's front end?
Yes, after an audit: dependency health, state management, bundle size and test coverage. The audit tells you whether to refactor or to replace screen by screen.
Do you build the design too?
Yes, including the design system. Or we implement your designer's work and tell you where it will be expensive.
How do you keep performance from decaying?
A bundle budget in CI and Core Web Vitals in monitoring, so a regression is caught by a build rather than by a user.
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.