Commitment ledger for sitework subcontractors that ties material buys to live budgets, delivery windows, and ERP job-cost codes.

1. Fresh growth funding shows investors believe trade-specific construction procurement has matured into a real software category.
2. The category is explicitly shifting away from generic marketplaces toward workflow software, which favors focused operational products with deep trade context.
3. ERP integrations are moving from nice-to-have to buying requirement, making a commitment-control layer newly deployable inside existing contractor stacks.
4. Predictive spend analytics are entering procurement, so buyers are ready to pay for earlier budget-risk detection rather than simple PO digitization.

Catalyst. SubBase's funding and roadmap show that construction buyers are finally adopting trade-specific procurement workflows with ERP links and predictive analytics, creating an opening for a narrow system-of-action product instead of another back-office record system.

The product gives each project team a shared material commitment ledger tied to estimate line items, cost codes, and delivery windows. Buyers request and compare vendor quotes, lock the selected commitment, and route exceptions such as substitutions, rush freight, or quantity overages for approval before trucks roll. Every commitment syncs into the contractor's ERP as a live exposure, so finance can see committed-versus-budgeted spend before invoices arrive. A predictive layer flags jobs where purchase timing, price drift, or field quantity changes are likely to blow the remaining budget. Suppliers can confirm deliveries and ticket details through a lightweight portal without forcing a full marketplace migration.

What's different. Most construction software either starts in accounting after the commitment is made or tries to win as a broad supplier marketplace. This company starts at the moment a field team chooses a vendor and creates a live financial commitment, which is where specialty contractors actually lose control. The defensible data asset is a trade-specific graph of quotes, substitutions, lead times, delivery performance, and committed-versus-final cost outcomes across local material categories that generic suites rarely capture cleanly.

Jobs to be done

flowchart LR
  Buyer[Project manager or controller] --> Pain[Late visibility into material commitments]
  Pain --> Product[Material commitment ledger]
  Product --> Outcome[On-budget jobs with earlier variance alerts]

Executive takeaways

• The category is real but still structurally open: SubBase just raised a $7M Series A, Kojo raised $39M and already processes over $1B of materials orders, yet the strongest public products still split across materials ops, procurement scheduling, and broad commitment logs rather than sitework-specific commitment control. [16][21][22][26][28]
• Customer pain is concrete, not abstract: contractors still buy materials through calls, texts, emails, spreadsheets, paper delivery notes, and downstream invoice workflows while payment cycles can stretch past two months. [10][11][19][30][31]
• Why now is credible: public highway, sewer, and water construction rose from $170.3B in 2022 to $226.6B in 2025, FHWA is pushing e-ticketing and digital as-builts, and contractors remain more bullish on public-sector than many private segments. [2][4][6][35]
• The best wedge is a control layer, not a marketplace: the product should own quote selection, approvals, substitutions, delivery windows, and quantity variance before the ERP sees a formal PO or invoice. [12][14][15][18][20]

Market definition

Workflow software for civil and sitework contractors that sits between field buying and the accounting or ERP system, turning material requests, quotes, commitments, delivery updates, and exceptions into a live financial exposure record before invoices arrive.

Customer and buyer

Primary operators are controllers, procurement leads, project executives, and project managers inside U.S. civil and sitework contractors working across highway, water or sewer, and site-preparation categories. The economic buyer is usually the CFO, controller, or VP Operations because the product matters only if it improves forecast accuracy, approval control, and margin protection inside existing Procore, Sage, Vista, or Foundation-style stacks. [1][13][19]

Buying triggers

• A project misses budget because material commitments, substitutions, rush freight, or quantity changes surfaced too late for finance to react. [7][10][11][15][19]
• A public-sector or utility-heavy job increases documentation pressure through BABA sourcing rules, water-infrastructure funding oversight, or e-ticketing adoption. [4][5][33][34][35]
• An ERP cleanup, branch expansion, or month-end forecast review exposes how much buying activity is still happening in email, phone calls, and spreadsheets. [12][13][14][19][20][30]

Willingness to pay

