Cemal Builds

What are you actually buying when you buy a portal?

Read that definition again and count the parts. A portal is a login and an identity for every buyer at every company. A catalog scoped to what that account is allowed to buy. Account-specific prices. An order flow. Often an approval chain, because the person choosing is rarely the person signing. Documents: invoices, statements, proof of delivery.

The reorder ladder: where should you stop?

Climb from the bottom. Stop the moment a rung solves the job you just measured. Each rung costs more to run than the one below it. Rung 1: A per-account order form with their agreed prices Solves: a named buyer opens one link, sees the items they actually buy at the price you agreed, enters quantities, submits. No login, no catalog to build, live in a day. Runs out: it shows no stock, no history and no invoices.

When is a real portal the honest answer?

Four conditions. If two or more are true, a portal is a reasonable build. If none are, you are buying a login page. Many accounts self-serving. Enough buyers that per-account handholding does not scale, and enough order frequency that they will learn the tool. Approval chains on the buyer's side. The person who picks is not the person who signs. A portal can hold a basket in "awaiting approval" for three days.

Build or buy: how do the options compare?

Three columns, because the first one is the option teams forget they have paid for.

When should you not climb the ladder at all?

Low order frequency. Ten accounts ordering twice a year will keep emailing. Let them. Every order is negotiated. If price, quantity and delivery are decided in a conversation, self-service has nothing to repeat. Your prices are not settled. A portal shows a price to a customer. If agreed prices still live in a spreadsheet nobody trusts, fix that first. Nobody owns it.