Every claim shows its page.
Each answer names the document and the page it came from. Open it, and the page sits beside the claim.
Start from one that works
BidScanCustom
Your company’s own BidScan. It reads the whole bid package, shows the page behind every answer, and carries the bid from the first read to the project package. One company per build, shaped with the people who use it.
Not the same product as BidScan at bidscan.ai. BidScan Custom is one company’s own build, made in its own space.
The first lookBid set · 4 documents
- Bid security
- A bid bond goes in with the proposal.Instructions to Bidders · p. 3
- Pre-bid meeting
- Not mandatory. Questions close before the due date.Invitation · p. 1
- Open question
- Who maintains the haul road? The documents don’t say.Asked, not assumed
- Unread
- Drawings, sheet C-4: no readable text.Said, not guessed
How it reads
Information leads. Analysis follows.
It says what it couldn’t read.
A page with no readable text is named as unread. Nothing on it is guessed.
It asks only what the documents can’t answer.
What the bid set settles, it settles. What it leaves open becomes a question for the bid lead, ranked by what it would do to your number.
Search the whole bid.
One box across every document in the package. Each hit names the document and the page.
The arc
From the first read to the project package.
01
The Bid Board.
Every bid in play: its stage, its due date and its value. The value is your company’s own number, never a figure the model came up with.
02
RFIs.
The open questions come with their page, ready for the letter. You read it and send it yourself. Each RFI is numbered, and when you mark it sent, it’s frozen with the time.
03
The Handoff Room.
The scan becomes the project package the job team starts from. Every line from the bid is cited to its page, with your team’s notes beside it. The estimate stays out, by construction.
- Project directory
- Contract and scope summary
- Key dates and obligations
- Compliance register
- Buyout list
- Submittal register
- Subcontractor scope sheets
- RFI and question log
- Kickoff agenda and notes
- Equipment and logistics
- Closeout requirements
Built for a real team
One company, many people.
- Your company is in every read. Its name, its trade and the work it takes on are part of every scan.
- People join by invitation. There’s no public sign-up. You decide who’s in, and who can start a scan.
- Branches keep their bids apart. Each branch works its own bids, and its people see what’s theirs.
What it won’t do
Not a replacement for your judgment.
- Fill a gap to look complete. If the documents don’t say it, it’s an open question, not a value.
- Price the job. The estimate is your team’s, and it stays out of the project package.
- Send anything. The RFI letter is a draft you read and send yourself.
- Make the call. It lays out what the documents say, and where. The call is yours.
How an engagement runs
Not a finished product off a shelf. The starting line.
- 01
A questionnaire first.
Before anything is built, you answer a short set of questions on how your company bids.
- 02
Your own build.
Your company gets its own BidScan: its own code, its own database, its own address. Nothing of any other company is in it. Your company, your trade and the work you take on are set up before the first scan.
- 03
Built with you from there.
It reads your bids from the first day. What’s particular to how you work, I build with your team, in your build, as the engagement goes. Your people tell me where to adjust it.
The demo
See it on a demo build.
A BidScan Custom demo is available to interested firms. Access to a demo build is granted after a meeting to understand your company: its size, its scale, and how it bids its trade.