Latest / Cash Flow Conversations with Fexingo: Working Capital, Receivables, and Small Business Finance / How Service Firms Protect Cash Flow With Milestone Billing
Transcript
- Lucas: Here is a number that keeps small service firms up at night: days sales outstanding. That is just a fancy way of saying how long it takes you to get paid after you send an invoice. For most consulting firms or creative agencies today in mid-September twenty twenty six, that number sits around forty five days. Some even hit sixty. And while that sounds like just accounting jargon, it is actually the single biggest threat to your ability to hire new people or take on bigger projects. Luna: Right. Because you are doing the work now, but you are funding the operation out of pocket until that check clears half a month later. It feels like a loan you did not ask for. Lucas: Exactly. And the traditional instinct is to blame the client. You think, oh, they are slow payers. But often the structure of the contract itself is inviting that delay. If you have a simple net thirty term on a three month project, you are essentially telling them they can hold your money for the entire duration of the engagement plus thirty days. That is a lot of trapped capital. Luna: So the solution is not to be nicer about chasing invoices, but to change the timing of when you ask for money in the first place? Lucas: Precisely. Today we are talking about milestone billing. It is not a new concept, but I am seeing a shift in how smart service providers are structuring it. They are moving away from lump sum final payments toward a series of smaller, triggered payments tied to specific deliverables or time periods. Let me give you a concrete example. There is a digital marketing agency called BrightPath Strategies based in Austin. Last year, they were struggling with cash flow despite growing revenue. Luna: I remember reading about BrightPath. They had some really strong case studies, but the owner mentioned constantly having to dip into personal savings to make payroll. Lucas: That was the problem. Their average client project lasted four months. They would do all the work, wait until the campaign launched, and then send one massive invoice. The client would sit on that invoice for another thirty days. So effectively, BrightPath was funding a ninety day cycle for every client. When they switched to milestone billing, they didn't change their prices. They just changed the rhythm. Luna: What did that rhythm look like? Did they just split the total by four? Lucas: They could have, but that is too simple. Instead, they structured it as twenty percent upfront upon signing, twenty percent at the midpoint review, and the remaining sixty percent in two equal installments tied to specific performance metrics or launch dates. This ensured that by the time they were halfway through the project, they had already collected forty percent of the total fee. That forty percent covers the overhead and labor costs incurred up to that point. Luna: So they are never more than a few weeks behind on covering their own expenses. That must feel completely different for the founder. Lucas: It changes the psychological dynamic entirely. When you collect upfront, you are not asking for a favor; you are fulfilling a standard business transaction. The client has already committed financially. By the time you reach the final invoice, it is a smaller number, which makes it easier for them to approve quickly. BrightPath saw their days sales outstanding drop from forty five days to twelve days within three months. That is a massive improvement in liquidity without raising a single dollar of external debt. Luna: But does that create friction with clients who are used to paying at the end? I imagine some procurement teams push back against upfront payments. Lucas: They do, especially larger enterprise clients. But here is the trick. You frame it as risk mitigation for both parties. If you say, 'I need fifty percent now,' the client hears, 'I don't trust you.' But if you say, 'Our standard process requires a kickoff payment to secure our resources and begin the audit phase,' it sounds professional. It signals that you are a serious operator with capacity constraints. Most reasonable buyers understand that services require advance allocation of staff time. Luna: I like that framing. It shifts the conversation from trust to resource planning. But what happens if the project stalls? If the client delays the midpoint review, does your billing stall too? Lucas: That is the critical part of the contract language. You cannot have vague triggers like 'upon completion of review.' You need objective, time-based or deliverable-based triggers. For BrightPath, they included a clause that states the second milestone is due either upon presentation of the interim report OR thirty days after the project start date, whichever comes first. This prevents a client from dragging their feet on feedback to delay payment. Time becomes the ultimate trigger. Luna: That is smart. It removes the ambiguity. So you are not waiting for them to decide when they are ready to pay; the calendar decides for you. Lucas: Exactly. And this also helps you identify trouble early. If a client is pushing back on the second milestone payment, you know there is dissatisfaction or budget issues before you have invested the last half of the project hours. It acts as an early warning system. If you only bill at the end, you might discover too late that the client is unhappy or broke. Luna: So it protects your cash flow, but it also protects your sanity by letting you kill bad projects earlier. That is a huge secondary benefit. Lucas: Absolutely. Now, let's talk about implementation. Not every service business fits the same milestone model. A law firm might use monthly retainers, which is a form of milestone billing. A construction consultant might use percentage of completion. The key is to align the billing events with moments of value delivery or cost incurrence. If you are selling a strategic advisory package, maybe you bill at the discovery phase, the strategy phase, and the implementation support phase. Luna: And you want those phases to be distinct enough that the client can clearly see what they are paying for. Otherwise, it feels arbitrary. Lucas: Right. Transparency builds trust. When you send an invoice labeled 'Phase Two: Strategy Development - Due Upon Approval,' the client knows exactly what work generated that charge. It is much harder for them to dispute or delay compared to a generic 'Project Balance' invoice sent months later. Specificity reduces administrative drag on both sides. Luna: Do you see any downsides to this approach? Is there a scenario where milestone billing hurts the relationship? Lucas: The only downside is if you over-complicate it. If you have ten tiny milestones for a small project, the administrative burden of tracking and invoicing each one outweighs the benefit. Keep it simple. Three to five milestones is usually the sweet spot. Also, ensure your team is disciplined. If you miss sending the milestone invoice on time, you lose the leverage. You have to be rigorous about triggering the billing event immediately when the condition is met. Luna: Got it. Discipline in execution is key. So, if these conversations have moved your work forward in some small way, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. It helps us keep digging into these practical financial details for you. Lucas: Thanks for keeping the show running. Back to the topic. One common mistake I see is founders trying to combine milestone billing with discount incentives. They might say, 'Pay fifty percent upfront and get ten percent off.' This can backfire. Luna: Why? Isn't encouraging early payment good? Lucas: It is, but mixing discounts with structural changes confuses the message. You want the client to adopt the milestone schedule because it is fair and operational, not because they got a deal. If you tie the payment structure to a price reduction, you signal that your standard rates are inflated or that you are desperate for cash. Just stick to the milestone structure. If they pay on time, reward them with excellent service, not a lower price. The value proposition is speed and reliability, not cheapness. Luna: That makes sense. You are selling predictability. Clients love knowing exactly when payments happen and how much they are. It helps them plan their own budgets. Lucas: Yes, and it positions you as a partner in their financial planning. When you help them manage their own cash flow by being predictable, you become harder to replace. A vendor who sends one confusing invoice at the end is easy to switch. A vendor who integrates smoothly into their quarterly planning is sticky. Luna: So it is not just about your working capital; it is about reducing churn risk by being easier to work with financially. Lucas: Exactly. Now, let's address the elephant in the room. What if a client refuses milestone billing and insists on net thirty end of project terms? This happens frequently with government contracts or very large corporations. Luna: Yeah, those procurement departments have standardized forms that are hard to modify. How do you handle that without losing the deal? Lucas: You negotiate the definition of 'completion.' If you must accept net thirty, try to define completion narrowly. For example, completion might be defined as 'delivery of final assets,' not 'client satisfaction' or 'project closure.' This allows you to issue the final invoice as soon as you hand over the files, rather than waiting for the client to run internal approval workflows that might take months. You control the trigger event. Luna: So you force the clock to start ticking as soon as you do your part, regardless of how slow they are to sign off. Lucas: Precisely. And in those cases, consider using factoring or a line of credit specifically for those large, delayed invoices. But that is a band-aid. The goal is always to structure the contract so you rarely need the band-aid. Milestone billing is the preventative measure. Luna: It sounds like the core lesson here is that cash flow is not an accounting problem; it is a design problem. You have to design the payment experience into the product. Lucas: That is the best way to put it. Most service owners design the service first and bolt on the billing at the end. Flip that. Design the payment rhythm alongside the service delivery. It transforms your finances from a reactive chase into a proactive engine. Luna: I think that is a powerful shift in mindset. If you treat every invoice as a milestone in the relationship rather than a cleanup task, everything changes. Lucas: Right. And it starts with looking at your current pipeline. Identify your top three active projects. Are you billing them on milestones or on hope? If it is hope, pick one and rewrite the agreement for the next phase. Start small, test the reaction, and adjust. You will likely find that most clients are perfectly fine with it once they understand the rationale. Luna: Agreed. It is worth the conversation. Better to have the awkward meeting about payment terms now than the stressful meeting about payroll in October. Lucas: Exactly. And by October, if you have implemented this, you will likely be in a stronger position to offer those clients better service because your own operations are stable. Healthy cash flow buys you options. It lets you say no to bad deals and yes to good ones without panic. Luna: So the question for listeners this week is not just how to get paid, but how to structure the engagement so that getting paid becomes the natural rhythm of the work. Lucas: Spot on. If you can make the money move as smoothly as the work itself, you remove a huge source of stress from your business. That is something you can carry into your next contract negotiation. Let us know how it goes.