Latest / Cash Flow Conversations with Fexingo: Working Capital, Receivables, and Small Business Finance / How A Roofing Firm Turned Payroll Into Working Capital
Transcript
- Lucas: There is a specific kind of panic that only construction owners know. It happens on the fourth Friday of the month when you have two hundred thousand dollars in work completed, but the checks are not coming until the thirtieth of next month, and your payroll processor is demanding cash today. Luna: Right, because the bank account sees the liability immediately, even if the revenue is stuck in legal limbo. It creates this weird disconnect where you are profitable on paper but technically broke. Lucas: Exactly. And most advice tells these business owners to cut costs or find cheaper materials. But I want to talk about a roofing company in Columbus, Ohio, that did the opposite. They kept their crew size stable, they kept their material quality high, and yet they managed to reduce their days sales outstanding by nearly forty percent in just eight months. Luna: Forty percent is massive. How did they do that without alienating their commercial clients who are used to net thirty terms? Lucas: They stopped billing based on calendar dates and started billing based on physical milestones. Instead of waiting for the whole roof to be finished, they tied invoice triggers to specific events: the day the old shingles were torn off, the day the underlayment went down, and the day the ridge caps were placed. Each event triggered a partial payment. Luna: So they are essentially monetizing the labor as it happens rather than waiting for the final punch list. That shifts the risk significantly away from the contractor. Lucas: It does, but here is the tricky part. The first time they tried this, the project manager sent an invoice for the tear-off phase, and the client’s accounts payable department pushed back hard. They said it violated the standard contract template they had on file with every vendor. Luna: Of course they did. Big corporate clients love predictability. They want one bill at the end. Asking for three separate payments adds administrative overhead for them. Lucas: The owner realized he was approaching this wrong. He was framing it as an internal convenience for his cash flow. So he changed the conversation entirely. He sat down with the property managers and explained that this structure actually protected budget by preventing change order surprises later. Luna: That is a brilliant pivot. You are selling certainty, not just speed. If the client pays for the tear-off, they know exactly what they paid for, and there is no ambiguity about whether the work was satisfactory. Lucas: Precisely. He framed the milestone invoice as a progress verification tool. The payment wasn't just money; it was the client signing off that the previous stage met quality standards. It turned an accounting request into a quality assurance checkpoint. Luna: I love that. It makes the client feel involved in the process rather than just being a wallet at the end. Did they face any resistance from their own crew initially? Lucas: Surprisingly, yes. The foremen were used to working through friction because they knew the check would come eventually. When you introduce milestone billing, the foreman has to document the completion of each phase rigorously. If they don't take photos and get the signature, the invoice doesn't go out. Luna: So it actually improved their operational discipline. They couldn't just rush through the underlayment because the money wasn't coming until the very end. Lucas: It forced documentation. And that documentation became their insurance policy. When a client tried to dispute a minor cosmetic issue months later, the contractor pulled up the signed milestone invoice from three weeks prior, which explicitly stated the work was complete and accepted. Luna: That is huge. Disputes usually happen at the end when emotions are high and memories are fuzzy. Having signed acceptance at each step locks in the agreement early. Lucas: It also freed up their cash to pay their suppliers faster. Because they were receiving payments every two weeks instead of once a month, they could negotiate ten percent discounts with their shingle supplier for early payment. Luna: Wait, so the margin improvement came from two places. First, better cash velocity reducing financing costs, and second, actual supplier discounts. That compounds quickly. Lucas: It does. On a five hundred thousand dollar annual contract, those discounts added another fifteen thousand dollars to the bottom line, completely separate from the interest savings. But we need to pause here for a moment because this kind of financial clarity is exactly why we do this show. Luna: We deliberately do not run ads on these episodes. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Lucas: It keeps us independent and allows us to dig into these operational details without worrying about sponsor requirements. Thank you for supporting the mission. Luna: Back to the math though, because I am curious about the timing. How long did it take for the new system to fully replace the old one across all their active jobs? Lucas: About six weeks. They ran both systems in parallel for one month to test the workflow. They found that the digital signature app they used reduced the time between job completion and invoice generation from four days to four hours. Luna: Four hours is instantaneous compared to mailing a PDF or waiting for a manager to review a batch of papers. That speed probably helped close the loop with the clients too. Lucas: It did. Accounts payable teams prefer digital invoices anyway. By sending them immediately after a milestone, they could process them during the same work week, avoiding the backlog that usually causes delays at the end of the month. Luna: So the technology enabled the process, but the process required the cultural shift in how they talked to clients. It sounds like a classic case of operations driving finance, not the other way around. Lucas: Exactly. Most businesses try to force finance onto operations. Here, the operational reality of how roofs are built dictated the financial structure. It felt natural to the workers because it matched the physical progression of the job. Luna: That is the key insight. If the billing cycle feels artificial to the person doing the work, they will resist it. If it mirrors the work itself, adoption becomes automatic. Lucas: Now, let me play devil's advocate for a second. Is this model scalable to smaller jobs? Say, a residential homeowner replacing a roof on a suburban house. Do you really need milestone billing for a twenty thousand dollar job? Luna: I think you do. Homeowners can be even more unpredictable with payments than commercial clients. They might delay because they are waiting on a home equity loan or simply forget. Milestones keep them engaged. Lucas: Agreed. For residential, you simplify it. Maybe just two milestones: deposit upon signing, and balance upon completion. But even that simple structure prevents the 'check is in the mail' excuse that drags out collections for weeks. Luna: It sets expectations upfront. You are telling them, 'Here is when the money is due,' rather than asking, 'Can you please send the money now?' The psychology is completely different. Lucas: It removes the awkwardness of chasing payment. The invoice isn't a favor; it's a scheduled event. And for the contractor, it means they never have to wonder if they can make payroll. The answer is always yes, because the money is already in the bank. Luna: That peace of mind is worth more than the percentage points saved on financing. It allows the owner to sleep at night instead of staring at the ceiling wondering about the float. Lucas: So if you are running a service business, look at your current billing cycle. Are you waiting for permission to be paid, or are you structuring your contracts to guarantee payment as value is delivered? Luna: It is a simple question, but it changes everything. Thanks for breaking this down, Lucas. Lucas: Thanks, Luna. Let me know if you decide to try milestone billing on your next project.