Asset Builder is designed for customer admins — for example RevOps, Product Marketing, Sales Ops, or Business Value teams — who create standardized content for their go-to-market teams.
​

No. You work with familiar PowerPoint and Word files. When you upload a template, Databook automatically maps the most relevant content to it, and Composer guides you through reviewing and refining the result — no manual setup required.
​

No. Start from an existing deck or document, or create a first draft however you like — including with tools such as Claude or Gamma. You then turn that draft into a template by marking the parts that should be filled in automatically with placeholders.
​

PowerPoint (.pptx) and Word (.docx). Each asset uses one template.
​

A placeholder marks a spot in your template that should be filled in automatically. You add one by typing a short, descriptive name inside double curly braces — like {{company overview}} — where you want the dynamic content to appear. A clear name helps Databook map the right content to it.
​

Placeholders are flexible. Depending on how you use them, Databook can fill a placeholder with a block of text, a set of bullet points, a numbered list, a full table (adding or removing rows as needed), or a dynamic image set through the image's alt text (for example {{company logo}}).
​

No. Slides and sections with no placeholders are kept exactly as you designed them — Databook only fills in the spots you've marked.
​

Check that it uses the {{ }} format exactly. A mistyped placeholder won't be recognized.
​

You may lose your placeholder mappings, industry targeting, and other configuration. Where possible, edit your existing file instead of replacing it. Asset Builder warns you before you replace a template.
​

When you upload your template, Databook automatically maps the most relevant content to each placeholder. You then review and adjust the mappings using Composer, the AI assistant in the asset builder — describe the change you want in chat and it updates the content for you.
​

Yes. Databook generates account-specific content each time the asset is requested, so it adapts to the target account automatically.
​

Yes. As you configure, you can ask Composer to generate a preview and choose an account for it to preview against. When everything is configured, generate a full preview and open the full-deck view to review the whole asset end to end.
​

You choose whether the people requesting the asset need to provide just an account (Account only) or an account and a specific buyer (Account + buyer). This determines what context Databook uses to generate the content.
​

When you're ready, choose Set Live. This opens a short confirmation step where you finalize how the asset is published and make it available to your team.
​

Yes. You can save a project as a draft and return to it any time — it appears in your asset list with a Draft status. Your work isn't saved automatically — a save banner appears while you have unsaved changes, and the builder warns you before you leave the page.
​

You control who can access the asset when you set it live.
​

Assets that are live show an Active status and appear in the list of assets your users can request in DatabookAI. You can also copy a shareable link from the confirmation screen and send it to your team directly.
​

Yes — reopen the project in the asset builder, make your changes, and set it live again.
​

Yes. Asset analytics let you track how often each asset is downloaded and which sellers are using it, so you can see what's driving value for your team.