Product DNA to Ready: a practical HiggsCat workflow

The answer

Provide a product link or description, review and confirm the Product DNA, then choose and edit a proposal in Swipe. Save starts a render job. Download from your private Library when the job is Ready. Reviewing a preview and completing an export are different steps.

This is a source-checked workflow guide dated 28 September 2026, not a newly generated video demonstration. Access and action availability depend on your workspace and allowance.

Social media for SaaS: a week of posts from one product feature →

1. Confirm facts before choosing a story

Use a website, App Store or Google Play link. If source information is missing, supply a description and review the draft. Correct the audience, product purpose and supported benefits before confirming. A proposed claim is not evidence just because it appears in a draft.

Confirmed Product DNA is versioned. A changed product needs a new reviewed version; do not assume earlier saved compositions change automatically.

2. Review the proposal as a viewer

Current daily proposals combine activity videos and five-photo carousels. Check the hook, readable text, relevant visual and caption. Use the available editing or text-remix controls and review the result before Save. Reference posts in Viral are inspiration, not a library of footage to download.

• Can a viewer tell what the product helps them do?
• Does the visual demonstrate the written claim?
• Is every assertion supported by your confirmed facts?
• Can you read the text comfortably on a phone?

3. Save once, then follow the job

Save reserves an export and creates a job for that composition. The job can be queued, rendering, Ready or failed. Repeating Save for the same candidate reuses its job; it does not create another successful export. A validated Ready result uses one allowance slot. A terminal failure releases the reservation.

The trial is seven days with three completed standard creatives. Your workspace shows the actual dates and remaining allowance. A reload or download does not replenish the trial. No general generation time or cost is promised here.

4. Retrieve the actual files

An activity export provides an MP4 and caption. A carousel ZIP contains five 9:16 images and five 4:5 images, plus a caption and manifest. Check the downloaded file before using it. These are output aspect ratios, not a claim about every platform's current recommended dimensions.

Ready files belong to the signed-in owner and remain readable after the entitlement expires. A Ready result is not automatically a published social post. Availability and acceptance of social channels are shown separately in Accounts.

Worked planning example — not generated media

Example brief: a small team wants to show how a product turns confirmed facts into a reviewed content proposal. Show the draft fact, the owner's correction, the chosen proposal and its final file check. This is a suggested demonstration structure, not a recording of an executed session.

• Input: one product description, one audience and a benefit you can demonstrate.
• Review: replace an unsupported promise with a factual, visible action.
• Output check: the right words, readable framing and a file that opens.
• Next step: use the free shotlist to plan your own evidence, then perform the steps in your workspace.

Method and limits

Prepared from the current Starter interface and its Save, rendering and download contracts. Existing historical acceptance supports the core flow; this page does not claim a fresh provider run. No customer prompt or private customer file is used. The planning example does not prove engagement, sales or generation quality.

Continue with a useful next step