Public list pricing is opaque, but the category clearly sells as annual subscription software rather than as a thin-margin marketplace take rate. ProcurePro explicitly frames itself as a small annual subscription, Bulk Exchange rejected take-rate pricing because contractors dislike margin leakage, and Kojo and Procore both sell enterprise control layers connected to accounting. That supports a branch or project-volume subscription if the product proves less waste, faster ordering, or fewer budget surprises quickly. [21][22][27][31] [21][22][27][31]

Category dynamics

Growth signal 10.0% CAGR

Validation signals

• SubBase’s June 2026 Series A confirms fresh investor appetite for trade-specific construction material procurement software.
• Kojo’s traction shows the adjacent category can scale: the company cites nearly 10,000 projects, 46-state reach, and a new spend-management push.
• Comstruct validates the same analog pain pattern around phone orders, printed delivery notes, and invoice reconciliation on large projects.
• Bulk Exchange proves that sand, gravel, and bulk-material sourcing remains sufficiently manual and fragmented to support new software entrants.
• Briq’s customer base and construction-finance automation focus show that buyers already budget for vertical software tied to forecasting and margin control.

Regulatory & technical constraints

• The product must coexist with Procore, Sage 300 CRE, Spectrum, Vista, Foundation, or similar accounting systems instead of creating duplicate cost records.
• Federally funded water and infrastructure jobs can require BABA-compatible sourcing and documentation discipline.
• States using e-ticketing and digital as-built workflows will expect structured ticket and delivery data rather than paper-only artifacts.
• Prompt-payment, lien, and retainage realities make invoice, waiver, and approval timing sensitive enough that workflow audit trails matter.

The field breaks into four camps: broad construction suites, trade-contractor materials platforms, procurement-orchestration tools, and construction-finance automation overlays. The startup wins only if it becomes the trusted pre-invoice commitment record for sitework materials rather than another generic sourcing marketplace or another after-the-fact accounting screen. [12][21][26][28][29][32]

Why incumbents do not win by default

• Broad construction suites. Procore already owns commitments and accounting connectors, but its public workflow starts once a PO or subcontract is formally created instead of at the earlier quote-selection and delivery-control moment where sitework margin leaks begin.
• Trade-contractor materials platforms. Kojo and Trimble Materials prove demand for contractor-facing materials software, but their center of gravity is broader materials ops, inventory, and ecosystem coverage rather than a sitework-first commitment-control ledger tied to budget variance.
• Procurement orchestration tools. ProcurePro and SubBase validate workflow appetite around procurement visibility and ordering, yet their public materials leave room for a deeper cost-code, quantity-variance, and delivery-window control layer focused on sitework-heavy buying.
• Construction finance automation overlays. Briq shows the budget for construction-specific forecasting and AP automation, but it still sits closer to finance process automation than to real-time material commitment capture on the job.

Sitework Material Commit Ledger is a pre-invoice commitment-control system for U.S. civil and sitework subcontractors that buy aggregates, drainage pipe, geotextiles, and related heavy materials across many live jobs. The beachhead is 100-400 employee subcontractors with 10-50 concurrent projects and at least $10M of annual material spend, because they are large enough to feel margin leakage from fragmented buying but still poorly served by generic procurement suites. The first product is not a marketplace and not a new ERP; it is a system-of-action layer that captures quote selection, approvals, substitutions, delivery windows, and quantity variance before invoices hit Sage, Vista, Foundation, or Procore-connected accounting workflows. That wedge matches the researched buying trigger: a margin-improvement mandate or a recent job miss where finance learned about material exposure too late to react. Go-to-market should start with founder-led branch pilots and ERP- or consultant-led introductions, because deployment credibility matters more than broad top-of-funnel volume at this stage. Public research supports a real and growing category, but it does not provide strong public proof on customer retention, exact willingness to switch, or pricing for a sitework-specific entrant, so the first 12 months must focus on paid pilots, implementation speed, and pilot-to-production conversion. The strongest strategic risk is that broad suites and adjacent specialists close enough of the workflow gap before the startup earns a trusted commitment dataset and repeatable channel.

Problem

• Regional sitework subcontractors commit material spend through calls, texts, emails, and spreadsheets days or weeks before the ERP records the cost.
• Controllers and project executives discover substitutions, rush freight, and quantity drift too late to protect cost-to-complete forecasts or job margin.

