Point Cloud to Revit Pricing Models

If you have ever requested three quotes for the same scan-to-BIM project and received three wildly different numbers, you are not misreading the market - you are watching three different pricing architectures collide. Before you can compare vendors, you need to understand which billing model each quote uses, what it includes, and which one actually protects your budget given your specific scope. What follows is a breakdown of all three models, the MEP cost multipliers vendors rarely volunteer, expedited surcharge mechanics, and four project cost scenarios illustrating how pricing logic applies across common project types.

---

Why Point Cloud to Revit Pricing Is So Confusing

Three billing structures circulate simultaneously in the scan-to-BIM market - hourly, fixed-fee, and per square foot - and most vendors never explain which one is cheaper for a given project type.

Consider a 10,000 sq ft single-floor office. An offshore shop might quote $0.08/sq ft ($800 total). A US firm might quote $0.35/sq ft ($3,500). Both numbers are technically defensible - but they are not the same deliverable. The $800 quote is likely LOD 200 architectural-only with no MEP, a generic Revit template, and a 10-day offshore turnaround with asynchronous RFI resolution. The $3,500 quote may include LOD 300 architectural plus basic MEP, your firm’s Revit template, a US-based modeler reachable by phone, and a 7-day delivery. Comparing them on a per-square-foot basis is like comparing a structural steel erection quote to a drywall quote because they both cover the same building.

The ambiguity runs deeper than discipline scope. One vendor may quote on net modeled area, excluding mechanical rooms, vertical shafts, and roof; another quotes gross building area with the suspended ceiling grid modeled as individual elements. The same 20,000 sq ft building can produce an $8,000 spread between two technically honest quotes that are simply measuring different things with the same label.

---

The Three Pricing Models Defined

Hourly

Hourly billing rates vary considerably across the US market and between domestic and offshore teams. Hourly billing is the right structure when scope cannot be fully defined before work begins: adaptive reuse projects where demolition reveals surprises, phased tenant improvements where design decisions are still in flux, or any workflow where the client needs iterative modeling with frequent course corrections.

An open-ended hourly engagement with no not-to-exceed clause can balloon on a complex project. If you go hourly, set a milestone check at 40% of the estimated hours - before the budget is committed, not after.

Fixed-Fee (Lump Sum)

A single price negotiated before work starts. For fixed-fee to work cleanly, four things must be true: the LOD is confirmed per discipline, the point cloud is already registered and clean, the deliverable format is agreed upon (.rvt version, shared parameters, naming convention), and the revision rounds are capped in writing.

Fixed-fee favors the client on well-defined scope. It favors the vendor on poorly defined scope - because every ambiguity becomes a change order opportunity.

Per Square Foot

A flat rate applied to gross floor area or modeled area. This is the most common shorthand in the industry and the most misleading. The same building can quote at $0.10/sq ft or $0.55/sq ft and both figures can be internally consistent - because discipline scope, LOD, and point cloud quality move the number by 4x or more.

Always ask: Does the rate apply to gross building area, net modeled area, or registered point cloud footprint? Then ask for a discipline matrix - what is modeled and what is not, by system.

Note on Blended Models

Many real proposals combine structures. Our typical proposal for a complex healthcare facility uses fixed-fee for the architectural shell (well-defined, traceable geometry) and hourly for MEP coordination and RFI responses (open-ended, iterative). This blended approach almost never appears in generic pricing guides, but it is the structure that actually matches real project risk.

Pricing Model Comparison Table

---

What a Per-Square-Foot Rate Actually Includes (and What It Does Not)

Market rates for scan-to-BIM modeling vary considerably based on discipline scope, LOD, regional labor costs, and project complexity (modeling only - assumes a registered point cloud is already delivered). The table below reflects illustrative ranges for planning purposes; actual quotes will depend on your specific variables.

What is typically excluded from per-sq-ft quotes:

