Development
Web development
SaaS platforms, customer portals, dashboards, admin panels and online stores on Next.js and React: tables, filters, charts, authentication and the wiring to your API.
- Reply to your brief
- within 24 hours
- First call
- 30 minutes, no commitment
- First working version
- in 3–4 weeks
Process
What happens, and when
The work is split into stages, and each one has a named result. You see it yourself rather than reading about it in a report.
Days 1–5
Understanding the product
We work out what the product is and who needs it: flows, roles, the boundary of the first version, not a promise to “build a website”.
You get — A list of screens and an estimate
Weeks 2–3
Screens and data schema
We design the screens and the data schema: what the user sees, what gets stored, what queries that creates. The stack is chosen here, for the task rather than by habit.
You get — The data schema and the chosen stack
From week 4
Build in weekly stages
We build a working version in weekly stages. Each one ends with something you can open in a browser and click, not a percentage of completion.
You get — A working version to open in a browser
Before launch
Onto the server
We put it on a server: domain, certificate, backups, monitoring and logs. Speed and behaviour on a phone get checked before users hear about the product.
You get — Domain, certificate, backups and monitoring
After launch
Fixes and further work
We fix what real users find and keep developing it — as a monthly block of hours or as separate tasks.
You get — Fixes for what real users found
What the work covers
Building the interface from the design
layout for phone, tablet and desktop, enquiry and contact forms with validation
Portals and dashboards
tables, filters, charts, routing and movement between screens
Catalogue and checkout
categories, search, product pages, cart, order placement, payment and delivery services wired in
Wiring the interface to the server
API calls, sign-in and sessions on tokens and cookies, what happens when a request fails
Indexing and speed
meta tags, readable URLs, sitemap and robots, server rendering, the weight of images and styles
Work on a codebase that already exists
narrow changes that leave the rest of the project alone, plus a note on what was wrong, why, and how to check it
What we need from you
- A Figma file, or an existing site to build the interface from
- If the interface talks to a server that already runs: access to its API and documentation
- For a project already in flight: the repository and a list of what to fix or add
Projects in this area
Logistics
Reista
A client portal for a haulier: consignment status, route and paperwork for every delivery, with no call to the dispatch desk. The portal was the smaller half of the job — before it, no system held a status at all: it lived in drivers’ messages and in a dispatcher’s memory.
−70%
calls to the dispatch desk
Next.js · TypeScript · PostgreSQL
Fintech
Splitta
Instalments for online stores: buyer checks, a payment schedule and refunds — on real payments from day one.
7 weeks
from first call to production
Next.js · Node.js · Docker
What people usually ask
Contact
Send a description of the task
A reply with the scope, the timeline and a budget estimate comes within 24 hours.
The first call is 30 minutes, with no commitment on your side.
01
You describe the task
Five questions in the form, or a plain email — whichever suits you.
02
We answer within a day
With the scope, the timeline and a budget estimate, based on what you told us.
03
We talk for 30 minutes
To clear up whatever is unclear. It commits you to nothing.