Every Thursday around eleven, a customer named Hugo — not his real name, he's one of those regulars every wholesale business has — calls the same number he's called for years and places the same order he places every week: forty units of one part, twenty of another, a few extras depending on the season. Someone on the team picks up, pulls up a blank order form, and types while Hugo reads off numbers from memory. It takes about ten minutes. During those ten minutes, the phone line is busy, so if another customer calls, they wait, or they call back, or — more often than anyone wants to admit — they just don't bother and the order slips to tomorrow.
Hugo isn't the problem. Hugo is a great customer. The problem is that placing his order requires a person on your side to exist as a translator between what Hugo wants and what your system needs, every single week, forever.
"We have a website" is not the same claim as "customers can order themselves"
I hear this a lot: "we already have a site, people can see our catalog." That's true, and it's also not the thing that's costing you ten minutes of staff time per regular customer per week. A catalog page lets someone look. It doesn't let them act — check what's actually in stock right now, see their own price for that specific item, submit the order, and get a confirmation, all without anyone on your team touching a keyboard on their behalf.
Self-service and "having a website" are different claims. Most B2B businesses have the second one and assume it covers the first.
The cost compounds because it repeats
A ten-minute phone order doesn't feel expensive in the moment. It feels expensive when you multiply it by every regular customer, every week, for as long as that customer keeps ordering — which, for your best customers, is years. That's not ten minutes. That's a permanent staffing cost built entirely around manually retyping things your customers already know, into a system they're not allowed to touch themselves.
And it's not just the typing. It's the phone line tied up during that call, the transcription error that happens when someone mishears "thirteen" as "thirty," the order that gets written on a sticky note because the person taking it was mid-call with someone else, and the fact that this only works during business hours — so a customer who wants to order at nine at night, which happens more than people expect with regulars who run their own operations outside normal hours, simply can't. Multiply that transcription risk by every product line in a typical order, and a single mis-typed quantity can mean a wrong invoice, a confused delivery, and a phone call to fix a phone call.
What changes when the order actually becomes self-service
A real customer portal flips who's doing the translating. The customer logs in, sees their own catalog with their own negotiated prices already applied, checks what's actually in stock, and places the order themselves — at eleven at night if that's when they're doing their books, not just between nine and six when your team is answering phones. The order lands directly in your system, with no retyping and no transcription risk, because it was never spoken out loud in the first place.
Your team's job changes from "type what the customer says" to "handle the orders that actually need a person" — the one-off, the unusual request, the new customer who needs guidance. That's a much smaller, much more valuable job than being a human keyboard for your regulars.
I've built this exact thing before
I built a B2B platform for an auto parts wholesale operation — inventory management, order processing, a pricing engine that handled different rates per customer, and a client portal so their wholesale customers could check stock and place orders directly instead of calling it in. The phone didn't disappear entirely — some customers still prefer it, and that's fine — but the customers who wanted self-service finally had it, and the team stopped being the bottleneck between a customer's intent and an order actually existing in the system.
That's really the test worth applying to your own business: for your regular customers, is your team currently the thing standing between what the customer wants and the order existing in your system? If the answer is yes, every week, for every regular, that's not a minor inefficiency. That's a cost with your company's name on it, paid every single week, that a self-service portal removes almost entirely.
Start with the process you already know by heart
You don't need to guess at this. You already know exactly who calls every week and exactly how long it takes someone on your team to type in what they say. That's the starting point — not a full catalog of every feature a portal could have, but the one repeating call that's costing you the same ten minutes, week after week, for a customer who would almost certainly rather do it themselves at a time that suits them.