• Point cloud registration and processing (separate line item or already completed upstream by the scanner operator)
• Clash detection reports
• Parameter population beyond basic family geometry (COBie data, cost parameters, asset tags)
• 2D sheet set creation (floor plans, sections, RCPs exported as sheets)
• IFC export and validation
• Expedited delivery surcharges

For a full breakdown of scan-to-BIM cost components including scanning, registration, and modeling as separate line items, see our dedicated cost resource.

---

How Much Does MEP Add to the Cost?

MEP scope is the single largest cost multiplier in scan-to-BIM work. Adding MEP disciplines to an architectural-only scope represents a substantial premium - commonly well over 50% depending on system density and LOD. Here is how the adders break down at LOD 300:

Data centers and laboratory/cleanroom facilities are outliers. Dense above-ceiling conditions with four to six crossing systems - power distribution, cooling, compressed air, specialty gases, IT infrastructure - push MEP modeling substantially above the rates for standard commercial work. These environments also require the highest scan density and the cleanest point clouds. For more on these project types, see our work with scan-to-BIM for dense MEP environments like data centers.

LOD matters at least as much as discipline scope. At LOD 200, a mechanical duct is represented at approximate size and centerline location - fast to model, lower value for coordination. At LOD 350, every fitting, reducer, flex connection, and access panel is modeled and clash-ready against structure and other disciplines. The LOD 350 model for the same floor can cost meaningfully more per square foot than LOD 200 for the same duct runs. For a detailed visual comparison, see what LOD 200 and LOD 300 models actually look like in Revit.

Worked example - 45,000 sq ft hospital floor, mid-rise tower, mixed occupancy with a populated mechanical plenum:

The Scenario B hospital below illustrates how these adders stack. Here is how the $18,000-$26,000 total decomposes across disciplines at LOD 300:

The range spread ($18,000-$26,000) reflects cloud density variation - a point cloud with dense plenum coverage compresses modeling time toward the lower end of the range. Medical gas required family-level accuracy throughout: those runs feed critical care equipment, and a misrouted branch in the model triggers a field coordination failure. On a hospital floor with less well-defined scan coverage or more complex routing, the upper bound is real.

For comparison: the same 45,000 sq ft floor at LOD 200 architectural-only would run approximately $9,000-$11,250 (at $0.20-$0.25/sq ft). The LOD and discipline scope - not the square footage - are what move the number from $9,000 to $26,000 on the same building.

---

Fixed-Fee vs Hourly: Which One Fits Your Project?

The decision turns on one question: how precisely can you define the deliverable before work begins? The table below maps scope clarity to the right structure with concrete consequences attached.

Fixed-fee is the right structure when the point cloud is registered and clean, LOD and discipline list are confirmed per AIA E203/G202 or the BIMForum LOD Specification, the project has a firm deadline with no mid-project design changes, and revision rounds are capped at one or two rounds in writing.

Hourly is the right structure when you are working on an adaptive reuse project where demolition or field investigation will reveal unknowns after modeling starts, or on a design-assist workflow where the Revit model feeds schematic decisions that are still in flux.

The red flag to watch for: A vendor offering a very low fixed-fee on a poorly defined scope is almost certainly planning to issue change orders - or delivering a model that meets the letter of the contract but not the spirit. We have reviewed competitor deliverables where the “LOD 300” model used in-place families for every non-standard condition throughout the building. Beyond being non-compliant with most LOD specifications, the file size consequence alone is significant: a 20,000 sq ft LOD 300 model built with in-place families for non-standard conditions can run considerably larger than one built with proper loadable families. More critically, in-place families cannot be scheduled or tagged in Revit - every MEP component built that way is invisible to downstream facility management queries, COBie exports, and clash detection workflows. If the facility manager tries to pull a duct schedule post-occupancy and gets a blank sheet, that is the deliverable failure that in-place family abuse produces.

Use our scan-to-BIM quote checklist to lock a fixed-fee scope. Minimum inputs required before any fixed price is binding:

