Software buying guide

Custom software or existing SaaS: frame the decision before choosing

The useful question is not “build or buy?” in isolation. It is which combination of an existing product, configuration, integration, and custom code meets the important workflows with acceptable ownership and change costs.

Start with the smallest intervention that fits

Configure an existing product

Prefer this when the workflow is common, permissions are adequate, exports are usable, and the team can accept the product’s operating model.

Connect existing products

Use integration when the tools are individually suitable but staff repeatedly copy data or lose status between them. Confirm API access and responsibilities first.

Build a custom system

Consider this when essential rules, roles, experiences, or controls cannot be represented cleanly without brittle workarounds. Custom does not remove maintenance; it makes that responsibility explicit.

Requirements template: describe the job, not a feature wishlist

  • Users and roles: who starts, reviews, approves, and administers each workflow?
  • Critical workflows: write the trigger, steps, decision points, and expected result for each must-have flow.
  • Data: identify the system of record, required imports/exports, retention needs, and acceptable manual exceptions.
  • Connections: list current systems, available API or export access, identities, and permission owners.
  • Acceptance: give representative test cases, including denied access, missing data, and recovery after a failure.
  • Operations: name who will answer user questions, authorize changes, maintain dependencies, and own production access.

Compare lifecycle cost without guessing a price

Use the same time horizon and usage assumptions for every option. Record setup and migration work; licences by role or usage; integration and hosting costs; internal administration; training; support; maintenance; security updates; vendor price or contract changes; and eventual data export or replacement work. Unknowns should remain visible as unknowns, not be replaced with invented figures.

A lower initial cost can still carry costly manual work or weak reversibility. A custom build can remove licence constraints yet require engineering, hosting, monitoring, and maintenance. Compare a realistic baseline, not an idealized demo of either option.

Decision checkpoint

  • Which requirements are genuinely mandatory, and who validated them?
  • Can an existing tool be tested with representative data before commitment?
  • Are access, export, integration limits, and termination terms understood?
  • What assumption is riskiest, and can a small prototype test it?
  • Who owns maintenance, security updates, documentation, and the exit plan?
  • What evidence will show that the selected option is accepted?

Source and scope

GOV.UK Service Manual: Choosing technology. This public-service guidance supports considering total cost, existing systems, lock-in, adaptability, and prototypes. It is general engineering guidance, not a Moroccan procurement or legal requirement.