Illustrative workflow

Client research and agency workflow

Turn a ten-account shortlist into three focused briefs and pitch packages, with reusable account learning.

Start with a reason to engage

For an agency choosing which accounts to pursue, useful research explains account fit, supports a point of view, and identifies questions for the first conversation. This illustrative workflow helps an agency decide where to focus its business-development effort.

Frame the agency’s market thesis

Start with the agency’s target market, services, commercial priorities, relevant experience, and capacity. Add account and buyer research only where it changes a decision. Keep the reason to pursue an account visible alongside the evidence and the unknowns.

The first output is a shortlist, not an outreach campaign. A small pilot establishes whether the research helps the agency choose better conversations.

Workflow

1. Frame ten candidates. Agree on market, account criteria, exclusions, and the services the agency can deliver. Capture each candidate’s account signals and likely buyer context.
2. Compare and choose three. Gather public company, competitor, and buyer information. Link observations to sources, separate facts from hypotheses, and review the shortlist with the agency.
3. Go deep on the selected accounts. Prepare a point of view, likely buying roles, message options, relevant agency proof, and questions to test the value hypothesis.
4. Enter the conversation and learn. The agency approves the package and leads the conversation. Record objections, corrections, and next actions so the next shortlist starts with better context.

A scorecard that supports a decision

Use a short qualitative review instead of a precise-looking score without evidence:

• Account fit: Does the company match the agency’s market and service strengths?
• Reason to act: What observable change or business problem makes a conversation timely?
• Buyer context: Who owns the problem, and what would they need to agree on?
• Relevant proof: Which actual agency experience supports the proposed work?
• Unknowns: What needs to be resolved before a pitch is useful?

The agency can choose research further, hold, or pass, with a reason and next action attached to each decision.

Example account brief and pitch

An illustrative shortlist

These three invented candidates show how a reviewer narrows a shortlist. Signals and decisions are synthetic; a real shortlist would link each observation to its public source.

Retailer A · Research further

Signal: Storefront expansion. Fit hypothesis: Acquisition and repeat-purchase measurement. Unknown: Reporting stack and ownership. Next action: Verify the expansion and prepare a measurement discovery question.

Manufacturer B · Hold

Signal: A new regional sales team. Fit hypothesis: Support for entering a market. Unknown: Whether marketing help is needed. Next action: Resolve the need before preparing a pitch.

Software company C · Pass

Signal: A product announcement. Fit hypothesis: No clear match to the agency’s services. Unknown: Buying intent. Next action: Leave it out of this round.

The agency selects Retailer A for a deeper brief; a signal alone does not justify a pitch.

The selected account

Synthetic scenario: a retailer expanding its online storefront. The company and expansion are invented for this example.

Account signal: Storefront expansion.

Hypothesis: The team may need a clearer connection between acquisition channels and repeat purchases.

Discovery question: How do you connect campaign reporting with repeat-purchase behavior today?

Suggested first step: Map the existing measurement approach and choose one gap to investigate.

Illustrative opening message

Your storefront expansion suggests a useful first conversation: how are you connecting acquisition spend with repeat purchases? We could start by mapping the current measurement approach and identifying one question worth testing.

The account brief provides the reasoning behind the message. A real package would attach public sources and relevant agency experience to support that reasoning.

What each selected account receives

A useful package holds the account brief, buyer context, value hypothesis, message options, discovery questions, and next action together. It includes links to the supporting observations and the relevant agency work. A reviewer should be able to see why the proposed conversation fits this account.

Before the pitch: test and revise

The Boutique Marketing Agency source material develops the pilot through five moves: understand the account, propose relevant ideas, shape the offer and entry point, evaluate reactions and objections, and refine the pitch package.

Before a client conversation, a simulated buyer panel can challenge the message from different perspectives: the marketing lead, finance, and operations. Compare variants for account relevance, evidence, clarity, and likely objections. Simulated reactions generate hypotheses to test; they are not customer interviews or measured buyer demand.

Illustrative revision: A draft promises “better growth.” A simulated finance reviewer asks how the agency would distinguish campaign effects from changes in customer mix. The strategist replaces the promise with a measurement-discovery proposal and adds that question to the account brief.

After the real conversation, record actual feedback and objections separately from the simulation.

Connect the workflow to the agency’s tools

The source proposal includes CRM history, market and analytics data, documents, and API-connected tools as possible inputs. A scoped integration could assemble account context when a record changes, prepare research and message variants, and route the package to a strategist for review.

Useful outputs include a structured account brief, a selection recommendation with reasons, a draft pitch, and a follow-up task. Approved conversations and delivery feedback can update the account record and reusable playbooks. Actual integrations depend on the agency’s systems and data access; this page describes the proposed operating model, not deployed CRM or campaign automation.

After the pitch: support delivery and retain learning

The older agency materials also describe an intelligence layer behind delivery. This is a possible extension of the acquisition workflow:

1. Audit: Combine approved analytics and campaign exports with tracking-health checks and competitor observations.
2. Plan: Compare spend scenarios with their assumptions, data gaps, and measurement approach.
3. Review: Prepare a weekly performance brief showing what changed, questions to investigate, and decisions for the strategist.
4. Retain: Carry approved decisions, experiments, objections, and account context into the next review.

Reviewable delivery artifacts

The legacy campaign concept names six useful outputs: a strategic brief with audience and rationale; a creative brief with goals, tone, and deliverables; a media plan with channel assumptions and proposed spend; a client presentation connecting the recommendation to evidence; a performance report comparing observations with the baseline; and a decision journal linking a decision to its owner, reasoning, and outcome.

A fictional journal entry might read: “Test repeat-purchase measurement before increasing spend. Reason: the acquisition report omits returning customers. Owner: account strategist. Next review: compare the joined records and revise the plan.” This preserves the reasoning that a later brief needs.

The strategist owns campaign direction, client commitments, and changes to spend. This proposed extension covers workflow tooling; campaign execution remains with the agency.

Agency review

The agency verifies the account signal, challenges the hypothesis, and checks that the proposed work matches its expertise. It approves the message and leads the client relationship.

Related work

Before connecting a workflow to customer data, use the AI and data readiness assessment. Explore the AI Harness Landscape comparison framework or the lab’s knowledge-assistant architecture.