Start with the job the software must do
Useful custom software examples show a specific job, the people doing it and the limits of the system. A label such as portal or platform tells you very little about whether a build is justified. Start by describing where work currently stalls and what a better outcome would look like.
Custom software is designed or adapted for particular requirements. That does not mean every component must be written from scratch. A tailored workflow can use an existing identity service, payment provider or messaging tool, with custom code connecting the parts that need to work differently.
The business patterns below are illustrative possibilities, not Project Hero customer case studies. The two public-service references are real services described by their operators. They show useful boundaries between shared components and the wider service, not evidence that your organisation should copy their architecture.
Customer portals: make a specific exchange easier
A customer portal might let an authorised customer view the progress of a request, provide missing information and download an approved document. Define which task justifies signing in. A portal that merely repeats information already sent by email may add effort without solving a meaningful problem.
List the records each customer can see and the actions each staff role can take. Ask what happens when a person leaves a customer organisation or needs access restored. Permissions and support routes are part of the product, even though they rarely appear in an early visual mock-up.
Before building, test whether your existing customer-management or support system can provide the same journey. A bespoke portal becomes a stronger candidate when established products cannot support an important requirement without awkward manual work or unacceptable compromises.
Operational tools: handle the exceptions as well as the queue
An internal scheduling tool could connect jobs, staff availability and customer instructions. Its value depends on the rules it must handle: a cancelled visit, a missing skill, an urgent reassignment or a booking made while someone is offline. Write those cases down before counting screens.
An approval tool is another pattern. It can route a request to the right person and retain a decision history. Define who may approve, who may amend the original request and what should happen when the approver is absent. A simple existing workflow product may already cover the requirement.
For either pattern, measure the present problem before making a business case. Record repeated manual steps and error correction. Avoid assuming that every minute removed from a task becomes a cash saving; the actual benefit depends on how the team uses the released time.
Integration services: connect systems without replacing them
Sometimes the useful custom element is a small integration rather than a new application. It might transfer an approved order into another system, validate required fields and notify a person when a record cannot be processed. The interface can be modest because most work happens between systems.
Ask which system is the authoritative source for each field. Plan for repeated messages, partial failures and changes to a provider's interface. Someone needs a safe way to investigate and retry failed work without creating duplicate orders or overwriting newer information.
Two real examples of reusable service components
GOV.UK Pay supports payments for public services and offers an API for integration into a wider digital service. Its published API capabilities include viewing payment history and issuing refunds. The practical lesson is to define the payment boundary rather than assume a custom application must create its own payment-processing system.
GOV.UK Notify supports email, text messages and letters, with editable templates, delivery information and API integration. This illustrates how a wider workflow can use a shared messaging component. These are government services with eligibility requirements, not recommendations that every private business can adopt them.
Custom software examples: decide what to build
For each of these custom software examples, compare three options: change the process, configure an existing product, or build a tailored component. GOV.UK's technology guidance encourages considering existing systems, testing assumptions and total ownership cost. Those are useful decision prompts for a business, although government-specific requirements do not automatically apply to it.
Write one complete journey with its inputs, roles, exceptions and expected output. Then ask a potential supplier to explain which parts already exist, which need custom work and which uncertainties should be tested first. A useful proposal should make the boundary clear enough that you can challenge it before committing to a build.