At 20 employees, you know where every dollar goes. At 50, you’re finding out where they went. Growth is supposed to improve margins.
But for a lot of roofing CFOs, it does the opposite. More crews mean more tools, more subscriptions, more integration headaches, and more places for money to leak before anyone notices.
Eric Weddle, CFO of Weddle & Sons Inc, has scaled through that stretch. Here’s what he’s learned about making software decisions that protect your margins instead of eating them.
1. Treat User Adoption Like a Financial Metric
When evaluating different software, it’s easy to get caught up in features and pricing. But for Eric, his first question is: Will my team actually use this? If this isn’t a leading thought, you often end up paying twice: once for the subscription, and again for productivity losses.
A guiding idea around adoption, Eric emphasized, was that revenue is generated in the field—by salespeople at kitchen tables and crews on roofs—not by him and his team in the office. So these teams’ opinions and experiences with software take precedence when choosing tools. If a tool doesn’t improve their job functions, they won’t force adoption.
When looking at a new software, Weddle & Sons follows a simple process:
Eric demos the app first to see how intuitive it is. If he’s feeling friction with it, there’s a good chance others on the team will too.
He runs a test with a few key people (branch, site, and sales managers) to simulate how it could work and to surface any issues that a demo might miss.
Once it’s ready to roll out company-wide, Eric gives teams some time to transition their workflows to the new app. But a firm cutover date for the new tool is key, though. Running two systems in parallel kills adoption and ruins the employee experience.
2. Know Your Nice-To- and Must-Haves
Every software change involves giving up some workflow or design that everyone’s grown accustomed to. Eric shared how teams can “fall in love” with certain features of their current tools, making change difficult. But the key is determining whether what you’re gaining significantly outweighs what you’re losing.
Two years ago, Weddle & Sons decided to change their CRM. They built their old process on highly customized (and high-maintenance) automations that linked their CRM to Box, QuickBooks, and other apps. But as they continued to scale, maintaining the stack became a part-time job for Eric.
After evaluating the options, they chose Acculynx. There were a handful of trade-offs and workflows that some branches missed, such as a standalone scheduling and dispatching tool. But what they gained would set them up for continued, scalable growth:
A direct supplier-pricing integration that would essentially eliminate the 4- or 5‑figure job-costing errors that keep CFOs up at night.
Reduced administrative burden. Fewer apps and manual automations mean that Eric and his team can focus on higher-value work.
Cost savings through consolidation. With a more robust CRM, one-off, redundant tools for cloud storage and signatures were removed from the books.
But Eric cautions against cutting too quickly based solely on paper comparisons. Cutting a seemingly redundant tool with strong field adoption can create more friction than the line-items savings are worth. For them, this outlier was their field documentation tool.
3. Review Annually, but Stay Current
At the end of the year, when project volume slows, you should audit your tech stack the same way you do your financials.
Eric’s annual review covers four areas:
Scalability. What’s working now that won’t hold up at next year’s projected headcount or revenue?
Performance. What failed to deliver and needs to be replaced or renegotiated?
Cost. What pricing changes or contract negotiations are on the table?
Consolidation. Where are you paying for overlapping functionality?
But in roofing, waiting until year-end to fix a broken process means losing margin for months. Eric suggests that business leaders should stay product-aware by taking calls from vendors and experimenting with AI tools so they know what’s available and can fix their problems sooner rather than later.
Using AI to Simplify Process
One task Eric oversees that he needed a solution for is managing subcontractor certificates of insurance. Each sub has their own agreements, expiration dates, and insurance information, and keeping this all straight is a chore — but one that needs to be done for business and insurance audit reasons.
Eric is currently testing Claude Code to build a secure web interface for subs to submit their documents directly. Once uploaded, his system parses the documents, extracts the key data, and has everything audit-ready without manual entry.
Eric and his team’s approach to AI in their tech stack follows this pattern: It’s not a forced addition, but a targeted solution to specific, recurring administrative drains on their time and focus.
Software decisions in roofing aren’t just operational — they’re financial. The wrong tools create hidden costs: estimating errors, low adoption, integration maintenance, and subscription bloat. The right tools reduce cost per job, protect margins, and scale with your business.
Want more practical tips like these from industry leaders? We run a free webinar every month with operators who’ve scaled through the same problems you’re solving.
