What it usually really means: Budget exists but isn't allocated to this. The value hasn't been made clear enough to justify creating budget. Or — genuine timing mismatch with the budget cycle.

Clarify first: "When you say there's no budget — is this a timing issue where budget opens in Q3, or is it that this initiative hasn't made it into the current planning cycle yet? I ask because those are pretty different situations."

If it's timing: "That's completely fair. Let's use the time between now and the next budget cycle to build the business case together — so when the cycle opens, you're not starting from scratch. Would that be useful?"

If it's not a priority yet: "Our pilots start at $3K for a single facility — which for most companies comes out of operational discretionary spend rather than requiring a capital budget request. Would it make sense to start there and use the pilot results to make the case for the broader program?"

What it usually really means: This isn't in their top three priorities. Or — the person you're talking to doesn't have enough internal pull to move this forward.

Clarify first: "That makes total sense. What are the top two or three things your team is most focused on right now?"

Listen for adjacent priorities. If they mention a capital project, shutdown, ERP rollout, or safety initiative — connect Prevu3D directly: "Actually that's exactly where we fit. The retrofit you mentioned — that's where not having accurate 3D facility data creates the most risk. This isn't a separate project from that — it's the data foundation that makes that project go better."

Never disparage the competitor. Ask what's driving the interest in that specific vendor first — the answer tells you exactly how to differentiate.

vs. NavVis: "NavVis is solid for factory floor visualization. The challenge is they require their proprietary VLX3 hardware. If you have existing Leica, FARO, or Trimble scanners, moving to NavVis means replacing hardware you've already invested in. We work with any E57/LAS data from any scanner you already own. And NavVis doesn't have native ERP integrations into SAP or Maximo."

vs. Matterport: "Matterport was built for real estate. After the CoStar acquisition their industrial roadmap is unclear. They don't have native CAD/BIM plugins, they don't integrate with SAP or IBM Maximo, and there's no asset tagging layer for industrial operations."

vs. Cintoo: "Cintoo is our most direct competitor — their TurboMesh processing is genuinely good. The difference is operational depth. Cintoo doesn't have native SAP, Maximo, or AVEVA connectors, and their CAD plugin ecosystem is narrower. They have a P&ID editor that we're building toward in RealityPlan™ — I'll be honest about that gap. But if the priority is connecting your digital twin to your enterprise systems and CAD tools, we're significantly deeper."

vs. Hexagon: "Hexagon is a fantastic survey-grade tool. Their challenge is they're hardware-centric — the ecosystem is built around selling Leica scanners. They use per-seat licensing which gets expensive fast at scale, and they don't have an operational asset management layer or ERP integration capability."

Clarify first: "I completely understand. Can you walk me through what the build would look like? What tools would you use, and who would own the integration maintenance?"

The questions that surface the real cost: "What's your internal timeline to get this built and operational?" / "When your ERP updates — and SAP updates regularly — who rebuilds the integration?" / "What's the cost of your engineering team's time while they're building this instead of running projects?"

The reality: "Customers who tried to build this internally before coming to us typically spent 12 to 18 months and significant engineering time before the project was abandoned. The proprietary meshing engine alone is the result of 7 years of development. We can have you operational on a single facility in weeks, not months."

Never minimize this objection. Security concerns are legitimate for critical infrastructure. Get IT involved as a partner early — not a blocker to get past.

What to provide immediately: SOC2 Type II certification · GDPR compliance overview · CyberSecure Canada certification · Security architecture overview · Data residency and encryption documentation

The offer: "The fastest way to get through this step is a direct conversation between your IT security team and ours. Our security team does these calls regularly. Can we set that up as the next step?"

On data ownership: "Your scan data is always yours. We host and process it, but the data itself is never locked in. You can export everything at any time."

Acknowledge the real concern: "That's a fair concern. Can I ask: when tools have failed to get adopted in the past, what was the biggest reason? Was it complexity, relevance, or the change management process?"

On complexity: "Prevu3D is browser-based. No installation, no training certification. If your team can navigate Google Maps, they can navigate Prevu3D."

On relevance: "We don't replace anything your team already uses. We sit alongside Revit, Plant 3D, and SAP — the workflow change is minimal."

On unlimited users: "There's no per-seat cost. That means you don't have to choose who gets access — everyone does. Adoption is much faster when there's no license allocation conversation."

This is a buying signal. They're already thinking about full deployment — they just want proof before committing.

Lean into it: "That's exactly the right instinct — and that's exactly why we structure our pilots the way we do. You shouldn't commit to a 40-facility rollout without seeing it work in your environment first."

Reference the scale proof: "Amsted Rail started with a single facility before rolling out to 40 locations across 6 continents. General Mills started with one plant and now runs 20+. Every major deployment started as a pilot on one facility."

Convert to a pilot: "Let's define the pilot together. One facility, 2–3 specific success criteria, and a timeline to present results to [VP / economic buyer]. If the pilot delivers — and I'm confident it will — you have the internal proof to take the broader rollout forward."

The funding narrative: "Prevu3D has raised $18.3 million in total funding from institutional investors — Cycle Capital, Brightspark Ventures, Desjardins Capital, McRock Capital, and Fonds de solidarité FTQ. The most recent round, $5 million from FTQ, closed in early 2026. These are growth-stage investors who've done full diligence on our business model and customer retention."

The customer validation: "General Mills doesn't standardize 20+ plants on a platform they don't trust to be around. Amsted Rail doesn't deploy us across 40 locations on 6 continents without confidence in our longevity. Deutsche Bahn has legal and procurement teams that run extensive vendor financial reviews."

The data ownership answer: "And practically — your scan data is always yours. You can export everything at any time. If anything ever happened to Prevu3D, you walk away with all your facility data in standard formats. You're not locked in."

What it really means: They're not engaged enough to commit to a next call. "Send me information" is almost never followed by a deal. It is a polite way of ending the conversation.

Acknowledge and redirect: "Of course — happy to send something over. Before I do, I want to make sure I send you something that's actually relevant to your situation rather than a generic brochure. Can I ask you two quick questions so I know what to focus on?"

Ask the two questions: "What's the biggest thing you're trying to solve on the engineering or operations side right now?" and "Who else at [Company] would be involved in a conversation like this?"

After they answer: "Based on that, I'll put together something specific. And given that [VP / ops lead] would be involved, would it make sense to set up a call so we're not doing this through documents? I find a 20-minute call covers way more ground than any PDF. How does [Day] look?"