One photo of your current model or render — a screenshot, a render still, whatever you’ve got right now. We’ll reply with the single biggest thing we’d change, and why. No render, no list, no obligation.
Why one thing, not a list
Ask most people for feedback on a render and you’ll get ten small notes back — a palette here, a prop there. Ten notes is easy to give and hard to act on. One prioritized verdict — the single change worth making before anything else — is the harder read to write, and the only one you can actually use today.
Three real renders, mid-progress and finished alike. Below each is the shape of what a reply looks like: one change, named plainly, and the reason it comes first.
01 Rooftop terrace
Not the pergola, not the planting, not the figures — the one thing: the terrace floor is catching two competing shadow directions off the slats and a nearby wall, so the eye can’t settle on a datum line before it starts reading the seating groups. Tighten the sun to one raking angle and that alone resolves it, before anything else on the frame gets touched.
02 Executive office
Not the artwork, not the furniture layout, not the palette — the one thing: the two roller blinds either side of the window are dropped to two different heights, and at a glance that reads as an oversight rather than a considered asymmetry. Level just those two elements and the one detail a first-time viewer’s eye catches first is gone.
03 Outdoor dining pavilion
Not the chairs, not the tree line, not the lantern — the one thing: the glazing behind the stone table is returning almost as much interior detail as the table itself is showing, so two materials are asking for the same attention in one frame. Drop that reflection down and the stone slab leads the image the way the brief clearly wants it to.
We’d rather you know exactly what you’re asking for than send a photo and be surprised by the answer.
The reply names exactly one change — not a punch list. If a second thing genuinely matters, we’ll say it’s worth a separate look rather than fold it in and dilute the first.
We don’t make a test render, a touch-up pass or a “quick fix” to show you what we mean. The read is written — what we’d change, and why — based on the photo you send.
If the read is useful and it turns into a job later, good. If it doesn’t, you still keep the read. Nothing about the reply commits you to anything.
A screenshot, a render still, a phone photo of a screen — whatever shows the current state. We’ll come back with one specific, honest verdict — not a form answer, and not a render.
Reply nowOne photo of your current model or render — a screenshot from your 3D software, a render still, even a phone photo of a screen. No polish needed, and it doesn’t need to be finished.
A list of ten notes is easy to write and hard to act on. Naming the single highest-leverage change is the harder, more useful call — and the one you can actually go do something with today.
No. That’s the point — the read is a written verdict, not a rendered image. If you’d rather see it than read about it, our regular free-render offers cover that.
A specific, honest verdict — not a form response — usually inside a couple of working days. If the photo needs more context to answer honestly, we’ll say so and ask.
Then that’s the answer, said plainly, rather than a critique manufactured to fill the reply. Not every image has one obvious lever — and we won’t pretend it does.
No. The read is yours regardless. If it turns into a project, we’ll talk about that separately — nothing here is priced or upsold.
Reply with it — we'll send back the one thing we'd change, no render made and nothing owed either way.
