Who signs off on a 3D sales platform, and what each approver asks

A marketing director at a developer we were pitching walked the whole development on her phone during the demo, watched the interior styles switch mid-tour, and told me at the end that she was sold. Six weeks later the deal had not moved. When I finally got her on the phone, finance was waiting on a number nobody had given them, legal had a data-controller question sitting in a queue, and IT wanted to know who they would ring at nine on launch night. The demo had won one person and had not reached the other four.

That is the shape of almost every stalled evaluation. A 3D sales platform is a committee purchase, and the committee has five seats. Each seat defends a different loss: a capital commitment, a brand, a recurring bill, a data liability, a support burden. So the same demo has to survive five unrelated cross-examinations. The champion's real job is to arm each of the other four seats with its one answer before the meeting, so no seat has a reason to sit on the file.

Below are the five seats and the one question each one asks. Name your own committee against this list, answer the five questions in advance, and route each approver to the deep-dive that satisfies them.

1. The developer principal: what shape is the commitment?

The principal is not asking whether it looks good. They want to know if this is capex or opex, if the smart move is to build it or buy it, and which cost scales if the project succeeds. That last part is the one that catches people. A real-time, per-viewer rendering setup bills a GPU slice for every concurrent buyer, so a launch-day traffic spike becomes a cost spike. Pre-rendered video has no per-viewer compute term. The principal wants to know which curve they are signing up for. That is a whole argument on its own, and it belongs to build vs buy interactive 3D. Hand it to them; don't relitigate it in the room.

2. Finance or procurement: what does the recurring bill do?

Finance has one fear: a bill that keeps growing and a change process that keeps invoicing. So their question is concrete. When a unit's price moves, or a floor sells out, does the sales team make that edit themselves, or does it become a support ticket the vendor charges for? On the Vinode Back Panel that edit is self-serve. The sales team makes it in the CMS, no ticket, no invoice. That is the kind of specific answer this seat needs, not a reassurance.

Finance also wants the shape of the commitment without a quoted figure. Vinode structures packages in tiers by size (up to 6 units, up to 250, and 500+) and quotes each project rather than publishing a price, which tells finance the commitment scales with the development. The full three-year recurring-cost model is its own piece: the true cost of ownership.

3. Marketing lead: will it look right, and load on a buyer's phone?

Marketing owns the brand and the buyer's first impression, so their question folds two things into one: does it look like our development, and does it actually load on the mid-range phone a real buyer is holding? A tool that renders beautifully on a demo laptop and stalls on an old handset fails this seat even if it passed everyone else. The test is to open a live project on the worst device you can find. How to score that properly, including device reality, offline behaviour, and the sample test on the renders, sits in the vendor checklist.

4. Legal reviewer: who is liable for the data?

Legal defends against a data liability, and their question is universal even though the statute isn't. Three things they need answered: who is named data controller, is there a data processing agreement, and what survives the export if you leave. The jurisdiction matters here. A St. Gallen or Polish project sits under GDPR; a Saudi development like Safa Al Fursan does not. The question is the same everywhere. The law you answer it under is not.

Here is the discipline that matters, and it applies to us too. Nobody should answer the controller question off a blog. It is a contractual question, and the right move is to put it to every vendor you evaluate, Vinode included. The framing, and how to actually check the controller line and the export seam, is in data ownership and GDPR for real estate leads.

5. Technical evaluator: who do we call when it breaks?

The technical seat is not evaluating the render pipeline. They want to know who picks up the phone when something goes wrong on launch night, and how many vendors they have to chase to get an answer. This is where a single-stack delivery earns its keep. When the 3D, the floor plans, the Back Panel CRM and CMS, and the site all come from one team, there is one number to ring instead of a finger-pointing chain between a 3D house, a web agency, and a hosting provider. The device and offline reality this seat also cares about is scored in the same vendor checklist, and the reason per-viewer streaming cost scales with traffic, a real operational risk on launch day, is worked through in pixel streaming vs pre-rendered 3D.

Who this doesn't help: developers with in-house 3D teams

If you are a serial developer with 3D artists and web engineers already on payroll, the committee is shorter. Your technical seat may argue to build the thing in-house, and the licensing math starts to matter. As of 2026-07-02, Epic charges $1,850 per seat per year for commercial non-game work on Unreal Engine (Epic Games pricing), and a median U.S. software developer runs about $133,080 a year before benefits. Those are the numbers that seat weighs. For everyone buying rather than building, this five-seat routing is the map. It will not do the sign-off for you, but it stops the deal dying in one seat's inbox.

Answer all five questions before the demo

Turn the five questions into a pre-flight checklist. Before you book the demo, get finance the change-process answer, hand legal the three data questions, give marketing a live link to open on a cheap phone, walk the principal through the cost-shape argument, and give the technical seat the one-vendor answer. The committee scales further than you'd think. The same five seats sign off on a 528-unit Riyadh development and a 110-apartment rental block in Switzerland. What changes across projects is the size of each seat's stake; the five questions hold steady. Answer all five in advance and the demo becomes the confirmation rather than the decision.