Put the system to work in thirty days

The practices in this book are useful only if they survive ordinary working conditions. A business needs records people can find, definitions they understand and reviews that lead to decisions. It does not need an elaborate system before the next enquiry can be handled better.

Thirty days is a suggested implementation window, not a promise that demand, cash flow or customer relationships will be transformed within a month. Adapt the pace to the work. Some opportunities take much longer to reach a decision, and evidence about repeat business may take a year or more to develop.

Start with a small set of connected records

Use the tools the team already understands if they can meet the practical requirements. The essential connection is between the customer decision and the work required to fulfil it.

These can be sections of a small shared system rather than five separate applications. Avoid copying the same information into several places unless there is a clear reason. Link to the accepted offer instead of retyping its terms into a spreadsheet where they may diverge.

Week one: establish the baseline

Choose a manageable set of current opportunities and one recently completed engagement. Do not begin by importing every historical contact. Define what makes work suitable, what requires investigation and what the business will decline.

For each current opportunity, record the last confirmed customer action and the next decision. Mark unknowns honestly. Check whether anyone has promised a date, output or price that is missing from the written record. Resolve the most consequential gaps first.

Then examine the completed engagement. Compare estimated effort with actual effort, identify unplanned work and check the timing of receipts. If time records are incomplete, use a clearly labelled estimate rather than inventing precision. The aim is to identify a useful question for the next job, such as whether review coordination is consistently underestimated.

By the end of the week, the team should share a definition of a viable opportunity and know which active promises need attention. A visually tidy contact list is secondary.

Week two: test one offer and one route

Select an offer with enough evidence to investigate further. Write the customer problem, alternative explanations, proposed output and remaining assumptions. Use a customer conversation or bounded pilot to test the weakest important assumption.

At the same time, run one manageable channel experiment from Chapter 3. Set a time and spending limit and record suitable conversations rather than only reach. Keep delivery commitments protected while testing. More enquiries are not a success if they cause existing work to fail.

For Fieldnote, the important finding is that customers need help consolidating approvals as well as rewriting information. The team updates its input and review requirements. It also learns that one prospect needs a service-policy decision before any writing package would be useful. Declining that immediate package is evidence of better selection, not failure to sell.

Week three: connect the offer to delivery

Apply the pricing, capacity and cash tests to one real proposal. Have another team member challenge the assumptions, especially tasks that occur outside the visible production work. Confirm who reviews customer input and what happens if it is incomplete.

Use the offer review exercise before sending the proposal. Check that every significant customer promise appears in the internal estimate and schedule. When an offer is accepted, preserve the version and verify the start conditions. Then create the delivery record from those agreed facts.

In the fictional Harbour Services engagement, approval of the service rules makes the package ready to offer. Acceptance and the agreed initial payment permit the production slot to be confirmed. Neither an encouraging call nor a probability in the pipeline substitutes for those conditions.

Week four: review exceptions and simplify

Hold a short review using the actual records. Focus on opportunities with changed evidence, overdue decisions, delivery risks or cash timing concerns. Agree an action and owner for each issue that matters now. End with a small number of decisions people can carry out.

Check the records themselves. Which fields changed a decision? Which were repeatedly misunderstood? Which information was stored twice? Remove unnecessary work, but keep information needed for accountability, legal obligations or sound delivery. Simplicity means the system supports its purpose with less effort, not that important evidence disappears.

Choose a continuing review rhythm that matches the business. A weekly opportunity and workload check may be appropriate for this example; a separate periodic review can examine completed-job economics and channel results. Do not compare immature enquiries with completed cohorts or treat one unusually good month as a dependable forecast.

Protect the records you depend on

Customer information and accepted offers are business assets. The Australian Cyber Security Centre’s Small business cyber security guide, January 2025 recommends multi-factor authentication, software updates and backups as basic starting measures. Use it to identify suitable protections and seek specialist help where the business needs more than the basics.

For the working system described here, assign responsibility for access and recovery. Keep the accepted version identifiable, limit access to people who need it and ensure a departing team member does not retain unnecessary access. Check that important records can actually be recovered; the existence of a synchronised folder alone does not demonstrate recovery from every kind of loss.

Follow one decision through the whole system

Harbour Services began with a brochure request. Investigation revealed inconsistent service explanations and an internal training deadline. Fieldnote waited for approved rules, proposed a bounded package and tested its economics. The accepted offer then guided the delivery record. A late editing error required a correction and an improved check. The review created a possible future update conversation without assuming an ongoing sale.

The value lies in those connections. Research changed the scope; scope informed the estimate; the estimate constrained the offer; the accepted offer governed delivery; delivery evidence improved the next decision. The case does not require every enquiry to convert or every project to run perfectly. It requires the business to notice what is happening and respond deliberately.

Your thirty-day commitment

Choose the first opportunity on which you will use the method. Name the person responsible for keeping its record current and the date of the first review. Write one improvement you expect to observe, such as fewer unconfirmed assumptions at proposal time, and decide how you will recognise it.

At the end of thirty days, ask whether the business is making clearer promises and seeing constraints earlier. Keep what helps, correct what misleads and continue learning from actual work. Winning an engagement is only one decision in a longer chain. The stronger business is the one that can explain why it accepted the work, fulfil the promise and use the result to choose well again.