synexasMATRIX
Request a demo
BUYING GUIDE

An AI assistant at your company.
What should the supplier deliver?

Start with a task your team needs to complete, not the assistant's opening screen. Compare supplier-delivered on-site AI, software-only tools and an in-house build by what each delivers, what remains your responsibility and how your team will decide whether the result is usable.

SynexasPublished Updated

AI-generated editorial illustration of an organized blank handover folio, a plain metal key, blue cloth and unmarked tabs in daylight.
AI-generated editorial illustration, not a photograph of a customer site or evidence of delivery.
AT A GLANCE

Compare the whole delivery.
Not just the assistant.

Delivery scope

Put the supplier's deliverables and your team's remaining work side by side, including anything excluded from the offer.

Fit for everyday work

Follow an everyday task from its inputs to the result someone needs to review and use.

Responsibility after setup

Name who operates, maintains and changes the system after installation, rather than leaving responsibility with an unnamed team.

Acceptance criteria

Agree on the task, inputs, reviewers and acceptance criteria before comparing results; leave untested points visibly unresolved.

QUESTIONS FOR THE SUPPLIER

Define what arrives.
Then identify what is missing.

Ask for a written account of what will be ready to use at handover: local hardware, a private assistant or workspace, and the setup needed for the agreed work. For each part, distinguish what the supplier delivers from what your team must provide. Separate ordinary setup from any custom workflow development you actually need. An on-site installation should not be assumed to require a bespoke project, nor should the word 'system' be taken to include every future change.

Apply the same questions to the alternatives. With software-only tools, identify who provides the hardware and completes setup. With an in-house build, identify who assembles the assistant or workspace and connects it to daily work. These are delivery choices, not a ranking of quality. Compare the work left to your team as well as the features shown in a demonstration.

QUESTIONS FOR THE SUPPLIER

Follow a real task.
Look beyond the conversation.

Describe a typical task, the information it starts with and the result the next person needs. Ask where the assistant helps, what still requires human judgement and who checks the output before it is used. Then ask what happens when the task or its inputs change: can the agreed setup accommodate that change, or does someone need to adapt it? Make that responsibility explicit rather than treating a convincing conversation as evidence that the whole task is covered.

QUESTIONS FOR THE SUPPLIER

Installation ends.
Responsibility continues.

Give operation, maintenance and future changes a named owner on the supplier's side or yours, as appropriate. Ask which activities are included and which need a separate agreement. Clarify what your team will receive and be able to keep using, and confirm any relevant rights and conditions in the actual offer. Ownership here is not just possession of a machine: your team needs to know who can resolve a problem, approve a change and carry the work forward.

QUESTIONS FOR THE SUPPLIER

Agree on the test first.
Check the result privately.

Choose one representative task and use the same inputs for each option. Before looking at results, agree on the expected output, the acceptance criteria and the people responsible for assessing it. Record what meets the criteria, what does not and what has not been observed. For the installed system, arrange for your team to check its real work privately before use; do not assume supplier access to working data. A demonstration can help explain the offer, but it does not replace this check. Keep acceptance with the people responsible for the work, and do not turn one satisfactory task into a claim about every future task.

One agreed delivery, three distinct responsibilities

  • Agreed delivery
    • Standard system, Workspace and setup
    • Optional, separately scoped custom work
    • Customer: private acceptance and assigned duties

Record usable deliverables, exclusions, acceptance criteria and named owners in the offer.

Confirm local hardware, Matrix Workspace and setup for the agreed everyday work.

Only where needed: distinguish custom workflow development from ordinary setup and agree its scope separately.

Your team checks real work privately. Name owners for operation, maintenance and changes, stating any supplier duties separately.

A proposed scope map, not evidence of a completed installation. Ordinary setup and support do not give Synexas access to working data. The sole exception is an optional custom-workflow proof using customer-authorized data under an NDA, at the customer's site or in Synexas's offline environment, as the customer chooses, with deletion afterwards. Personal data requires a lawful basis confirmed by the customer. Confirm the actual offer; custom development is not required for every installation.
Matrix product and delivery overview
SOURCES

One offer as a reference.
Confirm your own terms.

The Matrix product page describes local hardware, a private workspace and engineers who set it up for everyday work. It also describes agreeing the output and reviewers, followed by an on-site installation that the customer's team checks privately. This is one supplier's description, not independent evidence of successful delivery or a statement that every supplier includes the same work. Use the questions here to compare scopes, then confirm deliverables, responsibilities and acceptance in the offer you are evaluating.

Matrix product and delivery overview

Let’s make AI useful.
For your actual work.

Tell us about a job your team repeats, not your confidential files. We’ll show you how Matrix handles work like it.

Request a demo
DOWNLOAD

Security brief

Tell us where to send it.