Construction operations

Construction Bid Board

General contractors post scopes and drawings; vetted subcontractors bid with line-item pricing; GCs compare bids side-by-side and award — replaces email-and-PDF chaos.

Full planning bundle — BRAND, MRD, BRD, PRD, DESIGN
Branded styleguide — typography, color, components
4 previewable mockups

Cloning copies the full plan into a new project you own — edit it freely.

Inside the bundle

Styleguide and mockups

A look at the brand palette and screen-level mockups that ship with this plan. Cloning copies all of them into your project.

Mockups

Style guide

Styleguide

What this blueprint gives you

The bid-tracking and invitation-to-bid workflow modeled as software: general contractors invite vetted subs to bid on packaged scopes, subs reply with structured line-item bids tied to the plan documents, and GCs compare apples-to-apples on a single screen before awarding.

Five planning documents (BRAND, MRD, BRD, PRD, DESIGN) at senior-team depth, covering ITB packaging, sub vetting and invitations, plan/ drawing distribution, line-item bid forms, side-by-side bid leveling, award and contract handoff, and the audit trail that procurement teams actually need.

Planning documents

Preview the plan

Each blueprint includes the senior-level planning files. These cards show the opening text before you clone the full bundle.

Brand Guidelines Document

BRAND.md

Preview

BRAND — Construction Bid Board One line Stop running bids out of an inbox. Invite subs, get apples to apples bids back, award with a paper trail. Who it speaks to General contractors, estimators, and project executives running commercial, multifamily, or mid size residential jobs. They're spending evenings reconciling four versions of a PDF bid, two emailed quotes, and a sub who texted his number to the PM. On the other side: subcontractors who win or lose work based on whether they can find the

Design Specification Document

DESIGN.md

Preview

DESIGN — Construction Bid Board Information architecture GC app: Projects, Project detail (Bid package, Subs invited, Documents, Q&A, Leveling, Audit), Sub directory, Firm settings. Sub app: Inbox (all open ITBs), ITB detail (drawings, specs, addenda, bid form, Q&A), My bids (drafts + submitted + awarded), Firm profile. Shared: drawing viewer (modal/full bleed), document version history, audit log export. Admin (platform): firm verification queue, file processing health, support tools. Key scree

Market Requirements Document

MRD.md

Preview

MRD — Construction Bid Board The problem Bidding subcontractors on a commercial or multifamily job runs on email, Dropbox links, and a spreadsheet someone updates at 11pm. The GC sends drawings to 30 subs across 12 trades. Replies arrive over weeks in different formats — some PDFs, some emails, some hand marked plan sets. Comparing three plumbing bids requires manually translating each into the same line items. Addenda go out and half the subs miss them. When the job starts and a sub disputes th

Business Requirements Document

BRD.md

Preview

BRD — Construction Bid Board Business outcomes 1. GC seats × project volume. Revenue scales with paid GC firms and the number of active projects they run through the platform. 2. Sub network density. Invited subs that have an active account and view ITBs reliably — the asset that makes a GC stay. 3. Bid response rate per project. The headline operational KPI; high response rates → competitive bids → GC sees value. 4. Award to handoff time. From ITB sent to scope awarded; shrinking this is the GC

Product Requirements Document

PRD.md

Preview

PRD — Construction Bid Board Phase 0 — Foundations Auth + accounts: GC firm + roles ( admin , pe , estimator ), Sub firm + roles ( admin , estimator ), project level access control. Firm directory: a sub firm has a single profile (trades, service area, contact, optional prequal docs) used across all GCs. File pipeline: chunked upload, virus scan, PDF normalization, signed access URLs, immutable storage per document version. Acceptance: a GC creates a firm, adds 3 users in different roles, and co