Solution

• A material commitment ledger records quotes, approvals, selected vendors, delivery windows, substitutions, and quantity changes against estimate line items and cost codes before trucks arrive.
• One-way ERP sync and exception alerts turn each field buying decision into visible committed exposure so finance can review budget risk before invoices, tickets, and month-end surprises.

Why we win

• We start at the exact control gap where specialty contractors lose margin first: quote award through delivery commitment, before formal PO and invoice workflows in broader systems.
• Each deployment builds trade-specific data on quotes, lead times, substitutions, delivery reliability, and committed-versus-final cost outcomes that generic suites rarely structure cleanly.

Milestones

flowchart LR
  Wedge[Sitework commitment-control wedge] --> MVP[Branch pilot with one-way ERP sync]
  MVP --> Proof[Captured commitments and earlier variance alerts]
  Proof --> Expansion[More branches, adjacent trades, and analytics]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least one beachhead segment will fund a branch-level pilot from an operating budget tied to margin control rather than a broad software transformation budget.
• The product can capture more than 90% of target commitments before first delivery without creating duplicate entry that finance rejects.
• One-way ERP sync into the top beachhead stacks is sufficient to win the first sale before deeper bidirectional automation exists.
• Paid pilots convert to production at 50%+ because variance alerts and approval controls change forecast behavior, not just reporting.
• Incumbents and adjacent specialists do not neutralize the wedge before the startup earns data and workflow depth in sitework-heavy accounts.

Open diligence questions

• Which ERP and project-system combination appears most often in the first 20 qualified sitework accounts?
• What measurable margin leakage do target buyers attribute to late commitment visibility versus price inflation alone?
• How much supplier participation is required for a branch pilot to feel complete, and which intake mode works best first?
• Do controllers trust commitment-based alerts enough to change WIP reviews and approval behavior?
• Can distributor or consultant channels repeatedly source qualified pilots without turning the company into a custom implementation shop?

Model sanity

• Revenue engine. Base-case revenue comes from ~35 active paying branches by Q4Y3 at the top of the stated branch pricing band, with second-branch expansion doing as much work as net-new logos.
• Must go right. The packaged ERP connector and weekly variance-review workflow must turn paid pilots into production branches fast enough to keep the 60%+ conversion and 40% expansion assumptions credible.
• Model breaks if. If partner-sourced starts slip toward the downside case, cash goes negative before breakeven and the seed raise must happen earlier than Q2Y3.
• Next-round proof. A seed round is justified once Q2Y3 shows about 25 paying branches, predictive alerts live, and quarterly burn reduced below $100K.

Scenarios

Sensitivity

flowchart LR
  Leads --> PaidPilots
  PaidPilots --> ProductionBranches
  ProductionBranches --> ExpansionBranches
  ExpansionBranches --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: Y3 branch growth assumes one partnerships leader can sustain both new-logo referrals and the 40% second-branch expansion motion without an additional quota-carrying seller. · Gross margin reaches the target only if the first packaged ERP bundle avoids bespoke services, which remains an explicit operating assumption rather than a proven fact today. · The downside case goes cash-negative, so the company should raise the next round off the Q2Y3 milestone rather than waiting for full-year profitability. · Y1 blended revenue per branch is buoyed by pilot pricing; if pilots clear below the $30K midpoint, CAC payback stretches even if logo count stays on plan.

• Thin proof from public sources. Public evidence confirms funding and roadmap direction but does not show customer adoption depth or willingness to switch. Mitigation: Run early design-partner sales around one trade package and require measurable pre-invoice variance reduction before broad expansion.
• ERP and workflow integration drag. Contractors will resist if the product adds duplicate data entry or breaks established accounting controls. Mitigation: Start with one-way commitment sync and approval workflows that fit existing ERP processes before deeper bidirectional automation.
• Incumbent or distributor bundling. Construction ERP vendors or major distributors could add lightweight procurement features once the wedge proves valuable. Mitigation: Win with faster trade-specific execution, build distributor-facing delivery data loops, and own the commitment-level dataset incumbents do not already capture.