Evaluate
Evaluate the process, not the demonstration
A demonstration shows what the tool can do. A pilot shows what your business does with it, which is the only question that matters.
Avisual Studio is the visual agent workforce for interior businesses. A team trial lets a small group use Studio on real work. A process pilot goes further: it defines one workflow, records what it currently costs, runs Studio inside it for a set period, and measures the difference. Both end in a decision, and stopping is one of the allowed decisions.
Team trial or process pilot
Different questions, different amounts of work.
Team trial
A small group uses Studio on real work to answer: can our people run this, and does the output hold up? Light setup, no baseline required.
Process pilot
One defined workflow, one recorded baseline, one measured period. Answers: does this change how the process performs? More setup, and a decision you can defend.
Neither is self-serve, and neither is a button on this page. What a team arrangement includes, and what a pilot's scope covers, is agreed rather than published — so both start as a conversation rather than as a button, which is how the Studio pricing page words them too.
Name one process, narrowly
Broad pilots produce broad opinions.
Pick the request that arrives most often and irritates most reliably. That is usually where the process change is visible within weeks rather than quarters.
Write down where the process starts, where it ends, who touches it, and what it currently produces. If that cannot be written down, the pilot has no boundary and will not conclude.
Record what it costs today, before you change anything
Without this, the pilot can only produce impressions.
Volume
How many of these requests, over what period.
Time
From request to usable visual, including the waiting.
Who
Which roles are consumed by it, and what they stopped doing.
Quality bar
What counts as an acceptable result today, in your own words.
Set up the workflow, the references and the review rules
Configuration is where most of the effort actually is.
Workflow
The one process you defined, set up as a repeatable run.
References
The approved products, materials or drawing standards it may use.
Roles
Who runs it, who reviews it, and what may reach a customer.
Review standard
What a reviewer checks before the output leaves the business.
Run it on real work, long enough to pass the novelty
Early enthusiasm is not adoption.
Real jobs, real deadlines, the same people who will use it afterwards. A pilot run by enthusiasts on invented tasks measures enthusiasm.
Expect the first period to be slower than the baseline while staff learn the workflow. That is the cost of the change, and it belongs in the result.
An illustrative pilot shape
Illustrative only. Not a template, not an offer, not a commitment.
A showroom picks one category, three salespeople and their busiest weekday hours. Before starting, they record how many consultations currently include any visual, and how long a visual takes to arrive.
They configure one workflow with their approved product references, agree that any visual sent to a customer is reviewed by the branch manager, and run it on real consultations.
At the end they compare the same two measures, and choose one of the four outcomes. The details above are illustrative; a real scope is agreed with the business.
What that shape does not carry is a result. It is not drawn from a customer project, and no number in it has been observed — it shows how the parts of a pilot fit together, and nothing about what a pilot would find.
Compare against the baseline you recorded
Same measures, same definitions, same people.
Read the same four measures you wrote down before you started, defined the same way, across a period long enough that a busy fortnight does not decide it. A measure swapped mid-pilot for one that moved is not a finding.
Include the cost of the change in the comparison: configuration time, review time, and the slower first weeks. A result that counts only the good half is a result you cannot repeat when you extend it.
When a pilot is not worth running
A pilot costs real effort. Some of the time the honest answer is not to run one.
If the process does not repeat often enough to produce a baseline, there is nothing to measure against, and a pilot will produce the same impressions a demonstration would have — at more cost.
If nobody will own the workflow for the length of the pilot, it will be run by whoever is free that week, and the result will describe their availability rather than the process.
If the work needs exact technical modelling — measured coordination, fabrication layout, compliance documentation — that is outside what Studio produces, and no pilot changes that. A team trial is the cheaper way to find out whether the boundary bites before a pilot is scoped.
Four outcomes, all of them legitimate
Including the two that end the conversation.
Roll out
The process improved against the baseline and staff adopted it. Extend to more people or locations.
Refine
The signal is there but the configuration or the review rules are wrong. Adjust and re-run.
Pause
The business is not ready — data, ownership or timing. Stop cleanly and revisit when it is.
No fit
The process does not benefit, or the boundaries exclude the work. Stop, and say so plainly.
One gate, four allowed exits. A pilot that can only succeed is not an evaluation, and an evaluation whose losing outcomes quietly disappear is a sales process wearing its clothes.
Agree before you start which of the four each measure would point to. Deciding that afterwards is how a pilot becomes an argument.
What Studio does not do
The limits are part of the product. Read them before you plan work around Studio.
- No outcome is promised before a baseline exists.
- A pilot result describes that process, in that business, over that period. It is not a product claim.
- The illustrative pilot on this page is not a contractual commitment.
- Pause and no fit are valid outcomes and will be recommended when they are the honest answer.
- No price, term, duration or service level is published for a team trial or a process pilot. The scope is what determines them, and the scope is what is agreed.
Choose your next step
Each route below produces something you can look at and judge.