A creator’s public profile may show what they publish and how they describe their work. It does not, by itself, track a brand inquiry, the status of negotiations, usage rights, draft approvals, or the date an agreement expires. Those details need a shared process if more than one person is involved.
That process does not require a platform marketed specifically for influencer management. A configurable customer relationship management system (CRM) can provide a record of contacts, opportunities, tasks, and decisions. But a general CRM is not automatically a creator-management product. The team has to define the workflow, verify that the software supports the required steps, and keep human approval where a decision affects the creator’s rights or reputation.
Start with the handoffs
Before adding fields or choosing a tool, trace one partnership from first contact to close. A campaign might pass through these handoffs:
- Someone identifies or receives an inquiry from a potential creator or brand.
- A responsible person checks whether the proposed campaign is relevant.
- The creator or authorized representative reviews the requested terms.
- The parties agree on scope, dates, payment, usage, and approvals in writing.
- The team coordinates production, review, delivery, and publication.
- The parties close outstanding obligations and decide whether another conversation is useful.
This is a working model, not a standard lifecycle. Some partnerships begin with a creator’s inbound request; others begin with an agency or brand. Product seeding, affiliate work, a sponsored post, and a longer licensing arrangement need different records. Add a status only when it corresponds to a decision or handoff your team actually uses.
A useful pipeline makes the next responsible person and the next action visible. It does not decide whether a creator is a good fit or whether the brand’s offer is acceptable.
Keep the first record small and traceable
A shared record should help the team continue the conversation without copying more personal information than it needs. Start with:
| Record | What to capture |
|---|---|
| Contact | Name or business identity and the public channel used |
| Source | How the inquiry or discovery occurred, with a link and date |
| Campaign question | What the brand or creator is asking to do |
| Decision owner | Who can approve outreach, terms, and publication |
| Current status | The last confirmed step and next action |
| Open terms | Deliverables, dates, payment, usage, exclusivity, or approvals still unresolved |
| Agreement reference | Link to the signed document or authoritative record |
A social handle, follower count, or profile description is not a substitute for the original source or an agreed term. If a metric is relevant, record its source and date and say whether it was provided by the creator or displayed by a platform. Do not turn a public statistic into a guarantee about reach, audience fit, or campaign outcomes.
Use separate fields for what you observed, what a party said, and what remains uncertain. For example, “the profile lists a business email” is an observation; “the creator wants a paid partnership” needs confirmation. This simple distinction makes follow-up more accurate.
Turn an Instagram visit into a research note
A profile can help an agency decide whether a conversation is worth starting, but the first review should produce questions rather than a score that pretends to measure creator quality. Record the public source and the date, then keep visible evidence separate from assumptions:
| Public signal | What to record | What it does not prove |
|---|---|---|
| Bio and profile category | The creator’s own description and any public business contact route | That the account’s audience or offer matches a campaign brief |
| Recent posts and formats | A few relevant examples, with links and dates | Permission to reuse the work or a promise of future deliverables |
| Audience or engagement figures | The displayed metric, source, date, and whether it came from the creator or a platform | Unique people, qualified reach, sales, or campaign performance |
| Contact path | The public channel the creator invites brands to use | Consent to receive repeated outreach on every channel |
A useful handoff note can end with three short fields: why this profile may fit the brief, which facts still need confirmation, and who will make the first contact. If a creator’s analytics matter to a decision, ask for the relevant data and its reporting period; a public profile is not an analytics export. Do not infer rights, rates, availability, or audience composition from the content alone.
Keep discovery proportionate. Use the profile and contact route as intended, limit the information copied into the CRM, and avoid unauthorized automated collection. Meta defines scraping as automated collection and distinguishes authorized from unauthorized collection that violates its terms; teams should use permitted tools and processes. Meta — Scraping by the Numbers
Configure pipeline statuses around decisions
A pipeline can use a small set of states such as “New,” “Needs review,” “Terms under discussion,” “Agreed,” “In production,” “Awaiting approval,” and “Closed.” The names matter less than the evidence required to move a card forward. “Agreed” should mean the authorized people accepted the terms, not that someone sent a positive message.
For each status, decide who updates it and what should happen next. A “Needs review” status might create a task for the person responsible for evaluating the brief. “In production” may require a deliverable and due date. “Awaiting approval” should identify the reviewer and the version they are reviewing. A status alone cannot confirm that a contract was signed or a payment was received; link to the source record or have a person verify the event.
Bolten’s published CRM documentation describes configurable contact fields and opportunity funnels. Its guide says contacts, tasks, and products can be connected to an opportunity card, and that a WhatsApp contact can be added to Contact Management when the WhatsApp integration is enabled. These are building blocks that may support a partnership tracker after configuration and testing. The documentation reviewed does not establish a dedicated creator-management module, so an agency should not promise creator-specific features based on the CRM description alone. (Bolten — Organizing the CRM)
Treat channel connections as dependencies
If the team plans to capture WhatsApp conversations inside a CRM, confirm how the connection works before making it central to the process. Bolten’s current FAQ lists two connection methods: QR-code connection (unofficial, with a stated risk of blocking) and the official WhatsApp Cloud API, which Bolten recommends for professional, continuous use. That is a material implementation detail. The agency and client should check the provider’s current setup, terms, account requirements, and charges, and maintain a permitted fallback for messages that do not appear in the CRM. Verify them again before implementation. (Bolten — Partner FAQ: WhatsApp integration)
Do not assume that an Instagram profile is the same as an Instagram messaging integration, a publishing calendar, or an analytics feed. Verify each feature in current product documentation and in the actual account. If a capability is not documented or has not been tested, label it as an open question rather than including it in a client promise.
Record the agreement, not just the campaign name
Before production starts, make sure the authoritative agreement identifies the parties, deliverables, deadlines, payment terms, review process, usage rights, exclusivity, and any extension conditions that apply. Store the document or its location; use CRM fields only as an index to the terms.
For rights and payment, a status field is a reminder, not enforcement. “Usage ends on [date]” does not prevent a brand from using an asset afterward. “Paid” should be confirmed against the transaction record, not inferred from a message that says payment is being processed. If the parties change the scope, record who approved the change and update the agreement as needed.
Keep the workflow practical. An operator may need tasks for sending a brief, collecting a draft, checking that the correct person approved it, confirming a publication link, and closing the campaign. A task should have an owner, a date, and a clear completion condition. No automated status change should accept a rate, grant a right, approve a claim, or publish content without the authorization required by the agreement.
Review outcomes without inventing performance
When a campaign ends, confirm delivery and outstanding obligations. Save final links or files only as permitted by the agreement. If the parties review performance, identify the source, time period, and meaning of each metric. A platform metric such as views or engagement is not automatically a business outcome for the brand or proof that the creator caused a sale.
The team can also review its own process: Were approvals clear? Did a handoff get missed? Could the creator find the current brief? Were rights dates easy to locate? These questions can improve coordination without claiming the pipeline increased revenue or prevented every missed opportunity.
A later campaign should start with a new conversation about scope and terms. A previous partnership can inform planning, but it does not guarantee renewal, set a new rate, or establish that the next campaign will perform similarly.
Limit access and document data roles
A partnership record may contain names, contact details, conversation summaries, and commercial terms. Give access only to people who need it, choose fields that serve a clear purpose, and agree who can export or remove records when the engagement ends.
Under Brazil’s LGPD, whether a party acts as controller or processor depends on the real processing arrangement. ANPD guidance distinguishes who determines the purposes and essential means from who processes data on another party’s instructions. Do not assign the role to the creator, agency, operator, or software vendor by assumption. Document the actual arrangement and seek qualified advice where the data use or relationship requires it. (ANPD — Guide to processing agents and data protection officers)
Be especially careful with integrations that send contact data to an advertising or analytics service. Verify which fields leave the CRM, why they are used, who authorized the transfer, and how the arrangement is documented. A convenient toggle does not settle those questions.
Build around the creator’s authority
The useful system is not the largest list of fields or the most elaborate funnel. It is a record the creator and authorized team can understand: what was requested, what has been agreed, who owns the next step, and where the source of truth lives.
Start with one workflow and a small set of records. Configure the CRM only for steps the team has defined, test the channel dependencies, and revise the process after it has been used. Keep the creator in control of decisions about their work and rights. An Instagram profile can begin the relationship; the operating system is the set of clear agreements and human handoffs built around it.
