GHOST // RECON Playbook
RECON / PLAYBOOK / 12 FIELD CHAPTERS

THE BUYER
INTELLIGENCE FILES.

Learn how to recognise demand, verify useful questions, investigate real situations and build research that improves over time. This is strategy you can use directly—no AI subscription required.

FIELD INTELLIGENCE
DO NOT INVENT EVIDENCE
FIELD FILE / 01 OF 12

Situations, not demographic labels

A useful market description contains an event, a person and a consequence.

Demographics are easy to put in a presentation but rarely explain why anyone will take action this week. A description like “business owners aged 30–55” conceals different priorities, budgets and buying moments. Write a situation instead: what changed, what became difficult, what must happen next and what the buyer risks by doing nothing. The narrower description helps you investigate something observable rather than imagining the needs of millions.

A good situation statement can be tested without permanently narrowing your entire business. Describe the job or change first, then the practical consequence. “A salon owner preparing a second branch” points toward staffing, operations and booking friction; “beauty entrepreneurs” does not. Different situations deserve separate case files. Do not build one imaginary average buyer from incompatible circumstances.

The market is not an age bracket. It is a person encountering a situation worth responding to.
ILLUSTRATIVE FIELD CASE

A bookkeeping adviser might investigate sole traders hiring their first assistant. That event suggests specific questions about payroll, records and responsibility, but demand for paid help still needs validation.

YOUR FIELD OPERATION

Write three “When ___ happens, this person needs to ___ because ___” statements. Choose one and find a real question or enquiry that supports it.

WATCH FOR THIS TRAP

A detailed fictional persona is not evidence that someone with that experience exists.

FIELD FILE / 02 OF 12

The job beneath the product

Buyers care about progress, not your product category.

A buyer may not want “marketing technology,” “workflow transformation” or “intelligent scheduling.” They may want a deadline met, one less awkward conversation, a booking confirmed, or their team to stop repeating the same task. Ask what the buyer is actually trying to achieve. The answer is often more specific and more emotional than the feature vocabulary on your own website.

Next inspect the existing workaround: do nothing, hire someone, use a spreadsheet, ask a colleague, combine free tools, or accept a compromise. These alternatives matter even when they are not direct competitors. Map the functional need, the emotional cost and the social consequence. Someone sending quotes may want accuracy, peace of mind and the appearance of professionalism. Which of those matters most is something to research.

Your first real competitor is often the current workaround.
ILLUSTRATIVE FIELD CASE

A scheduling tool might replace messages, manual reminders and calendar notes. The strongest demand could be fewer missed appointments, not a desire for another app.

YOUR FIELD OPERATION

Ask two relevant people to walk through the last occasion they performed the task. Note what they used and what they would be reluctant to give up.

WATCH FOR THIS TRAP

Starting with your solution and finding ways to translate every response into praise for it.

FIELD FILE / 03 OF 12

Buying triggers and time windows

Timing turns broad relevance into a question worth answering today.

An imminent hire, a new location, a seasonal surge, an unsuccessful audit or a repeated failure may create a specific period when help becomes relevant. Some triggers are sudden; others accumulate. A recurring small irritation becomes urgent when a contract, responsibility or customer expectation changes. Do not confuse a plausible trigger with a proven frequent event.

Write the trigger as an observable change, not a vague aspiration. “Has accepted a larger contract” is investigable; “wants to grow” is not. Ask where people experiencing that change might ethically reveal questions: permitted communities, professional associations, public requests for recommendations, sales enquiries and first-party customer research. Preserve the date and setting; a signal from a different country or five years ago may mislead.

The better question is “What makes this important now?”
ILLUSTRATIVE FIELD CASE

A website service might be most relevant when a business announces a new location rather than merely because its current website looks dated.

YOUR FIELD OPERATION

Find five independent examples of the alleged trigger and record where each was observed. If the trail goes cold, revise the hypothesis.

WATCH FOR THIS TRAP

Presenting a speculative market shift as proven recurring demand.

FIELD FILE / 04 OF 12

The real cost of leaving things alone

The existence of a problem does not automatically create a purchasing decision.

A buyer may agree something is frustrating but still consider the workaround acceptable. Find out what actually happens when the issue remains unsolved. Is there wasted time, a missed deadline, staff anxiety, awkward client communication, reputational risk or administrative friction? Get concrete incidents rather than assuming that every annoyance represents a large financial loss.

Balance the cost of inaction against the cost of switching. The prospective buyer may fear a difficult migration, training time, unreliable support or simply making the wrong choice. Record both sides. Where useful, ask about task frequency and effort, but do not extrapolate one anecdote into an industry-wide financial claim. The evidence board should reveal uncertainty.

A useful problem has consequences, but a validated problem has evidence of those consequences.
ILLUSTRATIVE FIELD CASE

