Admin dashboards and internal tools · Build
Admin panels built around how your staff work all day
Back-office tools in React and Next.js for staff who spend the day in one system. On a construction ERP, staff find any of 150,000+ items down to the shelf.
EngagementHourly · remote
Hours9–18 CET · 4 h overlap
StackReact · Next.js · NestJS
Proof4 case studies
The service in 4 parts
01 · Who it’s for
A company whose staff spend the day in one system: stock, crews, listings, invoices. Often it has to run alongside an existing system that isn’t going away, and the data in both has to match.
02 · What we’ve built
- A construction company’s ERP, where warehouse staff find any of more than 150,000 items spread over 15 warehouses down to the shelf, and planners assign crews by trade to sites in several countries. We built its ten modules in six months.Case study 16 →
- A live dashboard for advertisers on a US platform for truck services. For accounts with more than 900 listings, a full year of history loads in under a second.Case study 05 →
- On the same platform, a separate CRM for the company’s own staff. It talks only to the admin set of API routes, which is kept apart from the routes customers use.Case study 08 →
- Six jobs that run on their own every day to handle renewals, downgrades, recurring charges and re-engagement. Their emails come from 55 templates and go out through one sending service.Case study 07 →
On the ERP, stock can be entered in three ways: by barcode in the warehouse, from the purchase order at goods-in, and by hand for everything else. With only one way in, people would start working around the system, and the stock on screen would stop matching the stock on the shelf.
03 · How we work
01 · WHERE WE STARTWe look at how the work is done today, including the spreadsheet people keep next to the current system. If the new tool ignores what that spreadsheet is for, people will go on using the spreadsheet.
02 · DECISIONSWhen we decide to build one module and buy another, we write the reason down. Anyone who later wants to change that choice can read what it was based on.
04 · Stack
ReactNext.jsNestJSNode.jsPostgreSQLMySQLTurborepoSAP integration
Proof
Where we’ve done this before
Case study 16 · Business systems150,000A construction company’s ERP, where warehouse staff find any of more than 150,000 items spread over 15 warehouses down to the shelf, and planners assign crews by trade to sites in several countries. We built its ten modules in six months.Read the case study →Case study 05 · Marketplace2M / dayA live dashboard for advertisers on a US platform for truck services. For accounts with more than 900 listings, a full year of history loads in under a second.Read the case study →Case study 08 · Marketplace506 routesOn the same platform, a separate CRM for the company’s own staff. It talks only to the admin set of API routes, which is kept apart from the routes customers use.Read the case study →Case study 07 · Marketplace6 jobsSix jobs that run on their own every day to handle renewals, downgrades, recurring charges and re-engagement. Their emails come from 55 templates and go out through one sending service.Read the case study →
FAQ
Questions about this service
Usually some of both. We would buy what every system of its kind already does and build only the part no vendor sells. On the construction ERP, that part was planning crews by trade across sites and countries.
It can. The ERP we built runs alongside SAP and keeps customers, items, orders, invoices, stock and finance in sync between the two.
Yes, as long as one database isn’t asked to do every job. On the advertiser dashboard, raw events go to one store and a daily summary per listing to another, and the yearly report reads only the summaries.
Next step
Describe the problem and we’ll come back with three options.
The first call takes 30 minutes, and you’re under no obligation.