The evidence
Procore ships resource leveling, RFI trees, submittal workflows, AIA G702/G703 progress billing, drawing markup with sheet takeoffs, prequalification, and bid leveling. A five-person residential crew opens invoices, estimates, chat, time tracking, and maybe daily logs. Everything else is bloatware. You pay for it because Procore prices it into every tier, but it never renders a dollar of value on your jobs.
Buildertrend is a lighter version of the same problem. Gantt charts, warranty management, selections libraries with vendor catalogs, purchase orders routing through a 4-step approval workflow. On a residential build with two active jobs and one bookkeeper, you use maybe four surfaces. The other 30 are training slides for a demo call.
Here is the audit I ran with a Tampa remodeler on Buildertrend. Over a 60-day window, I logged every screen the owner and the office manager opened. The tally: nine of forty two feature surfaces got opened more than once. Six got opened once, then never again. The remaining twenty seven never got a single click. That is a 70 percent bloatware tax on a $499 per month subscription. About $350 of every monthly bill was paying for real estate on a screen nobody visited.
Why the industry gets this wrong
The pitch is that comprehensive tools are better because you might grow into the features. That framing assumes features are free once you own them, but they are not. Features you do not use still slow the tool down. Every extra menu item is a cognitive tax on the field crew trying to find the one screen they actually need. Every extra data model is another migration when you cancel. Every extra checkbox is another 15 seconds on a demo call when you are trying to teach a new hire the software.
The other pattern is bundling for enterprise buyers. Procore sells the same product to a 1000-person GC and a 8-person residential crew, and the price scales with headcount but the feature set does not scale down. The 8-person crew is paying for the 1000-person feature graph. That is the tax, and it is not a bug in the pricing model, it is the pricing model.
The industry counter is: "You just have not adopted the full platform." That is a way of blaming the customer for a shape mismatch. Nobody buys a truck to use 30 percent of it. They buy a truck the right size for the load. Software should work the same way.
How Workhand answers this
Workhand ships what small crews actually use. Estimates with e-sign and a bid manager. Invoices with Stripe payment and email delivery. Per-job team chat with photo attachments and one-tap Spanish translation. Time tracking. Mileage. Materials catalog. Daily logs. Punch list. Cost tracking with profit visibility. COI tracking with expiration alerts. QuickBooks sync. AI receipt scanner. Offline mode. That is the graph.
What is deliberately absent tells you as much as what is there. There is no AIA G702/G703 progress billing. No RFI tree. No submittal workflow. No public API. No GPS geofencing time clock. Not because those features are bad. Because a small residential crew does not use them, and I refuse to price them into a $34.99 per month plan.
The Team plan at $89 per month is flat for up to 15 users. That is $6 per user per month at full utilization. Compare that to a $499 Buildertrend bill split 5 ways ($100 per user, 70 percent of it bloatware). The math on the pricing page is what happens when a product is shaped for its actual buyer.
Related frameworks
- The 15-Person Ceiling: the shape mismatch that creates the bloatware tax in the first place.
- The Owner-Operator Discount: why a bootstrapped SaaS can afford to ship less software and price lower.
- The Contractor Onboarding Death Zone: bloatware is what makes onboarding a 21-day trip through screens the crew will never use.