Pinned Tweet
Last week was intense.
I’ve been working on my portfolio video and learned a lot from @vedu_boi
Trying to copy his style has actually taught me a lot about making smooth transitions.
Still have a long way to go.
Now I'm diving deeper into color theory since thats probably my weakest area right now.
Your competitor is winning customers you could have had.
Two saas products can solve the exact same problem.
But when someone visits their websites, one explains its value in 10 seconds, while the other takes a full page to explain what it does.
Which one do you think they'll remember?
People have limited time and attention.
Make it easy for them to understand what your product does and why they should care.
5
I made a mistake with a client that changed how I approach product videos.
A client wanted a video to explain their product.
So I started thinking about the visuals, animations, transitions, and how to show the different features.
I put everything together and made the product look good.
But there was a problem.
The video wasn't communicating what the client actually wanted people to understand.
I had focused so much on showing the product that I missed the main message.
Thats when I realised I needed to change my process.
Now, before I even open after effects I ask:
Who are we making this video for?
What problem does the product solve?
What should viewers understand after watching it?
Once these are clear, I move on to the script, storyboard, and animation.
Because a video can look great, but if it doesn't communicate the right message, it hasn't done its job.
1
29
Your product does the same thing as a competitor. What makes it different?
Imagine two saas products solve the same problem.
Both have similar features. Both promise to save time.
You could make a list of features to compare them.
But that doesn't always help buyers understand the difference.
Here's how I'd show it in a comparison video:
1. Start with one common task.
Show a problem both products are designed to solve.
2. Show product A.
Walk through how a user completes that task. Highlight the steps involved.
3. Show product B.
Use the exact same task. Let viewers see how your product handles it.
4. Highlight the difference.
Maybe your product takes fewer steps, removes manual work, or offers a simpler workflow.
Now buyers can see the difference for themselves.
Don't just tell people why your product is better.
Give them something they can actually compare
2
46
Your demo might be showing too much and selling too little.
Imagine a potential customer starts watching your demo.
You open with a long company introduction.
Then you explain every feature, show different settings, and walk through multiple screens.
A few minutes pass, but the viewer still doesn't know how your product helps them.
Here's a simple structure that makes a demo easier to follow:
Start with the problem. Show a challenge your target customer faces.
Introduce the solution. Show how your product helps solve it.
Walk through one workflow. Let viewers see the product in action.
Show the result. Explain what becomes easier, faster, or better.
Give viewers a reason to care before asking them to watch how everything works.
A good demo should make buyers want to see more, not make them work to understand your product.
15
Stop listing features. Show what changes.
Imagine your saas product automates invoice processing.
You could say:
"Automate invoice processing with AI."
Sounds good. But what does that actually change for the customer?
Heres how I'd show it in a product video:
1. Show the old way.
Someone opens an invoice, copies the details, and enters everything manually.
2. Introduce your product.
Show the invoice being uploaded to your software.
3. Show the change.
The details are extracted automatically and added to the right fields.
4. Show the outcome.
No more copying numbers. No repetitive data entry. Less time spent processing invoices.
See the difference?
You're not just showing people what your software does.
You're showing them how their work could change after using it.
Thats what makes a product easier to understand and its value easier to see.
32
A feature nobody discovers might as well not exist.
Imagine your team spends weeks building a new feature.
It solves a problem your customers have been asking about.
You finally ship it.
You add it to your changelog and announce it on social media.
But most users never find it.
They keep using the old workflow because they don't even know there's a better way.
So the feature sits there, waiting to be discovered.
Help users find what's new.
Show them where the feature is, how it works, and what they can do with it.
Building something valuable is only half the job.
People need to discover it to experience its value.
1
23
If your saas sounds like five other products, you have a positioning problem.
Visit five saas websites.
You'll probably see the same phrases everywhere:
"All in one platform."
"AI powered workflows."
"Seamless collaboration."
"Save time and boost productivity."
Now imagine a potential customer visiting all five websites.
How are they supposed to remember yours?
If every product sounds the same, people have no clear reason to choose one over another.
Tell people who your product is for.
Show them the problem you solve.
And explain what makes your approach different.
Your customers shouldn't have to guess why they should choose you.
1
36
Complex integrations don't need complicated explanations.
Imagine your saas product connects with slack.
Your website says:
"Seamless, realtime integration with slack."
But what does that actually mean for your customer?
Instead of explaining it with more technical words, show them.
Start with someone switching between your product and slack to share updates.
Then show your product connecting to slack.
A task gets completed in your product.
And a notification appears in Slack automatically.
No manual updates. No switching between tools.
Now the customer understands what the integration actually does.
Sometimes, one simple visual flow can explain what a whole paragraph of technical copy can't.
26
Your best feature could be pushing users away.
Imagine a user opens your saas product to try a new feature.
They see dozens of settings and customisation options.
They don't know where to start.
So they click around, trying to figure things out.
But the more they explore, the more confused they get.
Eventually, they give up and leave.
Your feature could solve their problem perfectly.
But they never get to experience it.
Make the first step simple. Show users what to do. Let them discover the advanced options later.
The easier a feature is to use, the sooner people can see its value.
1
28
Your first five minutes after signup can lose a new user.
Someone finally signs up for your saas.
They're excited to try your product, so they open the dashboard.
But there are 12 menus, 30 buttons, and several options they don't understand.
They start clicking around, trying to figure out where to begin.
A few minutes later, they still haven't experienced what your product can actually do.
And thats where things go wrong.
A new user shouldn't have to figure everything out on their own.
Show them where to start. Guide them through one useful workflow. Help them reach their first small win.
The sooner users experience the value of your product, the more reason they have to keep using it.
2
2
76
Don't make people guess what they're paying for.
Imagine someone visits your website for the first time.
They go through your homepage, check out a few features, and then click on pricing.
But they're still trying to figure out:
What does this product actually help me do?
How will it make my work easier?
Why should I pay for it?
Now they're looking at your pricing without fully understanding the value of your product.
Before someone reaches your pricing page, they should already know what problem you solve, how your product helps them, and what they get out of it.
Your pricing page should help them decide which plan fits their needs.
It shouldn't be the first place where they understand why your product is worth paying for.
2
47
Your product is getting better. But does the market know?
Your team is shipping improvements every week.
You're adding new features, fixing problems, and making the product better for your customers.
You announce these updates in your changelog.
Your existing customers might notice them.
But what about someone discovering your product for the first time?
They visit your website and see the same old screenshots, features, and messaging.
They have no idea how much your product has improved.
And thats the gap.
You're building a better product every week, but the market is still seeing the old version of it.
Give people a reason to take another look.
Show them whats changed and how it makes their work easier.
25
You shipped a new feature. Your users are still doing things the old way.
Imagine your team just added bulk editing to your saas product.
Before, users had to update 50 records one by one.
Now, they can select all 50 and update them in seconds.
You announce the feature in your changelog and send an email.
But a week later, users are still editing records one at a time.
Why?
Because most of them never discovered the new feature.
Heres how you can help users find it:
- Show a small in app announcement when they open the relevant page.
- Add a tooltip near the new feature.
- Update your onboarding to include the new workflow.
- Create a short demo showing how it works and when to use it.
Don't just tell users what you've shipped.
Help them discover where it is, how it works, and how it makes their work easier.
2
1
78
How to create a feature video when your feature has too many settings.
Lets say your saas has a feature with 10 different settings.
You could try showing all of them in one video.
But your viewers would probably struggle to understand what actually matters.
So heres how I approach it:
Start with a use case.
Show what the user wants to achieve with this feature.
Pick the settings that matter.
You don't need to explain every option. Only show the ones needed to complete that use case.
Show them in action.
Walk through the workflow so viewers can see how each setting affects the result.
Show the outcome.
Let them see what they can achieve with those settings.
The goal isn't to explain every setting in your product.
Its to help users understand what they can do with it.
1
2
27
You're asking people to trust a product they've never seen working.
You tell them what it can do, how it saves time, and why they should use it.
But they're still left wondering...
"Okay but......how does it actually work?"
So instead of explaining everything, show them a real workflow.
Let them see how a task starts, how your product handles it, and what the final result looks like.
Its much easier to trust something when you can actually see it working.
1
24
Your competitor just got attention for a feature you've had for 6 months.
You built it weeks ago, shipped it, and moved on to the next thing.
Because well........the work was done.
But your competitor decided to make a big deal out of their launch.
They talked about what it does, and people started sharing it.
Now everyone's talking about their new feature.
And you're wondering how they got all that attention for something you've had for months.
You both built the same thing.
But they did a better job of showing people why it matters.
21
I worked with 3 founders, and all three had the same problem.
They knew their products were great, but explaining them was harder than they expected.
The first founder wanted to show every feature in his launch video.
But the script kept getting longer.
So we focused on one problem his product solved.
The second founder had a technical product.
But explaining how everything worked made the video difficult to follow.
So we simplified the story and showed the product through a real use case.
The third founder had several use cases to show.
But trying to fit them all into one video made the message confusing.
So we picked the one that mattered most to his ideal customer.
Three founders. Three different products.
But one common lesson:
You know your product inside out. Your customers are seeing it for the first time.
Your video needs to make that first experience easy to understand.
20
How to make a demo work for both technical and non-technical buyers
Imagine you're showing your product to a company.
The manager wants to know how it will save their team time.
The IT person wants to know how it works, what it connects with, and whether its secure.
Both are watching the same demo, but looking for different answers.
So how do you keep both interested?
Heres how I structure it:
1. Start with a problem they both understand.
Show a real problem the team faces. Keep the explanation simple.
2. Show how your product solves it.
Walk through one real workflow. Let them see the product in action.
3. Add the technical details.
Show the integrations, settings, permissions, or features that technical buyers need to evaluate.
4. Connect it back to the result.
Show how the workflow helps the team save time, reduce manual work, or get better results.
The key is to give each buyer the information they care about without making the other feel lost.
Show the value first. Then give them the details they need to trust it.
31
Your best feature could be driving customers away.
Imagine a user opens your product to try your latest feature.
They click around, see too many options, and don't know where to start.
After a few minutes, they give up.
Your feature could solve their problem, but they never get to experience its value.
Sometimes making a feature easier to understand can make all the difference.
1
33
If your saas sounds like five other products, people won't remember yours.
"All-in-one platform."
"AI-powered workflow."
"Seamless collaboration."
These phrases could describe hundreds of products.
Your customers shouldn't have to guess what makes your product different.
Be clear about:
Who your product is for.
What problem it solves.
How it helps people solve that problem.
The more clearly you explain your value, the easier it is for people to remember why they should choose you.
2
2
37


