A quick 3D scene mock for an agency pitch: Blender, stock assets and AI help

A 3D scene mock is a rough, low-detail model of a space or set (a shop interior, a stand at a trade fair, a product on a shelf) used to show a client where things go and what a viewer would see. It is not a final render. The best pitch mocks are fast, simple and honest.

This page is for an agency creative or freelancer who needs a concept scene for a pitch. It starts with the cheapest options, compares four routes, shows how to scope the mock, gives a two hour test with pass or fail marks, and covers scale, licence and security traps. If a 3D scene is overkill for your pitch, the lighter options are on moodboards in hours and storyboard to moving previs. If the pitch is a rebrand, rapid rebrand previews show three looks without any 3D work.

This page may contain affiliate links from which Blur Studio earns commissions.

The problem: a pitch needs a scene and 3D takes days

A client can read a layout from a sketch, but a 3D view makes the idea feel real. The risk is cost: hours of modelling for a pitch you may lose, and a polished look that makes the client think the work is nearly done. Both are fixable with scope and labels.

Cheapest first: photos, a sketch and a stock-asset blockout

• Real photos plus a sketch. A photo of the actual space with hand-drawn arrows is often enough to win the first meeting.
• A blockout. A blockout, sometimes called a grey box, is a scene made of plain boxes that show size and position, with no colour or detail. It fixes layout, scale and camera angle before any look is added.
• Blender with free assets. Blender is free 3D software. According to Blender's licence page, what you make with it (images, movies, project files) is your sole property and free to use commercially. Poly Haven, a library of free 3D models, textures and lighting maps, says all of its content is CC0, which means any use, including commercial, with no credit needed.

If someone on your team can drive Blender, a grey-box scene with a few CC0 models can be done in an afternoon. If nobody can, a freelance 3D artist for a half-day block is a safer buy than learning Blender under deadline.

Options compared

Route	What it is	Strength	Weakness
Blender with stock assets	Free 3D software plus free models	Predictable, free, you own the output	Needs someone who knows Blender
A freelance 3D artist	A person you pay for a time block	Dimensionally right, clean files	Ask for a quote; scheduling
Claude with a Blender MCP link	An AI assistant that drives Blender through a tool connection called MCP	Free to try on top of Blender	Inconsistent results; runs AI-written code (see security below)
Browser scene tools, for example Magnific 3D Scenes	A web tool where you pick a preset place, upload an image or a GLB model, place objects and shoot camera stills; no 3D skills needed, per its help page	Its help page says quick Standard captures use no credits, High Quality captures use AI credits, and the scene stays the same between shots. It is a vendor description, and I did not test the output	Credit use depends on the render; Street View places are not available on Enterprise plans
Event scene tools, for example Intangible	A tool aimed at events teams that turns a stage into a 3D scene you can reskin for each brand	The vendor says it keeps the structure when you swap brand and lighting; its page shows no prices (contact sales)	Built for events, so it may not suit a shop or product pitch
Higgsfield Blender plugin	An add-on that connects Blender to Higgsfield's cloud models	Scene Builder and 3D Model tabs inside Blender	Needs Blender 5.1 or later and plan credits; cost not published

The Blender MCP idea is not new. A May 2025 post from FOOH, a creative studio, describes it as a way to go from a concept to a rough 3D scene quickly for pitches, and also lists limits: natural language lacks precision for final production, results are inconsistent, and it is not stable enough for critical pipelines. It is not a replacement for a 3D artist. A later Picsart post describes a grey-box workflow where Claude builds a low-poly scene in Blender and a video model turns the render into a photoreal clip, with advice to lock the camera and keep the grey box simple. I could not verify who built Blender MCP, since sources differ, so I treat it as a community tool and not an official one.

Scope the mock to one question

Ask what the client must decide. "Where does the product sit, and what does a shopper see from the door?" is one question. Build only what answers it. Three to five camera stills beat a 30 second animation for pitch speed, because every still is a decision the client can point at.

A good brief for yourself has four lines: the question, the camera views (for example door view, aisle view, overhead), the three objects that matter, and the date you need it. Everything else is grey boxes.

Build once, shoot many views, then paint over

The saving in any 3D route is that one scene gives you many pictures. Build the scene once, then move the camera for each still. Browser tools such as Magnific's 3D Scenes say the same about their own product: the scene persists, so lighting and objects match across angles. A concept-art workflow described on The Prompt Index (a skills library, so treat it as one view) adds two habits worth borrowing:

• Time-box the blockout. It suggests spending no more than a quarter of the total time on the 3D stage, with plain shapes and no fine modelling. If the geometry looks good enough to hand in, you went too far.
• Paint over the render. Take the grey render and add mood, colour and materials in a 2D editor. That lets you hide rough geometry and still show the idea.

