From lead to bid to job, without retyping anything.
Capveon connects Dodge, your CRM, HeavyBid and Viewpoint, and does the work between them: qualifying bids, precon research, bid review, and keeping every record current. Nothing is replaced.
Auxiliary spillway under construction, Folsom Dam, California. U.S. Army Corps of Engineers, Sacramento District.
Every job lives in six systems. Your people are the integration.
The lead is in Dodge. The relationship is in the CRM. The last bid is in HeavyBid. The job costs are in Viewpoint. The spec is a PDF and the award is an email. Someone on your team spends their day moving information from one to the next.
What to chase, what it will cost and which job is about to slip is in those systems too.
One pursuit, from six systems.
One job, every system's piece of it, each figure linked to where it came from.
Water Reclamation Facility Expansion
One record, assembled from six systems.
- Lead feed
- Bid date in five weeks, $42M estimated, design-bid-build
- CRM
- Owner account, two contacts, last meeting eleven weeks ago
- Estimating
- Three comparable bids, one won at 10.8 percent margin
- ERP
- Comparable job finished 6 percent under estimate, one change order
- Documents and email
- Spec and Addendum 1 received; pre-bid meeting invitation in the PM's inbox
Fit 91 of 100. Pursuit brief drafted. Opportunity updated in the CRM after approval.
Bid or no-bid, decided from your own history.
Every lead from the feeds you already pay for, read in full and compared to your won and lost bids, job costs, certifications and crews. A fit score with the past jobs that produced it, in minutes.
- Reads every feed you already pay for
- Criteria you can see and edit
- Comparable past jobs, with how they performed
Precon research finished before the kickoff meeting.
Past jobs with this owner and how they went. Bids against this engineer's specs. Actual costs against estimates on comparable jobs. Subs and vendors used. One brief, and the estimate starts from your best comparable job instead of a blank sheet.
- Owner and engineer history from CRM, ERP and email
- Comparable jobs with actual performance
- Estimating system prefilled as a starting point
Read the bid set before anyone opens a spreadsheet.
The solicitation broken into requirements, each mapped to your qualifications, the gaps surfaced with the paragraph that created them. Estimating starts from a compliance matrix instead of a 400-page PDF.
- Requirements cited to the passage
- Gaps and unusual terms first
- Comparable past bids and outcomes
Systems that stay in sync. Forecasts that come from them.
An award email becomes a job in the ERP. A stage change in the CRM updates the forecast. The customer spelled four ways becomes one. Every write waits for a person. Once the systems agree, win probability, backlog and slip risk are forecast from your own history.
- Read-only first. Writes wait for approval.
- One record per customer, project and job
- Forecasts with the factors behind them
Next to what you already run
Nothing is replaced. Your lead feed tells you a project exists. Your CRM, estimating system and ERP hold what your team typed. Capveon reads all of it and does the work in between.
| Question | Lead feeds and plan rooms | CRM, estimating and ERP | Capveon |
|---|---|---|---|
| What it knows | That a project exists, and its documents | What your team entered, in that system | Every system's piece of every pursuit and job, resolved to one record |
| Qualification | Filters and keywords | Not covered | Scored against your history, with the evidence |
| Research and bid review | Documents attached | Not covered | Done, cited, before the kickoff |
| Data entry between systems | Not covered | Your people | Proposed by Capveon, approved by a person |
| Forecasting | Not covered | The pipeline, weighted by the rep | Predicted from your own outcomes |
Questions contractors ask
- Does this replace Dodge, ConstructConnect or Citylitics?
- No. They are sources. Capveon reads the leads and documents they deliver and does the work your team does after.
- Does it replace our CRM, estimating system or ERP?
- No. It connects to them read-only, reconciles what they hold, and writes back only after a person approves. Your team keeps working where they work today.
- How long does it take to get running?
- The first version is usually built with your team in a one to two hour working session: we connect read-only to the systems involved, pick the process that wastes the most time, and build that workflow.
- What if our data is a mess?
- It always is. Reconciling the same customer, project and job across systems is the first thing Capveon does, and it flags what it cannot resolve rather than guessing. Cleaning up is a result of the deployment, not a prerequisite.
- How is it priced?
- An annual subscription scoped to the systems connected and the workflows deployed. We share pricing on the first call once we know the scope.
The first workflow takes an afternoon, not a quarter.
Tell us the systems you run and the process that wastes the most time. We connect to them read-only and build the first version with your team in an hour or two, without replacing anything.