Pre-construction software: how takeoffs, estimates, plans, and bids fit together.
Back to Journal

Industry

Pre-construction software: how takeoffs, estimates, plans, and bids fit together.

Five tools, one data model. Why the future of pre-construction is a connected suite — not another point solution.

By Jacob Muzychenko

Pre-construction software is the layer of tooling that turns a set of plans into a winning bid. In 2026, pre-construction is typically five connected disciplines — takeoffs, estimates, plans (scope planning), bids (proposal packaging), and schedules — each historically served by its own standalone tool. The shift over the last two years has been away from stitching five point tools together and toward running all five on one data model, in one subscription.

This post walks through what each layer does, how they connect, and why the suite model produces better bids than the stack-of-tools model.

What is pre-construction?

Pre-construction — "pre-con" — is everything that happens between "we might bid this" and "we signed the contract." It's the part of the project where money is spent without revenue coming in, and it's also where margin is won or lost. A good pre-con workflow gets you to a signed contract faster, with a more accurate price, and fewer scope gaps.

The five layers of the bid stack

1. Takeoffs

Takeoffs are the measurement layer. You take a PDF blueprint and determine quantities: how many square feet of tile, how many linear feet of Schluter edge, how many drains. Every downstream layer depends on the takeoff being correct.

Common tools: Cedrus Takeoffs, STACK, PlanSwift, Togal.AI, Bluebeam Revu.

2. Estimates

Estimates apply prices to quantities. An estimate takes the takeoff's numbers, multiplies them by assembly rates or line-item prices, applies waste and markup, and produces a total cost.

Common tools: Cedrus Estimates (coming), ProEst, Sage Estimating, Clear Estimates, ConstructConnect.

3. Plans (scope planning)

Plans translate a won bid into an execution-ready scope: which rooms, which assemblies, which subs, which materials. This layer is where takeoff and estimate data becomes a usable project plan.

Common tools: Cedrus Plans (coming), Procore Project Management, Buildertrend, CoConstruct.

4. Bids

Bids package the estimate into a proposal the client will actually read. This includes scope narrative, exclusions, terms, schedule, and branded presentation.

Common tools: Cedrus Bids (coming), PandaDoc, Bidsketch, DocuSign Proposal.

5. Schedules

Schedules break the scope into time and crews. Which crew is where, when, for how long.

Common tools: Cedrus Schedules (coming), Microsoft Project, Smartsheet, Asta Powerproject.

The stitching problem

The traditional approach is to pick one tool for each layer. That means five subscriptions, five logins, five data models, five export/import cycles. Every time data moves between layers, something drifts — a waste factor changes, a line gets dropped, a client's name gets misspelled.

A typical pre-con workflow on five point tools runs the data through 4–6 manual handoffs between first upload and final bid. Each handoff is a chance for error and a drain on estimator time. Firms running this setup report spending 15–20% of pre-con hours on just moving data between systems.

The suite model

The alternative is a suite — one platform, one data model, five tools that share the same underlying project. A measurement drawn in takeoffs flows into the estimate without export-import. An assembly change in the estimate updates the bid automatically. When the bid wins, the schedule inherits the scope and crews without re-entry.

The suite model wins on three dimensions:

1. No data drift

Because there's only one data model, there's no drift between takeoff and estimate or between estimate and bid. Changes cascade automatically.

2. No integration tax

Point-tool workflows pay a constant integration tax — new release breaks an integration, CSV format changes, API rate limit, etc. Suites don't have this problem because there are no integrations between the five layers; it's all one app.

3. Pricing sanity

Five point tools at $49–$99 per seat per month each costs $250–$500 per seat monthly. A suite that covers all five at one seat price is typically $49–$99 total — one-fifth the cost, all five capabilities.

What to look for in a pre-construction suite

Not every "suite" is actually a suite. When evaluating, test for:

  • Shared data model.: Draw a takeoff, then see if the estimate opens with the quantities pre-populated (without a sync step). If it doesn't, it's not a suite.
  • Single subscription covers every tool.: If tools are sold as add-ons, it's still a point-tool pricing model dressed up as a suite.
  • One URL, one login, one UI.: If you have to switch apps between layers, the experience tax is the same as running five point tools.
  • Single vendor roadmap.: When the vendor ships a new tool (e.g., schedules), does it arrive inside your existing subscription? If yes, it's a real suite. If it ships as a new SKU, it's a stack.

Where Cedrus fits

Cedrus ships as a suite. Takeoffs is live today. Estimates, Plans, Bids, and Schedules are on the roadmap, and each arrives inside the existing subscription — no upsell, no SKU swap. The data model is shared: what you measure in Takeoffs is already half of the estimate.

The pricing model reflects this. One subscription covers every tool in the suite, per seat. When Estimates ships, Firm subscribers get it the week it's ready.

Frequently asked

What's the difference between takeoff software and estimating software?

Takeoff software measures quantities from a blueprint. Estimating software multiplies those quantities by prices. Some tools do both (Cedrus, STACK); others specialize in one layer and integrate with the other.

Do I need all five layers of the pre-construction stack?

Most contracting businesses use takeoffs and estimates daily. Plans, bids, and schedules become critical once a firm is running more than 10 active projects or has multiple estimators.

How long does it take to switch from a stack-of-tools to a suite?

Most firms migrate over 30–60 days, one layer at a time. Start with takeoffs, then estimates. Plans, bids, and schedules usually migrate together.

Is a suite always cheaper than a stack?

On list price, almost always yes. Suites make up for the lower price with stickier customers — since every layer depends on the others, leaving a suite is harder than leaving a point tool. The total cost of ownership is where suites shine.

Pre-construction software doesn't have to be five apps taped together. If you want to see what it looks like as one, try Cedrus — free on your first bid.

Read next

More from the journal.