1. Registered .rcp file delivered and confirmed clean
2. LOD specification per discipline in writing
3. Revit version confirmed (2022, 2023, 2024, or 2025)
4. Shared parameter file provided or vendor template approved
5. Naming convention documented
6. Number of revision rounds stated
7. RFI resolution process agreed upon (cloud ambiguity vs. scope change)

---

Expedited Turnaround Pricing: What Rush Fees Look Like in Practice

Standard turnaround in the US market for a 10,000-30,000 sq ft project at LOD 300 architectural typically falls in the range of 5-10 business days, though this varies by vendor and current workload. Larger projects (50,000+ sq ft with full MEP) typically run longer under standard scheduling.

When rush pricing is worth it: Construction holds where the contractor is billing standby time, disputes requiring as-built verification before a deadline, permit submissions with a hard filing window. When it is not: Design development phases where decisions are still in flux. Paying a rush surcharge to accelerate a model that will require three more revision rounds to reflect design changes is wasted money.

Critical rule: Any expedited request must be paired with a scope freeze. The moment a mid-project change order arrives on a rush job, the time advantage collapses.

How our expedited workflow actually runs: When our Trimble X7 crew finishes a scan, the device auto-registers on-board and we walk off site with a complete .rcp - no post-processing required. That file is on our shared server within 30 minutes of leaving the building. Some other scanner workflows produce a denser scan but typically require a post-processing pass before the registered cloud is modeler-ready. On a same-day or next-business-day turnaround, that distinction matters - the Trimble X7’s on-device registration lets us commit to same-day modeling start with confidence; workflows requiring a post-processing pass build in a processing buffer that has to be reflected in the schedule and priced into the commitment.

Once the cloud is live, field QA and modeling run concurrently rather than sequentially - the modeler calls the scanner operator directly to resolve shadow zone ambiguities in real time rather than waiting for a next-morning email cycle. For a 5,000 sq ft commercial build-out, this cuts the effective handoff lag from 24 hours to under 2 hours.

---

The Real Cost Drivers Behind Per-Square-Foot Price Variation

Square footage is a proxy for complexity - and a loose one. Here are the seven variables that actually move the price:

The stacking effect: A pre-1950 hospital with a dense mechanical plenum, a strict BEP, LOD 350 MEP, and a noisy legacy point cloud can legitimately price at multiples of the rate for a modern, open-ceiling warehouse at LOD 200 architectural-only - at identical square footage. When you see a wide quote range, this is the mechanism.

On building age and irregularity: The +15-35% overhead for pre-1950 non-orthogonal construction is not a contingency buffer - it reflects a concrete workflow difference. In a post-2000 orthogonal building, a modeler extrudes a wall profile once and it holds floor-to-floor. In a pre-1950 masonry building with settled floors and non-plumb walls, wall thickness commonly varies 2-4 inches between the first and third floor of the same wall assembly. That forces manual section cuts at 6-8 ft intervals rather than a single extrusion - three to four times the per-linear-foot modeling time on every exterior wall. Compound that across irregular column grids, non-parallel room geometries, and floor plates that are not level, and the overhead is structural to the project, not optional.

On point cloud quality: Our terrestrial scanner - the Trimble X7 - delivers a point accuracy of 3.5 mm @ 20 m (per the manufacturer’s published specifications) at typical station spacing of one station per 400-600 sq ft. When a registered .rcp is imported into Autodesk ReCap and handed to the Revit modeler, they are tracing clean geometry. When a client provides a legacy cloud at reduced density with some target drift, or a scan from a consumer-grade device, the modeler spends 20-40% more time on interpretation and QA. That time is real cost, and it drives the wide range on Scenario C below.

For context on how LOD selection affects scan-to-BIM scope and ceiling modeling, including the cost implications of modeling suspended ceiling grids and T-bar systems, see our companion article.

---

US Firm vs Offshore BIM Team: Where the Economics Actually Land

