Corb.
He knows every tool and price on the platform, he knows how an architectural project is actually put together, and he does the legwork rather than just describing it.
Most software assistants are a search box with manners. They'll tell you where a menu is and that's about the end of it. Corb sits across the whole platform: he knows what each studio does, what a job costs before you commit to it, what stage your project is at, and how a design statement differs from a planning statement. Then he goes and does the part you didn't fancy doing.
What makes an assistant worth having.
Right about the platform
His knowledge of models, credit costs and your plan comes from the same source the app bills from, so he cannot quote a stale price or a dead model.
Able to actually do it
He generates images, video, audio and documents, runs research, and sets your brand colours and voice. He does the work itself on your say-so, rather than pointing you at the menu where you could have done it.
Fluent in the discipline
He knows which RIBA stage or AIA phase a project's at and scopes his advice to it. He knows a design statement from a planning statement, too.
He knows which room you're standing in.
Ask a question inside the drawing studio and you get a drawing answer; ask the same question in the rendering studio and you get a rendering one. He reads the surface you're on, so you're not explaining your own context back to him every time you open the chat.
Open Corb
A director when the job needs one.
In Shoot he briefs like a director, thinking in shots, continuity and sequence. On the canvas he'll read a shot of the massing model you're actually working on and talk about the building in it rather than only the picture of it. He's also a prompting strategist, which matters more than it sounds. The difference between a usable render and a wasted credit is usually the brief, and most people have never been taught to write one.
He asks before he spends.
Credits are real money and he treats them that way. He proposes, shows you the cost, and waits. He'll put two or three options in front of you rather than one answer, and he expects you to pull them apart. He's an assistant, not a replacement, and every creative decision stays yours.
He looks things up.
Planning policy, local precedent, a material you've never specified before, what the practice down the road got away with on a similar site. He searches the live web and cites what he found, so an answer about the world outside the platform is checkable rather than remembered.
What Corb brings to the work.
Platform knowledge that cannot drift
Models, credit costs and plan entitlements come out of the same source the app bills from, rather than a list somebody has to remember to update.
Real actions
Images, video, audio, documents, research runs and brand settings, executed rather than explained.
Architectural project stages
He reads the RIBA stage or AIA phase a project is at and scopes advice to it, and he knows a design statement from a planning statement.
Cited web research
Live lookup for policy, precedent and context, with sources attached so an answer can be checked.
He answers like a photographer
Foreground, camera height and lens, which light dominates, entourage at real scale. Ask why a render reads flat and you get a photographer's answer.
Variations on your own image
On the canvas, one image becomes a spread. One thing moves at a time (the light, the weather, the camera height) and every prompt holds your building exactly as you drew it.
Frequently asked.
Ready to start? Jump straight in.
Every ArchAdemia Tools plan includes everything on this page. From £29 a month, all in, with no per-tool fees and no surprise charges.