For businesses
Your visual queue is your senior designers
Concept visuals, drawing interpretations, relights and presentation images all land on the same few people. Studio takes the production. It does not take the judgment.
Avisual Studio is the visual agent workforce for interior businesses. In a design practice, specialist agent teams do defined visual jobs: developing a rough concept, reading a drawing into an interior, refining lighting, and preparing a presentation image. The practice sets the design direction, the review rules and the professional boundaries, and Studio output does not resolve technical detail.
What visual work looks like across a portfolio
Not one render at the end of one job. A steady stream of small visual obligations across every live project at once.
A practice with eight live projects has eight streams of visual demand running at once: a direction to test before anyone commits hours to it, a drawing the client cannot read, a revision after every review, and one image at the end that has to be worth putting in front of people.
None of those is a big job. Together they are most of a week, and they arrive in whatever order the projects happen to be in.
The judgment inside them is real design work. The output around that judgment is production, and it is the production that arrives faster than anyone can absorb it.
The queue forms at production, not at judgment
Visual demand does not arrive evenly. The capacity that answers it does, and it is attached to a small number of people.
All of it queues behind a senior designer, a visualiser, or an outsourced partner with a schedule of their own. Whoever it is, they can only be in one project at a time.
When the queue forms, the review date moves. The cost of that is not the image. It is the fortnight, and the decisions that waited inside it.
The second cost is quieter. Concept exploration is the first thing a busy practice stops doing, because testing a second direction means asking a person who is already committed. So directions stop being tested, and the practice never sees what it did not look at.
The same stage, run two ways
Nothing is removed from the process. One step changes hands, and a review step is added where there was none.
Testing a concept direction today
- A designer marks up a rough source and writes what the direction should be.
- The request joins a queue behind whoever produces visuals in the practice.
- It comes back some days later, usually as one option.
- The review discusses that one option, because there was never budget for a second.
Testing a concept direction with Studio
- The same designer marks up the same rough source and writes the same direction.
- A Scene Design run takes the source and the direction and returns explorations of it.
- The designer reads them, discards what misses the intent, and keeps what is worth showing.
- The review discusses a direction rather than an artefact, because more than one was affordable.
A person chooses the stage, writes the direction, judges every result against the design intent, and decides what reaches a client. Studio has no view on whether the direction is right.
Four specialists under one responsible person
Each specialist maps to a stage a designer already recognises, and each one states its own limits on its own page.
The designer running the work
- Chooses which stage is worth handing over, and which is not.
- Writes the direction, in the practice's own language.
- Judges every result against the design intent before anyone else sees it.
- Decides what reaches the client, and answers for it.
Scene Design
Develops a rough source into explorations of a stated direction, at concept stage.
See the workflow this team runs inDrawing-to-Interior
Reads an elevation or plan into an interior view a client can respond to.
See the workflow this team runs inLighting and Mood
Shows an agreed design in the light the client keeps asking about.
See the workflow this team runs inEditorial Presentation
Prepares a finished project as one presentation image.
See the workflow this team runs inWhat stays with the practice
This list is not a courtesy. It is the operating boundary.
Design intent, and the reasoning behind it. Studio has no view on whether the direction is right, and it cannot tell you when a direction is wrong.
Specification. What is actually built, in what material, at what detail, remains the practice's decision and the practice's liability.
Client leadership. The conversation, the recommendation and the approval are yours, and a visual is only ever an aid to them.
Review. Every result is checked by a person before it leaves the practice. That is what a reviewable output is for, and it is the reason the rest of this page is worth reading.
What this page does and does not prove
One diagram, and an honest account of the two examples still owed.
The figure at the top of this page is published as an explanatory schematic. It is a diagram of where visual work narrows inside a practice. It shows no Studio output, and it establishes nothing about what Studio produces.
The two things this page owes you are a design project carried across more than one stage, and one client review conversation from drawing to approval. Neither is published yet. The Examples hub names both, states the standard each has to meet, and marks them as outstanding rather than filling the space with something weaker.
Until they exist, the honest way to judge this is the way you would judge a new hire: one job, on your own material, reviewed by someone in the practice whose opinion you already trust.
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 a design-firm example must showDesign Visual Production
The workflow the multi-stage design example would be drawn from, with each stage and its review point set out.
Open Design Visual ProductionClient Review and Approval
The workflow the review example would be drawn from, including what a client is and is not being shown.
Open Client Review and ApprovalWhat changes in the practice, stated as process
Not a saving. A change in where work sits, which your own numbers may or may not reflect.
Capacity
Production work stops queueing behind the people doing design work. That is the change everything else here follows from.
Seniority
A junior designer can produce a reviewable visual without waiting for someone senior to be free, and a senior designer spends the time reviewing rather than producing.
Exploration
Testing a second direction stops being a favour asked of a busy colleague, which changes what gets tested and not only what gets delivered.
Repeatability
The same stage runs the same way across projects, so the practice can compare results instead of comparing whoever happened to produce them.
Measurement
Whether any of this reaches your numbers depends on your own baseline. Measuring that is what a process pilot is for, and we do not assert it in advance.
What a practice needs in place first
Adoption in a practice fails on governance more often than on output quality.
Shared references
The materials, finishes and directions your practice actually specifies, written down once rather than described differently by each person who runs a job.
Approved stages
Which stages the practice runs through Studio, and which it does not. A stage nobody agreed to is the one that produces an argument in front of a client.
Roles
Who runs it, who reviews it, and who signs off before anything reaches a client. All three are people, and the third is not the same person as the first.
Project continuity
Where results live, so a project's visuals stay with the project rather than in the run history of whoever happened to make them.
Data, ownership and the technical limit
The short version. The full position is on the Trust page, and it is short too.
Studio produces communication visuals. It does not produce construction documentation, it does not verify a dimension, and it does not approve a design. Where a project needs a photoreal render for its own sake, that is still a render job and we will say so rather than sell around it.
Your project material is yours. The Trust page states Avisual's published position on data handling and points at the Privacy and Terms pages that carry it. Anything that needs a contractual answer is escalated to a person rather than improvised on a page.
Three routes, depending on what you need to settle
One person testing a stage, a workflow read end to end, or the trust position. They answer different questions.
One person, one stage
Set up a run against a source you already have, and judge the result the way you would judge any other draft.
Set up a design workflow runThe whole workflow, read first
The stages, the review points and the limits, before anyone in the practice runs anything.
Open Design Visual ProductionThe specialists, one by one
Each team states what it accepts, what it returns, what it preserves and what you have to check.
Open the agent teamsWhat Studio does not do
The limits are part of the product. Read them before you plan work around Studio.
- Studio produces communication visuals. It does not produce construction documentation, verify a dimension, or approve a design.
- Studio output does not resolve technical detail, and it is not a substitute for it.
- Design intent, specification, client leadership and approval stay with the practice.
- Process value depends on the practice's own baseline. We do not claim practice-wide savings without it.
- Every result is reviewed by a person before it reaches a client.
Choose your next step
Each route below produces something you can look at and judge.