MCN GUIDE #54 • MEDIUM

Building an Agency Brand Relationship Management System如何建立 Brand CRM?

A practical CRM architecture that turns scattered brand contacts, conversations, opportunities, creator matches, campaigns, and renewals into shared agency memory and disciplined commercial action.

Level
Medium
Agency systems
Core Objects
4 + Match
Account • Contact • Deal • Activity
Required Field
Next Action
Owner + date
Purpose
Relationship Memory
Not a contact dump
CRM is agency memory.

A Brand CRM should answer what the agency knows, why it believes it, who owns the relationship, and what must happen next.

A spreadsheet of names is not relationship management. The agency needs a connected view of the company, its buying committee, each active commercial initiative, the history of meaningful interactions, relevant creator matches, purchase requirements, delivered campaigns and renewal potential.

CRM value

Structured relationship context + verified opportunity evidence + accountable next action + reusable commercial learning

Start with the operating model and minimum data, then choose software. A sophisticated CRM cannot fix undefined stages, unclear ownership or a team that does not update records.

Section 1

Design the CRM Architecture Before Choosing Fields

Keep different concepts in separate linked records. This avoids duplicate contacts, overwritten deal history and reports that confuse a brand relationship with one campaign.

ObjectRepresentsPrimary question
AccountCompany, parent, brand, business unit or buying centerWho the agency is building a commercial relationship with
ContactOne professional stakeholderTheir role, authority, relationship, consent/channel and account connection
OpportunityOne potential purchase or defined commercial initiativeProblem, scope, value, stage, probability evidence, decision path and next step
ActivityOne meaningful interaction or taskWhat happened, outcome, participants, source, owner and next action
Creator matchEvidence-backed fit between an account/opportunity and a creatorWhy the match exists, restrictions, proof, status and feedback
Campaign handoffWon opportunity linked to delivery/finance systemsThe bridge from sales truth to execution, rights, reporting, invoicing and renewal

Relationship chain

Account ↔ contacts / buying committee ↔ opportunity ↔ creator matches ↔ activities ↔ won campaign ↔ result / renewal

Use one source of truth for each object. If campaign delivery, finance or creator systems remain separate, link them with stable IDs rather than copying inconsistent versions into every tool.

Section 2

Build an Account Record Around the Buying Center

A global company can contain many separate purchasers. The China skincare team, global social team and e-commerce unit may have different budgets, partners and approval paths. Model the hierarchy without duplicating the whole company.

Field groupMinimum record
IdentityLegal/company name, parent, brand, business unit, region, market, category and official domain.
Buying centerThe specific team or cost center that can initiate and fund creator work.
Strategic fitWhy this account belongs in the agency target market and which creator capabilities matter.
Commercial historyOpportunities, campaigns, revenue, contribution, payment behavior, disputes and renewal outcomes.
Relationship healthLast meaningful interaction, coverage, champion strength, sentiment, risks and next relationship goal.
Process mapBudget cycle, procurement, vendor status, MSA, PO, invoice, payment and approval requirements.
Partner mapMedia, PR, creative, e-commerce, KOL and other agencies influencing creator activity.
OwnershipAccount owner, executive sponsor, coverage team, review date and transfer status.

Parent company

Corporate hierarchy, global policies and aggregated commercial exposure.

Brand / division

Distinct category strategy, customer, positioning and creator relevance.

Buying center

The actual team, geography and cost center behind a specific purchase.

Section 3

Map Contacts as a Buying Committee

A title is a hypothesis. Store the person's functional role in the purchase and the evidence behind it. One contact may hold several committee roles; one role may involve several people.

Field groupWhat to capture
Professional identityName, title, function, company/buying center, location/time zone and verified professional channel.
Committee roleProblem owner, KOL evaluator, champion, economic buyer, operator, approver, procurement, finance or blocker.
Authority evidenceWhat they confirmed or demonstrated about budget, selection, approval, process and timing; include source/date/confidence.
RelationshipOwner, strength, last meaningful contact, preferred channel/cadence, open commitments and next value to deliver.
RelevanceObjectives, categories, audiences, creator preferences, concerns and evidence they respond to.
Data controlsBusiness purpose, source, consent/opt-out where applicable, retention/review date and access restrictions.

