From Quote to Cash: Why Most Proposals Disappear Into a Black Hole (And How to Stop It)

The Proposal That Got Lost Between Three Apps

Leila had sent the proposal on a Tuesday afternoon. She remembered it clearly — a $14,000 branding project for a Sydney-based logistics company, six weeks of work, good margin. She'd spent two hours putting it together in her proposal tool, exported it as a PDF, emailed it across, then logged it in her CRM as "sent."

Three weeks later, the client called to say they were ready to proceed.

Leila had no idea what they'd agreed to.

The proposal was in her email. The pricing breakdown was in a spreadsheet on her desktop. The scope notes were in a Google Doc she'd shared with her business partner. The follow-up she'd promised to send — the one with the revised timeline — was still sitting in her drafts folder, unsent.

She spent forty minutes reconstructing the deal before she could even reply to the client. Then another hour updating her project management tool with the scope. Then another twenty minutes creating an invoice in Xero, manually re-entering the line items she'd already typed twice.

The project was profitable on paper. In practice, she'd already burned three hours of her own time before a single deliverable was touched.

This is not a story about disorganisation. Leila is sharp, experienced, and runs a successful agency. This is a story about what happens when the stages of a business deal live in different tools.

The Stages Nobody Connects

For most businesses that send proposals regularly — agencies, consultants, trades, IT providers, accountants, designers, coaches — the commercial lifecycle of a client engagement looks something like this:

