Pricing and quotation guide
Self-service portal development cost
The cost of a self-service portal is driven by the tasks it lets customers complete. Each task that changes data or triggers an action needs integration with the system behind it, appropriate identity checks and careful testing. Help content and analytics add their own effort, and the portal needs regular upkeep. The return is measured mainly in support contacts that no longer need a person, which makes it one of the easier portals to evaluate.
This page explains what drives self-service portal cost and how to estimate the return.
Illustrative diagram
Self-service portal
- Tasks
- Steps and rules
- Integrations
- Identity
- Sign-in
- Verification
- Content
- Help articles
- Search
- Running
- Analytics and reviews
- Upkeep
What drives the cost
- Number of tasks
- Each task has its own steps, rules and testing.
- Integration per task
- Connecting to the system that holds the data or performs the action.
- Identity checks
- Sign-in and verification matched to risk.
- Help content
- Writing and organising articles linked to tasks.
- Analytics
- Tracking completion, abandonment and handovers.
Costs paid to third parties (separate from our fees)
- Hosting and monitoring
- Verification services such as one-time codes
- Help centre software, if used
- Support staff time for content and reviews
Read-only tasks such as downloading invoices are usually cheaper than tasks that change data.
Estimating the return
| Input | Where it comes from |
|---|---|
| Contacts by request type | A few weeks of tagged support contacts |
| Handling time per type | Timed samples or support system data |
| Expected self-service take-up | A cautious estimate, refined after launch |
| Out-of-hours demand | Contacts arriving outside opening times |
Use cautious take-up figures
Not every customer will use self-service, even for simple tasks. Some prefer to call, some will not find the task and some situations will need a person after all. Base the business case on a cautious share of each request type moving to self-service, and improve it with real figures after launch. Even a modest share of a high-volume request can represent many staff hours a year.
The out-of-hours value, where customers complete tasks when nobody is available, is real but harder to price.
Example: three tasks first
Illustrative example — not a client case study
Situation: A supplier's support team handles many requests for invoice copies, delivery date changes and returns.
- Contacts are tagged for a month to measure volumes and handling times.
- Invoice downloads, delivery date changes within rules and return bookings are built first.
- Take-up and remaining contacts are measured over the following months.
What this shows: The three tasks addressed the largest simple request types, and later tasks were chosen from handover reasons. This example is illustrative.
Ongoing costs
Platform
- Hosting and monitoring
- Integration upkeep as systems change
- Verification service fees
Content
- Article updates
- New tasks
- Search improvements
Review
- Monthly evidence reviews
- Support staff input
- Accessibility checks on changes
Help centre product or custom portal
Help centre product
Suits you when
- Most needs are information and contact forms
Watch out for
- Limited transactional tasks without integration
Custom self-service portal
Suits you when
- Customers need to complete tasks in your systems
Watch out for
- Build and integration effort
Both
Suits you when
- Articles in a help centre, tasks in a portal, linked together
Watch out for
- Consistent design and search across both
Comparing quotations
Ask each provider to price tasks individually, including the integration each needs and the identity checks proposed. Check whether analytics, help content structure, accessibility testing and a post-launch review period are included. A quotation for a portal 'with self-service' but no detail on which tasks complete in your systems may deliver mostly help articles. Ask how a new task would be added later and what it would involve.
Ask too how broken tasks would be detected after launch.
Phasing tasks
Building the highest-volume, simplest tasks first delivers much of the early return and proves the integrations. Later tasks reuse the same sign-in, verification and analytics, so each additional task usually costs less than the first.
Out-of-hours value
Tasks completed overnight or at weekends reduce Monday backlogs.
Questions about self-service portal development cost
What drives self-service portal cost?
Number of tasks, integration per task, identity checks, help content and analytics.
Are some tasks cheaper than others?
Yes, read-only tasks are usually cheaper than those that change data.
How is the return on self-service estimated?
From contact volumes and handling time by request type, with cautious take-up.
Will every customer use it?
No; plan with a cautious share and refine after launch.
Is a help centre enough?
For information needs, often; tasks in your systems need a portal.
What does a self-service portal cost to run?
Hosting, integration upkeep, content updates and regular reviews.
Do later tasks cost less?
Usually, because they reuse sign-in, verification and analytics.
Request a Custom Quote
Ask about Self-service portal development cost
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.