Core committee roles

  • Problem owner
  • KOL / creator evaluator
  • Champion
  • Budget owner / economic buyer
  • Day-to-day operator
  • Brand, legal or media approver
  • Procurement / vendor management
  • Finance / payment owner
  • Blocker or external agency influence

Coverage questions

  • Do we know who needs the outcome?
  • Who controls or reaches the budget?
  • Who chooses creators and partners?
  • Who can champion the proposal internally?
  • Who approves claims, rights and risk?
  • Who controls vendor onboarding and PO?
  • Who runs execution and accepts delivery?
  • Who releases payment?
Do not store unsupported personal judgments or irrelevant private information. Keep professional, sourced, dated relationship context for a legitimate business purpose and follow applicable privacy, marketing and retention rules.

Section 4

Define Opportunity Stages with Buyer Evidence

Stages must represent a change in the buyer's process, not the seller's optimism. Each stage has required evidence, an exit criterion and a next action.

StageMeaningRequired evidenceNext gate
TargetAccount fits the agency ICP; no qualified buying motion yetAccount hypothesis, fit evidence, owner and research actionResearch or first relevant contact
EngagedA relevant stakeholder has meaningfully responded or metContact role, interaction outcome, potential need and next meetingComplete initial qualification
QualifiedA real problem, owner, plausible value and timing existProblem, success criteria, buying committee, budget state and decision pathDiscovery or solution design
SolutionAgency and buyer are shaping creators, scope and commercial approachCreator-match rationale, scope, risks, pricing assumptions and stakeholdersProposal/brief alignment
ProposalA dated commercial proposal or response is under active reviewVersion, value, scope, competition, decision criteria, approval path and dateBuyer review / revision
CommitBuyer has selected the approach subject to named final stepsVerbal/written selection evidence, procurement/legal/PO gaps and close planContract, onboarding and PO
WonRequired commercial authorization is complete under agency policyFinal value, documents, handoff owner, delivery kickoff and invoice triggerExecute and expand
Lost / no decisionBuyer selected another path or initiative stoppedReason, evidence, competitor/no-decision cause, lessons and nurture dateLearn, close or re-enter later

Opportunity essentials

  • Named business problem and success criteria
  • Account/buying center and contacts
  • Estimated value with basis and currency
  • Budget state and owner
  • Decision criteria, process and target date
  • Scope, creators, rights and key risks
  • Competition / incumbent / no-decision risk
  • Next action, owner and date

Close-plan essentials

  • Remaining decisions and evidence
  • Decision owner for each step
  • Procurement and vendor onboarding
  • Legal/MSA/SOW and rights review
  • PO, invoice and payment requirements
  • Final creator availability and pricing
  • Delivery handoff owner
  • Mutually understood target dates

Section 5

Add a Creator-Brand Matching Layer

Do not paste a roster into every opportunity. Store a match record that explains why a creator fits this account and objective, what evidence supports the fit, and which commercial or risk conditions apply.

DimensionMatch evidence
AudienceGeography, language, demographics, interests, buyer relevance and community quality.
Brand fitCategory credibility, tone, visual world, values, reputation and conflict/exclusivity constraints.
ObjectiveAwareness, trust, launch, content production, commerce, live, localization or another defined outcome.
PlatformChannel strength, format ability, content cadence, account status and paid-use readiness.
EvidenceComparable content, audience data, performance history, brand feedback and commercial outcomes with context.
EconomicsRate, production needs, usage, exclusivity, agency cost, expected contribution and payment terms.
OperationsAvailability, turnaround, language, travel, approval behavior, reliability and account/access requirements.
RiskClaims, category restrictions, rights, conflicts, conduct, content sensitivity and contingency options.

Match quality

Objective fit + audience relevance + credible creator identity + operational readiness + viable economics − conflicts and risk

Suggested

Agency hypothesis; not yet validated with brand or creator.

Qualified

Core fit, availability, conflict and commercial assumptions checked.

Selected / declined

Record brand and creator decision plus reason to improve future matching.

Section 6

Capture Meaningful Relationship Activity

The CRM does not need every chat message. It needs decisions, evidence, commitments and context another owner would require to continue the relationship professionally.

