SVS Digital

AI consulting and solution selection

Buy, integrate or build an AI solution? Compare the options before a pilot

A polished AI demo can make the technology decision look settled before the company has defined the job. Buying a tool, connecting a managed AI service and developing a custom workflow create different responsibilities for data, integration, testing and support. Compare them against one bounded business task before asking for a quote or starting a pilot.

By SVS Digital · Published

Start here

Write one problem statement, representative cases and acceptance checks first. Then compare four routes: improve the process without AI, buy or configure packaged software, integrate a managed AI service into a controlled workflow, or develop a custom application and, less often, a custom model. Score every route against task fit, data access, integration effort, human review, measurable quality, security and legal checks, operating cost, supplier dependency, internal skills and an exit path. Pilot the smallest viable route only after the evidence identifies a clear advantage.

Give every option the same problem to solve

Describe the work without naming a product: for example, classify incoming service requests, show the employee the supporting policy and prepare an unsent draft. Record the trigger, current steps, users, monthly case-volume range, common exceptions, required result and actions that remain prohibited. A request to “add AI to customer service” is too broad to compare.

Define acceptance checks before supplier discussions. Use representative ordinary, difficult and out-of-scope cases. Specify expected routing, required evidence, permitted variation, review time and critical failures. The UK Government procurement guidance recommends a clear problem statement, openness to alternative solutions and an assessment of data, benefits, risks and lifecycle costs. Although written for public procurement, those questions are also useful in a private-company discovery.

  • One workflow with a clear start, result and owner.
  • Current baseline and sample period labelled as measured or estimated.
  • Representative cases, including exceptions and prohibited actions.
  • Acceptance checks that do not depend on one vendor's feature list.
UK Government: Guidelines for AI procurement

Compare four routes, including no new AI system

First test whether a clearer form, knowledge base, rule or ordinary automation removes the problem. For a standard workflow, compare packaged products, including features already licensed in your CRM, help desk, ERP or office suite and a new off-the-shelf product. The third route uses a managed model or AI service while your company defines the permissions, approved sources, review queue and system connections. The fourth uses custom application code and, less often, a custom-trained model when packaged and managed options cannot meet a documented requirement.

Do not use “custom” as one category. A company-specific workflow around a managed model leaves model operation with the service provider, while custom development adds ownership of more application code and possibly the model lifecycle. Microsoft distinguishes prebuilt services from custom models and highlights data control, customization, upkeep, performance and expertise as decision factors. NIST also says viable non-AI alternatives should be considered. Keep a no-go route in the comparison when the data, risk or expected value does not support a pilot.

  • Process change or deterministic automation.
  • A packaged product, already licensed or newly purchased.
  • Managed AI service inside a custom, reviewed workflow.
  • Custom application or model component with a stated reason.
Microsoft Learn: AI workloads on AzureNIST: AI Risk Management Framework Core

Verify data and integration claims before scoring features

List the minimum data needed for the task, its owner, sensitivity, location, retention needs and whether representative examples may be used for testing. Ask where inputs and outputs are processed, which parties receive them, how access is controlled and how records can be corrected or deleted. A product screenshot does not answer those questions.

Inspect each system connection separately. Reading approved documents, looking up a customer and writing a CRM note are different permissions. Confirm the supported API or export, identifiers, rate limits, failure messages, duplicate protection and reconciliation. If a live connection cannot be tested yet, record that as an unresolved dependency instead of treating an advertised integration as completed work.

  • Necessary fields and prohibited data documented.
  • Processing, storage, access and retention questions answered.
  • Actual source and destination interfaces checked.
  • Failure, retry, duplicate and correction paths included.
UK Government: Guidelines for AI procurementNIST: AI Risk Management Framework Core

Compare ownership and whole-life cost, not only the setup price

Estimate the same cost categories for every route: discovery, licences or model usage, implementation, data preparation, integrations, testing, security and specialist review, employee training, monitoring, support and later changes. Include employee review time and the work needed when a vendor changes a model, price, interface or product policy. Record ranges when volume is uncertain rather than presenting a precise annual figure without evidence.

Assign an owner for quality, incidents, access, supplier changes and retirement. Ask what the company can export, which logs and configuration it retains, whether another supplier can continue the workflow and how the system is disabled without losing open cases. Procurement guidance warns about vendor lock-in and calls for ongoing evaluation, support, training and end-of-life planning. The cheapest trial can become the costliest route when these duties remain unnamed.

  • Initial and recurring costs separated.
  • Internal review and support effort included.
  • Supplier, model and interface changes assigned to an owner.
  • Export, replacement and shutdown path documented.
UK Government: Guidelines for AI procurement

Gather route-selection evidence before committing to a pilot

Ask shortlisted suppliers to demonstrate the same cases, then use a sandbox where available. Record whether the expected result can be produced with cited sources, whether uncertainty is escalated to a person, how much reviewer correction is needed and which usage assumptions drive the indicative cost. Treat a prepared demonstration as evidence of capability, not proof of performance in your live process.

Validate the promised interfaces before selecting the route: inspect API documentation, test one read and one permitted write, confirm export formats, review available logs and check how access can be revoked. Record blockers such as prohibited data exposure, missing audit records, no supported export or an integration that exists only through manual copying. NIST calls for testing in conditions similar to deployment and documented limits; the later pilot brief should define full acceptance thresholds and stop conditions.

  • Same demonstration cases and questions for each option.
  • Sandbox evidence separated from supplier claims.
  • API, export, logging and access controls checked.
  • Route decision recorded as proceed, narrow, compare again or stop.
NIST: AI Risk Management Framework Core

Finish the route comparison with a decision record

Summarise the problem, options considered, evidence, assumptions, unresolved dependencies, expected cost range, principal risks, selected route and reasons the other routes were rejected. Name the pilot owner, users, technical owner, reviewer and any required security, privacy, legal or sector specialist. Set the date and evidence needed for the next decision.

The result may be configuration of an existing tool, a managed service connected to a reviewed workflow, targeted custom development, more discovery or no AI project. This guide is not a procurement specification, legal assessment or claim that one route fits every company. A route-selection review should make the tradeoffs visible before a commercial commitment, then turn the selected route into its own pilot brief and acceptance plan.

  • Selected route and rejected alternatives explained.
  • Assumptions and unresolved supplier claims visible.
  • Owners, specialist reviews and pilot boundary named.
  • Next decision tied to evidence rather than a launch date alone.

Sources and further reading

More guides

What would you like to build for your business?

Tell us where you need a hand. We’ll email you a brief and follow up about the next step.

Uroš Jovanović

Founder · SVS Digital

Hi, I’m Uroš.

I founded SVS Digital. We design and build custom digital solutions for businesses.

What kind of solution do you need?

Your reply