Build a route to enquiries you can maintain

Once a customer problem is credible, the next question is how suitable customers will encounter your offer. A channel is a route through which that happens: a referral, a search result, a professional event or an existing customer conversation. Choosing channels is a resource decision. Every route consumes time, attention or money before it produces work.

Fieldnote Studio has two people and existing delivery commitments. It cannot maintain a daily video programme, attend every networking event and answer enquiries immediately. Its useful starting question is therefore not which channel could reach the most people. It is which route can produce relevant conversations at a cost the team can sustain.

Match the route to a buying situation

Describe where a customer is likely to notice the problem. A firm updating its services may already be speaking to its web designer. A manager dealing with repeated misunderstandings may ask a trusted peer. Those situations suggest different routes: a relationship with complementary providers, a practical explanation customers can share, or a page that answers a specific question.

Write the reasoning before choosing the channel. “Our customers use social media” is too broad. “Owners reviewing their service pages ask their web designers about wording, so we will test introductions from two designers” identifies an event, an intermediary and a bounded experiment. It can still be wrong, but the team knows what it is testing.

A referral relationship should clarify what each business does, how introductions happen and whether any payment or other benefit is involved. Do not leave customers guessing about commercial relationships. Obtain permission before passing on contact details and let the customer decide whether to engage.

Let existing customers open doors, with permission

Satisfied customers are often the most credible route to similar customers, but only if they are willing. Ask directly whether a customer would be comfortable being mentioned, speaking to a prospective client or allowing a short description of the work, and respect a refusal without pressing.

Describe past work accurately and only with consent. A case description should say what was done, for what kind of business, and what changed, without overstating the result or attributing an outcome the work did not cause. If a customer agrees to speak to a prospect, brief them on the context and then let the conversation be theirs. A fabricated testimonial, an embellished result or an implied endorsement from someone who has not given one damages trust far more than having no testimonials at all.

Give the enquiry somewhere useful to land

A small service page can answer the questions required for an initial decision: who the service is for, the situation it addresses, what is included, what input the customer must provide and what happens after an enquiry. If price depends on scope, explain the variables rather than creating a false impression of a fixed fee.

Fieldnote describes a bounded document package with an agreed number of outputs and review rounds. It states that service rules must be approved by the customer. This limitation helps a prospect recognise whether they are ready; it also prevents the page from promising to resolve management disagreements through writing alone.

Make the next action proportionate. An initial enquiry does not need every company document. Ask for the business context, the immediate problem and a way to respond. Explain what information is useful and discourage the submission of sensitive customer records. Test the page on a phone and check that the enquiry route works. A polished description cannot compensate for a broken form.

Use the customer’s own words

The research in Chapter 2 produced something more valuable than conclusions: the phrases customers used to describe their problem. Customers rarely say “we need consistent customer-facing information”. They say “two of us gave the same customer different answers” or “we keep explaining what the premium package doesn’t include”. Pages, introductions and guides that use that language are recognised more quickly by the people who have the problem.

Fieldnote rewrites the opening of its service page around a situation from its interviews: “When a customer asks what a package includes, does everyone in your team give the same answer?” The sentence names an event the right reader has experienced and the wrong reader has not, which helps both decide quickly whether to read on.

Use those words honestly. Quoting a research participant publicly requires their permission, and a paraphrase of a common situation is safer than a quotation that could identify someone. Never present an invented statement as a customer’s words.

The same principle applies to headings, guide titles and the first line of an introduction from a referral partner. Each is a chance to describe a situation the right customer recognises. Test a few versions with people who match the customer description, asking which one sounds like their business, rather than relying on which one the team likes best. The version that sounds plainest to the team is often the one customers recognise fastest.

Answer the first enquiry well

The first reply to an enquiry shapes everything after it. A prompt, specific reply shows the customer that the business is organised and has read what they wrote. A slow or generic one invites them to keep looking.

Fieldnote sets itself a simple standard: every enquiry gets a personal reply within one working day, even if the full answer will take longer. The reply:

1. confirms what the customer asked about, in a sentence that shows it was read;
2. answers any simple question directly, such as whether the service covers their situation;
3. asks at most two or three questions needed to decide the next step;
4. proposes that next step, with a time.

Figure 1A useful first reply to an enquiry

1. 1Confirm what was askedshow it was read
2. 2Answer the simple questionsin plain terms
3. 3Ask two or three questionsonly what the next step needs
4. 4Propose the next stepwith a time

A long reply that tries to answer every possible question usually works less well than a short one that moves to a conversation. The detailed explanation belongs in the conversation, where it can be shaped to what the customer actually needs.

Ask only what the next step needs

The questions in a first reply should decide whether to proceed and how. For Fieldnote’s package, three questions usually suffice: how many services the information pack must cover, who would approve the final wording, and whether there is a date the material is needed by. Each answer changes what happens next. A pack covering twenty services is a different job; an unclear approver predicts revision loops; a near date tests capacity.

Questions that do not change the next step, such as annual turnover, number of staff or marketing budget, can feel intrusive at this stage and add little. They can come later if the work requires them. Asking for less also keeps the business from collecting personal or commercial information it has no use for.

