PricingDesign around a customer milestone
Choose the next result the customer needs: importing their first file, finishing a setup or finding a useful report. Begin from a state they recognize and show the result they should reach. A tour of every menu often obscures that first success.
Choose the stage of onboarding
| Moment | Source material | Successful delivery |
|---|---|---|
| First use | A current recording of one complete task | The customer can reproduce the result. |
| Feature adoption | A real example of the feature solving a problem | The value and required action are both visible. |
| Account handoff | An approved explanation of next steps | The right contact and action are stated accurately. |
| Product change | New screen footage and release wording | No old control or unsupported behavior remains. |
Try a first-success brief
Create a 35-second onboarding video from my product recording. Start from the new-user screen, show the three actions in my notes and hold on the completed result. Use the recorded explanation and readable captions. Keep the account and example data anonymous. End with the next action exactly as supplied. Make no claims about automatic integrations that the recording does not show.
Separate a reusable lesson from account details
Use safe demonstration data for a video intended for many customers. If an account needs different instructions, create a separate reviewed version rather than adding private details to the shared master. Store the final file in the system that manages customer access.
Keep ownership after publication
Assign someone to review the video when the underlying workflow changes. Retain the source, brief, approved MP4 and product version. Shorty edits and renders the file; your customer-success platform remains responsible for delivery, engagement tracking and follow-up.
How to evaluate the workflow
Run one representative edit through its first feedback round before planning a larger rollout. Save the brief, the first output, the revision and the approved file. Record upload time, processing time, review effort and charged credits separately. A fast first render is only useful if the result can be approved.
The workflow below is a suggested use of Shorty, not a customer case study. The linked browser test shows a real product edit and timing revision; it does not establish results for every type of team or footage.