Web apps that reinforce
the management system you already have.
The system stays. What changes is who talks to it.
There's a management system that works, paid for with years of configuration, and there are people in the company who never open it: the sales reps writing orders on a sheet and mailing them to admin, the KAM who can't use it in the showroom in front of a client. It's nobody's fault - 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 order-entry screen of the management system: it does everything, which is why it looks like that. On the right, the same thing for a sales rep in a showroom with a client waiting.
The screen on the left isn't an exaggeration: it's what anyone entering an order sees in a system configured to do everything - admin, warehouse, accounting, statistics. On the right there are only the fields the person selling needs, and the other thirty pieces of information are worked out by the system.
The point isn't that the management system is badly made: it does things the web app never will. But a rep in a showroom 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 selling campaign an order is hundreds of cells. If entering them takes one click too many per cell, the rep won't do it in the showroom - they'll do it at home in the evening, from memory, with the mistakes that come from that.
We know how much Excel gets used, and we don't pretend otherwise: the grid behaves like a spreadsheet - you move with the arrows, you type without clicking, you paste a block of cells. Anyone entering a whole order has nothing to relearn. Try filling it in.
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.
Excel import and export are always there, on every project. If the client has already prepared the order in their own sheet, they upload it and the grid fills itself in - with errors flagged line by line before confirming. And anything on screen downloads to Excel, because that's where someone will use it.
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.
These are things you only learn by doing them. Fifteen years, ten brands, more than thirty selling campaigns: the first time you hear the word capsule you don't know what it changes in the data model, the thirtieth time you know before anyone asks.
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?"
Today that question arrives by email and steals half an hour from someone in admin, who goes looking for the answer in three places. The same web app can show it to the client, along with the rest: their price lists, their terms, their past orders - and the next one, which they can enter themselves.
- 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.
If there's no management system behind it, or none is needed, the web app stands on its own: master data, price lists and orders live inside it.
We do the adapting. You change nothing.
We connect straight to the management system's database, as it is: we don't ask you to redo master data, change your codes or bend your process to our software. The work of understanding how it's built inside is ours - it's the part an off-the-shelf platform offloads onto you.
First we read how it's built
No installation is the standard one: over years of configuration every company has bent its management system to its own way of working. The first job is finding out where things actually are, and that isn't done by reading a manual.
We only write where it's allowed
Reading, we take what we need. Writing, we go through the routes the management system provides, so its own checks stay valid and nobody finds inconsistent data the next day.
Your codes stay yours
We don't ask you to rename items, redo master data or change your process to keep the software happy. The translation between your way of naming things and the web app is ours to write, once.
Connecting to the database doesn't mean writing into it at random. Reading, we read what's needed; writing, we go only through the routes the management system provides, so its rules stay valid. Who accesses what is decided row by row, and every call stays logged.
It starts from whoever will use it. Not from the specification.
- $ 01 · watch
Half a day with whoever will use it
Not with whoever writes the specification: with the rep, in the showroom or on the phone with a client. We watch how they do it today, including the spreadsheet they keep on the side. That sheet tells us which nine fields matter.
- $ 02 · build
One screen at a time, usable at once
We start from the screen that weighs most - almost always order entry - and put it in a real person's hands before building the rest. The others follow, already knowing what to correct.
- $ 03 · widen
Inside first, outside after
Once the reps genuinely use it, the same base opens up to clients: read-only first, then order entry. It isn't a second project, it's 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, and we'll help you connect it. Bespoke pays off when your way of selling is part of the value - collaborations, capsules, different terms per client, things that exist on nobody's menu.
Where we have already done it.
Real projects where this service went into production. Same logic, different contexts.
B2B portal for order and document management
A single digital channel for business customers, integrated with the company ERP.
ResultOperational autonomy for customers, manual requests to customer service eliminated.
Read the case study →Wholesale ecosystem for collections and media
Orders, replenishments, media and catalogues in a single platform, integrated with the company ERP.
ResultEnd-to-end digitised wholesale process, catalogues generated automatically, evolving since 2019.
Read the case study →The questions that come from people who already have an ERP.
How does order entry with sizes and colours work?
On a single grid: colours down the rows, sizes across the columns, a quantity per cell, and totals that update as you fill it in. It imports and exports to Excel, because that's still how a lot of orders arrive. What comes out lands in the ERP.
What is the difference between a bespoke web app and an off-the-shelf wholesale platform?
An off-the-shelf platform asks you to fit your process to its own. This is the other way round: you start from whoever will use it - the sales rep, the KAM in the showroom, the client placing the order - and the software adapts to how they work. Fifteen years, ten brands, more than thirty selling campaigns.
Does it work with Microsoft Dynamics, SAP or NetSuite?
Yes. We adapt to the ERP that's there, not the other way round: we connect to its APIs and you change nothing.
Is it only for the sales side, or for clients too?
Both. The same app the sales team uses can show a client their own price lists, their terms, their past orders and where the current one stands - so "where is my order?" stops arriving by email in the back office.