Win rate, cycle time and estimate accuracy from the quotes you already sent
VenturusEQ records every outcome with a reason and shows what the numbers say: quotes sent and orders won, win rate by account, process and estimator, three cycle clocks in median hours, and a forecast weighted by the probability your team records. Quote-vs-actual accuracy compares the awarded estimate with what the work cost, bucket by bucket, and nudges. It never rewrites a template.
What the win-loss dashboard shows
Sent and won
Quotes sent, orders won, and the amounts behind both, over 30, 90 or 365 days. Counts of your own quotes, nothing modeled.
Win rate by account, process and estimator
By account, by process and by estimator. Which customers say yes, which kinds of work you win, and whose quotes convert.
Three cycle clocks: received to draft, draft to sent, sent to order
Each reported as median hours rather than averages, so one stuck quote does not hide the shape of the rest.
Probability-weighted forecast
Every open quote carries the probability your team recorded. The forecast is the sum of the open work weighted by it.
Reasons and competitors
Won, lost or no-bid, each with a reason, a probability, the competitor named and the buyer's feedback.
Quote opens, counted without tracking anyone
View counts and the last view on every sent quote, recorded as salted hashes rather than people. A saved view lists quotes that were never opened.
How quote-vs-actual accuracy works
The comparison
When a quote is awarded, its cost snapshot is frozen. Actual costs are then posted against the won job inside the product, by cost type, from the job's own records: labor and expense actuals, and procurement commitments and receipts. The accuracy view lines the actual cost to date and the estimate at completion up against the frozen snapshot bucket by bucket: material, labor, subcontract, overhead and other. A part that was estimated at two hours of labor and took three shows the gap in the labor bucket, not as a single blended number.
The portfolio view rolls the variance up by the template that produced each estimate and points at the ones that drift.
Why it only advises
A template that rewrote itself from last month's variance would price next month's work on one job's bad day. Nothing writes back to a template: an administrator changes it deliberately, and the changed template must pass the activation gate again before it can price a line.
Governed formulas and templates →Getting the numbers out
The quote log as CSV or XLSX
Every quote line with its hours by bucket, its values and its outcome, for the whole year. It is the same data the win-loss dashboard reads, so the spreadsheet and the dashboard never disagree.
Events as they happen
Stage changes, outcomes, requote requests and awards leave as signed webhooks the moment they happen, for a CRM or a dashboard of your own.
Integrations →Common questions
Can I see how long our quotes take to get out the door?
Yes, for your own shop. Three cycle clocks, received to draft, draft to sent and sent to order, report median hours over 30, 90 or 365 days, the control center band shows open, due soon, overdue, unassigned and the average wait, and due dates default from your own time-to-quote setting, so overdue means what you decided it means.
Can it show which estimator wins the most?
Yes. Win rate by estimator sits beside win rate by account and by process. Every line has an estimator and the quote log records hours by bucket per line, so the numbers are attributable rather than guessed.
Does the forecast use AI?
No. It weights each open quote by the probability your team recorded and adds them up. Change a probability and the forecast changes. The AI in VenturusEQ reads drawings; it does not predict wins.
See it on one of your own RFQs
Send us a drawing and a model you have already quoted and we will walk through it with you in the product, in your rates. If you would rather look first, the interactive demo is open, with no form in front of it.