For businesses
The same constraint shows up differently in each business
Every interior business runs into the same wall: visual work waits on a small number of people. What that costs, and what fixes it, depends on how you operate.
Avisual Studio is the visual agent workforce for interior businesses. It is most relevant where visual work recurs — in design production, client review, or employee-led sales consultation. Which workflows apply, who operates them, and how adoption is governed depend on the business model. This page routes you to the version of that answer that matches yours.
Which of these is you
Each page maps the workflows, the operator and the adoption path to that operating model.
Interior design firms
Visual work queues behind senior designers, a visualiser or an outsourced partner, and client review waits on it.
Open the design-firm pageKitchen, cabinetry and furnishing businesses
Design and sales cross the same scarce specialists, so routine visual requests interrupt project work.
Open the kitchen and cabinetry pageMaterial brands, retailers and showrooms
Customers hold a sample and cannot judge it in their own room, and visual service depends on a specialist who is not on the floor.
Open the showroom pageSame capability, different job
Who operates it, and what the customer is deciding, changes what good looks like.
In a design practice
A designer runs it. The job is to move a design toward something a client can respond to.
In a kitchen or cabinetry business
Design and sales staff both run it. The job is to keep the client conversation moving without pulling design capacity into it.
In a showroom
A salesperson runs it, with the customer present. The job is to answer a product question inside the conversation.
What this page does and does not prove
One diagram, and a plain account of what each business type is still owed.
The figure at the top of this page is published as an explanatory schematic. It is a diagram of one constraint drawn above three processes. It shows no Studio output, and it establishes nothing about what Studio produces.
What is owed here is one worked example per business type: the source, the direction a person gave, the result, and what each one does and does not establish. This page publishes no worked example, and neither does any page below it — the Examples hub sets out the standard one has to meet and lists what has been committed to, and nothing on that list has been published yet.
Naming a customer, a brand or a project beside a result is a separate approval rather than a copy decision, which is the other reason nothing here is attributed.
Until those examples exist, judge this the way you would judge a new starter: one routine request, on material you already work with, checked by whichever of your people is hardest to please.
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 here has to showThe workflows an example would come from
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 teamsWhen Studio is not worth your time
Said plainly, because finding out later is expensive for both of us.
If visual requests are occasional rather than recurring, the process change has nothing to act on and the effort will not repay itself.
If the work requires exact technical modelling — measured coordination, fabrication layout, compliance documentation — that is not what Studio produces, and a visual will not substitute for it.
If nobody on staff will own the workflow, adoption stalls regardless of how good the output is.
Three ways in, in order of commitment
Start at the smallest one that would change your mind.
One person, one job
One routine request, run on material that matters to you, judged the way you would judge any visual before it goes in front of a client.
A team trial
A defined staff group runs it repeatedly, so adoption becomes visible rather than anecdotal.
A process pilot
One visual process, your own baseline recorded first, agreed measures, and a rollout decision at the end.
The second and third rungs are explained in full on the team trial and process pilot page: what each one covers, what you would have to record before starting, and what a decision at the end looks like. Neither is a button. What a team arrangement includes, and what a pilot's scope and terms are, is agreed rather than published, so both start as a conversation rather than as a button. Ask Studio Consultant, from the link at the top of this page, from that page or from the Studio pricing page, is where that conversation starts.
The first rung is the one you can take on your own today. Each business page below carries the run its own staff would set up, with the workflow already chosen.
What Studio does not do
The limits are part of the product. Read them before you plan work around Studio.
- Studio is most relevant where visual work recurs. Occasional visual requests are not a fit.
- Studio produces communication visuals. It does not produce technical, dimensional or contractual documents.
- Value differs by business model, workflow and level of adoption, and depends on your own baseline. We do not assert it in advance.
- Your employee operates Studio and leads the customer relationship.
- This page publishes no worked example. It routes to the pages that state what one would have to show.
Choose your next step
Each route below produces something you can look at and judge.