Offshore BIM teams can deliver LOD 200-300 architectural models at rates meaningfully lower than a full-service US firm. For well-defined, low-complexity commercial work (single-floor tenant improvements, basic architectural documentation with a clean cloud and a complete BEP), that cost gap is defensible and real.

The economics shift on three specific project conditions:

Coordination-heavy MEP work. A 12-hour time difference turns a 2-hour RFI resolution into a 2-day email chain. On a tight construction schedule where the GC is holding a subcontractor pending model confirmation, that 2-day gap has a real dollar cost that often exceeds the per-square-foot savings.

US building code interpretation embedded in family selection. Choosing the correct Revit family for a fire-rated assembly, an ADA-compliant fixture, or a seismic-braced duct hanger requires US code familiarity that is difficult to specify in a scope document and difficult to audit in a delivered model. The most common deliverable defect in offshore LOD 300 MEP models is not a gross error - it is centerline-only ductwork submitted as LOD 300, with blank shared parameters and floor-to-floor copy-paste of duct routing that ignores beam framing clearly visible in the point cloud. The ductwork looks modeled; it is not coordinated. Catching this in a QA audit requires comparing every major duct run against the cloud and the structural model - work that costs time and money after delivery rather than preventing the error upstream.

Tight turnarounds. Offshore teams are well-suited for phased, planned work with clear deliverables and reasonable timelines. They are not structured for 48-hour response windows.

Field-to-model continuity. When the same firm that scanned the building builds the Revit model, shadow zone ambiguities get resolved by a phone call. Because the same team runs the capture and manages the modeling under one project manager, the modeler can ask the person who ran the Trimble X7 what was behind the mechanical unit that blocked the east wall - a quick clarification, not a return-visit scope request. The offshore alternative is a revised scope request, a photo request back to the client, a return-visit quote, and a 2-day cycle. On a 10,000 sq ft project with three or four shadow zones, that cycle time difference is measurable in budget and schedule.

For a detailed breakdown of the US firm versus offshore BIM team tradeoffs, including what a proper QA audit of an offshore deliverable looks like, see that resource.

What to audit in any BIM deliverable regardless of origin:

• Family LOD matches the specified LOD per discipline matrix
• Shared parameters are populated, not blank
• No in-place families used where loadable families were required - in-place families inflate file size and cannot be scheduled or tagged
• RVT file size is proportional to scope
• Registration residuals documented - ask for the registration report confirming station-to-station residuals are within acceptable tolerances for your project requirements

---

How to Get a Defensible Fixed-Price Quote: A Step-by-Step Checklist

Step 1: Provide the registered point cloud. Deliver an .rcp (Autodesk ReCap) or .e57 file - not raw scan data. Raw scans require registration, which is a separate upstream cost. See pricing context for laser scanning minimum project fees for what to expect on the scanning and registration side. The registered cloud is the single most important input for de-risking a fixed-fee engagement.

Step 2: Define LOD per discipline. Use the AIA E203/G202 framework or the BIMForum LOD Specification. “As detailed as possible” is not a scope - it is an open-ended hourly engagement written to look like a fixed price.

Step 3: Specify Revit version. State 2022, 2023, 2024, or 2025. Version mismatches cause rework - and in a fixed-fee engagement without a version spec, the vendor prices that risk back into the quote.

Step 4: Provide your Revit template and shared parameter file. If you do not have a firm standard, confirm the vendor’s template is acceptable in writing before work starts, not after the model is delivered.

Step 5: Cap revision rounds. State the number included (typically one or two) and define what constitutes an RFI versus a scope change. RFIs (questions about the cloud geometry) should be absorbed by the vendor. Scope changes (adding a discipline, upgrading LOD mid-project) are always additional.

Step 6: Define the complete deliverable. Is it a .rvt model only? Or does it include 2D floor plans, reflected ceiling plans, sections, and an IFC export? Each additional deliverable type carries cost.

