Last verified: August 27, 2026
What You Can Now Do
Context Memo now gives you an Assets library on every brand page: one brand-scoped place to browse, upload, and manage the images and media tied to that brand. Before this, your media lived in three or four places at once, CMS uploads, a brand kit somewhere, one-off attachments stuck to a single memo or landing page. Now every generated asset draws from the same curated set, so a memo hero image and a paid ad mock pull from the same shelf. The task this changes: you stop hunting for the right logo file or screenshot before assembling a page, and you stop accepting the stock placeholder the builder reaches for when it can't find anything better.
Where It Is in Context Memo
Open any brand page and select the Assets tab. Images pulled during initial brand extraction are already sitting there: logos, favicons, hero images scraped from your site. Two related capabilities shipped alongside it and live in the landing page builder: scan-offers, which reads your positioning and public pages and surfaces the offers a buyer is likely to convert on, and conversion spine additions, which push those offers into the builder as recommended blocks with ad copy variants that reference media from the Assets library.
How to Use It
- Open the brand page and select the Assets tab. You'll see what extraction already captured from your domain. Review it first, because extraction pulls what your site exposes, not always what you'd choose.
- Upload the rest of your media. Drag-and-drop or bulk upload product screenshots, team photos, customer logos, campaign graphics. This is the set every downstream generation will draw from, so upload the approved versions, not the近 ones.
- Tag each asset. Tags are how the builder decides which image belongs in which block. Untagged media still lives in the library, but it gets picked less predictably.
- Run scan-offers on the brand. The scan reads your positioning and public pages and returns the offers a buyer is likely to convert on: free trials, audits, demos, gated resources. Check the list against what you actually sell today.
- Open the landing page builder and accept the conversion spine blocks. Recommended offer blocks appear with ad copy variants already referencing library media. Swap the image from the Assets picker if the pick isn't the one you want.
- Publish, then watch crawl and citation activity on the page. The signal to look for is whether the page gets crawled and cited with your visual identity intact rather than a generic template rendering.
Why We Built It
The complaint was consistent: "the page looks nothing like our brand." Operators would generate a landing page, get a stock photo and a placeholder hero, and then spend the next twenty minutes re-uploading assets they already owned, from a Slack thread or a shared drive, one file at a time. Offer blocks had the same problem in a different register. With no read on what the brand actually sells, the builder defaulted to a generic template CTA, which means the page shipped with an offer nobody on the team had approved. AI-generated content is only as good as the inputs it can reach. Siloed imagery and unknown offers produced pages that were fast to make and wrong to publish, and the rework erased the speed.
What It Does Not Do Yet
A few honest limits.
- Assets are brand-scoped, not shared across brands. If you manage several brands in Context Memo, you upload the shared media (an agency mark, a partner logo) to each brand library separately. There's no cross-brand asset pool yet.
- Tagging is a manual step. Extraction populates the library, but it doesn't classify what it finds. Nothing auto-tags a screenshot as a product screenshot. If you want predictable image selection in generated blocks, budget a few minutes to tag on the first pass.
- Scan-offers reads what's public. If an offer isn't visible on your site, the scan won't surface it. Offers behind a login, in a sales deck, or still in planning need to be added by hand.
- This is not a DAM or a CMS. The library holds the media that feeds AI-visible surfaces built inside Context Memo. It isn't version control, it isn't rights management, and it isn't a replacement for your marketing site's media handling. Keep your system of record where it is and treat the Assets tab as the curated subset that feeds generation.
- Asset choice in generated blocks is a recommendation, not a guarantee. The builder picks from tagged media. Review the picks before you publish, particularly on pages carrying a customer logo or a screenshot with product data in it.