Working Note: Early Activation for New Agency Teams Situation in plain language Most new teams start a project, but most don't invite a client in the first week — only 28% do. Since teams that do invite a client tend to come back more the following month, client invitation looks like a meaningful early step, not just a nice-to-have. Support tickets pointing at unclear invitation emails suggest at least part of the drop-off is a communication problem, not a demand problem. What the evidence shows Only 28% of new accounts invite a client in week one. Support tickets describe the invitation email as unclear. Teams that invite a client return more often in the following month. Reasonable assumptions (not confirmed) The unclear email is a meaningful cause of low invitation rates, not just an incidental complaint from a vocal minority. Teams that don't invite a client are less likely to see the product's full value (client approval loop), which may affect their motivation to return. New teams understand what "inviting a client" is for, but hesitate or fail at the mechanics. Unanswered questions Is the 72% who don't invite a client failing at the email step, choosing not to invite anyone yet, or unsure why they'd want to? Does the return-rate correlation hold regardless of team size, agency type, or project complexity — or is it explained by something else (e.g., more organized teams both invite clients and return more)? At what point in the invite flow do people drop off — never starting it, starting and abandoning, or sending it but the client never responding? Where customers may be getting stuck Between creating a project and inviting a client — the first-week gap suggests this step is either skipped or attempted and stalled. At the client's end — if the invitation email is unclear, clients may not be completing their side of the loop even when a teammate sends it. This is a correlation between invitation and return visits, not proof that invitations cause retention — worth keeping in mind before treating it as guaranteed. Recommended actions to test Rewrite the client invitation email Problem addressed: Clients reportedly find the current email unclear, which may block the invite step even when a team member initiates it. Audience: Clients receiving invitations (indirect: the inviting team member). Effort/dependency: Low — copy and possibly template design change only, no permissions or backend work. Signal of success: Increase in the percentage of sent invitations that clients accept/complete, tracked against the current baseline. Add in-app guidance nudging invitation during project setup Problem addressed: Teams may not invite a client simply because it isn't surfaced as an obvious next step after creating a project. Audience: New team admins/owners setting up their first project. Effort/dependency: Low-to-moderate — in-app messaging or checklist item, no permissions changes needed. Signal of success: Increase in the share of new accounts that invite a client within the first week (above the 28% baseline). Send a short onboarding email sequence reinforcing the invite step Problem addressed: Teams may create a project and then get busy or forget the client-invite step is available/valuable. Audience: New account owners in their first week. Effort/dependency: Low — email sequence build, no product changes. Signal of success: More accounts inviting a client within week one, and/or higher click-through on the invite prompt within the email. Priority order and trade-off Rewrite the invitation email first — it directly addresses a named, evidenced problem (unclear email) with the lowest effort and fastest turnaround. In-app guidance second — it targets the assumption that invitation isn't prominent enough, but requires more design/build time than an email edit. Onboarding email sequence third — likely to reinforce the other two changes, but on its own is a weaker lever if the email or in-app prompt issues aren't fixed first. The trade-off is speed versus reach: the email rewrite is fastest to ship and test in isolation, while the in-app guidance and sequence take more coordination but may capture teams who don't reach the invite step at all. Next questions or data checks before a larger commitment Pull invitation funnel data: how many teams start the invite flow vs. complete it vs. never begin it? Check whether the return-rate correlation holds across different agency sizes or use cases, to rule out a confound. Ask clients directly (via a quick survey or support follow-up) what specifically was unclear about the invitation email. Confirm whether clients who receive the invite but don't act are a separate problem from teams that never send one.