The AI Content Builder works best when you give it real source material. This guide explains the 3 source types, their limits, and how to pick the right one.
1. Why sources matter
Without a source, the builder writes from your prompt alone. With a source, it writes from your actual calls, content, and research.
This is the difference between a generic draft and one your team can use.
2. The 3 source types
Click Add context sources in the AI Content Builder panel.
| Source | Use it for | Limit |
|---|---|---|
| Transcripts | Turning a customer call into a battlecard, a recap, or an objection guide. | 1 transcript |
| Spekit | Keeping new content consistent with what you already published. | No stated limit |
| Web | Public information Spekit does not hold, such as a prospect's funding news. | 1 web source |
3. Attach a call transcript
- Open a Spek.
- Click Add context sources in the AI Content Builder panel.
- Click Transcripts.
- Search your calls, or pick one from Recent calls.
- If the call is not listed, click Upload transcript and choose your file.
- Write your prompt and press enter.
ℹ️ Note: You can attach 1 transcript at a time. Synced call recordings appear in the list automatically. You can also upload a transcript file from another tool.
4. Attach existing Spekit content
- Open a Spek.
- Click Add context sources.
- Click Spekit.
- Search, or pick from Recently viewed by you.
- Write your prompt and press enter.
💡 Pro Tip: Attach an existing Spek when you want the new content to match its structure or wording. Say so in the prompt, for example "follow the same format as the attached Spek".
5. Add a web source
- Open a Spek.
- Click Add context sources.
- Click Web.
- Type a search term or phrase.
- Click Add. Spekit searches the web and adds what it finds to your sources.
- Write your prompt and press enter.
ℹ️ Note: You can add 1 web source at a time.
6. Prompt examples
Attaching the source is only half the job. Tell the builder what to take from it.
From a call transcript
| Goal | Prompt |
|---|---|
| Discovery recap | Extract the top 3 pain points the prospect mentioned and draft a discovery recap for this account. |
| Deal risk | Find any budget or timeline mentions. Draft a deal risk summary highlighting red flags. |
| Next steps | List every commitment made by both the rep and the prospect in this call. |
| Objection handler | Find where the rep was asked about pricing. Rewrite their answer into a pricing objection handler for the team. |
| Knowledge gaps | Identify any question the rep could not answer, and write the answers for the next call. |
| Competitive insight | The prospect mentioned [competitor]. Based on their comments, draft a competitive section on why our product won them over. |
From Spekit content
| Goal | Prompt |
|---|---|
| Combine sources | Using the attached roadmap and pricing sheet, summarize how the upcoming features support the Q3 price change. |
| Match the tone | Compare this draft to the attached brand voice guide and rewrite the intro to match it. |
| Technical accuracy | Using the attached security whitepaper, update the data privacy section so it is accurate. |
| Build a comparison | Using the attached battlecard, create a short comparison table for a prospect. |
7. Best practices
How you choose and use sources decides how useful the first draft is.
| Practice | Why it matters |
|---|---|
| Attach the source before you prompt | The builder uses what is attached when you press enter. Attaching after does nothing. |
| Pick the most specific source you have | 1 relevant call beats 3 vaguely related ones. |
| Say what to take from it | "Pull the top 3 objections from the attached call" works better than "use this call". |
| Point at a moment in the call | "Find where the rep explained pricing" gives a sharper result than a whole-call summary. |
| Check the output against the source | The builder can summarize a call inaccurately. Read it before you publish. |