Guides
Answers long enough to be useful
Each guide answers one question properly, states what its evidence is, and names where it stops. Five guides are published on this hub so far, alongside the questions the rest will answer and the standard they are held to.
Avisual Studio is the visual agent workforce for interior businesses. This hub sets out the process questions Studio's guidance answers, the standard a guide has to meet before it is published here, and the conditions under which Studio is the wrong answer. It is organised by the decision you are trying to make. Five guides are published on this hub so far, and the routes below go to the workflow, agent-team, evidence and trust pages that carry the rest of the published detail today.
A knowledge layer, not a content programme
Few guides, revised rather than republished, each carrying its own evidence.
There is already a great deal of generic writing about AI and interiors. Very little of it is based on running the work, and almost none of it tells you when the tool is the wrong choice.
Each guide here states its conclusion first, shows the evidence behind it, and names the conditions under which it does not hold. It is written against the workflows Studio publishes and whatever examples exist on the day it is written.
They are organised by the decision you are trying to make rather than by date, and the three sections below are those decisions. Five guides are published on this hub so far, at least one under each of the three; for the questions they do not answer, this page publishes the question and the standard rather than the answer.
Design visual production
Drawings, client communication, preservation and review.
This section answers three decisions a design practice has to make: whether visual agents can take repeatable production work without giving up design control, what a drawing can carry into a room view and what has to be inferred from it, and which decision AI visualisation is genuinely good at compared with traditional rendering.
Each of those three has a guide below. The Design Visual Production and Client Review and Approval workflow pages state what Studio does at each step behind them, and each agent-team page states what it accepts, what it returns and what your staff still have to check.
Can visual agents take production work without losing design control?
Which visual jobs are safe to assign, what the workflow preserves and what it infers, where traditional rendering is still the right answer, and how to test the conclusion on your own week.
Read the design-firms guideWhat does a drawing carry into a room view, and what has to be inferred?
What an elevation preserves, what the visual infers, what has to be reviewed before a client sees it, and the minimum a drawing has to meet to be worth sending.
Read the elevation-to-interior guideWhich decisions is AI visualisation genuinely good at, compared with traditional rendering?
Seven criteria that decide one output at a time, two hybrid patterns and why each is coherent, where each approach fails, and the case for using neither.
Read the rendering comparison guideVisual sales
Product in room, category fidelity, staff-led consultation.
This section answers the showroom decisions: how a product-in-room visual is produced with a member of your staff operating it, where category fidelity stops, what has to be disclosed to the customer looking at it, and how to check it on one category before committing to more.
All four of those are answered by the guide below. The Human-led Visual Sales Consultation workflow page states what Studio does at each step behind it, and the surface specialists listed on the Agent Teams page state what each one accepts and returns for a given product category.
How can a showroom use product-in-room visualisation during a staff-led consultation?
The four inputs the model requires, what each product category can honestly show and what it cannot, what the customer is told while looking at the screen, and the check to run on your own stock first.
Read the product-in-room guideBusiness and implementation
Capacity, governance, measurement and adoption.
This section will answer the questions an owner asks: how to separate governed repeatable work from the expert judgment that has to stay with a person, what to measure before and after so the difference is visible rather than anecdotal, and what adoption asks of the staff who have to run it.
The first of those has a guide below. No guide in this section is published for either of the other two questions yet: the Business Value page publishes the value argument and the measures it depends on, and the team trial and process pilot page explains how an evaluation is scoped and what it does not commit you to.
How do you handle more visual requests without overloading your best people?
The test that separates repeatable work from expert judgment, the governance a distributed workflow needs, the two ways over-automation fails, and the measure that shows whether the queue actually moved.
Read the specialist-bottlenecks guideHow these guides are made
Stated first, so you can discount them appropriately.
Every guide here is written against the workflows Studio publishes and whatever examples exist on the day it is written. Where a claim rests on a controlled demonstration rather than a customer result, the guide says so on the spot.
Where we hold a professional opinion the evidence does not settle, it is marked as an opinion. Where a statement is a product claim, it points at the page that describes the capability, so the two are never read as the same kind of thing.
We do not publish comparisons against named competitors, because we cannot run their tools under conditions we would accept as fair.
Each guide carries the date it was last revised, and we revise rather than republish.
Five guides have been published against this standard so far. That is why this section comes before the three above it rather than after them: it is the part of this page that stays true whatever is or is not written yet.
Reading is not evidence
The pages that publish what Studio does today, while the guides are being written.
The evidence standard
What a published example has to carry before it goes on this site: the source, the direction given, the result, and the limits of what it establishes.
See what an example has to carryThe workflows these guides analyse
Three published workflows, each naming its input, its job, its output and the person who stays responsible for it.
Open the workflowsThe specialists that run them
Each agent team states what it accepts, what it returns, what it preserves and what your staff have to check.
Open the agent teamsTrust and data
What happens to the images and product information a business puts into Studio, and which questions Avisual's published Privacy and Terms pages answer today.
Read the trust informationWhat Studio does not do
The limits are part of the product. Read them before you plan work around Studio.
- These guides are editorial analysis by Avisual. They are not independent research and do not present themselves as such.
- Evidence, professional opinion and product claim are kept apart and labelled separately in every guide published here.
- We do not publish comparisons against named competitors.
- Five guides are published on this hub so far, at least one under each of the three decisions. For the questions they do not answer, this page states the question and the standard, and routes to the pages that publish what Studio does today.
Choose your next step
Each route below produces something you can look at and judge.