File types you can use
Format | Best for |
PowerPoint (.pptx) | Slide-based assets where layout and visuals matter — decks your team presents to or shares with customers. |
Word (.docx) | Document-based assets — longer-form, text-led content such as briefings and write-ups. |
Each project uses one template in one of these formats.
Example GTM use cases
Asset Builder works well for standardized content your team needs repeatedly across many accounts. For example:
PowerPoint
QBR decks — consistent quarterly business review templates populated with account-specific detail.
First-call decks — discovery-ready decks tailored to each prospect.
Account plans — structured plans that adapt to the target account.
Executive point-of-view on an account — a POV deck to present to a customer.
Word
Executive briefings — concise written briefings on a target account.
Solution positioning — how your solution maps to an account's priorities.
Account points-of-view — a written POV on an account or opportunity.
Asset Builder is designed for repeatable, standardized content that should look and read consistently across many accounts — not one-off, ad hoc documents.
Choosing what viewers provide when they request the asset
When you configure an asset, you set what your team needs to provide when they request it. This determines the account-specific context DatabookAI uses to fill in your content.
Option | What the viewer provides |
Account only | The viewer chooses an account, and the asset is generated using that account's data. |
Account + buyer | The viewer chooses an account and a specific buyer, and the asset is generated using data relevant to that account and buyer. |
This setting appears in the configuration summary while you're building the asset. See Mapping and reviewing content for where this fits in the setup flow.