PRD: PavingOS — Vertical Operating System for Paving Contractors

1. Summary

PavingOS is a vertical operating system for SMB paving contractors ($2M–$20M revenue) focused on fixing the most painful, expensive blind spot in the business:

Estimates are wrong, and no one knows why until it’s too late.

The product’s wedge is an estimating → job costing feedback loop that helps owners price work correctly, understand margins, and professionalize operations without adding office overhead.

This is not generic construction software.

This is paving-specific execution software, designed for commercial and light municipal work.

2. Target Users & ICP

Company Profile (ICP Sweet Spot)

Revenue: $2M–$20M

Stage: Owner-operator transitioning to professional management

Work Type: Commercial + light municipal

Trade Focus: Asphalt paving (initially)

Tech Stack Today: Excel + QuickBooks + duct tape

Explicitly out of scope (for now):

<$2M mom-and-pop shops (too price sensitive, chaotic)

$20M+ mid-market / enterprise (too much reporting + integration drag)

Residential paving (homeowner chaos, thin margins)

Primary Users

Owner / GM

Wants confidence in pricing

Wants margin visibility before mistakes repeat

Still close to day-to-day ops

Estimator (often the owner)

Needs fast, defensible estimates

Wants templates grounded in reality, not guesswork

Ops / Office Manager

Needs clean handoff from estimate → job → invoice

Wants fewer manual corrections

Foreman (Secondary)

Needs minimal-friction job execution

Not interested in “software,” only speed

3. Core Jobs-to-Be-Done

Owner / Estimator

Price jobs accurately and consistently

Understand why margins miss

Improve estimates over time using real data

Ops

Turn approved estimates into executable jobs

Capture job outcomes with minimal friction

Invoice faster, with fewer errors

Foreman

Know what the job is, where to be, and what’s expected

Record what actually happened without paperwork

4. Problems & Pain Points

Estimating

Estimates live in Excel and intuition

No feedback loop from actual job performance

Pricing errors repeat silently

Job Execution

Field data is incomplete or delayed

Paper tickets, texts, memory-based reporting

Actuals captured too late to matter

Financials

Invoicing lags job completion

Change orders missed

Job profitability discovered after the fact

5. Product Strategy & Wedge

Initial Wedge (What Customers Buy For)

Estimating + job costing feedback loop

This is the non-negotiable entry point.

Not CRM.

Not scheduling.

Not payroll.

Owners buy when they believe:

“This will fix my pricing and margins.”

What We Replace First

Estimating spreadsheets

Generic estimating tools (JobNimbus, Joist, etc.)

Frankenstein workflows

We do not replace QuickBooks.

6. Proposed Solution (MVP Scope)

Core Principles

Extremely opinionated

Trade-specific

Workflow-first

Field friction ≈ zero

MVP Capabilities

1. Paving-Specific Estimating (Core Wedge)

Assemblies:

Labor

Equipment

Materials (tonnage, sq ft, mobilization)

Production-rate driven pricing

Reusable estimate templates

Historical job performance surfaced inline

Simple margin visibility

This is the heart of the product.

2. Estimate → Job Conversion

Approved estimates convert directly into jobs

Scope, assumptions, and pricing flow through

No re-entry

3. Field Execution (Minimal, Foreman-First)

Mobile job view

Start / complete job

Capture:

Labor hours (job-level)

Notes

Photos

No mandatory typing

<10 seconds per interaction

4. Actuals & Variance Tracking

Estimated vs actual:

Labor

Equipment usage (basic)

Simple variance signals

Feeds back into estimating templates

5. Invoicing + Accounting Handoff

One-click invoice from completed job

Line items derived from estimate + adjustments

Sync to QuickBooks Online only

7. User Stories (High-Level)

Owner

As an owner, I want to see margin variance so I can fix pricing before repeating mistakes.

As an owner, I want to trust my estimates without micromanaging.

Estimator

As an estimator, I want to reuse proven templates instead of guessing.

As an estimator, I want real job data baked into future estimates.

Ops

As ops, I want jobs to flow cleanly from estimate to invoice.

As ops, I want fewer billing errors and faster cash collection.

Foreman

As a foreman, I want today’s job info without paperwork.

As a foreman, I want to record what happened quickly and move on.

8. Non-Goals (MVP)

Explicitly not building:

Full ERP

Payroll processing

Residential workflows

Deep municipal compliance

CRM-heavy lead management

QB Desktop support

NetSuite / enterprise integrations

9. Integrations Strategy

Launch

QuickBooks Online only

Customers

Invoices

Chart of accounts mapping

Job → invoice flow

Payroll

No payroll integrations in v1

Provide:

Job-level labor tracking

Exportable summaries / CSVs

10. Workflow Depth & Configuration Philosophy

Opinionated by default

Templates over free-form

Minimal configuration

Toggles only after proven patterns

If a customer asks for deep customization early:

They are not your ICP

Or they are operationally broken

Both are red flags.

11. Field Reality Constraints

Friction Tolerance

Almost zero

Gloves on

Phones dying

Crews will bypass friction instantly

Offline Support (Day 1 Requirement)

Minimum viable offline:

View job details

Mark job started / completed

Capture notes + photos

Sync later without data loss

If the app fails on a jobsite:

Trust is gone

Account churns