Back to Writing

Choosing software that fits your business workflow

A product demo and a custom proposal can promise to fix the same awkward handoff. Give each supplier the same job, exception and handover requirements so you can see what their offer actually covers.

Share

Start with the work your team needs to finish

Someone receives a job request in one system, looks up the customer account and copies the details into another. When the account name doesn't match, the request waits while they find out where it belongs. You've decided this handoff needs fixing. Now a software demo promises a ready-made workflow, and a developer's proposal promises something built around your business.

Comparing custom software with an off-the-shelf product gets difficult when each offer covers a different part of that work. The product demo might finish at a completed intake form. The custom proposal might include creating the job, but leave support and account corrections for later discussion. You need to see how each offer handles the whole request before choosing.

Shortlist suppliers that can demonstrate your mandatory requirements and offer an ownership arrangement your team can sustain. If you're still deciding which work deserves attention first, start with choosing a workflow to automate. For this comparison, the job stays fixed. You're choosing how to deliver it.

Give every supplier the same finished job

Consider a hypothetical small business with separate intake and job-record systems. An authorised staff member submits an internal job request. The workflow finds the approved customer account, creates the job in the existing register and records which request it came from. A named operator handles requests that can't be matched. There are no customer messages, prices or delivery commitments in this example.

Before looking at features, write down what you need to see in the demonstration or its records. For this hypothetical workflow, the requirements could be:

  • Each created job belongs to the approved account and links back to its source request.
  • A missing account mapping leaves the request visibly unresolved and alerts the responsible operator.
  • Access allows authorised staff to submit and resolve requests within their responsibilities.
  • After a failure, the operator can establish whether a job was created before attempting recovery.

Separate these from preferences such as screen layout or notification wording. Ask suppliers to mark each outcome as demonstrated, requiring additional work or still unverified. If a requirement remains unverified, ask for a test or an explicit exclusion before relying on the offer.

The NSW Government's buy, build or borrow framework considers alternative sourcing routes against the need and ongoing costs. It's public-sector guidance, but the shared brief is useful for a small-business purchase too. Define who may authorise corrections and any consequential actions using your own approval boundaries.

Identify what each route would actually involve

Configuring a product means using supported settings, forms and rules to meet the requirement. Start by inspecting software you already license, including its supported templates. Ask where the final job record will live and whether the required behaviour is available in your actual plan. If using the product means replacing the job register, include migration and changes to staff routines in the proposal.

Connecting products means keeping the intake and job systems and transferring information between them. Someone must define how fields correspond, maintain the account matches and handle failed transfers. A connection listed in a product catalogue still needs checking against your workflow. Have the supplier demonstrate the finished job.

Commissioning a custom part means specifying exactly which behaviour someone will develop for you. It might resolve a particular mapping problem or coordinate job creation across existing systems. State what it reads, what it may change and which systems remain responsible for the underlying records. A proposal to replace everything needs its own justification and scope.

These routes can be combined. A supported form could feed a configured automation with a small custom step for a demonstrated gap. Ask the supplier to distinguish ordinary settings from changes to the product itself. The Government Digital Service's guidance on building, buying and configuring technology warns that excessive customisation can complicate maintenance and upgrades. Ask what happens to each proposed change when the product updates.

Each route needs evidence of fit and ownership

For a configured product, have the demo show account matching and unresolved requests. Confirm who will maintain the settings, handle updates and have administrator access after handover.

For connected products, have the supplier show field mapping and recovery. Agree who owns and monitors the connection.

For a custom part, use the demo to check the specific gap and its exceptions. Confirm code access, hosting and support arrangements for handover.

AI also needs a defined job. Copying known fields and looking up an approved account mapping can be specified as rules. Interpreting a free-text request may warrant an AI step, with checks on its output. Anthropic's Building effective agents recommends starting with the simplest adequate solution and adding complexity when needed. That's engineering guidance, not evidence that any purchasing route will save your business money.

Run a routine request and an exception through each option

Use the hypothetical intake workflow to prepare the same demonstration cases for every supplier. No particular product, licence or configuration has been tested here. Each proposed capability remains unverified until the supplier shows it working in the relevant setup.

