Web apps that reinforce
the system you already have.
The system stays. What changes is who talks to it.
There's a management system that works and there are people who never open it: those screens were never designed for them. We put a web app in front that speaks their language and writes into the system that's already there.
The same order, seen from two sides.
On the left the management system screen: it does everything, which is why it looks like that. On the right the same thing for a rep in a showroom. A rep uses nine fields, and if getting to them means skipping thirty, the order ends up on a sheet of paper.
Sizes and colours. The screen where it's won or lost.
In a campaign an order is hundreds of cells. The grid behaves like a spreadsheet - arrows, direct typing, paste a block - and Excel import/export are always there.
Four colours, seven sizes, twenty-eight cells for a single item. In a campaign there are two hundred items: this is where it's decided whether the rep uses the web app or goes back to the spreadsheet.
Preorders and campaigns
Campaigns opened and closed on dates, price lists per season, orders collected before the goods exist. The difference between a preorder and a normal order isn't a flag: it changes availability, confirmations and deposits.
Size and colour grid
Different assortments per item, sizes that can't be ordered, minimums per colour, predefined packs. These are the constraints that make orders go wrong when the software doesn't know them.
Warehouses and availability
Multiple warehouses, committed stock, what's arriving and when. The rep needs one answer: can I sell this or not. The calculation behind it is never a subtraction.
Price lists and client terms
Different prices, tiered discounts, payment terms, deposit percentages. They already live in the management system: the web app applies them, it doesn't reinvent them.
An off-the-shelf platform asks you to adapt the process. Here it's the software that adapts to you.
And then there's whoever asks "where is my order?"
The same web app shows the client their orders, price lists and terms - and the next order they can enter themselves. Deposit request, confirmation and reminder go out on their own.
- 02 AugOrder enteredBy the rep in the showroom, or by the client themselves.
- 02 AugDeposit requested30% per the client's terms. Email and PDF go out on their own.auto
- 05 AugOrder confirmedOrder confirmation generated from the management system's data.auto
- 10 SepIn productionA status that comes from the management system, without asking anyone.
- 15 SepShippedTracking to the client and a reminder for the balance.auto
The three steps marked auto are done by nobody: deposit request, order confirmation and reminder go out on their own, with the client's terms already in them.
The people selling
Reps, KAMs, showroom. Order entry, availability, client history - all usable standing up with a tablet in hand.
The client watching
Progress of their orders, documents, price lists and terms. The "where are we" email stops arriving.
The client ordering
They enter it themselves, with their prices and their constraints already applied. The order lands in the management system without anyone retyping it.
We do the adapting. You change nothing.
We connect to the management system's database as it is: reading, we take what's needed; writing, we go only through the routes the system provides. Your codes stay yours.
It starts from whoever will use it. Not from the specification.
- $ 01 · watch
Half a day with whoever will use it - including the spreadsheet they keep on the side.
- $ 02 · build
One screen at a time, in a real person's hands before building the rest.
- $ 03 · widen
Inside first, outside after: the same web app with different permissions.
If the process you have in mind is already the industry standard, an off-the-shelf platform costs less and starts tomorrow: we'll say so. Bespoke pays off when your way of selling is part of the value.
The projects completed over the yearsGo to the case studies