Scan-to-BIM Company vs Freelancer vs Offshore Team

Pick by who owns the three things that decide whether a scan-to-BIM model is usable: point cloud registration, QA against the scan data, and the final handoff. A scan-to-BIM company is the right call when field scanning is in scope, the building is complex, or you need one accountable contact from capture to delivery. A freelancer fits a narrow, well-defined modeling task when the point cloud is already registered and you can supply the standards. An offshore team adds production capacity for large, tightly specified jobs. The label matters far less than where ownership lives, and a cheap model with no clear owner is the most expensive option once a design team has to fix it.

The differences that actually matter

Every provider can produce a Revit file. The gap shows up in the parts buyers do not see in a screenshot: whether the point cloud was reviewed before modeling started, whether geometry was checked against scan slices, whether someone wrote down what was excluded, and whether one person will answer for the final package. Those are the dimensions worth comparing, not the org chart.

Here is how the three options usually break down. Treat it as a starting point, not a rule, because a strong freelancer can beat a weak company on a small job.

Scan-to-BIM company

A company earns its premium when the workflow has to be managed, not just executed. Field capture is the clearest case. If existing conditions still need to be scanned, the company runs the crew and the scanner, and a full scan day on a building can run up to roughly 12 hours on site. Our field work uses a Trimble X7, which self-levels and auto-registers scans in the field so the data is verified before anyone leaves. From there the same team owns registration, modeling, and QA: raw scans become a registered point cloud (E57), the cloud is indexed for Revit (RCP/RCS), and the model is built to the agreed LOD with geometry checked against point cloud slices rather than eyeballed.

The real product is accountability. One contact explains intake, scanning, registration, modeling, QA, and delivery, and one contact answers when a reviewer flags something. That is what you are paying extra for, and it is worth it on complex buildings, multi-deliverable jobs, and anything that will feed design coordination. See our scan-to-BIM services and 3D laser scanning for how field capture and modeling connect.

Freelancer

A freelancer is a good fit for a narrow, well-defined task. The classic case is a registered point cloud you already own, an architecture-only model (walls, floors, doors, windows, structure), a known Revit version, and a clear LOD target. When you can hand over clean data and a tight spec, a skilled modeler is fast and economical.

The risk is not that the person works alone. It is that there is no second set of eyes and no capacity headroom. If the scan data turns out to be incomplete, if scope creeps into MEP, or if the modeler is unavailable mid-project, there is no backup and no separate reviewer to catch a level set wrong or an opening missed. Keep freelancer scope small enough that a single point of failure is an acceptable risk, and write down the exclusions so a gap does not surface as a surprise.

Offshore team

Offshore modeling shops are built for production capacity. When the scope is large, the modeling categories are clearly defined, and your Revit standards are documented, a team can move through square footage quickly and at a low hourly rate. They are usually modeling-only, so they expect a clean, registered point cloud delivered to them.

Two things decide whether it works. First, standards have to be written down, because a team you cannot look over the shoulder of will model exactly what the spec says and nothing it does not. Second, someone onshore has to own review and answer RFIs, or time-zone gaps turn a one-day question into a three-day delay. The headline risk is split ownership: if one party scans, another models, and a third reviews, somebody still has to decide whether the final package matches the agreed scope.

Why blended teams are the honest answer

Most good projects are not pure. The structure that works on US projects is usually blended: local field capture, modeling that may run through a partner team, and one accountable owner who reviews the output and signs off. That is how we run work where modeling is delivered through partners. The field scanning and the accountability stay with us, and the modeling capacity scales with the job.

A blend only works when the roles are explicit. Define who captures field data, who registers the point cloud, who models, who checks the model against the scan, who answers client questions, and who owns final delivery. Without those six roles named, the client ends up stuck between teams the first time a ceiling is not visible or a pipe disappears behind a wall.

What to ask any provider, regardless of type

The same questions cut through every label. What is included and what is excluded? Who reviews the point cloud before modeling? What Revit version and what LOD? How is QA performed, and who does it? How many review rounds are included, and how are comments handled? What happens if the scan data is incomplete? And the one that matters most: who owns the final handoff. The deliverable should be a package, not just an RVT file, including the linked point cloud, model and QA notes, documented exclusions, coordinate notes, and consistent file naming. If a provider cannot answer the ownership question crisply, the label is not your problem; the workflow gap is.

On price, lower is reasonable when scope is genuinely simple and risky when scope is vague. The cost climbs the moment LOD is undefined, MEP scope is fuzzy, registration quality is unknown, or QA is not actually included. For how that plays out against value, see scan-to-BIM price vs value, and to compare specific providers head to head, how to compare scan-to-BIM companies.

FAQ

What is scan-to-BIM?
Scan-to-BIM is the process of turning a 3D laser scan of existing conditions into a building information model, usually in Revit. The field scan produces a point cloud, the cloud is registered and indexed, and a modeler builds intelligent objects (walls, floors, structure, and sometimes MEP) to an agreed level of detail.

Who is responsible for the final model and deliverable?
Whoever you name in the contract. This is the core of the company-versus-freelancer-versus-offshore question. On split teams it is easy for capture, modeling, and review to each assume someone else owns the handoff. Name a single accountable owner before work starts, and define what the final package includes.

How much does scan-to-BIM cost?
There is no single price per square foot and no neutral benchmark; standards like USIBD LOA define accuracy, not price. Cost tracks element density and LOD, not floor area. Scan-only field work is billed by the day or hour, modeling-only is often priced per square foot or per hour, and turnkey bundles both. A dense MEP model costs many times what an architecture-only shell does at the same square footage. See our LOD guide for how detail drives the number.

How do I import a point cloud into Revit?
Convert the registered scan (commonly E57) into Autodesk’s indexed format (RCP/RCS), then use Insert, Link Point Cloud in Revit and position it on the correct shared coordinates. Getting coordinates and units right at link time is what keeps the model aligned through every later step. See the scan-to-BIM quote checklist for what to confirm before pricing.

The bottom line

A company, a freelancer, and an offshore team can each be the right answer. Do not choose by label. Choose by who owns registration, QA, and the final handoff, and whether field scanning is in scope. If you want one team to own capture and accountability while modeling scales to the job, request a quote and tell us the building, the scope, and whether you already have a registered point cloud.

Last reviewed: May 2026.