Start with a routine request whose account mapping is present. Follow it from submission to the resulting internal job. Check the account, required fields and source link in the destination system. Ask which steps were automatic and which required someone behind the scenes. Record any manual work that will remain with your team.

Next, remove the account mapping. The required result is a visible unresolved request assigned to the operator. Ask the supplier to show where it waits, how the operator learns about it and what happens after the mapping is corrected. Check that resuming creates the intended job and preserves the original request. A guessed account match would fail this requirement.

The missing mapping gives you a specific question for each route. Can the configured product represent that unresolved state? Can the connection hold the request and resume it? Does the custom scope include both the operator's correction and recovery? Record whether the supplier demonstrated the answer, proposed additional work or identified a gap. Don't mark the route as passed while that handling remains unverified.

Then ask about an uncertain result. Suppose the job system accepts a new record, but the connection fails before confirming success. How does the operator discover whether the job exists? Ask for recovery that checks the destination before creating another job. If that behaviour remains outside the demonstration, request a separate test and written acceptance criteria.

Check capacity against the work you expect to put through the system, too. Microsoft's Power Platform request-limit documentation says successful and failed actions count, including retries and pagination, and that connector limits also apply. For a proposal using that platform, ask the supplier to assess your expected workload, failures and recovery against the current licence and connector limits. Other vendors need their own checks.

If the mapping itself is incomplete or disputed, assign someone to resolve it. Whichever route you choose, agree the inputs and access it needs. Getting business knowledge ready for an AI workflow covers that preparation. A purchasing decision can include this work explicitly, with responsibility and cost agreed before implementation.

Agree who will keep the workflow working

The person who builds the workflow may leave, a connection may need new credentials or a product update may alter behaviour. Name a business owner who can decide what should happen and agree who supplies the technical support. Ask for a handover that another authorised person can use.

Microsoft's cloud-flow sharing guidance makes the distinction concrete for Power Automate. Connections have their own credentials, and removing an owner can require updating connections so the flow keeps running. Ask the supplier to show how credentials and connections would keep working if the original builder left.

Include these ongoing responsibilities in the brief so suppliers can explain and price them.

  • Who investigates failed requests, and where will your team see unresolved work?
  • Who maintains account mappings, permissions and connection credentials?
  • Who checks updates, and what support and response arrangements are included?
  • What access, documentation and rights will let another supplier maintain or replace the work?

For custom work, get the code, hosting access and contractual rights specified. For configured products, get administrator access and configuration records. For connections, include mappings and recovery instructions. Ask suppliers to identify exclusions and recurring charges alongside the initial implementation. Use those scopes in your automation ROI assessment, including the human effort that remains.

Dependencies can be worth accepting. The GDS guidance on managing technical lock-in in the cloud treats the benefits and switching effort as a deliberate trade-off. Assess the benefits and switching effort of a custom developer and hosting arrangement too. Ask how another operator would reconstruct the workflow from exported records, account relationships, settings and documentation. Include that reconstruction in the handover demonstration.

If an integration or custom requirement remains unresolved, describe the missing behaviour and the cases that expose it. That gives an automation scoping discussion a concrete starting point and lets a supplier explain exactly what additional work would cover.

Choose from the evidence the demo leaves behind

You've fixed the copying problem when a request reaches the correct job record and staff can deal with the requests that need attention. Choose the route that demonstrates that handling and comes with an ownership commitment your business can sustain. A configuration that meets those requirements may be sufficient. A specific, demonstrated gap can justify connecting systems or commissioning a custom part.

Keep unanswered requirements visible in the decision. You can commission a bounded test, revise the scope or deliberately retain manual handling while the gap is resolved. Record what your team will still have to do.

Send the same routine request, missing-account-mapping exception and handover requirements to each shortlisted supplier. Ask each to demonstrate the handling and return a written account of remaining gaps.

Get Started

Let's talk about what's slowing your business down.

Book a free intro call. We'll look at where time is going and whether a custom AI system makes sense for your business.

Book a Call