Protocol InstituteBusiness

Feed · thread · version 1 · updated 27 September 2026

SIG-P4B 2026-08-13

Session of 13 August 2026. Participants: rafa (UTC+1), Andre Comeau.

This was a one-on-one working session between rafa and Andre Comeau to scope a potential "Protocols for Business" case study focused on the construction bidding/estimating pipeline. rafa presented findings from experiments run with his father-in-law (Virgil), a former heavy-civil construction CEO, showing that an LLM could reproduce a bid estimate within ~10% and even flag design errors from solicitation PDFs. The conversation examined why this analysis isn't already automated, identified the core bottleneck (canonical drawings live in non-machine-readable PDFs), and mapped the industry incentive structure that keeps the status quo in place. They ended by discussing how to structure the project, funding, and roles.

Key points

  • The experiment (rafa): rafa fed a solicitation bid PDF to an LLM (referenced as "Opus five or whatever") and, in ~30 min of runtime (~1 hour with probing/adversarial analysis and blind agent reviews), produced numbers within 10% of a full organizational bid produced by Virgil's team. He also had the model generate a "takeoff analysis." Andre confirmed "takeoff analysis" is a real, standard industry term (not just Michigan-specific).
  • Takeoff analysis defined: A table comparing the design engineer's requested materials vs. the actual planned/likely materials, and both against the contractor's read of the visual plans and real-world conditions.
  • Where value really sits (rafa relaying Virgil): The final bid number is largely deterministic (driven by subcontractor and material/equipment prices where risk is passed to others). The estimator's real leverage is in the accuracy of quantities and pricing for maximum profit opportunity.
  • Finding design errors = profit (rafa): When given a different spec, the model found a design error. This is commercially valuable because contractors often make money via change orders when they catch design errors.
  • The four core questions rafa raised: (1) Why isn't someone in the office already running PDFs through ChatGPT? (2) Why doesn't existing bidding software do this analysis? (3) Why doesn't solicitation-bid software (e.g. BidNet) do it? (4) Why is this analysis done off PDFs instead of raw CAD data?

Source: Protocol Institute meeting archive · PI website commit 830dfb6 · raw recording notes. Summarized by c3po, the Protocol Institute's session pipeline, from the session's Discord thread and recording.

Follow

Follow this blyg. Paste the feed into any RSS reader, or the blyg's address into Blygger Studio or another blyg client:

https://protocolsforbusiness.com/blyg/feed.xml

https://protocolsforbusiness.com/blyg/

To follow every member too, import blogroll.opml.

Join the conversation

This is a feed, not a forum. Two ways to answer a post:

  • Talk about it on Discord. The group meets in the Protocol Institute Discord, channel #protocols-for-business: join the Discord.
  • Respond from your own blyg. Quote this post in a thread, or publish a response to it (in Blygger Studio: follow this blyg, then use Respond or Quote on this post). Your blyg sends a Webmention; once it is verified, your post is listed under Responses here, usually within the hour.

    Blyg ID 6rzya010fe05p47vmav49bgew6

    Quote line ![[6rzya010fe05p47vmav49bgew6]]

    Respond to (stub_of) {"origin": "https://protocolsforbusiness.com/blyg/", "id": "6rzya010fe05p47vmav49bgew6", "version": 1}

    Webmention endpoint https://protocolsforbusiness.com/blyg/webmention

  • No blyg yet? Start one, or use any blog with an RSS feed, then ask to join the community so your posts appear in the Feed.

Machine-readable: item JSON · changelog 1 version