kakinang INSIGHTS · 2026-10-03
Only have a PDF media kit? How can brands find collaboration details quickly?
A brand manager on a phone may not open a long PDF. AI Help me outline a public creator media-kit FAQ can answer from approved public material, while the creator confirms each deal.

Separate public facts from private terms
Mark every page of the kit as public, available on request, or internal. Put platforms, formats, audience data with measurement dates, and approved examples into short text answers. Keep private contacts, unconfirmed availability, and negotiable rights out of automatic answers. A PDF remains useful for download, but a readable page makes the essentials accessible immediately.
Start with ten recent collaboration emails or direct messages and copy the questions brands actually used. Common first-round questions cover audience location, current performance, excluded topics, formats, draft review, and publication process. Split answers into durable public facts and volatile facts. Portfolio links and formats may be stable; follower counts, average views, availability, and minimum budgets need an as-of date. If a metric comes from one platform dashboard, identify that platform, period, metric definition, and whether it reflects organic activity. One viral post is not the average account result. Say what a portfolio example delivered rather than inventing a sales uplift. If a number must stay private, say recent statistics are available after the campaign goal is understood. Give the page a three-sentence opening about the audience, main format, and good-fit partnerships, then use the wording a brand would use for questions such as buying content without an account post. This is editorial work, not a PDF conversion task.

Test the questions a brand actually asks
Publish a collaboration page and bind its approved facts to the kakinang knowledge base. Test questions about short video formats, delivery deadlines, and paid ad usage. The first may be answerable from public facts; deadlines and rights require a human check. Request brand, product, intended use, and preferred date before a follow-up, and check the mobile page and media-kit link.
Build a test sheet with the real question, the approved public answer location, the AI result, and the human decision boundary. Cover formats, excluded industries, portfolio, pricing conditions, dates, licensing, payment process, and contact route. Ask each question in several natural ways, such as 'What does a short video cost?' and 'Do you have a fixed Reels package?' The answer should flag an individual quote when the scope is unknown. Negative tests can ask for a private phone number, undisclosed client names, or guaranteed reach; the correct route is an honest limitation and a public contact method. A chat button needs surrounding visible text explaining why details are requested and who will respond. Collect only a contact, brand, reply address, goal, and desired timing for the first handoff, and do not ask again for facts already supplied. Use fictional proposals for testing rather than past clients' confidential terms.

Keep one current source of truth
Assign an owner and review date to each public claim. Update the page and knowledge source together when audience figures, prices, or terms change. Check the last successful sync and any error in the console before assuming new facts are live. Sample real inquiries monthly and add answers only when they can safely be public. The objective is a faster, clearer first conversation, not an automatic agreement.
Maintain a change list. Review audience figures when a new report arrives, add a case only after permission, and update excluded industries and contact routes when policy or staff changes. Record who checked each update, the evidence, and effective date, especially for prices and licensing. If the old page promised three revision rounds but the new package has two, updating only the downloadable PDF leaves the chat knowledge stale. Check the page, knowledge source, and download together. If a crawl is still processing or failed, use the last known answer and let a person explain the change. Each month, choose repeated visitor questions that are poorly answered and publish only the answers safe to share. Do not add pages merely to increase page count. Evaluate whether a brand finds accurate facts, whether a lead contains a usable brief, whether staff must re-ask basics, and whether outdated copy caused misunderstandings. Page views and chat counts alone do not show a better collaboration experience.
Before uploading any PDF, make a separate public copy and remove private phone numbers, client personal data, unpublished rates, and confidential contract terms. Do not assume file text receives automatic personal-data masking: even an appendix may be extracted for search. Review every page, table, and image before an owner approves upload. Keep detailed audience reports and case-specific quotes for verified contacts. Check portfolio links as an unfamiliar visitor every quarter: a once-public post may now be private, a case page may have been removed, or a download may fail. Review translated terms with someone competent in that language before they appear to grant rights. Show a last checked date and clarify which figures are current public facts and which are only a starting point for negotiation.
Questions teams ask
Can I upload the PDF without editing it?
You can use it as a source, but verify extraction, public scope, and currency; give critical facts a readable page.
Should I publish a rate card?
Publish a range if useful, and flag that scope, licensing, and timing require confirmation.
Can AI accept a collaboration?
It can collect requirements and explain approved facts; the creator should accept the terms.
How do I evaluate the page?
Test real brand questions and check whether inquiries contain enough context to answer.
Sources and further reading
- How To Create an Influencer Media Kit: Steps and What To Include — Shopify
- Creating Helpful, Reliable, People-First Content — Google Search Central
- Ecommerce Customer Service: Guide and Best Practices — Shopify