Scope, timeline, or budget — whichever is genuinely unresolved right now. Reply with it and we’ll tell you honestly how we’d scope the render phase around it. No render, no pitch.
Why not just quote it?
A quote answers a question you’ve already resolved. Most render briefs stall on one that isn’t — how many views it actually needs, how much the timeline compresses the process, or which finish decisions are still open. We’d rather answer that first, in writing, before either of us commits to a number built on an assumption.
01 Scope
A scheme built from repeating units — offices along a corridor, units in a block, bays in a facade — raises the same question every time: does the render phase need one representative view, or does every condition genuinely differ enough to earn its own frame? We’d rather answer that before a quote than after one, because the honest answer is often fewer views than the brief assumes.
02 Timeline
A fast-track or modular project usually means a fast-track render phase too — and that trade is real: fewer review rounds, tighter turnaround windows, less room to iterate the light or the material read before delivery. We’d rather name that trade in the scope than discover it mid-project as a missed deadline.
03 Budget
A space with several distinct programs under one roof — a pool, a spa, a gym, a lounge — carries several distinct finish-level decisions, and each one moves the render brief. We’d rather scope the phase around what’s actually decided than around what a first-pass budget number assumes is decided.
We’d rather you know exactly what you’re asking for than send something and be surprised by the answer.
We don’t make a test render, a sample frame or a proposal deck to show you what we mean. The reply is a scoping answer, in writing, based on what you send.
Scope, timeline, or budget — pick whichever is actually unresolved right now. You don’t need all three answered to get a useful reply.
If the scope is useful and it turns into a project later, good. If it doesn’t, you still keep the answer. Nothing about the reply commits you to anything.
Scope, timeline, or budget — just the one that’s genuinely unresolved. We’ll come back with an honest, specific scope for the render phase — not a form answer, and not a render.
Reply nowJust the unknown itself, in your own words — "we don’t know how many views we’ll need," "the build is on a compressed timeline," or "the finish level isn’t locked yet." No drawings or CAD are required to start.
No. The reply is how we’d scope the render phase around that specific unknown — what we’d hold fixed, what we’d leave flexible, and why. Pricing, if it comes up, is a separate, later conversation.
A specific, honest scoping answer — not a form response — usually inside a couple of working days. If we need one more detail to answer honestly, we’ll ask for it.
Those three cover most of what stalls a render brief before it starts, but reply with whatever the real unknown is — the scoping answer works the same way.
No. The scoping reply is yours regardless. If it turns into a project, we’ll talk about that separately — nothing here is priced or upsold.
Yes. Our regular free-render offers deliver an actual image. This one deliberately doesn’t — it answers the planning question that usually comes before any render gets made.
Reply with it — we'll send back an honest scope for the render phase, no render made and nothing owed either way.
