Build or buy a customer self-service portal
A small business-to-business software company decides whether to build a customer portal, licence one, licence and extend one, or defer. The log shows a contractual renewal date doing the work of elim...
The options
The question: Should the organisation build a customer self-service portal, licence one from a vendor, licence and extend one, or defer the decision?
Option 1: Build the portal in-house
For
- Estimate. The engineering team sized the three requested capabilities at 200 engineer-days: invoice access, user administration and single sign-on.
- Evidence. The portal would run on the organisation's existing authentication and data model, so no customer personal data would leave the current processing arrangements and no new sub-processor authorisation would be needed.
Against
- Risk. The 26-week estimate assumes engineering capacity is released in October and that all four engineers then work on the portal. The billing migration has already slipped twice; a third slip, or any call on the engineers from the existing product, places launch beyond the January renewal date, which is the one deadline with a contract attached to it.
- Risk. Building commits the organisation to operating a customer-facing service it has never operated before, at an ongoing effort figure that is an estimate rather than an observation.
Option 2: Licence a portal from a vendor and use it unmodified
For
- Evidence. The vendor quoted an annual licence for the organisation's seat count with invoice access, user administration and single sign-on included in the base tier, and a standard data export on termination.
- Evidence. Two reference customers of comparable size were live within seven weeks, and neither required engineering attention after the first month of operation.
- Recommendation. Licence the portal from the vendor and use it unmodified, subject to sub-processor authorisation being obtained before launch. The January renewal date is contractual and only the two licence-based options reach it with margin. The recommendation accepts a higher estimated five-year cost than building (about 214,000 against 174,000 euro), weak branding and no roadmap control for an initial term, in exchange for meeting a contractual commitment and learning which capabilities customers actually use before committing 96,000 euro to building them.
Against
- Risk. Branding is limited to a logo and a colour pair. For the enterprise customers who requested this, the portal is the visible face of the product to their own staff.
- Risk. Engaging a new sub-processor requires prior authorisation from at least one customer whose agreement restricts it. If that authorisation is refused or delayed, the option cannot launch on time and the advantage over building disappears.
Option 3: Licence a portal and extend it through the vendor's interface
For
- Evidence. The vendor's interface covers all three requested capabilities, so the customer-facing presentation can be the organisation's own while the underlying service remains the vendor's.
Against
- Risk. Two of the three reference customers the vendor provided for extended deployments had extensions break on a vendor upgrade, one losing approximately three weeks to recovery. That cost recurs on the vendor's release schedule rather than the organisation's, and is the reason the five-year cost of this option is recorded as unknown rather than estimated.
- Risk. This option carries the compliance obligations of buying and a substantial part of the maintenance burden of building, without the full control of either.
Option 4: Defer the decision to December 2026
For
- Rationale. Deferral would allow the billing migration to complete before any competing demand on engineering capacity, removing the dependency that makes the build estimate uncertain.
Against
- Risk. Deferral misses the January renewal date under every option that could follow it. One renewal carries self-service access as a condition, so the cost of this option is a renewal placed at risk rather than a saving.
Criteria and values
| Criterion | Option 1 | Option 2 | Option 3 | Option 4 |
|---|---|---|---|---|
| Adds a new sub-processor | No | Yes | Yes | No |
| First-year cost | 96,000 EUR | 41,000 EUR | 63,000 EUR | — |
| Five-year cost | 174,000 EUR | 214,000 EUR | — | — |
| Ongoing engineering effort per month | 3 day | 1 day | 2 day | 0 day |
| Reversibility at two years | moderate | high | moderate | — |
| Control over the roadmap | full | none | limited | — |
| Time to first customer use | 26 week | 7 week | 10 week | 32 week |
What constrained the decision
- Constraint. Two of the four engineers are committed to a billing system migration until October 2026. Any option requiring substantial internal build competes directly with that programme for the same people.
- Constraint. One of the three enterprise customers has made self-service invoice access a condition of its renewal, which falls due in January 2027. That date is contractual rather than aspirational and bounds every option.
- Constraint. The same customer's data processing agreement requires prior written authorisation before any new sub-processor is engaged. Any option placing customer data with a vendor requires that authorisation to be sought and granted before launch.
- Assumption. The loaded cost of an engineer-day is 480 euro. All build and effort figures below are derived from that rate; if it is materially wrong, the ranking of the two build-inclusive options against the licence-only option changes.
- Assumption. Customer demand stops at the three capabilities requested. No option has been sized for a wider portal, and the five-year cost figures assume no significant scope growth. This assumption is the one most likely to fail.