Next.js | React | Node.js
Next.js and React on the front, Node.js and APIs behind it. The internal tools, customer portals and custom applications a commerce platform cannot be, built by someone who knows what it has to talk to.
In one paragraph
Applications built on Next.js, React and TypeScript with Node.js services behind them, over REST and GraphQL: customer and dealer portals, internal operations tools, reporting dashboards, and custom products that sit alongside a commerce platform rather than inside it. The useful difference from a general web agency is that these almost always have to agree with a store, an ERP or both, and the integration is usually where the project actually lives.
What this is
A lot of the work described as eCommerce is not inside the store at all. It is the portal a dealer logs into, the tool the operations team uses to fix what the store got wrong, the dashboard that answers whether last month was good. Commerce platforms are built to sell things, and they are poor at being all three.
What makes these projects succeed or fail is rarely the frontend. It is whether the application and the systems it depends on agree about state, under load, when one of them is briefly unavailable. That is the part this work takes seriously.
What this page is not
This is application development. If what you need is a storefront built on an existing commerce platform, the Magento and Shopify pages are the right ones.
What usually brings this in
The operations team runs the business out of spreadsheets.
Nothing is auditable, two people know how it works, and onboarding a third takes months.
B2B customers want self-service and there is nowhere to send them.
Order status, reordering and invoices all arrive by email, which is a cost that scales with revenue.
The reporting everyone relies on is a manual export.
Decisions are made on numbers that are a week old and occasionally wrong.
An integration was built once and nobody will touch it.
It fails silently, the failures are found days later, and the fix is always manual.
What gets built
- Customer and dealer portals
- Authentication, account hierarchy, order history, reordering and invoice access, reading from the commerce platform and the ERP rather than keeping a third copy of the truth.
- Internal operations tools
- The things the team currently does in spreadsheets, with permissions, an audit trail and validation that stops the mistakes the spreadsheet allowed.
- Dashboards and reporting
- Numbers pulled from the systems that own them, on a schedule or live, with the definition of each metric written down so two departments stop disagreeing about revenue.
- API layers and integration services
- A service that sits between systems and owns the translation, with retries, idempotency and observable failure, rather than a cron job nobody is watching.
- Rendering strategy that fits the content
- Static, incremental or server-rendered chosen per route against what the data actually does, because the wrong choice is either a stale page or an unnecessary server bill.
Technologies
- Frontend
- Next.js
- React
- TypeScript
- Tailwind CSS
- Backend
- Node.js
- PHP
- GraphQL
- REST APIs
- Data
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Elasticsearch
- Infrastructure
- AWS
- Vercel
- Docker
- GitLab CI
- Jenkins
How delivery runs
Scope, in writing
What the work is, and what it explicitly is not. The second half is the one that protects both of us, and it is written before anything is quoted.
Architecture before code
The data model, the integration points and the failure modes, agreed on paper. Most of the expensive mistakes in commerce are made here and discovered six weeks later.
Build in reviewable slices
Work lands in increments you can see running, not in one drop at the end. You find out early if something is going the wrong way, which is when it is still cheap.
Test against the real thing
Production-shaped data, production-shaped traffic. A checkout that works on twelve test products tells you nothing about one carrying a hundred thousand.
Deploy, document, hand over
Release process written down, documentation aimed at your team rather than at me, and a defined window afterwards where fixes are mine.
Relevant builds
- Custom platform · B2B
Procurement and approvals platform
Scalable B2B procurement platform streamlining purchase requests and approvals.
- B2B workflows
- Approvals
- Integrations
- Web platform · Manufacturing
Engineering manufacturer platform
A modern engineering brand platform built for discovery and enquiry.
- Web platform
- Technical SEO
- Content
Questions
- Do you only build things connected to eCommerce?
- Not only, but that is where the work is strongest, because the domain knowledge is what makes the integration decisions good. A business application with no commerce component is well within scope; a project where the value is entirely in a field I have never worked in is not the best use of your budget.
- Can you work inside our existing codebase and team?
- Yes. That is contract engineering: your repository, your board, your review cycle, your definition of done, for a fixed term. The pricing page covers how it is structured.
- Do you use a database, and which one?
- Whichever the data shape argues for, which is usually PostgreSQL or MySQL. The more useful question is normally whether the application should own data at all, because a second copy of the truth is how two systems start disagreeing.
- What about hosting and deployment?
- AWS where there is existing infrastructure to fit into, Vercel where the application is Next.js and the team is small. Either way the release process gets written down, because a deploy only one person can do is a risk rather than a convenience.
Describe what is in front of you and you get a written scope and a figure, usually within a few days of a short call. No charge for either.