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.

Figure 1Five connected records

• Fieldnote working system
  • Opportunity notedecide whether to pursue
  • Offer and acceptancepreserve the promise
  • Pipelinecoordinate open decisions
  • Capacity and cash viewstest feasibility
  • Delivery and review recordfulfil and improve

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.

Figure 2Thirty days to put the method to work

1. Week 1Establish the baselinecurrent opportunities and one completed engagement
2. Week 2Test one offer and one routean evidence test and a channel experiment
3. Week 3Connect the offer to deliverypricing, capacity and cash tests on a real proposal
4. Week 4Review exceptions and simplifychoose a continuing rhythm

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.

Keep the system light enough to last

A method that takes too long to maintain is abandoned in the first busy month. Set a time budget for keeping the records and stick to it. For a two-person business, half an hour a week for the pipeline review and a few minutes after each customer conversation to update the record is usually enough. The monthly clean-up and the end-of-job review add perhaps an hour each.

If the budget is regularly exceeded, the records are probably doing more than the decisions require. Look for fields nobody uses, reports nobody reads and information typed into two places, and remove them. The aim is a system that is cheaper to keep than the mistakes it prevents.

Recognise the common ways the method fails

The practices in this book tend to fail in predictable ways. Knowing them makes them easier to catch early.

Figure 3Early signs the method is slipping

• Ask: Open records with next-action dates in the past
• Ask: Stages used loosely, such as "accepted" before acceptance
• Ask: Offers sent without a check against the estimate
• Ask: Changes agreed by email but not recorded
• Ask: Reviews skipped because "nothing went wrong"
• Ask: Records kept by one person only

None of these is a reason to abandon the approach. Each has a simple correction: a date fixed in the weekly review, a definition re-read, a step added to the offer template, a habit of recording changes the same day. The real risk is not noticing the slippage for months, by which time the records describe a business that no longer exists. The weekly review is the natural place to ask, briefly, whether any of these signs has appeared.

Look for evidence that it is working

After thirty days, the results that matter are mostly visible in the records themselves rather than in sales figures, which take longer to move. Useful signs include:

• every open opportunity has a named owner and a next action with a future date;
• every offer sent in the period can be traced to a decision record and an estimate;
• capacity and cash were checked before any new start date was promised;
• at least one completed job has an estimate-against-actual comparison and one specific change arising from it;
• the team can explain why each declined enquiry was declined.

These are modest measures, and deliberately so. They show that the business is making its decisions on evidence. Better sales, steadier cash and fewer delivery surprises are the expected consequences over the following months, and they will be easier to attribute when the underlying records are sound.

Adapt the method as the business grows

The records described here suit a small team. As the business grows, some parts will need to change. More people handling enquiries may justify sales software that enforces the stage definitions and reminds owners of due actions. More jobs running at once may justify a proper scheduling tool for the capacity view. A bookkeeper or accountant may take over the cash forecast.

Move to new tools when a real coordination problem appears, not before. When you do, carry the definitions across deliberately: the evidence required for each stage, the meaning of planning contribution, and the distinction between accepted value and received cash. Software can make records easier to keep, but it cannot decide what they should mean, and a new tool configured without those definitions will quietly reintroduce the vague stages and blended numbers this book set out to remove.

Teach the method to someone new

The final test of the system is whether a new team member can use it. Give them the definitions, one completed job’s records from enquiry to review, and the current pipeline, and ask them to explain the state of two open opportunities and what should happen next. Where they hesitate, the records or definitions need improving.

Teaching in this way also spreads the habits that keep the system alive. A business in which everyone understands why each record exists is far less dependent on the one person who set it up, and far more likely to keep making clear promises when that person is busy, away or has moved on.

Plan the second month

The first thirty days establish the records and habits. The second month is when they start to produce evidence worth acting on. Plan it before the first month ends, while the lessons are fresh.

A practical second-month plan has three parts. First, carry forward the improvements identified in the reviews, each with its owner and date, and check at the next weekly meeting whether they happened. Second, continue the channel experiment that looked most promising, or start the second one, using the same records so the results can be compared. Third, schedule the follow-up review of the first month’s enquiries, about two months after they arrived, as Chapter 3 recommended, so that the slower conversions are counted fairly.

Keep the plan small. One or two improvements actually made are worth more than a long list of intentions. The aim of the second month is not to add new practices but to make the first month’s practices routine, so that they continue when the business is busy, which is exactly when they matter most.

Note in the plan which questions are still open, such as whether the assessment-only option attracts customers or whether the input check shortens delivery. Each open question should have a date by which the records will have enough evidence to answer it. Those dates turn the method from a set of habits into a steady way of learning what works for this particular business.

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.

Figure 4One request followed through the whole system

1. 1Enquiry"A better brochure by month end"
2. 2Decision recordinconsistent inclusions; training date
3. 3Offerdefined package, 40/60 payment
4. 4Pipelineapproval of rules made it ready
5. 5Deliveryinputs checked, changes recorded
6. 6Reviewuse observed; next conversation planned

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.