1. Per-user pricing at $50 to $500 per user per month is the Bloatware Tax with a smile.
The enterprise pricing model treats every user like a seat in an office. But a construction crew is not an office. Your foreman needs an account to log time. Your bookkeeper needs an account to send invoices. Your subs need accounts so you can chat with them about the punch list. That is 8 to 12 accounts before you have added anyone doing revenue-generating work. Per-user pricing punishes you for having a working crew. You end up either paying $600 to $2,000 per month for a five-person shop, or you share logins, which is a security liability and a support nightmare.
Workhand's Team plan is $89 per month flat for up to 15 users. Not per-user. Total. The 15-user cap is the ceiling because that is the shape of a small-crew tool. Above 15 you have graduated to a different kind of business and probably need a different kind of tool. Read the deeper cut on The Bloatware Tax.
The consensus we reject: "Per-user pricing is fair because you pay for what you use." What you actually pay for is a sales team that needs to justify a $2 billion valuation, not the software.
2. Most crews under 15 people should NEVER pay for Buildertrend.
Buildertrend starts at $499 per month. For a five-person residential crew that is $100 per user per month, and roughly 70 percent of what you are paying for is features you will never open. AIA G702 and G703 progress billing. Gantt scheduling. Resource loading. Bid leveling. Submittal workflows. All of those are legitimate features for a 40-person GC running commercial jobs. They are also all things a Tampa pool builder or a residential remodeler will not touch once in a year.
The math on a small-crew Buildertrend bill is roughly $350 a month spent on screens nobody opens. That is $4,200 a year that could have hired a part-time bookkeeper for the season instead. Read the full teardown on The 15-Person Ceiling.
The consensus we reject: "You need enterprise-grade software to run a serious business." Serious does not mean big. A serious three-person crew needs a tool shaped for a three-person crew, not a stripped-down version of a Fortune 500 GC's tool.
3. GPS geofencing time tracking is spyware theater, not accountability.
Time-and-attendance apps that sell "GPS geofencing" as accountability are selling a management fantasy. The pitch is: your crew clocks in when they enter the jobsite radius. If they leave, the system knows. In practice, GPS on a job phone is inaccurate to 30 or 50 feet, drains the battery, gets denied at the OS level by half the crew on day two, and turns your relationship with the field into a monitoring relationship instead of a working one.
The actual accountability system in construction is the same as it has always been. You know if the crew was on-site because you can see the work. You know if the sub showed up because the demo pile is bigger. GPS does not add signal, it adds surveillance. It turns your best foreman into someone who feels watched, and it is the first reason a good crew looks for a different shop. Workhand ships time tracking without geofencing on purpose.
The consensus we reject: "GPS proves the crew was there." No. Work proves the crew was there. GPS proves the phone was there, and a lot of the time the phone was in the truck.
4. AIA G702 and G703 progress billing is enterprise cargo-culting for residential crews.
AIA G702 and G703 forms are the standard for commercial construction progress billing. They exist because on a $12 million school project with a 24-month timeline, you need a formal application-for-payment format that the architect, owner, and lender can all reconcile against a schedule of values. That is a real problem for a real customer.
It is not a problem a residential pool builder has. On a $70,000 pool build with a 10-week timeline, the customer pays a deposit, a gunite progress draw, an equipment set draw, and a final. Four invoices, plain English, plain math. Software that forces you into an AIA workflow to bill a homeowner is imported complexity from a different industry, and it slows down the closing. The industry ships AIA billing on residential-tier plans to look feature-rich, then charges you for it every month.
The consensus we reject: "AIA billing is the professional standard." It is the professional standard for commercial projects. On residential, it is friction.
5. English-only construction PM software fails in Florida, Texas, California, Nevada, and Arizona.
34 percent of US construction workers are Hispanic per the Bureau of Labor Statistics. In Sun Belt states with strong residential and pool construction industries, that number climbs closer to 50 percent, and on specific trades it is often the majority. Any construction PM tool that ships an English-only field experience is telling half its buyer's crew that they are not the customer.
Vendors respond with "we have Spanish support" and mean they translated the marketing site. Or they added Spanish to the chat and left invoices, estimates, daily logs, punch items, and settings in English. Neither is enough. If the field crew cannot self-serve the whole app in Spanish, you still need someone in the office translating on demand, and the productivity multiplier does not kick in. Workhand ships a full app UI translation in English, Spanish, and Portuguese, plus per-message chat translation. Read The Spanish-Speaking Field Multiplier.
The consensus we reject: "Spanish is a nice-to-have localization." No. In Sun Belt residential construction, Spanish is a first-class product surface, not a checkbox.
6. Manual COI tracking spreadsheets are a lawsuit waiting to happen.
A three-column spreadsheet with sub names, policy expiration dates, and a color-coded status is not a tracking system. It is a record-keeping system with no signal. The office manager has to remember to look at it, has to remember to filter by upcoming expirations, has to remember to call the sub, has to remember to update the row when the new cert lands. Anyone who has run an office knows what happens to that four-step chain on a busy Wednesday. It breaks.
Standard-form general liability policies exclude coverage for uninsured subs. If a sub works your job with a lapsed policy and there is an incident, the carrier reclassifies that labor as direct payroll at your next audit and your premium can jump 20 to 30 percent. On $200k of subcontracted labor, that is a five-figure hit that lands months after the miss. Push and email alerts at 30, 14, and 7 days out are not a nice-to-have, they are premium protection. Read The COI Expiration Cliff.
The consensus we reject: "We check COIs once a year at renewal, that is enough." It is not. Policies get cancelled mid-term for non-payment. Once a year is once a year late.
7. Public API access matters less than a well-designed inbox.
Every enterprise PM tool advertises a public API as a premium feature. On a demo call the salesperson will spend ten minutes on the Zapier integrations and the webhook framework. For 95 percent of small-crew contractors, that section of the demo is theater. Nobody with a five-person crew is writing Zapier automations at 9 PM on a Sunday.
What actually moves the needle is the shape of the daily work. Can you send an estimate and get an e-signature without a laptop? Can the field crew log a punch item with a photo in three taps? Does the invoice email arrive with a payment button that actually works on the customer's phone? Those are the questions that decide whether the tool gets used past week two. A public API is a feature for a customer who can afford an integrations engineer. If you can afford one of those, you can also afford Procore.
The consensus we reject: "A modern SaaS needs an open API." A modern SaaS for small crews needs an inbox that works on a phone in a work glove.
8. Owner-built SaaS should undercut VC-funded competitors by design, not by accident.
Buildertrend has raised roughly $220 million. Procore raised more than $500 million before going public. That capital gets serviced through per-user pricing that mostly funds a sales team and marketing team. A bootstrapped SaaS with one owner does not have that overhead. The savings are structural, not discretionary. It is not that a bootstrapped tool "should be" cheaper as a marketing angle. It is that a bootstrapped tool cannot be as expensive without pocketing money it did not earn.
Workhand is one person plus AI tooling under Innovative Ops LLC. The cost stack is hosting, Stripe, a small AI budget, and my time. That is why the Team plan is $89 flat for 15 users instead of $499 for the same shape from a competitor. Read The Owner-Operator Discount.
The consensus we reject: "You get what you pay for." What you actually pay for on enterprise SaaS is the distribution machine that closed you, not the software.
9. Free trials should not require credit card entry for a $89 per month product.
Requiring a credit card to start a free trial is a sales tactic. It works because a percentage of trials convert to paid via forget-to-cancel, not via delight. On a $500 per month enterprise product with a six-week sales cycle, maybe the tactic makes sense. On a $89 per month small-crew product, requiring a card upfront is an admission that the tool is not confident enough to earn the paid conversion on its own merit.
Workhand's Free plan is genuinely free, forever, on one job with one teammate. No card required. If it fits your work, upgrade. If it does not, keep the free account and use it as your COI tracker or your estimate builder. That is not a growth hack, that is what "free plan" is supposed to mean.
The consensus we reject: "Card upfront filters serious prospects." What it actually filters is trust. Serious prospects notice the ask.
10. The best construction PM software is built by an operator, not for a Fortune 500 GC.
The dominant construction PM tools were designed by product teams staffed with people who have never framed a wall, poured a slab, or set a piece of gunite equipment. That shows up in the shape of the tool. Every screen assumes a desk. Every workflow assumes an office manager. Every default assumes a Fortune 500 change-order approval chain. Meanwhile the actual buyer is standing in a Florida pool cage at 2 PM in July trying to get the plumbing sub back on Thursday.
Workhand was built by a working project manager for a working project manager. Every design decision anchors to: what does this look like on a phone in a work glove at 2 PM in July. If the answer is "extra tap" or "menu buried" or "requires signal," it does not ship. That is not a marketing story. That is a design constraint. It is also why the tool is shaped the way it is, and why the price is where it is. Read the founder story for the full background.
The consensus we reject: "You need a big team of product managers to build serious software." Sometimes. But for a small-crew construction tool, you need one operator who has done the work, and enough discipline to keep the feature graph small.
Closing note
Every position on this page is something a Buildertrend, JobTread, Procore, or Housecall Pro salesperson would push back on. That is fine. If the industry told me all ten of these were correct, I would suspect I was wrong about something.
The point of naming them is not to win an argument. It is to give you a clear picture of what Workhand is and what it is not. If you run a crew of 15 or fewer and the ten positions here read like common sense, we probably built a tool for you. If they read like heresy, we probably did not, and Buildertrend is a good tool that will fit your shape better.
The seven frameworks that underpin these positions live at workhand.app/frameworks. The tool itself lives on the App Store and Google Play. The founder is at [email protected].