How the suite fits together

The suite covers a bid from the invite to the sendoff. Each piece stands on its own, but they are built to hand work to each other.

The three pieces

contractor-bid (free engine). A Python CLI and MCP server that runs on your machine. Point it at a bid folder and it triages the PDFs, pulls scope and spec pages into packets, builds takeoff workbooks from your measurements, and packages sendoffs. It is MIT licensed and local-first: your documents stay on your machine. Full reference lives at the engine docs.

Contractor Takeoff (hosted app, in pilot). The same engine’s brains behind a team workspace. A bid board shows every bid’s status, due date, owner, and next action. Each bid carries its own document library: plans, specs, addenda, bid forms. AI-assisted review flags scope and spec pages, and every finding links to the source page so you can check it in seconds. See the overview.

Plan Markup (Mac and browser). Where the measuring happens. Calibrate a sheet’s scale, draw lengths, areas, and counts, group them into takeoff totals, and export CSV for your pricing workbook plus marked-up PDFs for the GC. See the overview.

The handoffs

1. A bid invite lands. In Contractor Takeoff you make a workspace for it, drop in the plan set and specs, and let triage flag what matters. On your own machine the free engine does the same job from the command line.
2. You measure in Plan Markup. Markups live in a sidecar file next to the PDF, so the plans themselves are never touched. Takeoff totals export to CSV for whatever you price in.
3. Markups made on a bid’s documents show up inside that bid’s workspace, because Plan Markup embeds inside Contractor Takeoff as the document viewer.
4. When addenda land, sheet overlay and markup transfer in Plan Markup carry your work to the new sheets, and Contractor Takeoff’s alerts point at what changed.
5. At sendoff, Contractor Takeoff exports a deterministic bid packet: workbooks, scope summaries, supplier packages, calendar entries.

What no piece of the suite does

• It does not price the job. Your numbers, your judgment.
• It does not measure for you. A measurement exists because you drew it.
• It does not invent findings. Anything the AI surfaces links back to a page in your documents.