The Proposal You Sent Last Tuesday: Do You Know Where It Is Right Now?

Fatima sent the proposal on a Tuesday afternoon. Forty-five minutes of work, a well-structured PDF, a competitive price. She hit send, made a note in her head to follow up on Friday, and moved on to the job she was already behind on.

Friday came. She forgot.

The following Wednesday, the client emailed to say they'd gone with someone else. Not because the price was wrong. Not because the scope was off. Because the other firm called on Thursday to ask if they had any questions.

Fatima runs a mid-sized consulting firm in Brisbane. She's good at her work. Her proposals are thorough. Her pricing is fair. But somewhere between the moment a lead comes in and the moment a project gets delivered, things fall through gaps she can barely see.

This is not a story about one lost job. It's a story about a system problem that plays out in thousands of businesses every week.

The Lifecycle Nobody Tracks End-to-End

When you break down how a piece of work actually moves through a business, there are roughly six stages:

• A lead comes in (referral, inbound, outreach)
• You scope the work and send a proposal or quote
• The client accepts (or doesn't, or goes quiet)
• The project gets kicked off and delivered
• You invoice for the work
• The client pays

Simple on paper. But in most businesses, each of those stages lives in a different place. The lead is in your inbox, or maybe a CRM if you're organised. The proposal is a PDF in a folder somewhere. Acceptance is an email reply you may or may not have filed. The project is in a project management tool. The invoice is in Xero. Payment is tracked in your bank feed.

Nobody has a complete view. And in the gaps between those systems, money disappears.

What Leakage Actually Looks Like

Leakage is a bland word for something that genuinely hurts. Here's what it looks like in practice.

The follow-up that never happened. A 2024 study by the Sales Management Association found that 44% of salespeople give up after one follow-up attempt, while 80% of deals require at least five touchpoints. Most small business owners aren't salespeople, they're tradespeople, consultants, designers, engineers. Following up feels awkward. Without a system that flags outstanding proposals, it just doesn't happen.

The accepted quote that never became a project. The client said yes. You said great. Then nothing was formally kicked off. Three weeks later, the client is frustrated because nothing has started. You're confused because you thought they were getting back to you with a start date. This happens when proposal acceptance lives in email and project creation lives somewhere else entirely.

The scope that drifted and nobody noticed. The original quote was for twelve hours. The project ran to nineteen. Because the quote and the project tracker were never connected, nobody flagged the blowout in real time. The invoice went out for twelve hours anyway, because that's what the quote said.

The invoice that went out late. The project finished. The team moved on. Two weeks passed before someone remembered to raise the invoice. In service businesses, late invoicing is one of the most common and most preventable causes of cash flow problems. A 2023 Xero Small Business Insights report found that Australian small businesses wait an average of 23 days beyond payment terms to receive payment. If you're also invoicing late, that gap compounds fast.

The payment that was never chased. The invoice went out. It wasn't paid. Nobody noticed for six weeks because the person who delivered the project isn't the person who monitors accounts receivable, and the person who monitors accounts receivable doesn't know which invoices are for completed work versus work still in progress.

Each of these is a separate failure. But they all share a common root: the stages of the business cycle are disconnected from each other.

Why Disconnected Tools Make This Worse

Most businesses try to solve this with a collection of tools. A CRM for leads. A document tool for proposals. A project management platform for delivery. An accounting package for invoicing. A spreadsheet somewhere in the middle to tie it all together.

The problem isn't any individual tool. The problem is that they don't share data.

When your CRM doesn't know the proposal was accepted, you can't automatically trigger a project. When your project tool doesn't know the original quote amount, you can't flag scope creep in real time. When your invoicing system doesn't know the project is finished, nothing prompts you to raise the invoice. When your CRM doesn't know the invoice is outstanding, nobody follows up.

You end up doing the connective work manually. Copying data from one system to another. Checking multiple dashboards to get a picture that should be automatic. Relying on memory and sticky notes to bridge gaps that software should close.

This is exactly how admin time balloons. What should be a 20% slice of your working week creeps to 35%, then 45%. The time you should be spending on craft, on delivering excellent work, and on business development, on finding the next client, gets eaten by coordination overhead. It's the kind of slow drain that doesn't feel catastrophic on any given Tuesday, but compounds into a real problem over months.

What a Closed Loop Actually Looks Like

Closing the loop means every stage of the quote-to-cash cycle is visible in one place, and each stage flows naturally into the next without manual intervention.

Here's what that looks like in practice.

Lead comes in. It's logged in your CRM automatically, or with a single entry. No separate spreadsheet. The lead is associated with a contact record that carries the full history of that relationship.

Proposal is created and sent. The proposal pulls from the client record. It's tracked: sent on this date, viewed on this date (if you have read receipts), follow-up scheduled automatically for three days out. You don't have to remember. The system does.

Client accepts. One action converts the proposal to a project. The quoted scope becomes the project brief. The quoted value becomes the project budget. The client record updates. Nothing is re-entered.

Project is delivered. Time is tracked against the project. Costs are recorded. If hours exceed the quoted amount, you see it in real time, not after the fact. You can have a conversation with the client before it becomes a problem, not after you've already absorbed the loss.

Invoice is raised. When the project hits completion, the invoice is generated from the project data. The quoted amount, the actual hours, the agreed payment terms. No manual data entry. No risk of invoicing for the wrong amount because you're working from a PDF that's three weeks old.

Payment is received and reconciled. Payment hits the bank. It reconciles against the invoice. The project is marked complete. The client record reflects the full history: lead source, proposal date, project duration, invoice amount, payment date.

At any point in this cycle, you can look at one screen and know exactly where every piece of work stands. Which proposals are outstanding. Which projects are running over budget. Which invoices haven't been paid. Which clients haven't heard from you in ninety days.

This is not a fantasy. It's what a single-database system makes possible.

The Single Database Difference

There's an important distinction between tools that are integrated and tools that are unified.

Integrated tools talk to each other. When you accept a proposal in your CRM, a Zapier automation fires and creates a project in your project management tool. Usually. Unless the automation breaks. Unless the field mapping is wrong. Unless someone changed a dropdown value and forgot to update the zap.

Unified tools share one database. There's no sync to fail because there's no sync. The proposal and the project and the invoice and the client record are all the same data, viewed through different lenses. Change the client's billing address once and it updates on every open invoice, every project, every contact record, because there was only ever one record.

This matters for the quote-to-cash cycle specifically because the data that lives in your proposal (scope, price, timeline, client details) needs to be exactly the same data that lives in your project, your timesheet, and your invoice. Every time that data is copied from one system to another, there's a chance for error, a chance for delay, and a chance for the whole thing to quietly fall apart.

For Any Business That Sends Proposals

This isn't a problem that belongs to one industry. Consultants lose it when proposals go quiet and nobody follows up. Agencies lose it when accepted briefs don't convert cleanly into scoped projects. Trades businesses lose it when variations aren't documented and invoiced. Designers lose it when projects run long and the original quote is the only number anyone remembers. Health practitioners lose it when treatment plans aren't connected to billing. Event managers lose it when the approved proposal and the actual delivery drift apart without anyone tracking the difference.

The quote-to-cash cycle is universal. And the leakage points are remarkably consistent across industries: poor follow-up on outstanding proposals, weak handoffs from sales to delivery, no real-time visibility on budget versus actuals, and invoicing that happens too late or for the wrong amount.

The businesses that close the loop aren't necessarily better at their craft. They're better at seeing the whole picture.

Starting Points If You're Not There Yet

If your current process involves a combination of email, PDF proposals, a project tool, and Xero with some spreadsheets bridging the gaps, you're not unusual. Most businesses are built this way. It works until it doesn't.

The first step is usually just mapping what you have. Draw the six stages from lead to payment. Write down where each stage currently lives. Then mark every point where data has to be manually re-entered or where a human has to remember to do something. Those are your leakage points.

For some businesses, fixing two or three of those points with better process is enough. For others, especially those sending more than ten proposals a month or running multiple projects simultaneously, the overhead of managing disconnected systems becomes its own full-time job.

The businesses that have moved to a unified system consistently report the same things: fewer dropped proposals, faster project kickoffs, better real-time visibility on project profitability, and shorter payment cycles because invoices go out on time and follow-ups are automatic rather than optional.

None of that requires a big technology transformation. It requires a system where the data you enter once follows the work all the way through.

Fatima eventually found that system. She still sends proposals on Tuesday afternoons. But now, Friday's follow-up is already scheduled before she closes her laptop. And when a client says yes, the project is live before she's finished reading the email.

The work didn't change. The visibility did.

If you want to see how Opus handles the full quote-to-cash cycle, the [features page](https://opus.net.au) walks through each stage, or you can start with the free tier and map your own workflow against it.