For review, some 3D platforms (Vectary's agency page, for example) offer a private link with comments on the 3D canvas. That is a vendor feature claim; stills in a deck work for most pitches and leave no link to expire.

A two hour time-box test with pass or fail

Before you commit to a route, give it two hours on one scene.

1. Write the one-question brief above.
2. Build a grey-box scene with the route you want to test.
3. Render three stills from three camera views.
4. Show them to a colleague who has not seen the brief and ask which layout they prefer and why.

Pass: your colleague can say which layout they prefer from the stills alone. Fail: more than half the time went on fixing geometry the AI got wrong, or the stills cannot answer the question. If it fails, switch to a stock-asset blockout or hire an artist.

Scale and dimension checks

AI-built scenes often ignore real size: doors that are too low, counters at odd heights, shelves that do not fit a person. Put one object of known size in every scene (a 2 metre door or a human figure) and check proportions before you send anything. If the mock will drive a real build or a print order, take dimensions from a measured plan, not from the mock.

Label it as concept and keep a licence list

• Label. Put a footer on every slide: "Concept visual, not final design." Clients and procurement teams have been burnt by mocks that looked like deliverables.
• Licence list. Keep a one-line note per asset in the project folder: where it came from and its licence. Poly Haven is CC0. Free-tier output from some AI 3D tools carries a licence that needs credit. For example, Meshy's Free plan uses CC BY 4.0, and its paid plans give private, customer-owned assets, according to its pricing page. Stock models from other marketplaces vary from CC0 to credit-required to editorial-only.
• Not unique. I would not assume an AI-made asset is unique or cleared everywhere. Check each tool's terms.

This is information, not legal advice, so check local law and each marketplace's current rules.

Security: letting an AI agent run code in Blender

This one matters. Picsart's post says Blender MCP runs AI-generated code inside Blender without guards, and that the Blender developers recommend a virtual machine or a computer with no access to sensitive information. Do not run it on a laptop that holds client files or saved passwords. Save and back up before each AI step. The same caution applies to any connector that lets an agent control Blender, including the bridge Higgsfield describes in its help center (a custom connector at bridge.higgsfield.ai/mcp).

Where Higgsfield fits and where it does not

According to Higgsfield's help center, its Blender plugin needs Blender 5.1 or later on Windows or macOS. It has tabs for Scene Builder (a described set lands in the open scene as editable geometry), 3D Model (a mesh placed at the 3D cursor, with materials), Character Animation, Image and Video, Camera and Asset. It uses plan credits at web rates, and generation runs in the cloud. The Claude connection, covered in the MCP guide, also lists 3D tools for turning an image into a 3D file.

What is not published: the credit cost for 3D, which plans include it and how good the Scene Builder output is. I found no independent test of it, so I will not claim quality beyond the help text. Run one real scene and read the cost from the button. For credits, see how to spend credits wisely and Higgsfield pricing explained, and check higgsfield.ai/pricing for the current numbers.

My honest view: if you already pay for Higgsfield and use Blender, the plugin is a quick way to get a rough set and a few meshes to start from. You do not need a Higgsfield credit to do an AI-assisted mock, since Blender and Claude with Blender MCP are free to try. And it is the wrong tool for final render quality, for anything dimension-critical, or if your team cannot install Blender 5.1 or later. If a pitch needs a moving look rather than a model, Higgsfield Cinema Studio or a mood video for the pitch may be quicker.

Review checklist before you send

• One question answered per still.
• A known-size object in every scene, and proportions look right.
• Footer on every slide: concept visual, not final design.
• Licence list saved for every asset.
• Work saved and backed up; no client files on the machine that ran AI-written code.
• A note on how you would rebuild it properly if you win.

Who should skip it

• A skilled 3D artist is better when the mock will become the final render or must be dimensionally right.
• Your pitch is about mood, not space. A moodboard or storyboard is lighter.
• Nobody on the team can install or learn Blender 5.1 or later. Hire a block of an artist's time.
• Your machine holds sensitive client data and you cannot use a separate one for AI-driven tools.
• You would be tempted to present the mock as final. Do not build it.

How I'd approach this

I would write the one-question brief, then try a plain Blender grey box with CC0 assets for the time-box test. If the team is fast in Blender, I would stop there. If not, I would try an AI-assisted route, such as the Higgsfield Blender plugin, in a separate, safe setup, and hire an artist for a half day if the stills did not answer the question. I would send three to five stills, marked concept only, and keep the licence list in the project folder. If you win, I would rebuild with real dimensions and real product files. For a related job, see a 3D view of a product for your website.

If your agency pitches often, the part worth building once is the pack around the mock: a brief template, a folder structure, a licence list, a concept label and an approval step. Blur Studio builds that repeatable creative workflow, client approval portal or asset library around these tools, which you can read about here.