Step 7: Confirm shadow zone protocol. If shadow zones are discovered during modeling that require a return scan visit, define upfront who pays and what the process is. On buildings over 20,000 sq ft, a shadow zone requiring a return visit happens on the majority of projects - plan for it contractually rather than arguing about it after the fact.

For the technical mechanics of how point clouds move from the scanner to Revit, see the complete scan-to-Revit modeling workflow and our guide on how to import a point cloud into Revit.

---

Sample Cost Scenarios: What Real Projects Actually Cost

The ranges below are illustrative industry scenarios - not binding quotes. They reflect the pricing logic and cost structure that apply to these project types based on discipline scope, LOD, cloud quality, and turnaround. Your specific variables will shift the numbers.

Scenario A is the clean baseline - a modern orthogonal office, limited MEP scope, client-provided cloud. The basic MEP (ductwork and plumbing mains only, no fittings) keeps the number below $4,200. Adding fittings and electrical at LOD 300 would push this to $5,500-$7,000.

Scenario B is the most common complex engagement type. See the discipline cost breakdown in the MEP section above - the $18,000-$26,000 range decomposes into architectural shell, mechanical, plumbing and medical gas, electrical, and fire protection line items, each at a defined LOD 300 rate applied to 45,000 sq ft. Dense, accurate plenum coverage drives the number toward the lower end of the range. Medical gas adds a specialized discipline layer that cannot be treated as a simple duct trace - those runs feed critical care equipment and require family-level accuracy throughout.

Scenario C illustrates the noise penalty at scale. A legacy scan at reduced density with some target drift adds 25-30% to modeling time versus a fresh clean scan. The LOD 200 architectural-only scope keeps the absolute number manageable, but the noise penalty is visible in the wide range: a clean modern cloud at 120,000 sq ft would quote $7,500-$10,000 at this LOD. The $4,000 spread between floor and ceiling of the range is the noise tax.

Scenario D shows the rush surcharge at small scale. The base modeling cost for a 3,500 sq ft restaurant is $1,400-$2,000. The 3-business-day rush carries a surcharge bringing the all-in total to $1,800-$2,600. Scope was frozen before rush authorization - no MEP additions mid-project. Rush delivery at this scale is appropriate when a hard deadline - permit filing, lease commencement, or contractor hold - cannot be moved and the scope is fully frozen before authorization.

For a deeper look at what these deliverables produce in terms of downstream construction savings, clash detection value, and facility management ROI, see our scan-to-BIM cost vs. value breakdown.

---

FAQ

Is hourly or fixed-fee better for a scan-to-BIM project?

Fixed-fee is better when scope, LOD, and deliverables are locked in writing before work begins - specifically when you have a registered .rcp or .e57 in hand, a confirmed discipline matrix, and a capped revision round structure. Hourly is appropriate when scope will evolve: adaptive reuse projects where demolition reveals conditions that change the modeling approach, or design-assist workflows where the model is a live input to design decisions rather than a documentation deliverable. The practical test: if you can fill out all seven items on our scope checklist before work starts, go fixed-fee. If more than two items are TBD, go hourly with a not-to-exceed cap at 120% of estimate.

Why do per-square-foot scan-to-BIM quotes vary so much?

Because the rate is a compressed label for seven compounding variables: LOD target, discipline scope, point cloud quality, ceiling and plenum complexity, building age and orthogonality, BEP and template requirements, and revision structure. A pre-1950 hospital floor requiring LOD 350 MEP from a noisy legacy cloud can legitimately price at multiples of a modern open-ceiling warehouse at LOD 200 architectural-only - at the same square footage. When you receive a quote range, ask the vendor to break down which of those seven variables is driving the spread rather than trying to negotiate the headline number.

How much does MEP modeling add to a scan-to-BIM quote?

