What can we help with?

BuildVision reads construction documents, pulls out the equipment data, and structures it so both sides of the transaction can use it. Reps get bid triage, pipeline visibility, and CRM integration. Contractors get procurement tools, equipment tracking, and submittal management.

You send it documents from wherever they live: Outlook, BuildingConnected, or direct upload. BuildVision labels each page, finds the equipment schedules, and pulls out spec data. Reps get structured project records pushed to their CRM. Contractors see equipment decisions, submittals, and lead times tracked across their projects.

Equipment manufacturer reps who want pipeline visibility without manually reviewing bid packages. General contractors on commercial, industrial, and institutional projects. MEP subcontractors managing equipment selections across multiple GC relationships.

Reps get bid requests by email, download files from five different platforms, review hundreds of pages, and type the data into a CRM. GCs don't know what equipment their subs picked until it's too late to change it. Subs track lead times in spreadsheets and email chains. Everyone is looking at the same transaction with different information. BuildVision reads the documents and gives both sides a shared, structured view.

Today, a bid desk coordinator opens emails, downloads files, reviews documents, and types the data into a CRM. BuildVision does that part. It adds logged equipment decisions, lead time tracking, and digital submittals on top of however you already work. You keep your process and your relationships.

Venture-backed. Series A led by Norwest Venture Partners. Production workload: 200k+ AI executions this quarter across 12 production prompts (see buildvision.io/benchmark).

Mike Powers and Christophe Prakash. Mike bought equipment at scale at Source Blue, then ran enterprise sales at BuildingConnected (acquired by Autodesk). Ben Lyddane is COO. He spent about 10 years selling HVAC equipment at supplier firms before moving into software.

BuildVision processes your incoming bid packages. It reads the documents, finds the equipment, and tells you which projects have your products specified, which list you as an alternate, and which have a product match but didn't name you.

Instead of your team opening emails, downloading files, and typing data into a CRM, BuildVision does that part.

All pages across all documents. It labels each page by type, then pulls out: basis of design product, listed alternates, equipment specs (tonnage, voltage, efficiency, coil types, filter ratings, sound criteria, and dozens more), engineer of record, project metadata, and links to the source pages. Atlas normalizes all of it: unit conversions, supplier names, equipment type classification.

Atlas is BuildVision's database for normalizing equipment data. It maps standardized component types, spec sections, rep identities, and unit conversions. When two engineers use different terminology for the same thing, Atlas makes it comparable. It also maps equipment across reps to equivalent product categories for competitive analysis.

Yes, through two approaches. Direct API integration sends structured equipment data to the selection software's endpoints. A browser-based agent can navigate the UI for systems without APIs. BuildVision has demonstrated both with multiple top 10 firms. The API mapping process typically takes a few weeks.

For every equipment package on every project, BuildVision identifies which product is basis of design, which are listed as alternates, and which have a product match but are not listed. Sales managers can see across their territory which engineering firms are specifying their products and where they are losing position.

It tracks the gap between what's specified and what a supplier can provide. Under-select and you eat cost overruns after bid day. Over-select and you price yourself out of the job. BuildVision flags both, per parameter.

Priority structure: schedule data first, plan details second, specification third. When conflicts are detected, the system flags the discrepancy and shows both values. BuildVision can also generate two selections: one matching the documents exactly and one applying engineering judgment. The delta is surfaced to you.

Yes. BuildVision extracts the engineer of record and tracks which firms are specifying which products across your catalog and pipeline. You get a clear picture of how you're positioned with specific engineering firms.

Yes. For direct sales offices, data sharing is straightforward. For independent reps, a data sharing agreement governs what flows where. Markup, margin, and confidential transaction data stays with your organization.

Yes. Upload your product literature and BuildVision builds a searchable interface on top of it. Ask any question, get answers with links to the source document. Works internally or customer-facing.

Yes. BuildVision monitors your Outlook inbox and BuildingConnected, processes incoming bid requests, and runs them through the extraction pipeline.

You can see what equipment your subs picked, whether submittals are in, and whether lead times are going to blow the schedule. It creates a paper trail for owner reporting too.

If you run procurement in-house, you can send RFQs, receive quotes, level bids, and track it all from the same place.

No. It sits alongside whatever you already do. BuildVision captures data that already exists in the process and puts it in one place.

Yes. Activate it on projects at any stage. Subs can log current equipment selections, and the platform tracks from that point forward. The extraction pipeline can also process existing project documents retroactively.

A full view of equipment decisions across your projects: what's been selected, submitted, approved, and what lead times are tracking against the schedule. For teams running procurement in-house, BuildVision provides RFQ tracking, quote comparison, bid leveling, and reporting on equipment spend across your portfolio.

BuildVision captures submittal requirements from the project documents and keeps a digital record of each equipment selection. The review tool compares submittals against the construction documents and flags discrepancies.

Yes. Works across delivery methods including Design-Build, Design-Bid-Build, and CM at Risk.

Yes. Both teams run the same project independently. You compare outputs, see where recommendations differ, and decide when you're ready to hand off more.

