Sitework estimating software exists because earthwork bids are a different animal than almost anything else in construction. You're pricing grade changes you can't fully see, soil conditions that shift across a single lot, haul distances that change as the job progresses, and scope that has a habit of expanding the moment a dozer blade hits something unexpected. Generic estimating tools weren't built for this — and using one costs you either margin or the bid itself.
This guide is for GCs and estimators who need to pick the right tool for sitework specifically — not the most popular platform, not the one with the best demo, but the one that fits how sitework bids actually get built.
If you do enough earthwork that volume is more than a fifth of your bid workload, buy a purpose-built civil tool like Heavy Bid — a general-purpose 2D takeoff platform will cost you margin on every dirt bid. The right pick depends on your mix, so here's the short version before the deep dive.
Quick Picks
- Heavy civil and earthwork-driven bids: Heavy Bid — built for cut/fill and mass haul, not bolted on after the fact.
- Multi-trade GCs who occasionally bid sitework: STACK — fast 2D takeoff and strong vertical-trade coverage, with manual workarounds for earthwork volumes.
- Small-to-mid shops on a tight budget: PlanSwift — affordable and flexible, but you'll be doing cut/fill math outside the tool.
- Enterprise and BIM-connected workflows: Autodesk Takeoff — strong 3D model integration if you can absorb the cost and learning curve.
- GCs who need takeoff plus subcontractor bid leveling in one place: Struvia — AI-assisted takeoff with bid management for the full plan-to-award workflow.
Why Sitework Estimating Is Harder Than Almost Any Other Trade
While most estimating is arithmetic, sitework estimating is a geometry problem wrapped in a risk assessment. You're working from topographic data, civil drawings, and geotech reports — none of which give you a clean quantity to plug into a spreadsheet.
Sitework is uniquely brutal because errors compound underground. A miscalculated cut volume doesn't show up on a punch list. It shows up when you're 60% through the job, your equipment hours are blown, and you're staring at a Construction Change Order Management: A GC's Field Guide conversation you don't want to have.
The Variables That Blow Up a Sitework Bid
Soil type alone can swing your earthwork costs by 30% or more on a given project. Sandy loam moves differently than clay-heavy fill, and if the geotech report says one thing and the field says another, you're eating the difference. Shrink and swell factors compound this — native soil that measures 10,000 cubic yards in the ground might yield 12,500 yards of loose material in a truck, and that gap directly affects your haul cost.
A 10% error in cut/fill volume on a 50,000-cubic-yard commercial site project can translate to a $50,000–$80,000 swing in earthwork cost alone, depending on your local disposal and import rates. That's not a rounding error — that's the difference between a profitable job and a break-even one.
Haul distance is the other killer. Moving material 2 miles is a fundamentally different cost than moving it a half mile, and that number changes as the site develops. Weather risk — rain days, frozen ground, dewatering — adds another layer that most estimating tools don't touch at all.
How Sitework Differs From Electrical, Plumbing, and Mechanical Estimating
Electrical Estimating Software: A GC's Buying Guide (2026) and Best Plumbing Estimating Software for GCs in 2026 are built around a core assumption: quantities are linear or unit-based. You're counting fixtures, measuring conduit runs, pricing assemblies. The math is real, but the geometry is simple. HVAC Estimating Software: How to Cut Bid Time in Half and Roofing Estimating Software: 7 Features That Win Bids follow the same logic — duct runs, equipment schedules, square footage of membrane.
Sitework doesn't work that way. You're calculating volumetric quantities from surface models, and the accuracy of your estimate depends on the quality of the topographic data you're working from. A roofing estimator can eyeball a plan and get within 5%. A sitework estimator who eyeballs a grade change is writing a check they don't know about yet.
What Sitework Estimating Software Actually Needs to Do
To choose the right tool, define your functional requirements for sitework. Not a feature checklist — a functional minimum that reflects how bids get built in the real world.
2D and 3D Takeoff From Civil Plans
Most estimating tools handle 2D takeoff well. You upload a PDF plan, trace areas and lengths, apply unit costs. That works fine for vertical trades — it's essentially how most HVAC estimating software and roofing estimating software workflows operate. For sitework, 2D takeoff gets you part of the way there, but it doesn't tell you what's happening between contour lines.
3D surface model takeoff — where you're importing a DTM or working from digitized contours — is what separates a precise earthwork estimate from an educated guess. The best sitework tools let you work in both modes: 2D for site improvements like paving and curb, 3D for earthwork volumes.
Cut/Fill Calculation and Mass Haul Analysis
Automated cut/fill calculation isn't a luxury — it's the core function a sitework estimating tool has to perform. Manual spreadsheet methods require you to slice the site into cross-sections and calculate volumes by hand, which introduces compounding error at every step and takes hours that most bid schedules don't have.
A mass haul diagram goes further. It tells your superintendent where material is moving from and to across the site, which affects equipment staging, cycle times, and whether you need to import or export material. A simple volume number doesn't give you that. A superintendent who's been running dirt for 20 years can look at a mass haul diagram and immediately spot whether the estimate's equipment plan makes sense — the problem is most estimating tools never produce one.
Equipment Productivity and Cost Integration
The gap between a sitework estimate and a sitework budget is usually equipment. Most tools give you a volume; the best ones tie that volume directly to excavator cycle times, dozer production rates, and operator and fuel costs — inside the estimate, not in a separate spreadsheet you have to reconcile later.
If your tool produces a cubic yard quantity and then hands you off to Excel to figure out what it costs to move, you haven't saved as much time as you think.
The Main Sitework Estimating Tools Compared
Comparison Table: Sitework Estimating Software at a Glance
| Tool | Best For | Key Strength | Key Limitation | Est. Cost |
|---|---|---|---|---|
| STACK | Multi-trade GCs | Fast 2D takeoff, strong vertical trade coverage | Limited volumetric earthwork capability | ~$2,000–$5,000/yr |
| PlanSwift | Small-to-mid GCs | Affordable, flexible plugin system | Manual workarounds needed for cut/fill | ~$1,500–$2,500/yr |
| Autodesk Takeoff | Large GCs, enterprise | Strong 3D model integration, BIM-connected | High cost, steep learning curve | $10,000+/yr |
| Heavy Bid | Heavy civil contractors | Built specifically for earthwork and mass haul | Less suited for vertical trade scopes | ~$3,000–$8,000/yr |
| Struvia | GCs managing full bid workflow | AI-assisted takeoff + subcontractor bid management | Newer platform, growing feature set | Contact for pricing |
Where General-Purpose Platforms Fall Short
STACK and PlanSwift are genuinely strong tools for what they were designed to do. If you're estimating Structural Steel Estimating Software: A GC's 2026 Guide workflows, MEP scopes, or roofing, they handle 2D quantity takeoff efficiently and integrate reasonably well with cost databases. The problem is sitework.
Neither platform was built for volumetric earthwork. You can use STACK to measure disturbed area and apply a cost-per-square-foot, but that's not a cut/fill calculation — it's a rough approximation that works until it doesn't. The Reddit estimating communities are honest about this: the workaround most STACK users describe for earthwork is exporting to a spreadsheet and doing the volume math manually. That's not a workflow; that's duct tape.
PlanSwift has a similar gap. It's extensible through plugins, but the earthwork plugins available don't match the depth of purpose-built civil tools. If your sitework volume is more than 20% of your annual bid workload, a general-purpose platform is going to cost you time on every single estimate.
Where AI-Assisted Tools Are Changing the Math
AI-driven estimating platforms have gotten genuinely useful in the last two years — not because AI understands soil conditions, but because it's very good at reading plans and extracting quantities fast. Pattern recognition across civil drawings, automated quantity identification, and rapid assembly matching are areas where AI reduces the time from plan receipt to a working estimate by a meaningful margin.
What AI doesn't replace is estimator judgment on the variables that matter most in sitework: soil risk, haul logistics, weather exposure, and the site-specific factors that don't show up on a drawing. A platform that uses AI for the mechanical parts of takeoff while keeping the estimator in control of the risk variables is a better model than one that tries to automate the whole thing.
The Top Sitework Estimating Tools, Reviewed
The comparison table gives you the one-line version. Here's the longer read on each platform — who it's actually built for, where it breaks down on dirt, and the moment you'll know you've outgrown it.
Heavy Bid (HCSS)
Heavy Bid is the heavy-civil incumbent, and on earthwork-driven bids it earns the reputation. It's best fit for contractors whose workload is dominated by mass excavation, grading, and utilities — DOT work, large site development, infrastructure — where cut/fill, haul analysis, and crew-and-equipment production rates need to live inside the estimate. It's a poor fit for a multi-trade GC who bids two dirt jobs a quarter; the depth you're paying for sits idle most of the year. Pricing is quote-based and scales with seats and modules, and it lands at the upper end of this category — budget for implementation and training on top of the license. The strength is production-based estimating that ties volumes to real equipment hours rather than a flat cost-per-yard; the cost is a learning curve that assumes a dedicated estimator. If you're a general-purpose 2D platform user who keeps exporting earthwork to a spreadsheet, and dirt is becoming a third of your bids, that's the trigger to move to Heavy Bid.
STACK
STACK is a fast, cloud-based 2D takeoff platform that's strongest for multi-trade GCs and vertical-trade specialists who occasionally touch sitework. Best fit: shops that want quick on-screen quantity takeoff, easy collaboration, and broad trade coverage without a heavy install. Poor fit: anyone who needs true volumetric earthwork — STACK has no real cut/fill engine, and the common workaround is measuring disturbed area and finishing the volume math in Excel. Pricing is plan-based and billed annually, generally in the low-to-mid four figures per year, with year-over-year increases that long-time users have flagged. The pros are speed and a short ramp-up; the con is that on a grading-heavy bid you're approximating, not calculating. The switching trigger is the day your earthwork spreadsheet workaround starts costing you bids you should have won.
PlanSwift
PlanSwift is the budget-friendly, extensible takeoff tool for small-to-mid shops that need flexibility without a big annual commitment. It's best fit for contractors who do mostly vertical or flatwork takeoff and want a familiar, point-and-click interface. For earthwork specifically, the honest picture is that core PlanSwift doesn't do cut/fill on its own — you lean on a third-party plugin like Earthwork Pro (a modest one-time add-on, well under a thousand dollars) to get basic grading volumes. That makes it a poor fit for high-volume earthwork; the plugin handles simple sites but doesn't approach the depth of a purpose-built civil tool. Pros: low cost of entry and a large plugin ecosystem. Cons: bolt-on earthwork that strains on complex grading and a desktop-era workflow. If your sites are getting bigger and the plugin starts producing numbers you don't trust, it's time to step up.
Autodesk Takeoff
Autodesk Takeoff is the enterprise, BIM-connected option, and its value is almost entirely about ecosystem fit. Best fit: large GCs already standardized on Revit, AutoCAD Civil 3D, and Autodesk Construction Cloud, where pulling quantities directly from coordinated 3D models eliminates re-tracing. Poor fit: a small earthwork-focused shop that doesn't live in Autodesk — you'd pay enterprise pricing for integration you won't use, and it isn't a dedicated cut/fill estimator the way a civil-specific tool is. Pricing is subscription-based through Autodesk and runs high once full implementation is factored in. The pro is unmatched model-to-takeoff continuity for BIM workflows; the con is cost and a steep learning curve for teams not already in the Autodesk world. The trigger to adopt it is organizational, not estimating-driven: when the rest of your company moves onto Autodesk Construction Cloud, takeoff should follow the models.
Struvia
Struvia is the pick for GCs who need the full plan-to-award workflow in one place, not just a takeoff number. Best fit: general contractors managing sitework scopes who have to take off quantities and then level a stack of subcontractor bids across earthwork, utilities, and paving — the part most takeoff tools ignore. It's a less natural fit for a solo earthwork sub who only wants raw cut/fill volumes and nothing else. Pricing is quote-based; contact for current numbers rather than assuming a public list price. The strength is AI-assisted takeoff paired with built-in bid leveling, so the scope-gap problem that sinks sitework bids gets caught before award instead of after; the trade-off is a newer, still-expanding platform. If you're running takeoff in one tool and managing sub bids in spreadsheets, consolidating both into Struvia is the move that closes the gap.
How to Evaluate Sitework Software for Your Specific Operation
Small Shop vs. High-Volume Estimating Team
A two-person estimating team running 15–20 bids a month has a different problem than a GC with four dedicated estimators and a bid calendar that never empties. The small shop needs speed and simplicity — a tool that gets them to a number fast without a six-week training curve. The larger operation needs consistency, template management, and the ability to hand off estimates between team members without rebuilding context from scratch.
One GC we talked to running a mid-size sitework operation in the Carolinas put it plainly: "We were using a tool that worked great for one estimator. The second we tried to bring someone else in, we spent two weeks just explaining how the spreadsheet was structured." That's a scaling problem, not a software problem — but the right platform prevents it.
Integration With Your Existing Stack
Sitework estimating doesn't end at bid submission. The quantities and costs in your estimate need to flow into project management, subcontractor management, and cost tracking. If your estimating tool doesn't talk to Procore or Buildertrend, you're re-entering data on every project handoff — and data re-entry is where errors live.
Ask every vendor a direct question before you buy: what does the export look like, and how does it map to your project management platform? A CSV dump is not an integration.
Total Cost of Ownership Beyond the License Fee
The license fee is the number vendors lead with. It's rarely the number that matters most. Training time, data migration from your existing system, productivity loss during ramp-up, and the ongoing cost of manual workarounds for the 20% of functionality the tool doesn't cover — those are the real costs.
Most estimating teams underestimate ramp-up cost by a factor of two. A $3,000/year tool that requires 80 hours of setup and three months to reach full productivity has a real first-year cost that's significantly higher than the invoice. Factor that in before you sign.
The Subcontractor Bid Management Problem Sitework GCs Overlook
The Reddit and forum discussions about sitework estimating software focus almost entirely on takeoff. That's understandable — takeoff is where the technical complexity lives. But for GCs managing sitework scopes, the harder problem often isn't the takeoff. It's what happens after you send the plans out.
Why Scope Gaps Kill Sitework Bids More Than Price Errors
Picture this: you're estimating a 5-acre commercial site development. You send the grading and utilities scope to three earthwork subs and get bids back with a 25% spread — the low is $480,000, the high is $600,000. The instinct is to assume the low bidder is sharper on price. The reality, more often than not, is that the low bidder excluded rock excavation, off-site haul disposal, and erosion control — three line items that add up to exactly the gap you're looking at.
A 25% spread on a sitework bid is almost never pure unit price difference. It's scope. And if you don't catch it before award, you're either eating a change order or fighting with a sub over what they thought they were pricing.
Leveling Sub Bids Across Earthwork, Utilities, and Paving
Bid leveling for sitework means building a scope matrix — every line item that should be included, mapped against what each sub actually included or excluded. For a site with earthwork, underground utilities, paving, and landscaping subs all bidding simultaneously, that matrix can have 40–60 line items.
Tools that only handle takeoff leave estimators doing this in a spreadsheet. That's the hardest, most judgment-intensive part of the process, and it's where mistakes that cost real money get made. A platform that supports bid leveling alongside takeoff closes a gap that most estimating software ignores entirely.
Frequently Asked Questions
What is sitework estimating software and who uses it?
Sitework estimating software is a category of construction estimating tools built specifically for earthwork, grading, utilities, paving, and related civil scopes. Primary users include general contractors with significant site development work, civil subcontractors, earthwork specialists, and land development companies. Unlike general estimating platforms, sitework tools are designed to handle volumetric quantity calculations, topographic data, and the equipment productivity factors that drive earthwork costs. They solve problems that standard takeoff tools — built for vertical construction — aren't equipped to handle.
How is sitework estimating software different from electrical or plumbing estimating software?
Electrical estimating software and plumbing estimating software are built around linear quantities and unit-count assemblies — wire runs, conduit, fixtures, pipe lengths. The geometry is straightforward and the cost drivers are well-defined. Sitework estimating works from surface models and topographic data, calculating volumetric quantities that depend on grade changes, soil conditions, and haul logistics. The core math is three-dimensional, not linear. That's why a general-purpose tool that works well for electrical or plumbing scopes often fails when you try to use it for earthwork — the underlying calculation model is different.
How much does sitework estimating software cost?
Entry-level platforms like PlanSwift start around $1,500–$2,500 per year and can handle basic sitework takeoff with manual workarounds for earthwork volumes. Mid-range tools like STACK run $2,000–$5,000 annually. Purpose-built heavy civil tools like Heavy Bid range from $3,000 to $8,000 per year depending on seat count and features. Enterprise platforms like Autodesk Takeoff can exceed $10,000 annually once you factor in full implementation. The right price point depends on your bid volume — a team running 10 sitework bids a month has a different ROI calculation than one running two.
Can AI-powered estimating tools handle sitework accurately?
AI tools are genuinely accurate for plan reading and quantity extraction — identifying areas, lengths, and counts from civil drawings faster than manual digitizing. Where they still require human oversight is in the judgment-heavy variables: soil type and behavior, site-specific haul logistics, weather and seasonal risk, and scope interpretation on ambiguous plan details. An AI-assisted platform that accelerates the mechanical parts of takeoff while keeping an estimator in the loop on risk factors is a realistic and useful tool. An AI tool that claims to fully automate a sitework estimate without human review is overselling what the technology actually does.
How long does it take to implement new estimating software?
Most teams reach full operational speed in 4–8 weeks — not the 30-minute onboarding vendors show in demos. The first two weeks are typically consumed by data setup: importing your cost database, building templates for your most common project types, and migrating historical bid data. Weeks three and four involve running live bids in parallel with your old system to catch gaps. The teams that rush this process end up with a tool that's configured for the demo, not for how they actually estimate. Budget the time upfront and you'll avoid a painful rebuild six months in.
Do I need separate software for mechanical, structural steel, or roofing scopes?
It depends on your bid volume in each trade. If you're a GC that touches mechanical estimating software and structural steel estimating software needs only occasionally — subbing those scopes out entirely — a single platform with reasonable multi-trade coverage may be sufficient. If you have in-house estimators dedicated to mechanical or structural steel scopes, trade-specific tools will outperform a generalist platform on accuracy and speed. The honest answer is that most GCs running mixed scopes end up with a primary estimating platform plus one or two trade-specific tools for their highest-volume specialties. The integration between those tools matters more than which specific products you choose.
Making the Switch: What a Realistic Transition Looks Like
Switching estimating software mid-season is one of the more disruptive things a GC can do to their estimating department. Vendors won't tell you that. The demo always happens on a clean dataset with a cooperative plan set — not during the three weeks in March when your team is running six bids simultaneously and the civil sub just sent revised drawings at 4 PM.
The teams that transition successfully share one trait: they pick a defined start date, run parallel systems for four to six weeks, and assign one person to own the migration. That person's job is building templates, documenting the new workflow, and being the internal resource when the rest of the team hits a wall. Without that owner, the transition drags on for months and the old spreadsheets never actually go away.
A Denver-based estimator said something that stuck with us: "We thought we were switching software. What we were actually doing was rebuilding how we estimate — the software just forced us to make decisions we'd been avoiding for two years." That's the real value of a platform change done right. It's not just a tool swap. It's a process reset.
The teams that struggle are the ones who treat implementation as an IT project rather than an estimating project. The software vendor handles the technical setup. Nobody but your estimators can build the cost structure, the templates, and the workflows that make the tool actually useful on a real bid.
Go in with 60 days, a dedicated owner, and the expectation that your first three bids in the new system will take longer than usual. After that, the efficiency gains compound.
Sitework estimating is complex enough without fighting your software. The right sitework estimating software handles volumetric takeoff, integrates equipment costs, and supports the bid leveling workflow that turns a pile of sub quotes into a defensible number. If you're evaluating tools that cover the full workflow — from plan receipt through subcontractor bid management — see how Struvia works. It's built for GCs who need more than a takeoff tool.
*Reviewed by Weston Burnett, Co-Founder and CTO of Struvia.*