Bid / no-bid intelligence for subcontractors
Stop pricing jobs you were never going to win.
RFiQ reads the whole bid package — spec book and drawings — pulls the scope that belongs to your division, checks the GC and the developer against your own win history, and hands back a verdict you can argue with.
Reads the drawings, not just the spec book
Grounded in your win history
Every factor shown, every call overridable
Design partners are onboarding now. No spam, no pricing pitch.
Package · 412 pp · 64 sheets4 min 11 s
92
GO
Chase it. Scope fits what you self-perform.
Scope fit94
GC history88
Developer history64
Geography96
Why
014-of-11 with this GC’s Southeast office — above your book average.
02Your division is 91% self-perform on this one; nothing you hand off.
03Developer is new to you. Payment terms unproven — flagged, not fatal.
Watch it read a package
Forty seconds, start to verdict. No edits, no speed-up on the parts that are slow.
A medical-office package the way a GC sends it — the project manual and the E-series drawings, nothing renamed. Every line it finds carries the page or sheet it came from.
The problem
Estimating capacity is the bottleneck. Not opportunity.
Invitations are infinite
Fifty to three hundred packages a year land in one inbox. Nobody reads them all; somebody has to decide which ones get an estimator.
Estimators are not
Every hour spent pricing a job you were never going to win is an hour stolen from a job you could have taken.
The call is made on feel
Gut, tribal memory — “we never win with that GC” — and whoever talks loudest in the Monday meeting. The data to decide well exists. It’s just scattered.
The cost of a bad bid/no-bid call is lopsided.
Chasing a loser burns estimating hours you can count. Passing on a winner is invisible — you never find out what you left on the table. Both compound, quarter after quarter.
One trade at a time
A tool that reads every division reads none of them well.
Scope hides in a different place for every trade. Electrical lives in the E-series; painting lives in a room finish schedule nobody cross-checks against the spec. So RFiQ ships one division at a time, and each one knows where to look.
Divisions 26 · 27 · 28LIVE
Electrical
Gear, lighting, low-voltage and fire alarm — located across the spec book and the E-series, with drawing stage, square footage and owner-furnished equipment read off the sheets.
See the electrical pageDivision 09LIVE
Painting & coatings
Walls, exterior, high-performance coatings and stain — cross-read against the room finish schedule, where the Level 5 note and the exposed structure nobody priced tend to hide.
See the painting pageTell us whichNEXT
Your division
Mechanical, drywall, concrete, roofing — the loop is the same, the hiding places are not. Design partners decide the order we build in.
Put your trade in the queueHow it works
Package in. Verdict out. Reasoning attached.
01
Drop the package in
Project manual and the drawing set, however your GC sent them. Big PDFs are the normal case, not the exception.
Project manualDrawing setAddenda
02
RFiQ reads all of it
Your division located across specs and sheets, pulled into structured line items you can click back to the source page.
Your CSI divisionPage-level citationsReview flags
03
You get a verdict, and the argument behind it
GO, CAUTION or NO-GO with every factor exposed. Disagree and override — that override trains your next verdict.
GO / CAUTION / NO-GOFactor breakdownOverride logged
DAY ONENo history in the system yet? Upload your past bids as a spreadsheet and RFiQ starts from “you’re 4-of-11 with that GC’s Southeast office” instead of “first time”.
Inside the verdict
Nothing is a black box. Every number opens.
Scope, extracted
Located across the spec book and the drawings, line by line, with the page it came from. Division 26 shown.
26 05 19Low-voltage conductors & cablesp. 118
26 24 16Panelboards — 12 branchp. 141
26 51 00Interior lightingp. 166
27 15 00Horizontal cablingp. 204
28 31 00Fire detection & alarmp. 231
Built for recall — flagged for review, never silently dropped.
Who you’re bidding to
GC and developer resolved to the regional office — because one office is not the other.
General contractor4/11
Regional GC · Southeast office
11 bids · 4 wins · last won 8 months ago
Developer0/0
First time on your book
No history · payment terms unproven
Engineer of record6
Seen on 6 prior packages
Specs run tight; few addenda
Signals off the drawings
The things that quietly swing labor value and margin, read straight off the drawing set.
Drawing stageIFB
Square footage142,000
Owner-furnished3 items
Addenda issued3 to date
Stage matters: an IFB set and a DD set are not the same bet, and RFiQ says so.
RFiQ decides whether to bid. It is not a takeoff tool, not an invitation aggregator, and not a contract-risk reviewer — it hands off to the ones you already use.
Your data
Your bid history is the asset. We treat it that way.
We don’t train on your data
Your packages and your bid history are used to answer your questions. They never become someone else’s model or someone else’s benchmark.
One org, one wall
Every document, scope item and win record is scoped to your organisation. There is no cross-customer pool, aggregate or otherwise.
Documents on your terms
Set how long packages are kept after a verdict. Delete a project and its extractions go with it.
Every verdict is auditable
Who ran it, what it said, what changed, who overrode it and why — kept as a record you can pull, not a log we hide.
Access you control
SSO and per-seat roles, so the estimator, the chief and the owner see what their job requires and nothing more.
No silent changes
When scoring criteria change, the change is recorded against the verdicts it affects. Old calls stay explainable.
Ask before you bid.
We’re taking on a small number of subcontractors as design partners. You bring real packages and real bid history; we bring the verdict engine and move fast on what you tell us is wrong.