MEP scope adds substantially over architectural-only pricing at the same LOD - commonly well over 50% depending on system density and building type. On the Scenario B hospital example (45,000 sq ft, LOD 300), the architectural shell runs approximately $12,600; stacking in mechanical ($6,300), plumbing and medical gas ($4,950), electrical ($3,600), and fire protection ($2,250) produces a total in the $18,000-$26,000 range. Medical gas is the highest-stakes line item - not the most expensive per square foot, but the one where family-level accuracy is non-negotiable because incorrect routing maps directly to clinical risk. For data centers and labs with dense above-ceiling conditions, MEP alone can push well beyond the rates for standard commercial work.

What is a typical expedited surcharge for rush scan-to-BIM delivery?

Rush delivery carries a meaningful premium that reflects overtime labor and project displacement. One detail that affects whether same-day delivery is even possible: the Trimble X7 auto-registers on-device and produces a deliverable .rcp before the crew leaves the site. Scanner workflows that require a post-processing pass typically need additional time before the cloud is modeler-ready. On a next-business-day commitment, that distinction is the difference between modeling starting at 8 AM versus later in the day - meaningful when the entire delivery window is one day.

Can I save money by hiring an offshore BIM team?

For well-defined LOD 200-300 architectural models with a clean registered cloud and a complete BEP, offshore rates are genuinely lower and the savings are real. The most common deliverable failure mode in offshore LOD 300 MEP work is not gross geometry error - it is centerline-only ductwork submitted as LOD 300, blank shared parameters, and floor-to-floor copy-paste duct routing that ignores beam framing visible in the point cloud. Catching these in QA requires systematically comparing every major duct run against the cloud and structural model. If you go offshore, require a QA audit checklist before accepting the deliverable and check specifically for those three failure patterns. See the full US vs. offshore BIM tradeoff breakdown for what an audit workflow looks like in practice.

Do I need a registered point cloud to get a fixed-price quote?

Yes. For a binding fixed-price, we need a registered .rcp or .e57 - not raw scan stations. Unregistered data introduces unknown density gaps and shadow zone distributions that make fixed-fee pricing a contingency-loading exercise rather than an accurate quote. If scanning and registration have not happened yet, those are separate upstream costs. See laser scanning minimum project fees for what to expect on the capture side.

What does the RFI contingency in your scope table actually cover?

On a 10,000-30,000 sq ft engagement at fixed-fee, we build in an RFI hour allowance for cloud ambiguities - shadow zones behind equipment, partial occlusions of wall conditions, scan geometry that is clear in the field but ambiguous from the registered cloud alone. This is not a change order mechanism; it covers questions that the modeler needs answered to correctly interpret existing conditions. Anything beyond that - adding a discipline, upgrading LOD, incorporating new design intent - is a scope change and priced separately.

---

Get a Scope-Locked Quote That Reflects Your Actual Project

We deploy the Trimble X7 terrestrial laser scanner as our primary capture instrument. The X7 auto-registers on-device and delivers a modeler-ready .rcp before we leave the site - no post-processing delay. For parts, detailed work, or reverse-engineering applications, we also deploy the Creaform MetraSCAN and handheld scanners. Both the terrestrial and handheld workflows deliver accurate point clouds at standard station and capture densities, with registration residuals documented in the report we provide with every deliverable. Because we run the capture and manage the modeling under a single project manager, shadow-zone ambiguities get resolved by a direct clarification, not a multi-day offshore email cycle.

We quote hourly, fixed-fee, per square foot, or blended - the structure we recommend is the one that matches your scope’s actual state of definition, not the one that makes our proposal look cheapest upfront. On a well-defined scope with a clean registered cloud, we will commit to a fixed price. On an adaptive reuse engagement where demolition is still ongoing, we will tell you hourly is the right structure and set a not-to-exceed milestone at 120% of estimate.

Send us your point cloud or building details and we will return a transparent, scope-locked quote with a full discipline matrix and delivery timeline.

Request a quote at weare-capture.com/services/scan-to-bim/