A coach may spend time rearranging appointments. Whether a new tool is worthwhile depends on frequency, consequences and how the current routine works.

YOUR FIELD OPERATION

Ask one actual buyer: “What happened the last time this problem cost you something?” Distinguish their description from your interpretation.

WATCH FOR THIS TRAP

Invented ROI and urgency language used to inflate a minor inconvenience.

FIELD FILE / 05 OF 12

A hierarchy of evidence

Do not let a convincing hypothesis wear the costume of a verified fact.

Customer Detective distinguishes firsthand observations, externally traceable signals and unverified hypotheses. Firsthand evidence includes something you personally observed or heard with permission. External signals include attributable public comments, reviews, requests and reports. An assumption is a proposed explanation not yet tested. These classes are not perfect quality guarantees; they stop us accidentally treating imagination as certainty.

Preserve the exact source, context and limitations. A firsthand interview may be revealing but unrepresentative. A popular public complaint may attract unusually frustrated voices. Multiple blogs may repeat one original report. Contradictory observations are valuable. Store minimal private information, avoid publishing identifiers or confidential remarks, and remember that a source being public does not automatically mean it can be reused without care.

An evidence board should make the gaps visible, not hide them behind confidence percentages.
ILLUSTRATIVE FIELD CASE

“I heard three enquiries about first-hire paperwork in our own inbox this month” supports a limited observation. “All contractors need our service” does not follow.

YOUR FIELD OPERATION

Record one firsthand observation, one independent external signal and one explicitly labelled guess. Write down what each does not prove.

WATCH FOR THIS TRAP

Counting five articles repeating one claim as five independent sources.

FIELD FILE / 06 OF 12

Talk to buyers without pitching

Ask about the most recent real incident, not imaginary future enthusiasm.

“Would you pay for my amazing solution?” produces polite predictions and may flatter the interviewer. Better questions reconstruct behaviour: when did this last happen, what did you try, what went wrong, who else was involved and how did you decide what to do? Let the buyer choose the language. A question such as “What annoyed you most about the current system?” already assumes they are annoyed.

Useful follow-ups include “Why that approach?”, “What happened next?” and “What alternatives did you consider?” Respect consent, confidentiality and the interviewee’s time. Someone who says they would not change their process has given you valuable evidence. Do not turn a research invitation into an unsolicited sales pitch unless there is a separate clear agreement.

Ask people to describe a past decision, not to approve an imaginary new offer.
ILLUSTRATIVE FIELD CASE

A creator who says they need “better marketing” might, in a detailed conversation, reveal that collecting testimonials is a bigger obstacle than content production.

YOUR FIELD OPERATION

Write five neutral questions for your chosen segment. Conduct one permission-based conversation and record two things that surprised you.

WATCH FOR THIS TRAP

Pitching first and mistaking encouragement for purchasing intent.

FIELD FILE / 07 OF 12

Collect the buyer’s own vocabulary

The phrases used at the moment of difficulty are often more useful than marketing jargon.

Experts and buyers can describe the same difficulty in very different ways. An adviser might say “cash-flow forecasting”; a business owner might say “I never know whether I can pay myself.” Collect the practical phrase, the underlying concern and the situation where it appeared. Real language can improve search-oriented answers and make an educational page immediately relevant.

Compare phrasing across buying stages. Someone first noticing a problem may ask “Why does this keep happening?”; someone evaluating solutions may ask “Will this work with what I already use?” Direct language should come from permitted enquiries, ethically conducted interviews or attributable public discussions. Never fabricate direct quotations and never assume one memorable phrase represents an entire market.

The best copy often begins as careful listening.
ILLUSTRATIVE FIELD CASE

For a scheduling app, test “Stop chasing booking confirmations” against “Smart scheduling workflow automation.” Let actual buyer response inform the decision.

YOUR FIELD OPERATION

Collect ten real customer phrases, group them by the concern they express and choose one useful question for Buyer Questions Studio.

WATCH FOR THIS TRAP

Inventing a customer inner monologue and passing it off as observed behaviour.

FIELD FILE / 08 OF 12

Reachability before channel obsession

Theoretically valuable buyers may be impractical to reach with your available time and resources.

Some people gather around predictable roles, associations, marketplaces, events and recurring tasks. Others are difficult to identify or approach. Research where a relevant buyer might encounter the problem or seek advice. Distinguish channels you own, audiences you rent, and distribution accessed through partners or editors. Their access rules and trust requirements matter.

Check geographic fit, posting permission, customer intent, your available time, paid costs and whether a credible introduction is possible. A channel is not good merely because it looks cheap or popular. RECON identifies plausible habitats; ACCESS tests realistic routes. A narrow reachable group can sometimes be more useful to investigate than a large unlocatable one, but the economics still need checking.

