Start with the mental model.
The opening line makes the product premise plain before showing interface details.
← Back to selected work
Sley case study
A launch video that made an AI computer feel credible, useful, and product-led.
Sley needed a first impression that avoided the usual flashy AI-demo energy. The work was to turn a simple hook, product UI, motion restraint, and brand reveal into a B2B launch asset people could understand quickly.
Proof
The proof is the actual 58-second launch video, not a description of one.
The video shows a clear narrative: text hook, product name, UI walkthrough, app/channel surfaces, final message, and CTA.
Embedded portfolio proof: the actual Sley launch video file from the local chat cache, copied into public preview assets.
58sLaunch-video runtime, enough to show hook, product, proof surfaces, and CTA.
12Frames extracted into portfolio assets for visual proof and auditability.
1Solo owner for direction, feedback, and final shipping judgment.
B2BRestrained visual direction instead of generic AI hype or over-motion.
SignalThis is strong proof of creative direction because it shows taste under constraints: what to emphasize, what to cut, how to pace product UI, and when the launch asset feels ready.
Frames
The narrative is visible frame by frame.
These stills prove the video was structured around comprehension, not just motion.
Name the product clearly.
The product name gets a quiet reveal instead of being buried under visuals.
Show the ask-to-action loop.
The UI shows the product responding to a described task, which supports the hook.
Make work visible.
The board view shows that Sley is about operating work, not only chatting.
Prove connected surfaces.
Slack and Telegram-style channels communicate practical workflow reach.
End with the payoff.
The final line turns the product into a simple promise: stop managing, start talking.
What I paid attention to
Most of the work came down to a handful of small choices.
What should land first, how long to stay on the product, and when the video was ready to leave alone.
Start with one clear line.
“If you can describe it” gave me a simple way to introduce Sley before showing the interface.
Let the product explain itself.
I moved from the assistant to the work board, apps, and channels so people could see what Sley actually does.
Keep the type out of the way.
The product already had a lot to explain, so I avoided effects that would compete with it.
Stop before it felt overworked.
This needed to help with a launch, not turn into a motion-design showreel.
End with the next step.
The final card simply says the whitelist is open and gives people somewhere to go.
Use AI, then edit like a person.
AI helped with production. The pacing, cuts, copy, and final call were still mine to make.
Why this project matters
It is a small project, but it shows how I work when the product story is still taking shape.
I found a simple way into a technical idea, worked through the details, and shipped something the team could actually use for the launch.
Story firstOne clear opening line before the interface appears.
Product on screenEnough of the UI to make the promise believable.
Calm visual directionNo extra effects fighting for attention.
A finished launch assetNot a concept or storyboard, but the video the team used.