01
Package ingestion
Email content, attached PDFs, .eml files, and image uploads parsed and normalized into a single intake record. Nothing gets missed in an inbox thread or buried attachment.
Bid Intake · Agentic System
A crew of agents that turns inbound general contractor bid packages — emails, PDFs, drawings — into structured triage, scope checklists, and risk flags. Built with a commercial millwork shop. The same patterns extend to drywall, structural steel, mechanical, glazing, and other specialty trades.
Queue recommendation
Risk flags
Scope checklist
Specialty subcontractors live or die by their bid volume and bid quality. Every general contractor inquiry is hours of work just to figure out whether to chase it: read the email, open the drawings, scan for scope, check the schedule, weigh the general contractor relationship, decide. Most of that time isn't estimating. It's sorting.
The problem isn't your estimator. The problem is that nobody else has read the package by the time it hits their desk.
Every inbound bid package gets read first by the crew. Email body, attached PDFs, drawings, and any prior notes get parsed into a single intake record. Company rules — minimum project value, service area, prioritized trades, declined work types, risk patterns — apply automatically. By the time the estimator opens the file, the bad bids are already flagged and the good ones are pre-triaged.
Six agents, working before the estimator does.
01
Email content, attached PDFs, .eml files, and image uploads parsed and normalized into a single intake record. Nothing gets missed in an inbox thread or buried attachment.
02
Project type, location, trade scope, dates, and stated value extracted explicitly from source documents. No invented details, no hallucinated numbers — just what the general contractor actually wrote.
03
Drawing sets parsed and checked against typical completeness expectations. Missing sheets, vague details, and ambiguous specs surfaced before you commit time.
04
Configurable risk signals (unrealistic schedule, vague scope, residential, outside service area, payment patterns) applied to every package. Bad bids flagged early.
05
Each package routed to a recommendation: estimator review, needs clarification, deprioritize, decline. Your estimator works the right packages first.
06
On approved packages, a second pass produces a scope-by-area skeleton with stated measurements, an uncertainty register, and specialty flags. Not a takeoff, not a price — a head start.
The crew watches the inbox or shared folder where general contractor bid packages arrive. Each new package gets ingested, parsed, and triaged within minutes. Results land back in your team's existing workflow — a shared workspace, a review UI, or whatever channel your estimator already uses. No new tools to learn. No data migrations.
Company rules are configurable per shop: name, description, service area, minimum project value, prioritized and deprioritized project types, declined work, and risk signals. The same crew, tuned differently per business.
A general contractor sends a bid invitation Tuesday afternoon. PDFs attached, schedule in the email body, .eml file with the full thread. Here's what happens before your estimator opens it Wednesday morning:
Package ingested.
Email body, attachments, and prior thread context parsed into a single intake record within minutes of receipt.
Rules applied.
Service area, project type, minimum value, and known general contractor patterns checked automatically.
Drawings scanned.
PDF pages parsed for scope, key dimensions, and obvious completeness gaps.
Triage produced.
Structured markdown with project summary, scope checklist, risk flags, drawings status, and a queue recommendation.
Estimator opens the file.
Already knowing it's a fit, what's missing, what's risky, and what to look at first.
Sunday stays yours.
The Bid Intake agentic system is a working full-stack application — multi-agent crews, PDF and email parsing, configurable per-company rules, a review UI, and persistent job state. It was built and tuned with a commercial millwork shop in the Baltimore/DC market with strong concentration in healthcare, education, and institutional work. The same patterns apply to any specialty subcontractor receiving general contractor bid packages: drywall, structural steel, mechanical, glazing, electrical, and adjacent trades.
Built for real bid packages
Multi-format intake: pasted email text, PDF drawings, .eml threads, image uploads. Not a toy.
Configurable per shop
Company rules drive how every package is judged. Same crew, your business logic.
Estimator-first design
Markdown output, review UI, estimator notes on documents, decision tracking. Built for the workflow that already exists.
Bid Intake is currently in a partner-engagement phase. We work with one or two specialty subcontractors at a time to tune the crew to your trade, your service area, your general contractor relationships, and your historical bid patterns. Engagements start with a paid pilot followed by a monthly retainer.
We'll look at three recent bid packages your team triaged, show you what the crew would have produced, and discuss whether your trade and bid volume are a fit. No pitch, no obligation.
A: No. The crew handles triage and an optional scope skeleton — what's in the package, what's missing, what's risky, what's worth chasing. Pricing, quantity takeoffs, and the final bid number stay with your estimator. The crew gives them a head start, not a replacement.
A: The crew was built and tuned with a commercial millwork shop, but the architecture is configurable per shop. Rules, project types, vocabulary, and risk signals adjust per trade. We've designed it to extend cleanly to drywall, structural steel, mechanical, glazing, and adjacent specialty trades. The first 2-4 weeks of any new-trade engagement is tuning the crew to that trade's specifics.
A: PDF drawings, .eml email files, pasted email text, image uploads, and inline email bodies with attachments. If you receive packages in a format we haven't seen yet, we'll add support.
A: Every triage output is a recommendation, not a decision. Your estimator opens every flagged package and confirms or overrides the recommendation. The crew gets better as you log decisions — over time it learns your business's actual judgment patterns.
A: On infrastructure we operate, with per-customer isolation and encrypted credentials. Bid package contents are not used to train shared models and are not visible across customers.
A: First triage outputs on real bid packages typically come within 2 weeks of kickoff. Crew tuning continues for 4-8 weeks as your estimator feeds back on which calls were right and which weren't.