Should a small business buy industry software or have its own built?
Buy the industry package when your work looks like the rest of your trade’s. ServiceTitan, Jobber, Buildertrend and Procore do the common jobs well for a monthly fee. Have your own built for the part of the business that’s particular to you, which is usually the part still running on spreadsheets beside the package. Most companies end up with both.
When is the industry package the right call?
It’s the right call when the package already does most of what your company does all day. ServiceTitan and Jobber run a service company’s calls, dispatch board, invoices and payments. Buildertrend runs a home builder’s schedules, selections and client updates. Procore runs the drawings, RFIs and submittals on a commercial job. Other contractors have already paid for those features to be built and corrected, and you get the result for a monthly fee.
Buying also gets you things a small company shouldn’t build for itself. The vendor keeps it running, answers the support line and keeps up with the phones your crews carry. A new hire may have used it at their last job.
If you’re starting out, or you’re running on paper and a wall calendar, buy the package for your trade and use it the way it comes. The same goes if you already have one and your people use it. When an owner shows me a setup like that in the first hour, I’d tell them to keep it.
When does having our own built make sense?
It makes sense when the part of the business that sets you apart is the part the package doesn’t cover. Packages are designed around a typical company in the trade. How you price, how you pay your people, what you promise customers and which jobs you take are yours, and they rarely fit the vendor’s screens.
You can usually see it without opening the software. There’s a spreadsheet beside the package that someone updates every day. People type the same job into two places. You pay for add-ons nobody opens, and the report you want each Monday gets put together by hand. I cover those signs on the page about outgrowing spreadsheets.
Having your own built rarely means replacing the package. In most cases I’d keep it for what it does well and build the piece that’s yours next to it, with the two sharing data so nothing is entered twice. That keeps the custom part small, and a small piece of software is cheap to change when the business changes.
What does custom software cost now?
With me it costs $2,000 to $6,000 a month, depending on how much there is to do. It’s month to month, and you can stop at the end of any month. A year comes to $24,000 to $72,000.
The comparison most owners make is hiring a developer. The Bureau of Labor Statistics puts the average software developer’s pay in Dallas-Fort Worth at $138,810 a year as of May 2025. That’s the wage alone, before benefits.
For most of the 20 years I’ve built software, a system built around one company took a team to plan it, design it, write it and test it. I built a web agency that worked that way and sold it in 2024. A small business couldn’t pay for that. Now I use AI to write much of the code, so one engineer can do what used to take a small team.
Your company owns what gets built: the code, the hosting, the domain and every account. It starts with an hour at your office at no charge. You show me how the work gets done, and I say what I’d do next.
Can’t we build it ourselves with AI?
Yes, and plenty of owners have. The person who knows the business best can now sit down with an AI tool and have working screens quickly, built on the company’s own data and its own words for things.
The vendors have noticed. ServiceTitan publishes a guide for contractors on the hidden costs of AI-built software. ServiceTitan sells the alternative, so read it with that in mind. Its points about upkeep, security and who looks after the thing once it’s built are fair ones.
The trouble I see more often is that the tool works and the team doesn’t use it. I wrote about why on the page about software built with AI that the team won’t use.
Outside help seems to matter. MIT’s NANDA project studied AI projects at large companies and reported that “external partnerships see twice the success rate of internal builds.” Those were big companies. I think the reason carries over to small ones: someone has to work out who does what and when before anything gets built.
What does this look like for a home builder?
A builder in Aledo or Weatherford usually has Buildertrend for the schedule, selections and client updates, Excel for the estimate and job costing, and QuickBooks for the books. Buildertrend does its part well, and I’d keep it.
The trouble sits between them. A buyer upgrades the countertops and signs a change order. Someone has to update the estimate sheet, reissue the purchase order, tell the superintendent and bill the buyer. Each of those lives in a separate place, and the one that gets missed comes out of the margin. Job costing has the same gap: actual costs land in QuickBooks, the budget lives in Excel, and someone matches them by hand at the end of the job, when it’s too late to act on.
That’s the piece I’d build first. A change order gets entered once, and the estimate, the purchase order and the buyer’s bill all pick it up, with Buildertrend still running the schedule.
What does this look like in a field service company?
A plumbing, HVAC or electrical company around Weatherford usually has the package already. Jobber is built for smaller crews and ServiceTitan for larger shops, and either one handles the phone call, the dispatch board, the tech’s phone and the invoice. QuickBooks keeps the books. For that work, buying was the right decision and I wouldn’t replace it.
What sits outside the package is usually whatever the owner worked out for themselves. Often it’s how techs get paid, with commissions and bonuses figured in a spreadsheet from a report someone exports every pay period. It can be job costing on larger installs, where materials and labor from several visits have to be matched against the bid. Maintenance agreements and warranty callbacks are common ones too.
Those are the places I’d look. If the office manager works out commissions by hand every pay period, I’d build that one piece and have it read the finished jobs from the package. The techs keep the tool they know, and the office stops retyping.