Choosing a web portal development company and defining the work properly: what B2B portal development actually has to model in identity, permissions and integration, and why portals are quoted so inconsistently

Portal is one of the least precise words in this market, covering everything from a page behind a login to a full self service platform replacing a service desk. That imprecision is why portal quotes vary so widely, and defining the work properly is most of the value a buyer can add before shortlisting.

Identity is the first and largest decision

Who are the users, where do their accounts come from, and who decides what each can see. A portal where a customer's own staff administer their colleagues' access is a substantially larger build than one where you create every account, and business to business portals almost always need the former eventually. Establish whether account hierarchies and delegated administration are in scope before any quote, because retrofitting them touches everything.

Permissions in a business portal are organisational

A customer organisation has branches, roles and approval chains, and a portal that ignores them forces work back onto the phone. Head office may need to see everything and restrict what branches can order; an approver may need to authorise before an action takes effect. That structure is the difference between a portal that is adopted and one that is a second system nobody uses, and it is routinely absent from a first specification.

The integration inventory is the real scope

A portal is a window onto systems you already run, so its scope is the list of those systems, what each one provides, how fresh the data must be, and what the portal does when one is unavailable. Get that inventory written with a named owner per system before committing to a plan, because those owners have their own priorities and their availability is the critical path far more often than the portal build is.

Self service only pays if it removes the phone call

The business case for a portal is deflection: work customers do themselves that staff used to do. That only happens if the portal is faster than phoning, which means the top few reasons customers currently contact you should be the first features built. Ask for the support contact reasons by volume and build against that list. Portals scoped from an internal wish list rather than from contact data reliably fail to deflect anything.

Questions people ask about web portal development company

Why do portal quotes vary so much?

Because portal covers everything from a page behind a login to a self service platform replacing a service desk. Identity, delegated administration, permissions structure and the integration inventory are what actually set the price.

What is most often missing from a portal specification?

Organisational permissions: branches, roles and approval chains inside the customer, plus delegated administration so customers manage their own users. Retrofitting either touches every screen.

How do we make sure the portal gets used?

Build against the top reasons customers currently contact you, taken from real support volumes, and make each faster than phoning. Portals scoped from an internal wish list reliably fail to deflect anything.

Sources

Related answers

Get your agency shortlistDescribe your project