One place to manage equipment selections, submittals, and procurement across all your active projects and GC relationships. Send RFQs to your reps, get structured quotes back, and level bids.

No. Subs can use BuildVision independently. The network value increases as more project participants join, but it works standalone.

Yes. All activity is organized by job with role-based permissions controlling what each party can see.

It doesn't replace your reps. You keep your existing relationships. BuildVision records the transaction and your preferred reps get priority when you send RFQs.

No. Reps are still how equipment gets specified and sold. BuildVision gives reps better visibility and a faster path to the projects that matter.

It depends on document quality and how the account is tuned. During the pilot, we tune extraction for your equipment and document formats. Production workload and upcoming per-task accuracy scores are published at buildvision.io/benchmark.

Thousands per customer. We currently handle the full incoming bid volume for reps with national sales networks.

PDF and Word format drawings and specifications, plus any other document types commonly found in bid packages. The Outlook and BuildingConnected integrations handle file downloads automatically.

A typical commercial project with a few hundred pages processes in minutes. Selection software integration adds 10-15 minutes per equipment unit depending on complexity. BuildVision is actively parallelizing processing to reduce total turnaround.

Working on it. Quantity takeoff for equipment that appears in multiple locations on drawings is live for some equipment types and still being developed for others.

If an engineer emails asking for a 500-ton air-cooled chiller for a hospital in Texas, BuildVision reads the request, maps it to the selection software, and returns a preliminary selection. Works with informal requests, not just formal spec documents.

Anthropic and Google, through enterprise agreements with dedicated model access. No open models, no shared API endpoints. When a better model comes out, we swap it in. You don't have to do anything.

POs are generated and tracked inside the platform. Each equipment transaction has a record from selection through delivery.

Mechanical, electrical, and plumbing equipment: HVAC (chillers, rooftop units, air handlers, fan coils, VAV terminal units, split systems, heat pumps, boilers), ventilation (fans, ERVs, louvers, dampers), plumbing fixtures, electrical distribution, controls, and fire protection.

Microsoft Outlook and BuildingConnected. BuildVision monitors your inbox, syncs project invitations, and downloads documents as they come in.

We integrate with several project management platforms and are adding more. Contact us about your specific stack.

No native app. Runs in a web browser on desktop and mobile.

Depends on your org structure. BuildVision supports centralized and regionalized admin with project-level access controls. The team configures it with you before rollout.

SOC 2 Type 2 compliant with completed formal data audits. Start the review process early because it takes time on your end.

Yes. We add integrations based on what customers ask for. Tell us what you use.

A formal agreement governs what data flows where. Reps keep their selection software and catalogs. Markup, margin, and confidential transaction data stays with your organization.

No long-term contract required. Begin with a sign-up and trial and expand based on your team's experience.

Yes. For contractors, starting with one project is the standard path. For reps, pilots typically start with a few sales offices over approximately six months. BuildVision sends a pilot proposal with scope, success metrics, and accuracy targets.

Three phases. Requirements definition. Live project support with engineers evaluating quality. Evaluation and scaling. Metrics, data governance, and accuracy targets are agreed on before starting.

For contractors: kickoff call, project setup, walkthrough. Most teams are live within days. For reps: pilot scoping, engineers on-site, workflow mapping, and iterative quality improvement over a few months.

For contractors: a project with construction documents and a point of contact. For reps: access to participating sales offices, an understanding of your CRM structure, and ideally some test projects. Start the cybersecurity review process early.

Contractors: days. Upload documents and start sending RFQs. Supplier pilots: 2-3 months from first conversation to active pilot. We can process sample projects right away while the formal agreement gets finalized.

Equipment reps, GCs, and specialty subs in commercial construction. Happy to connect you with teams in a similar workflow.

hello@buildvision.io or through your existing relationship. If someone referred you, let us know.

Project metadata (name, location, bidders), basis of design status, equipment specs, and engineer of record.

What they do NOT see: margins, confidential financial data, or any transaction data from downstream parties.

Markup, margin percentages, and confidential transaction data. Never shared upstream. A formal data sharing agreement governs it.

Upstream parties see pipeline and equipment data. They do not see what downstream parties charge their customers or what margins they earn.

Role-based access at the organization, project, and user level. You control which team members see sensitive data, which external parties can access project information, and what flows to which network participants.

For enterprise deployments, we support centralized and regionalized admin structures configured during implementation.

Yes. You pick what to share and with whom through project-level settings. Teams can share procurement status with project owners, and reps can share with their customers. Internal data stays internal.

No. We don't sell customer data. Project data is not aggregated or sold to competitors, research firms, or anyone else. Each organization's data is siloed.

We make money from customer contracts, not from selling your data.

You own your project data. BuildVision does not sell or share project-level data with third parties. Reps see only the data relevant to their products on specific projects. BuildVision maintains siloed data environments per organization.

Encryption at rest and in transit, role-based access controls, SOC 2 Type 2 compliant. Data is siloed by organization. We do not train models on customer data.

No, and we never will. Your documents and project data are used only to run the service for you. Our enterprise agreements with AI providers include data isolation and prohibit training on customer inputs.