Log after a meaningful interaction

  • Date, channel and participants
  • Account, contacts and opportunity
  • Purpose and concise outcome
  • New confirmed evidence and source
  • Decision or commitment made
  • Open question, risk or objection
  • Material shared and version
  • Next action, owner and date

Do not use activity notes for

  • Unfiltered call transcripts as the only summary
  • Private gossip or sensitive irrelevant data
  • Promises that conflict with the proposal/contract
  • Hidden pricing or scope exceptions
  • Personal task lists with no commercial context
  • Copying the same note into several records
  • Replacing campaign delivery documentation
  • Replacing consent or opt-out records

The perfect CRM note

What changed? What evidence supports it? What did each side commit to? Who does what by when?

Section 7

Define Account Ownership and Relationship Cadence

One accountable account owner coordinates the relationship; specialists contribute without creating conflicting messages. Ownership is responsibility, not personal possession of the contact.

Account owner

Relationship outcome

  • Account plan and coverage
  • Commercial consistency
  • Opportunity priorities
  • Next-action discipline
  • Internal coordination

Opportunity owner

One buying motion

  • Qualification and stage
  • Creator solution
  • Close plan
  • Proposal and negotiation
  • Handoff completeness

Executive / specialist

Targeted leverage

  • Strategic sponsorship
  • Creator/content expertise
  • Legal/finance/operations input
  • Escalation
  • Renewal or recovery

Weekly pipeline

Review stage changes, next actions, blockers, creator-match gaps, proposal decisions and stale opportunities. Update the record during the review.

Monthly account

Review relationship coverage, active initiatives, campaign health, revenue, payment, risks, whitespace and next value-creating touch.

Quarterly portfolio

Re-rank target accounts, concentration, category demand, win/loss learning, partner ecosystem, creator fit and resource allocation.

Section 8

Enforce CRM Hygiene with Small Hard Rules

Required rules

  • One account hierarchy and duplicate policy
  • One accountable owner per account/opportunity
  • Stage exit criteria and required evidence
  • Every open opportunity has a next action, owner and date
  • Amounts include currency and basis
  • Contact authority marked confirmed/inferred/unknown
  • Won deals require delivery/finance handoff
  • Closed-lost records require a reason and learning

Data stewardship

  • Named administrator/process owner
  • Required-field and option-set governance
  • Duplicate review and merge process
  • Stale-record review and closure
  • Role-based access and export control
  • Consent/opt-out and suppression handling
  • Retention/deletion policy
  • Audit of integrations and automation

Complete

Required fields and relationships are present.

Current

Evidence, stage and next action reflect reality now.

Consistent

Teams use the same definitions, formats and option values.

Minimize required fields at the beginning. A smaller set used consistently creates more value than a perfect schema the team avoids.

Section 9

Automate Administration—Keep Judgment Human

Good automation candidates

  • Create follow-up task from a logged meeting
  • Flag open opportunities with overdue next actions
  • Enrich approved company-level data with source/date
  • Sync calendar/email metadata where authorized
  • Generate draft summaries for human review
  • Notify on stage, amount or close-date changes
  • Create delivery handoff checklist after won
  • Deduplicate with a review queue

Keep human approval for

  • Authority and relationship assessment
  • Stage advancement and forecast judgment
  • Creator-brand fit and conflict decisions
  • External messaging and promised scope
  • Pricing, rights and commercial exceptions
  • Sensitive notes and data retention
  • Merging ambiguous accounts/contacts
  • Closing or reassigning strategic relationships

Automation gate

Reliable trigger + clean data + explicit rule + reversible action + exception owner

Do not auto-send relationship messages merely because a field changed. Relevance, consent, timing, cultural context and account politics need human judgment.

Section 10

Build a CRM Dashboard that Drives Action

Accounts

Target / active

By owner and tier

Coverage

Committee mapped

Champion, budget, operator

Pipeline

Value by stage

Amount with basis

Movement

Stage velocity

Age and conversion

Actions

Due / overdue

Owner and priority

Matching

Qualified creators

Feedback and gaps

Forecast

Evidence bands

Not one weighted total

Revenue

Won / repeat

Contribution and payment

Pipeline health

  • New qualified opportunities
  • Stage conversion and age
  • Slipped close dates
  • No-next-action records
  • Proposal-to-decision time
  • Loss/no-decision reasons

