Source: https://polysh.io/use-for/

ONE WORKSPACE. MANY USEFUL HANDOFFS.

# You know the work.  Help someone else  do it.

From a first customer session to an internal procedure, Polysh turns what you know into something people can watch, read, and follow.

[Request access](https://polysh.io/contact/)[Find your use case](#customer)

A WALKTHROUGH THAT WORKS TWICEVIDEO + GUIDE

## Show it. Explain it. Leave the steps.

Workspace members

Workspace Members Invitations

1. 01
  **The video**     A narrated explanation for seeing how the workflow works.

2. 02
  **The guide**     Steps and screenshots for doing the task yourself.

3. 03
  **The handoff**     Share the format your audience needs next.

*Illustrative workflow. Sample content, not a product screenshot.*

CUSTOMER TEAMS

## For the people who help customers

Explain the feature, guide the first session, and answer the next question.

### [Product demos](https://polysh.io/use-for/product-demos/)

Introduce a feature with a focused demonstration and a guide for trying it.

[See the workflow](https://polysh.io/use-for/product-demos/)

### [Customer onboarding](https://polysh.io/use-for/customer-onboarding/)

Show the shortest path from a new account to the first useful action.

[See the workflow](https://polysh.io/use-for/customer-onboarding/)

### [Customer support](https://polysh.io/use-for/customer-support/)

Turn a clear troubleshooting explanation into an answer you can reuse.

[See the workflow](https://polysh.io/use-for/customer-support/)

INTERNAL TEAMS

## For the people who keep work moving

Make your internal know-how easier for the next person to follow.

### [Employee onboarding](https://polysh.io/use-for/employee-onboarding/)

Help a new teammate follow the internal tasks that come with a new role.

[See the workflow](https://polysh.io/use-for/employee-onboarding/)

### [SOP documentation](https://polysh.io/use-for/sop-documentation/)

Capture the procedure, the prerequisites, and the result someone should check.

[See the workflow](https://polysh.io/use-for/sop-documentation/)

### [Training videos](https://polysh.io/use-for/training-videos/)

Give the learner a narrated lesson and a reference for putting it into practice.

[See the workflow](https://polysh.io/use-for/training-videos/)

PRODUCT TEAMS

## For the people who explain the product

Show a complete task or leave the useful part of a demo behind.

### [Software tutorials](https://polysh.io/use-for/software-tutorials/)

Explain one complete software task from the starting screen to the result.

[See the workflow](https://polysh.io/use-for/software-tutorials/)

### [Sales enablement](https://polysh.io/use-for/sales-enablement/)

Leave the workflow your buyer needs to share with the person who missed the call.

[See the workflow](https://polysh.io/use-for/sales-enablement/)

CHOOSE THE FORMAT FOR THE MOMENT

## Seeing the task and doing the task  need different things.

Start with the same screen recording. Create the output that helps your audience take the next step.

### A narrated video

For introducing a feature, showing a sequence, or explaining the choices along the way.

[Explore narrated videos](https://polysh.io/products/narrated-videos/)

### A step-by-step guide

For following along, checking a result, and finding one action without searching through a recording.

[Explore guides](https://polysh.io/products/step-by-step-guides/)

### Both, from one recording

For a lesson or handoff that needs an explanation now and a reference later.

[See how it works](https://polysh.io/how-it-works/)

GOOD TO KNOW

## Different jobs.  The same workspace.

**Are these separate products?**

No. These are different ways of using Polysh. Recording, narration, guide creation, and sharing are part of the same workspace.

**Do I have to produce both a video and a guide?**

No. Make the output your audience will use: a narrated video, a step-by-step guide, or both.

**Where should I start?**

Pick one task you explain often. Capture it in a sample workspace, review the script, then create and check the output before sharing it.

START WITH SOMETHING YOU KNOW

## Your next explanation  could go a little further.

Record the workflow. Give it a little Polysh.

[Request access](https://polysh.io/contact/)

Access is currently by team invitation.