The most visible portal cost is often the least informative: the software subscription. It tells you what it costs to use the platform, but very little about what it costs to deliver and sustain your service.

A useful ownership calculation follows the work across departments and across time. It includes the initial implementation, the recurring cost of running it and the changes needed to keep it relevant. There is no universal multiplier that turns a licence price into that total.

Separate the initial project from the operating commitment

Initial design includes research, content, accessibility, identity and the customer interface. Development turns that design into working functionality. Integration connects the interface to records and actions. Configuration adds business rules, while testing checks the combined behaviour.

These are related but distinct costs. Combining them into a single implementation line makes it difficult to understand later change requests. Record what each investment delivered, which assumptions it relied on and which team or supplier owns its maintenance.

Change is a recurring workload

Consider an illustrative service organisation introducing a new membership category. The commercial decision may be simple, but it could affect eligibility, pricing, renewal notices, booking permissions and financial reporting. Each affected component requires a change, review and release.

Track these changes over a representative period. Distinguish new capabilities from corrections, policy updates and maintenance caused by changes in connected systems. That distinction shows whether spending expands useful service or simply keeps the existing experience functioning.

Include the work that never reaches the technology budget

Staff may rekey information, reconcile conflicting records, correct failed requests or explain an unclear status. Those activities are part of the cost of delivering the service even when they sit in operations rather than IT.

Use a sample of real requests to identify the work involved. Record handling time and repeat contacts, but avoid treating every minute as an immediately recoverable cash saving. Capacity released from routine administration may improve service without reducing expenditure. That is a valuable outcome, but a different financial claim.

Build an ownership ledger

  • Platform: licences, hosting and any agreed usage charges.
  • Implementation: initial design, development, integration and configuration, recorded separately from annual running costs.
  • Maintenance: fixes, dependency updates, integration changes and regression testing.
  • Service evolution: change requests, new services, content and accessibility improvements.
  • Security and assurance: access reviews, monitoring, recovery arrangements and appropriate specialist assessment.
  • Operations: support, manual workarounds, reconciliation and supplier management.

Avoid double counting supplier retainers and the individual tasks they cover. Keep one-off costs separate, or use a clearly stated allocation period when comparing options. Include internal effort consistently across both the existing service and any proposed replacement.

Compare the cost of an outcome

A lower subscription does not guarantee a lower operating cost. Equally, a higher platform price is not justified by an untested promise of automation. Compare the whole service under the same assumptions: supported jobs, demand, reliability, governance and human involvement.

Model an ordinary operating period and a period with substantial change. Identify which costs would actually disappear, which would transfer and which would remain. An integration still needed by other applications is not a saving simply because one portal is retired.

Use evidence before expanding

An alternative approach should demonstrate the work it can remove and disclose the new work it introduces. Avelyndo’s pricing separates the platform from implementation, while the Proof of Value tests a defined scope first.

This framework is a way to examine your own costs, not a claim about typical portal budgets or guaranteed savings. The strongest business case is built from your ledger, your requests and observed results.