Make sure enquiries actually arrive

A channel experiment is worthless if the enquiries it produces disappear. Forms break after website updates, notification emails land in spam folders, and shared inboxes are read by nobody in particular. Each failure is silent: the business simply sees fewer enquiries and may wrongly conclude that the channel does not work.

Simple checks prevent this. Send a test enquiry through every route after any change to the website, and at least monthly otherwise. Confirm that the message reaches the person responsible, on their phone as well as their computer. If the form sends an automatic acknowledgement, read it as a customer would: it should confirm that the message arrived, say when a reply can be expected, and avoid promising anything the team cannot deliver.

Decide who owns each route. For Fieldnote, one person checks the enquiry inbox each working morning and records new enquiries in the shared list before replying; the other covers during leave. Writing that down takes a minute, and it is what makes the one-working-day reply standard achievable rather than aspirational.

Count progress towards work

Channel activity and commercial progress are different measures. Publishing four posts records effort. Receiving six enquiries records a response. Confirming that two enquiries fit the offer records something closer to a sales opportunity. Keep those measures separate.

Figure 2Four different things a channel can produce

1. 1Effortpublishing four posts
2. 2Responsereceiving six enquiries
3. 3Fittwo enquiries match the offer
4. 4Opportunityan agreed next conversation

For a two-week experiment, Fieldnote records the following fictional results:

The guide produced more enquiries, while introductions produced more suitable conversations during this short period. Neither result proves a permanent winner. The guide may keep working after publication; introductions may depend on one unusually helpful contact. Two weeks and ten enquiries are too little evidence for a dependable conversion forecast.

Figure 3Two-week channel experiment, fictional results

	Introductions	Practical guide
Team time	5 hours	7 hours
Enquiries	4	6
Fit the service	3	2
Agreed next conversations	2	1
Team time at A$85 per hour	A$425	A$595

Record enough context to interpret the numbers: the time window, the audience, the definition of fit and whether opportunities have had time to progress. Ask customers how they heard about you without assuming they used only one route. Someone may read a guide after a referral and later search for the business name. A simple record can retain both influences rather than assigning false precision to one source.

Give each experiment time to mature

Enquiries do not convert into work on the day they arrive. A customer may take weeks to gather information, consult a colleague or wait for a budget. Judging a channel two weeks after starting it measures only its fastest responses.

Fieldnote therefore reviews each channel experiment twice: once at the end of the activity period, recording enquiries and fit, and again about two months later, recording which of those enquiries became conversations, proposals and paid work. The second review uses the same group of enquiries, not whatever arrived recently, so the comparison is fair. It also records the time spent on each enquiry after it arrived, which is part of the channel’s real cost.

Only after the second review does the team decide whether a channel deserves more effort. That patience protects against a common error: abandoning a route that produces slower but better-suited work in favour of one that produces quick but unsuitable enquiries.

Keep the review simple enough that it actually happens. A dated reminder in the shared calendar, the list of enquiries from the original period and a short note of what happened to each is enough. The point is not a precise conversion rate, which a handful of enquiries cannot support, but an honest comparison of which route brought work the business wanted, at a cost it could sustain.

Include the cost of your attention

At an illustrative planning value of A$85 per hour, five hours represents A$425 of team time and seven hours represents A$595. These are internal economic estimates, not necessarily cash payments. They make an invisible cost visible.

Do not yet divide that cost by sales if the enquiries are still open. Later, compare a mature group of enquiries with the contribution earned from its completed work. Include relevant direct spending and the time spent preparing material, responding and following up. A channel with cheap clicks can be expensive if most enquiries require lengthy explanations before being declined.

Also check the effect on delivery. If a successful campaign creates more suitable work than the team can handle, the response is not automatically to accept everything. Adjust availability, scheduling or the offer. The capacity test in Chapter 5 applies regardless of how attractively the enquiry arrived.

Figure 4Before scaling a channel that works

• Do: Mature cohortcompare completed enquiries, not open ones
• Do: Full costdirect spending plus preparation, responses and follow-up
• Do: Delivery effectadjust availability, scheduling or the offer
• Avoid: Accept everything it bringsattractive arrival does not create capacity

Respect permission when making contact

For Australian commercial electronic messages, consult the ACMA’s guidance on avoiding spam. Consent, identification of the sender and a working unsubscribe mechanism are central requirements. A publicly visible address is not blanket permission to send marketing. Keep evidence of consent and implement withdrawal requests through the actual sending process. This short note is not a complete compliance assessment; check the rules for the message, recipient and jurisdiction involved.

Operationally, separate a requested response to an enquiry from permission for an ongoing marketing list. Do not silently turn one into the other. A spreadsheet of contacts is still a record of people whose expectations matter.

Exercise: define a channel experiment

Choose one route you can maintain for a defined period. Write the customer situation, the material or conversation you will offer, the time and spending limit, and the signal that would justify continuing. Include a stopping condition, such as repeatedly reaching the wrong type of customer.

End the experiment with a decision: continue, change the message, change the audience or stop. Preserve what you learned even when the channel fails. The next chapter follows a suitable enquiry into a conversation that produces a clear decision record.