How to make account-specific creative without making up the account

Build account-specific creative by turning a sourced account brief into a visual explanation of one relevant offer. Write the brief first, choose an image or short video, then review it in the landing page or ad where it will appear. Keep the account's verified facts separate from your proposal. That prevents a personalized page from quietly inventing a customer relationship, business problem or endorsement.

A useful first batch is ten accounts and ten hero images. The batch tests whether you can produce ten accurate, reviewable proposals within a budget. It does not, by itself, prove that personalization increases conversion.

Make the account brief inspectable

Each brief needs an account ID, official domain, relevant product or service, intended reader, source URLs and capture date. Add a separate field for the proposed offer and another for the visual idea. “The company offers fleet maintenance” can be a sourced fact. “Its operations team needs our scheduling product” is a hypothesis for the campaign.

Keep the evidence short enough for a reviewer to check. Firecrawl's scrape documentation describes extracting page content as Markdown or structured data. Save the supporting passage as well as the URL; a company homepage can change between research and review.

Stop before generation when the account has no relevant use case, the source is ambiguous or the proposed visual depends on invented results. Also record which reference assets you may reuse. Reading a product page and licensing its photography are separate decisions.

Choose a visual that explains the offer

Consider a hypothetical scheduling vendor approaching a fleet-maintenance company. A hero image could show an illustrative workshop schedule with an obvious place to request a service slot. Keep the interface generic unless the account has provided its real workflow. Label the result as a concept so the recipient can judge the proposal without mistaking it for a screenshot of their systems.

Use the same creative structure across the first batch, changing the documented use case. For example:

Create a hero illustration for a proposed fleet-maintenance booking page.
Audience: An operations manager comparing scheduling workflows.
Show a workshop calendar and a simple service-request path.
Use the approved palette and supplied reference assets only.
Leave open space for a headline and a real HTML call-to-action button.
Do not invent customers, performance numbers, badges or endorsements.
Keep all people fictional. This is a concept for discussion.

Write the headline separately. You can then correct a service name without paying to regenerate the background, and the button remains an actual page control. Review the crop at mobile size before accepting the image. If the concept will also appear in outreach, follow the email image and message checks before sending it.

Match the model to what must stay accurate

An abstract workflow illustration, a face and an exact product photograph pose different requirements. For text-heavy material, retain text in the page or design layer. For a product, inspect shape, labels and colors against the input. Use people only when the brief needs them, and avoid implying that a real employee participated.

Provider documentation helps identify eligible endpoints. For instance, fal's image-editing API accepts reference images, while its Kling v3 Pro image-to-video endpoint exposes duration and audio controls. Neither page establishes which model will preserve your particular product best. Test representative source material and record the exact variant.

Keep five-second video as an optional second step for an accepted still. Give it one motion, such as a restrained camera movement, and inspect the entire result. Do not animate a business metric or product function that the source material cannot support. Use the personalized-video cost calculation to decide what the extra production would need to earn back.

Cap production before submitting the batch

Give each account a cumulative production allowance and the whole batch a separate ceiling. For illustration, a $2 account allowance and a $20 ten-account ceiling are hypothetical policy settings, not provider quotes. Include research, rendering and any permitted retry in the plan.

Use Vaaya to obtain the current service call and set its max_cost_cents; the tool reference documents this per-call control. Maintain the account and campaign totals in the workflow. Reserve pending spend before launching concurrent jobs, and stop when the next permitted call would exceed the remaining allowance.

Store the source brief, prompt, output, quote, reported charge and review decision together. If an image fails because it depicts the wrong service, fix the brief before retrying. A second model cannot correct missing account research.

Review the placement and measure the response

A reviewer should see all ten variants alongside their sources, then open each landing or ad preview. Check text, crop, accessibility, factual claims and the destination link. Require human approval before publishing a page, launching an ad or sending a message; approval to produce creative covers only production.

Assign stable account, campaign and variant IDs. A suggested event sequence is creative_viewed, cta_clicked and qualified_reply, with the latter recorded from the approved outreach system. PostHog's event-capture documentation explains recording events with properties. Use pseudonymous IDs and keep recipient details out of public reports.

Clicks show interaction, while replies need review to establish whether they address the offer. Compare outcomes within equivalent audiences and a fixed observation window; ten different accounts are not ten interchangeable test cells. Keep these campaign observations in the authorized team's workspace. Publish examples of the creative and production method only with the required permissions, and leave response claims out until the evidence supports them.

Questions

What should change in account-specific creative?

Change the visual explanation to fit a documented use case, buyer role or product. Keep claims grounded in source material. Adding the account's logo alone does not establish that the offer is relevant.

Which image model is best for account-based marketing?

Test the exact model and settings against the asset's requirements: product fidelity, faces, layout and text. Provider features narrow the candidates, but your own representative outputs determine whether a model is suitable.

Can ten account variants prove a conversion lift?

Ten variants can validate the production and review process. Different accounts bring different audiences, so raw click or reply rates do not isolate the creative's effect. A causal comparison needs a suitable experimental design and enough observations.