• Lead comes in
• Qualification conversation happens
• Proposal or quote is prepared
• Proposal is sent
• Follow-up happens (sometimes)
• Client accepts (or doesn't)
• Project kicks off
• Work is tracked and delivered
• Invoice is raised
• Payment is received

Ten stages. In most businesses, those ten stages span at least four or five different tools. The CRM handles stages one through four. A project management tool takes over at seven. Invoicing happens in the accounting software. Follow-up lives in email. Time tracking is somewhere else entirely.

The gaps between those tools are where money goes missing.

Not dramatically — not in the way a lost client or a bad debt goes missing. Quietly. In unbilled hours that didn't make it onto the invoice. In scope that expanded but was never formalised. In proposals that were accepted verbally but never converted into a signed document anyone could find. In invoices raised six weeks after project completion because nobody flagged that the work was done.

A 2023 study by Xero found that Australian small businesses wait an average of 23 days beyond their payment terms to receive payment. But the more interesting number is how much of that delay originates before the invoice is even sent — in the administrative fog between "project done" and "invoice raised."

What Leakage Actually Looks Like

Let's be specific, because "leakage" is one of those words that sounds abstract until you put a number on it.

If you send ten proposals a month at an average value of $8,000, that's $80,000 in potential monthly revenue flowing through your pipeline. Here's where it typically leaks:

Proposals that go cold without follow-up. Research consistently shows that a second or third touchpoint significantly increases conversion rates on proposals, yet most business owners admit they follow up inconsistently. If you're losing even one $8,000 proposal per month to this, that's $96,000 a year in revenue that walked out the door because nobody sent a second email.

Scope creep that never gets invoiced. The original quote was for X. The client asked for Y and Z along the way. Those additions were handled, because that's what good operators do. But they weren't documented against the original proposal, so they didn't make it onto the invoice. This is almost universal in service businesses, and the average unbilled scope in a typical agency or consulting firm is estimated to run between 8% and 15% of project revenue.

Delays between project completion and invoicing. When your project management tool and your accounting software don't talk to each other, someone has to manually trigger the invoice. That someone is usually the business owner, who is also doing the work, also chasing new clients, and who will get to it when they get to it. Two weeks of delay on a $14,000 invoice, across twelve projects a year, is a meaningful cash flow problem.

Accepted proposals that never formally convert. A client says "yes" in an email. You start the work. Six months later, there's a dispute about what was agreed. The proposal is in your email. Their version is in their email. Nobody signed anything, and the two documents have diverged because you sent a revised version and forgot to update your records.

None of these are catastrophic in isolation. Together, they're the slow drain that keeps a profitable business perpetually cash-poor.

Why Disconnected Tools Make This Worse

The instinct, when you identify a gap like this, is to add another tool. A better proposal tool. A CRM with follow-up reminders. A project management system with invoicing triggers.

But adding tools to a disconnected stack doesn't close the gaps — it adds more of them.

Every integration between two separate systems is a potential point of failure. Data that exists in your CRM as a "deal" has to be manually recreated in your project tool as a "project." The line items in your proposal tool have to be re-entered in your accounting software as invoice lines. The hours tracked in your time-tracking app have to be exported and matched against the project budget someone built in a spreadsheet.

The information exists. It just exists in five places, in five slightly different formats, with five different owners.

This is where the administrative burden compounds. The Business Triangle — the rough framework of how business owners divide their time between craft, business development, and administration — assumes that admin stays around 20% of your working week. When your tools don't connect, admin expands to fill the space. You spend time reconciling data instead of doing work. You spend time chasing your own records instead of chasing new clients. The drift from 20% admin to 40% admin to 60% admin is rarely caused by one big problem. It's caused by dozens of small friction points, each one taking fifteen minutes, adding up across a month.

Closing the Loop: What the Full Lifecycle Should Look Like

The alternative to a disconnected stack isn't a more complicated stack. It's a system where the stages of a deal are connected by design — not by integration, but by shared data.

Here's what that looks like in practice.

A lead comes in. You log it once. That single record carries forward through every stage: the qualification notes, the proposal details, the accepted scope, the project tasks, the time tracked, the invoice raised, the payment received. You never re-enter the client's name. You never copy line items from one document to another. When the project is marked complete, the system knows what was quoted and what was delivered — and can prompt you to invoice accordingly.

This is the architecture Opus is built around. One database. One record per client, per project, per engagement. The proposal you send is connected to the project that gets created when it's accepted. The hours your team logs flow directly into the cost side of the project's P&L. When it's time to invoice, the line items are already there — you're confirming, not recreating.

Follow-up doesn't fall through the cracks because it's attached to the proposal record, not floating in someone's email inbox. Scope changes get logged against the original agreement, so when the invoice goes out, you can see exactly what was quoted, what was added, and what needs to be billed.

The Follow-Up Problem, Specifically

One thing worth dwelling on: the gap between "proposal sent" and "proposal accepted" is where most businesses are weakest.

The proposal goes out on a Tuesday. The client is busy. They mean to reply. They don't. The business owner is also busy — doing the work, running the business, handling everything else. A week passes. The proposal is still sitting in the CRM as "sent," but nobody has looked at it since.

A well-structured system puts a follow-up task on the proposal automatically. Not a generic reminder, but a specific one: "It's been five days since Leila sent the branding proposal to Pacific Freight Solutions. No response recorded. Follow up?"

That's the difference between a 30% proposal conversion rate and a 45% one. Not a better proposal template. Not a more persuasive pitch. Just a reliable system that ensures every proposal gets a second look from a human being before it goes cold.

What This Means for Cash Flow

For businesses that invoice on completion — which is most service businesses — the speed of the quote-to-cash cycle is a direct driver of cash flow health.

A proposal that takes two weeks to follow up on, then another week to convert, then another three weeks to kick off, then another four weeks to deliver, then another two weeks to invoice, then another three weeks to get paid — that's a 15-week cycle on work that could have been a 10-week cycle with tighter process.

Five weeks of additional float, across a pipeline of twelve active projects, is a significant working capital difference. For a business doing $1.5 million a year, compressing that cycle by even 20% can mean the difference between drawing a salary comfortably and watching the bank account nervously every fortnight.

This isn't about chasing clients or being aggressive with payment terms. It's about not being the source of the delay yourself.

A Note on Scope: It's Not Just Service Businesses

It's worth being clear that the quote-to-cash problem isn't unique to agencies or consultants. Any business that sends proposals or quotes before work begins faces the same structural challenge.

A landscaping company quoting a $45,000 garden redesign. A catering business pricing a corporate event. An IT provider scoping a network upgrade. A physio clinic quoting a rehabilitation program. A training provider pricing a custom course for a corporate client.

The tools differ. The industry language differs. But the gap between "quote sent" and "invoice paid" — and the leakage that happens in that gap — is consistent across every sector.

The businesses that close that gap most effectively aren't necessarily the ones with the most sophisticated sales process. They're the ones with the most connected operational system. When the quote, the project, the delivery, and the invoice are all part of one continuous record, the gaps don't have room to form.

The Practical Starting Point

If you're reading this and recognising your own business in the Leila scenario — the reconstructed proposals, the manually re-entered line items, the invoices that go out late because nobody triggered them — the starting point isn't a wholesale systems overhaul.

It's asking one question: at which stage does information stop flowing automatically and start requiring manual transfer?

For most businesses, the answer is somewhere between "proposal accepted" and "project created." That's the first gap to close. Once the acceptance of a proposal automatically creates a project with the right scope, budget, and client details, everything downstream gets easier.

From there: connect your time tracking to your project costs. Connect your project completion to your invoicing trigger. Connect your invoicing to your payment reconciliation.

Each connection you make is administrative time you get back. Time that goes back into the work, or into finding the next client, or into running the business the way you intended to when you started it.

Opus is built to hold all of that in one place — the CRM, the proposal pipeline, the project management, the time tracking, the financial reporting, and the Xero integration that keeps your accounts clean. If you're curious about how it fits together, the [features page](https://opus.net.au) is a good place to start, or you can try it on a small project with the free tier and see how the data flows before committing to anything.