A group you can help and reach is more actionable than an impressive audience statistic.
ILLUSTRATIVE FIELD CASE

A specialist product for small clinics may deserve an association or supplier-led route instead of a broad social feed, depending on real availability.

YOUR FIELD OPERATION

Name three plausible routes to one buying situation. Write one permission or trust barrier for each, then investigate one in Distribution Radar.

WATCH FOR THIS TRAP

Choosing a channel first and inventing a customer persona to fit its audience.

FIELD FILE / 09 OF 12

Compare without fake precision

Prioritisation should expose your assumptions and evolve when the evidence changes.

Customer Detective lets you rate urgency, reachability, offer fit and perceived economic viability from one to five. The total is simply a transparent summary of your own current judgement. It is not a conversion forecast, a market size estimate or a statistical confidence score. The evidence count beside it tells a different story.

A self-rated buyer situation with 18 points and only guesses may deserve more basic research than one with 15 points and several genuine enquiries. Rather than obsessing over a numerical winner, identify what fact could change the order. Two options can be compared with small, ethical tests while you keep the costs of being wrong low.

Transparent judgements are useful because they are easy to revise.
ILLUSTRATIVE FIELD CASE

Two groups score 16 and 14 in your own comparison. The second has firsthand enquiries. Neither number alone can decide the better market.

YOUR FIELD OPERATION

Create two buyer files, rate each and define one test that would make you change your preference.

WATCH FOR THIS TRAP

A mysterious “90% opportunity score” unsupported by any market data.

FIELD FILE / 10 OF 12

Who experiences the problem—and who approves?

In some purchases the user and the payer are not the same person.

A professional service or operational software purchase may involve a daily user, an internal advocate, a manager and a budget holder. Each may need a different answer. The user might ask whether the change saves effort; an approver may ask about risk; a manager may ask how long implementation takes. Mapping these roles prevents acquisition messages from assuming every interested person can make the purchase.

Do not impose corporate procurement complexity on straightforward solo purchases. Use the exercise where the decision is shared, expensive or risky. Ask recent customers who was involved, what evidence they requested and where the purchase slowed. Keep private identities out of a public asset.

The decision path is part of the buyer situation.
ILLUSTRATIVE FIELD CASE

A small clinic’s receptionist might experience booking problems while an operations manager researches options and an owner signs off.

YOUR FIELD OPERATION

Ask a recent customer how the decision was reached. List the most important question for the user, champion and approver.

WATCH FOR THIS TRAP

Writing the same pitch for every role and mistaking delay for lack of interest.

FIELD FILE / 11 OF 12

Run research that could prove you wrong

An experiment is useful when its outcome could change your next move.

“People will love this offer” is not testable. “Owners preparing to hire their first employee would find a first-hire checklist worth requesting” is a clearer hypothesis, though it still requires a real audience and a responsible way to measure interest. Start with one buyer situation, one relevant resource or message, one route and one observable outcome.

Decide what to do if the response is positive, negative or inconclusive before launching. A few responses can reveal objections but rarely justify broad market claims. If the test fails, investigate whether the problem was weak, the route unsuitable, the message confusing or the asset insufficiently useful. Record the result in the Observatory rather than quietly forgetting it.

The smallest test should be cheap enough to repeat and honest enough to teach.
ILLUSTRATIVE FIELD CASE

A niche partner who finds a co-branded checklist useful offers evidence about partner relevance—not automatic proof that the eventual buyers will pay.

YOUR FIELD OPERATION

Write a test with a specific hypothesis, action, observable response and follow-up decision. Avoid changing every variable at once.

WATCH FOR THIS TRAP

Changing buyer, offer, message and channel together, then claiming to know which caused the result.

FIELD FILE / 12 OF 12

Build an acquisition memory

Your research should become more useful and accurate over time—not merely more voluminous.

A durable buyer dossier can hold changing triggers, real objections, useful phrasing, lost assumptions and field results. Preserve when a signal appeared and what was happening at the time. Without that context, an old observation can become misleading. Do not let a beautifully designed document fossilise an uncertain idea.

Revisit promising segments when the market changes. New tools, job patterns, regulations, competitors and customer expectations can create or dissolve urgency. Keep research separate from public marketing assets. The confidential dossier can contain assumptions and operational notes; a publicly distributed page should provide verified, appropriately phrased help. Maintain the page you own when circumstances change.

What we learned should outlast what we launched.
ILLUSTRATIVE FIELD CASE

An old help page may still receive interest while its advice has become obsolete. A scheduled accuracy review can be more valuable than producing another generic post.

YOUR FIELD OPERATION

Schedule a quarterly buyer review: one changed assumption, one new signal, one stale public asset to refresh and one next test.

WATCH FOR THIS TRAP

Treating the completion of a document as proof that the buyer model is permanently correct.