Pricing
What you are paying for, and where the prices are published
Studio usage is counted in runs, so this page defines a run before it compares anything. It then sets out the four routes businesses take, states the commercial terms Avisual publishes, and links the page where the current plans and prices are maintained rather than keeping a second copy of them here.
Avisual Studio is the visual agent workforce for interior businesses. Usage is counted in runs: one job, through one workflow, producing one reviewable output for a staff member to judge. Businesses adopt Studio by one of four routes — free runs for evaluation, individual use, team use, or a process pilot that changes how a visual step works. Avisual publishes its current Visual Studio plans and prices on its Visual Studio pricing page, and this page links that page rather than restating the figures. Avisual's Terms of Service, effective 2 July 2026, state that free runs are for evaluation and are not an assured production allowance, that paid plan allowances renew per billing period as described on the pricing page, that either party may end the agreement at any time, and that liability is capped at the amounts paid in the twelve months before a claim. How a paid allowance meters against the run defined here, which failed generations are refunded, any team or pilot commercial term, and the tax treatment of a price are not published anywhere, and this page names them as open rather than answering them.
One run is one job through one workflow
Everything on this page is counted in runs, so the unit comes before any comparison of routes.
Studio usage is counted in runs, so the unit comes first. A run is one job: a staff member supplies the source the workflow asks for, gives a direction with it, an agent team produces one reviewable output, and that person decides whether it is used.
One consequence of that definition is worth stating before any route is compared. Testing three material directions on one drawing is three jobs rather than one, because each direction is a separate instruction producing a separate output to judge. Adjusting a direction and running again is the normal shape of the work rather than a sign that something went wrong — it is also the single biggest reason two businesses with the same number of projects use Studio very differently.
This page uses that definition to explain what moves usage. It does not use it to calculate an allowance: Avisual's published Visual Studio pricing page states each plan's allowance in its own units, and that page rather than this one is where the arithmetic belongs.
Four routes into Studio, from evaluating to changing a process
These are ways of adopting Studio, not the names on a price list. The published plan names and prices are on Avisual's Visual Studio pricing page.
The four below are routes rather than products: they describe where a business is when it starts paying attention to cost, and what it is trying to decide. Avisual publishes its plan names and prices in one place, linked from the two routes below that a published plan covers and again at the end of this page, and this page does not rename or repackage them.
Free runs, for evaluation
The route that exists so you can settle one question before committing to anything: whether a relevant workflow does something useful on the kind of material you actually work with. Avisual's Terms of Service state that free runs are for evaluation and are not an assured production allowance, so treat them as proof rather than as a production tier. The starting allowance is published on the Visual Studio pricing page.
Read what free runs includeIndividual use
For one person running Studio as part of their own work — a designer, a visualiser, a showroom salesperson, a sole practitioner. The decision is usually about how many directions the work needs rather than about how many people will use it. The published plans that cover individual use, and their prices, are on the Visual Studio pricing page.
Read the published plansTeam use
For several staff running the same workflows, where results have to stay comparable between people and someone has to be able to see what is being produced. What a team arrangement includes — shared workspace, roles, governance or reporting — is not published on this site, so it starts as a conversation rather than as a button.
Ask about team useProcess pilot
For a business changing how a visual step in its process works: a defined workflow, a selected staff group, a measurement plan and a rollout decision at the end. No commercial term attached to a pilot is published, because the scope is what determines it and the scope is the thing being agreed.
Ask about a process pilotWhat makes one business use more runs than another
Four variables, in roughly the order they move the number. Headcount is on the list, but it is last, and that is the point.
How many jobs you put through
The number of drawings, rooms, products or scenes that go through Studio in a month. Start here: it is the variable you can count from your own current workload, without knowing anything about Studio.
How many directions you test
Testing three material directions on one drawing is three jobs. This is where usage actually grows, and it is often where the value is too — the alternative is picking one direction because a second one would have cost another week.
Which grade of output you need
Avisual's published pricing treats presentation-grade, client-facing output separately from the everyday output you work with while deciding. Which grade a job needs is a usage decision before it is a quality one, and the distinction is published on the Visual Studio pricing page.
How many staff run it
More people running Studio means more runs, though not in proportion: two people testing carefully can use fewer than one person exploring broadly. Headcount is the weakest of these four predictors, which is why it is last.
One thing that does not appear as a variable above, because it belongs to the source rather than to the plan: an incomplete drawing or a poorly lit photograph needs more direction and more attempts before the result is right. Improving what goes in happens before Studio is involved at all, which is why it is the first thing to look at.
What is published about cost, and what is not
Two documents carry the commercial answers. Both are named and linked here, together with the questions neither of them reaches.
A pricing page is where a marketing site invents commercial terms, so this one states its sources. There are two of them. Avisual's Visual Studio pricing page carries the current plans and prices. The Terms of Service, effective 2 July 2026 and stating in their opening paragraph that they govern this website and the Visual Studio service, carry the terms that apply to free runs, paid allowances, ending an agreement and liability.
The figures are not repeated below, and that is a decision about maintenance rather than a claim that they are unavailable. A price copied onto a second page is a price that will eventually disagree with the first one, and a visitor who reads the stale copy has been misled by a page that was trying to be helpful. Where a commercial question has no published answer anywhere, it is named as open instead of being filled in.
- Where the current plans and prices are published
- Avisual publishes its current Visual Studio plans and prices on its Visual Studio pricing page, linked at the end of this section and again below. That page is where the figures are maintained and where they should be read; this page keeps no second copy of them, so there is only one version to keep correct.
- Free runs and paid allowances
- The Terms of Service state that free runs are for evaluation and are not an assured production allowance, and that paid plan allowances renew per billing period as described on the pricing page. They also require you to keep your account information accurate and your credentials secure.
- Ending an agreement, and what survives it
- The Terms of Service state that either party may end the agreement at any time, and that the sections which by their nature survive — content ownership and liability — continue to. They also state that Avisual may update the service and the terms, and that material changes are posted on the Terms page with a new effective date.
- The liability position that applies to a paid arrangement
- The Terms of Service state that, to the extent permitted by law, the service is provided as-is; that nothing in them excludes rights which cannot be excluded under the Australian Consumer Law; and that otherwise Avisual's total liability is capped at the amounts you paid in the twelve months before a claim. They are governed by the laws of Victoria, Australia. Trust sets this out alongside the rest of the published position.
- How a paid allowance meters against a run
- Not published. Avisual's Visual Studio pricing page states each plan's allowance in its own units. Whether the run defined at the top of this page maps one-for-one onto what a plan meters is stated nowhere, so read the allowance on that page rather than converting it from the definition here.
- When a failed run is refunded or re-credited
- Not published. Avisual's Visual Studio pricing page states that an AI support agent reviews failed generations and supports refunds where applicable. Which circumstances qualify, what form the remedy takes and how long it takes are stated neither there nor in the Terms of Service, and this page states none of them. Ask before you plan around it.
- Team and process pilot commercial terms
- Not published. No price, commitment, term, duration or service level attached to a team arrangement or a process pilot appears in the Terms of Service, on Avisual's Visual Studio pricing page, or anywhere on these Studio pages. Trust carries the same item in the same state.
- Running Studio before you register
- Not published. Avisual's published route to free runs begins with creating an account. Whether a run is possible without one, and what an unregistered session would carry over if you registered afterwards, is not stated on this site. Trust and How It Works carry the same item in the same state.
- Tax treatment of a published price
- Not published. Neither the Terms of Service nor Avisual's Visual Studio pricing page states whether tax is added to a published price or already included in it. Ask before you budget from a figure.
Visual Studio plans and prices
The current plans, what each one includes, and the figures themselves. This is the page the facts above point at, and it is where the prices are maintained.
Read the published plans and pricesTerms of Service
The full text behind the free-runs, paid-allowance, termination and liability facts above, including acceptable use and the governing-law position.
Read the Terms of ServiceTrust
What Avisual publishes about the material you upload — collection, purpose, hosting, retention, your rights and ownership — and the questions the published documents do not reach. A data question is answered there rather than here.
Read the Trust pageWhat businesses ask before they commit
Answered from the published documents, with the open questions named rather than smoothed over.
Can I try Studio before paying?
Yes. Avisual publishes a free starting allowance on its Visual Studio pricing page, and the Terms of Service state that free runs are for evaluation and are not an assured production allowance. They exist so you can judge the output on material that matters to you before any commitment — treat them as proof rather than as a production tier.
Why are the prices not repeated on this page?
Because they are published and maintained on Avisual's Visual Studio pricing page, which this page links from its routes, from the section naming its sources, and from the closing step. Restating them here would create a second copy that eventually disagrees with the first, and whoever read the stale one would have been misled by a page trying to be helpful. The prices are neither withheld nor waiting on a decision; they are one link away.
Can I use the visuals commercially?
The Terms of Service state that you may use the visuals you generate for your business purposes, that visuals are AI-generated and should be reviewed before client-facing or commercial use, and that virtually staged or digitally furnished property images must be disclosed as such. Trust sets out the ownership position alongside this.
How do I cancel, and what happens to what I have paid for?
The Terms of Service state that either party may end the agreement at any time, and that content ownership and liability survive it. What happens to an allowance you have paid for and not used is not published, and neither is a refund position, so ask about both before you rely on either.
Is a failed run charged?
Avisual's Visual Studio pricing page states that an AI support agent reviews failed generations and supports refunds where applicable. Which circumstances qualify and what form the remedy takes are not published there or in the Terms of Service, so ask before you plan around it.
What happens to the drawings and photographs we upload?
That question is answered on Trust rather than here. Avisual's published Privacy and Terms pages cover what is collected, what it is used for, that customer content is hosted on Google Cloud infrastructure, several retention rules, your right to ask for access, correction or deletion, and that you keep ownership of everything you upload. Trust states those answers and names the questions neither document reaches.
What Studio does not do
The limits are part of the product. Read them before you plan work around Studio.
- This page states no price, allowance or billing figure of its own. Avisual publishes its current Visual Studio plans and prices on its Visual Studio pricing page, which is linked here and is where the figures are maintained. They are not unpublished and they are not pending.
- The Terms of Service state that free runs are for evaluation and are not an assured production allowance. No route on this page is presented as usage without a limit.
- The four routes on this page are ways of adopting Studio, not plan names. This page does not rename, repackage or map the published plans.
- No price, commitment, term, duration or service level attached to a team arrangement or a process pilot is published anywhere on this site, and this page states none.
- A run produces one reviewable output. It does not produce an approved, verified or client-ready deliverable on its own, and your people remain responsible for professional judgment, product suitability, technical specification, customer commitments and final approval.
Choose your next step
Each route below produces something you can look at and judge.