## Activation Read The account is created, then nothing: no files, no invite, no second person in the workspace. The gap is not effort, it is exposure — a studio owner alone in an empty tool will not put a paying client inside it, because the invite is the first thing the client will judge and there is nothing yet to judge but a blank project. Every day that passes without one real file and one real date in the workspace makes the invite feel more like a risk than a step, and roughly seven in ten trials end there. --- ## Sequence Overview | Message | Trigger | Action requested | Success metric | |---|---|---|---| | 1. Name the work | First load of the dashboard with zero projects on the account | Create project | Project created within 10 minutes of message view | | 2. Put the work in | Project screen opens with zero files, no upload in progress | Upload a file | First file uploaded within 48 hours of message view | | 3. Show the loop | First file upload completes and the file preview opens, zero comments on the account | Add a comment | Comment created within 15 minutes of message view | | 4. Fix the date | Project holds at least one file and one comment, deadline field empty | Set deadline | Deadline set in the same session as message view | | 5. Open the door | Project has file, comment and deadline, no collaborator invited, session idle 60 seconds on the project screen | Invite your client | Invite sent within 72 hours of message view | --- ## 1. Name the work **Trigger:** First load of the dashboard with zero projects on the account, before any other screen is reached. **Placement:** Inline empty-state block in the centre of the dashboard, replacing the project list. No overlay, no dismiss timer. **Copy:** A project holds one client's files, comments and dates in one place. Name yours after a job you have on the desk right now, not a test one. **Action requested:** Create project **Success metric:** Project creation event within 10 minutes of message view, read as a rate over all users who saw the empty dashboard. **Why it works:** A project named after real work sets up a workspace worth showing a client, instead of a sandbox the owner would never invite anyone into. --- ## 2. Put the work in **Trigger:** Project screen opens with zero files attached and no upload in progress. **Placement:** Inline drop zone filling the file area of the project screen, with the action label directly beneath it. **Copy:** Nothing is in here yet. Add the current version of the work so notes land on the file itself instead of scattering across your inbox. **Action requested:** Upload a file **Success metric:** First file upload event within 48 hours of message view, read as a rate over users who created a project. **Why it works:** One real file turns the empty account into something with contents, which is the minimum the owner needs before the workspace is presentable to a client. --- ## 3. Show the loop **Trigger:** First file upload completes and the file preview opens, with zero comments recorded on the account. **Placement:** Anchored tooltip beside the comment field in the file preview, dismissible, never over the file itself. **Copy:** Comments attach to the version they refer to, so feedback stays with the work. Leave one on this file and read how it lands before your client does. **Action requested:** Add a comment **Success metric:** Comment creation event within 15 minutes of message view, read as a rate over users who uploaded a first file. **Why it works:** The owner tests the client-facing mechanism privately, so the invite is no longer a bet on an untried tool. --- ## 4. Fix the date **Trigger:** Project contains at least one file and at least one comment, and the deadline field is empty. Fires on next project screen load, not mid-edit. **Placement:** Single-line prompt in the project header, next to the empty deadline field. **Copy:** A date on the project tells your client what is due without them asking you for a status. Add the deadline for this job. **Action requested:** Set deadline **Success metric:** Deadline set event in the same session as message view, read as a session-level completion rate. **Why it works:** The date gives the client a reason to be in the workspace, which is what makes the invite a working step rather than a demonstration. --- ## 5. Open the door **Trigger:** Project holds a file, a comment and a deadline, no collaborator has been invited, and the session has been idle on the project screen for 60 seconds with no open form. **Placement:** Side panel sliding from the right of the project screen, closable, with the action as the only button. **Copy:** Your client sees this project only: its files, comments and date. Nothing else in your studio is visible to them. Add their email to open it up. **Action requested:** Invite your client **Success metric:** Invite sent event within 72 hours of message view, read as a rate over users who reached a project with file, comment and deadline. **Why it works:** It answers the exposure question directly, at the one moment when the workspace already holds enough to be worth a client seeing. --- ## Sequence Logic The order moves from private to public: the first four messages build a workspace the owner would not be embarrassed to share, and only the fifth asks them to share it. Message 1 gives the account a real job to hold, message 2 gives that job contents, message 3 lets the owner use the feedback mechanism themselves before a client does, and message 4 adds the date that gives the client a purpose for logging in. Each step raises the value of the workspace and lowers the cost of the invite, so by message 5 the remaining barrier is scope of visibility, which is the only thing that message addresses. Reversing any pair would ask the owner to expose an account with less in it, which is exactly what the drop-off data shows they refuse to do. --- ## If The User Does Not Act | Message | Fallback | |---|---| | 1. Name the work | On the next dashboard load, offer a pre-named project drawn from the studio name captured at signup, editable in place, so naming is a correction rather than a blank field. | | 2. Put the work in | On the next visit to the project screen, narrow the ask to a single reference image rather than the working file, keeping the same upload action. | | 3. Show the loop | On the next file preview open, surface a comment placed by the studio account on the file as an example thread the owner can reply to instead of starting one. | | 4. Fix the date | On the next project screen load, present the deadline field pre-filled with a date two weeks out, requiring confirmation or adjustment rather than entry. | | 5. Open the door | On the next project screen load, replace the email field with a copyable project link the owner can send from their own mail client, keeping the invite outside the tool if that is where their trust sits. |