Relationship health

  • Accounts with multi-threaded coverage
  • Champion and budget-owner gaps
  • Last meaningful interaction
  • Campaign-to-renewal conversion
  • Revenue/account concentration
  • Payment or service-recovery risks

Section 11

Forecast from Evidence, Not Stage Percentage Alone

A stage-weighted pipeline can create false precision. Separate the opportunity amount, expected timing and confidence, and explain the evidence behind each.

Pipeline

Plausible opportunities still requiring major buyer validation

Problem/fit exists; budget, authority or process may be incomplete

Best case

Qualified deals that can close in the period if named steps succeed

Buying process and timing mapped; meaningful gaps remain

Commit

Deals with strong buyer evidence and a credible final close plan

Selection and remaining procurement/legal/PO steps are explicit

Pipeline coverage

Qualified open opportunity value ÷ revenue target for the same period

Stage velocity

Opportunities exiting a stage ÷ opportunities entering that stage cohort

Forecast accuracy

Compare forecast snapshot to actual outcome—do not rewrite the old forecast

Track amount changes, close-date slips and stage reversals. They reveal qualification and coaching problems that a current-state dashboard hides.

Section 12

Implement the Minimum Viable CRM in 30 Days

Days 1–7Define
  • Name process owner and executive sponsor
  • Define objects, stages and exit criteria
  • Choose minimum required fields
  • Define ownership, access and privacy rules
Days 8–14Configure
  • Build account/contact/opportunity/activity objects
  • Create controlled option values and IDs
  • Add creator-match and handoff links
  • Create core views and templates
Days 15–21Migrate & pilot
  • Clean target accounts and active deals first
  • Merge duplicates and assign owners
  • Pilot with one sales/account team
  • Fix friction and unclear definitions
Days 22–30Launch & govern
  • Train through real opportunities
  • Run weekly review inside the CRM
  • Publish dashboard and data-quality queue
  • Set monthly governance and improvement cycle

Migration priority

Start with active opportunities, strategic accounts, current contacts and recent meaningful history. Archive or stage lower-value legacy data instead of delaying launch for a perfect migration.

Section 13

Common Brand CRM Failures

  • !Creating one record per brand name while ignoring parent company, business unit, region and separate buying centers.
  • !Treating every contact as a lead instead of mapping their function, authority, influence and relationship to an actual initiative.
  • !Allowing opportunity stages to describe seller activity—‘proposal sent’—without buyer evidence or an exit criterion.
  • !Storing creator matches as unranked follower lists with no objective, brand-fit reasoning, availability, rights or economics.
  • !Logging meetings as notes but omitting decision, commitment, owner and next dated action.
  • !Letting each salesperson invent fields and stages until pipeline reports become incomparable.
  • !Automating outreach or stage changes from weak signals, creating spam, false forecasts and damaged relationships.
  • !Using the CRM as employee surveillance rather than shared commercial memory and a decision tool.
  • !Keeping stale personal data, unsupported gossip or irrelevant private information without a legitimate business purpose and retention policy.

Section 14

Brand CRM Readiness Checklist

Architecture

  • Accounts, contacts, opportunities and activities are separate linked objects
  • Buying-center hierarchy is defined
  • Creator matches and won-deal handoffs use stable links/IDs
  • System of record is named for each data type

Commercial process

  • Opportunity stages have buyer-evidence exit criteria
  • Required qualification and close-plan fields exist
  • Every open deal has a next action, owner and date
  • Won/lost/no-decision rules are explicit

Relationships and data

  • Buying committee roles and authority evidence are mapped
  • Account and opportunity ownership are clear
  • Consent/opt-out, access and retention rules operate
  • Duplicates, stale records and reassignment have workflows

Management

  • Weekly pipeline and monthly account reviews run in the CRM
  • Dashboard exposes action, stage, coverage and quality gaps
  • Forecast snapshots use evidence bands
  • Administrator governs fields, integrations and automation
SAIKO CRM RULE

The CRM is valuable when the next person can understand the relationship and make the next good decision.

Structure the account, map the buying committee, qualify the opportunity, explain the creator match, record the commitment, and assign the next dated action.

A contact list remembers names. A relationship system remembers how business actually moves.
SAIKO Agency Operations Playbook • MCN Guide #54
Ready to scale your creator strategy in China?
Explore All MCN Guides →