Turn your product page into a useful content plan.

Start with what’s true.

Open your product page and write a short brief before writing a single hook. Keep the details a customer could check. Leave out adjectives such as “revolutionary” and promises you cannot demonstrate.

For your product, collect the name, three useful capabilities, who they help and the evidence you can show. If a detail is missing, ask the person who owns it. An empty field is better than a made-up claim.

Find the moment before someone needs your product.

A feature list tells you what exists. A customer moment gives you a reason to post. Write down what someone might be trying to do when the product becomes useful.

These are starting hypotheses. Replace them with language from your own support questions, sales conversations or comments as you learn what people care about.

Same product. Three different reasons to watch.

Give each post one job. A relatable problem can earn recognition. A demonstration can explain the product. A question can reveal what to make next.

Explore three treatments below. Each includes a hook, a shot list and a next step, so the idea is ready to brief rather than just save in a notes app.

ONE PRODUCT. THREE WAYS IN.01 / 03

The problem

The problemThe demonstrationThe question

Wall of text / ORIGINAL EXAMPLE BRIEF

“I had an idea for a video. Then I opened four different tools.”

Start with the work around the work: switching between tools before you have anything to show.

1. Film a simple desk scene with the hook on screen.
2. Cut to the creative task you were trying to finish.
3. Show Oakgen’s tool navigation, with private details hidden.

See the creative tools in Oakgen.

These are original example briefs; film or create your own product-specific footage.

Start with what you can show convincingly. Software often benefits from a focused screen recording; a physical product may need a close-up or a demonstration in someone’s hands. Match the format to the evidence.

Write the post. Then remove what you can’t prove.

Keep the hook close to the customer’s task. Follow it with something visible, then ask for one next step. Before you approve the draft, read every claim as if a customer asked you to back it up.

Check the recording against the current interface. If a feature takes several steps, show those steps or label the edit. Don’t turn a shortened demo into an implied speed guarantee.

Build a month with variety.

Choose several jobs for your content, then alternate them. Here’s a first week for the Oakgen example. Each row gives the next post a different purpose.

For the remaining weeks, revisit those jobs with a different feature, question or example. “Teach one step” could become a walkthrough of a video input, then a voice option. A question from week one can become a later demonstration.

Thirty ideas do not require thirty consecutive posting days. Choose a pace you can produce and review. Leave space to respond to useful comments instead of treating the plan as fixed.

Review the finished post, not just the idea.

Watch the export on a phone. A good brief can still become a video with unreadable captions, a missing product detail or an unclear ending.

• Claims match the product. Check feature access, limits and any numbers against current information.
• The evidence is visible. The recording shows what the hook promises, without exposing private data.
• The post works on a small screen. Read the captions, inspect the crop and listen to the audio.
• The assets are yours to use. Confirm rights for footage, music, voices and people shown.
• Someone owns the next step. Set a date, a timezone and a reviewer before moving it out of draft.

Use your chosen publishing tool if the account and format are supported. Otherwise, keep the calendar as your checklist and publish manually. A planned date is not a confirmation that a post went live.