Why "The Software Can't Track That" Is Finally Going Away Words: Erin KoetsPhotos: CrewTracksFor as long as specialty contractors have used field software, most of them have kept a workaround somewhere: a spreadsheet on a foreman's laptop, a whiteboard in the trailer, or a text thread where crew leads send block counts at the end of the day because the app everyone paid for was never built to hold that number.That gap has always come down to the same thing. Building software that fits how a masonry company actually runs (tracking production by unit, by course, by crew, by job) costs real money to design and maintain. For a platform built to serve every trade, that investment rarely made sense unless you were one of the biggest customers. So specialty contractors got the standard dashboard, learned to work around it, and kept the spreadsheet.That is starting to change, and the reason is simpler than most people expect.AI Is Not The Point, Lower Costs AreMost contractors have heard enough about artificial intelligence to be skeptical, and that skepticism is fair. The industry has watched plenty of technology promises land flat or add more steps instead of fewer.Here is a more useful way to think about what is actually happening. AI did not create a new capability that mason contractors have been waiting for. What it did was bring down the cost of building trade-specific tools. The foundational engineering work (designing the system architecture, building the infrastructure, and testing how everything connects) used to take months. That timeline is shorter now. It is short enough that building a custom module for one company's workflow actually makes financial sense to do, not just as a favor for a large account but as something we can offer more broadly.That shift matters because "we need it to track one more thing" used to be a request that quietly went nowhere. Now it is one that can be answered.Building Tools That Fit How You WorkCrewTracks is built for subcontractors, and even within that group, no two operations run exactly the same. A masonry company tracking production by the unit has different needs than a concrete contractor managing material deliveries across six sites. Trying to squeeze everyone onto the same dashboard has never worked well, so we are building a modular system. There are standard modules any customer can add, and custom modules built around what a specific company actually needs.On the standard side, we have an attendance module and a PTO module in development. These cover the basics every subcontractor deals with regardless of trade: who showed up, who is out, and how that connects to payroll. For a masonry company running multiple crews across several jobs at once, having that information in the same place as time and production cuts down on a lot of back-and-forth.The custom side is where it gets more interesting. What we have found is that the value is not just in having a new report to look at. It starts earlier, at the point where data actually gets captured. A lot of the numbers that matter most to mason contractors never make it into software at all. Block counts, units laid by crew, production by day and by job. Those numbers live on whiteboards or in texts or in someone's memory because there was never a practical place to put them.A custom module fixes that. Outside of our native production tracking, a crew lead can log brick or block counts in the field, tied to the job, at the end of the shift. Once that number is in the system, it connects with everything CrewTracks is already tracking: hours worked, crew assignments, and job codes. You can start seeing units laid per man-hour, production trends across a project, and comparisons between crews over time. Those are not numbers you can pull out of a generic time tracking app. They come from capturing the right data in the first place.We already have a material tracking module and a trucking and ticket module in use, both built because specific companies asked for them. Our developer put it this way:"We have a material tracking solution and a trucking and ticket module, but have others in the works. The biggest piece of this has been putting all of the infrastructure in place. So now we're poised to start producing them."That infrastructure work is done, which means the next module builds faster than the first one did.What This Means For Your OperationIf your company has a reporting need you have been working around, it is worth a conversation about whether a custom module could cover it. The data that matters most to how you bid, run, and bill jobs does not have to live outside your software.If you are comparing field management platforms, it is also worth asking whether the system you are looking at can grow with you. A platform that can add purpose-built tools around your existing workflow is a different investment than one you will outgrow and have to replace a few years down the road.We built the module system because contractors kept telling us what was missing. That is still how it works.About: Build Smart
