Co-experience: Turning shared links into signups

Calendly reached a reported $70M in annual recurring revenue (ARR) on roughly $550K of outside capital.¹ The reason is structural, not clever: you cannot use Calendly without making a stranger use Calendly too. Every scheduling link is a demo that the recipient completes, for free, before anyone asks them to sign up.

That is co-experience, and nothing else wins a new user for less.

Your user cannot turn it off either. A referral program needs them to act. A badge is on by default, but it can be removed, and paying to remove it is often the point. Co-experience has no switch, because the distribution is a side effect of somebody doing their job. It is also the hardest to add later: either your product touches non-users during normal use or it does not. Document signing is the other clean case, since the counterparty has to use the product to complete the transaction at all.

What is co-experience, and how is it different from other viral loops?

Co-experience is a PLG acquisition pattern where normal product usage puts the product itself in front of non-users. The recipient doesn’t see an ad or a referral prompt. They use the thing, get their own outcome from it, and form an opinion before ever visiting your site.

The distinction that matters is who does the work. Referral programs ask your user to promote you. Embedded virality shows a stranger your logo. Co-experience hands the stranger the product.

The difference sets the ceiling on each pattern. A logo produces awareness. A completed task produces a judgment, which is why this pattern asks so little of the person converting: the recipient has already answered “does this work” before you ask for an email.

Does co-experience apply to your product?

The pattern is not a growth tactic you can bolt on. It’s a property of what your product does, so the answer arrives quickly and is often no. That is worth knowing on page one of this section, not page nine, because the eight patterns after it are all things you can choose.

Why co-experience works: the recipient is pre-qualified

Exposure is not what does the work. It’s that the person on the receiving end already has the problem, right now.

Someone sending you a Calendly link is doing so because scheduling was annoying. You, receiving it, are also someone for whom scheduling is annoying, which is why you’re in this email thread. The product turns up attached to a problem you obviously have, already solved, costing you nothing. No amount of ad targeting buys that.

It’s also why the pattern rewards designing for the recipient rather than the paying user. That feels backwards, and it’s where most attempts go wrong. The booking page, the video player, the signing flow: those are non-user surfaces, and they’re doing the selling. The instinct is to pour effort into the creator experience because that’s who pays them.

Find where people already share, then own that moment. Nobody invented the behavior. People emailed “here are some times that work” long before scheduling links existed. DocuSign didn’t invent signatures, it made an existing exchange digital. Loom didn’t invent screen recording. It collapsed recording and sharing into one step. The pattern works when it removes friction from an exchange that was already happening, and fails when it invents an exchange nobody wanted.

Three ways the loop gets built

Calendly: the output is the product

Calendly’s scheduling link is simultaneously the feature and the distribution. There is no separate share step to optimize, because sharing is the only way to use it. That’s the strongest version of the pattern and the rarest: the loop cannot be skipped, forgotten, or turned off.

The design consequence is that the booking page carries the company. The booking page asks the recipient for nothing but a time, because that page is the entire sales pitch to a stranger.

Zoom: let non-users in without an account

Zoom’s contribution was removing the last barrier. Joining a Zoom meeting has never required an account, so invitees experienced the product directly rather than reading about it. The 40-minute cap on free meetings² comes later, and where a limit belongs is its own subject.

DocuSign: build on an exchange that can’t happen alone

Nobody signs a contract by themselves, so every use of DocuSign involves a non-user who has to operate the product to get their own thing done. DocuSign has reported new people touching its platform climbing from roughly 40,000 a day in late 2014, to 85,000 by early 2016, to about 300,000 by May 2017.³ Most of them can only be signers, not customers. DocuSign does not say so, but the arithmetic allows nothing else. That’s the point: the product recruits its own future buyers as a side effect of people using it.

Two things follow. Products built on two-party exchanges get the loop for free and can’t switch it off, which is the same structural gift Calendly has. And the recipient wants your product most in the seconds after they finish signing. That handoff is the one moment your product has the recipient’s full attention, and it costs nothing to use.

If your product touches groups, not pairs, the numbers are better still: a five-person meeting exposes four non-users for one person’s effort.

When the pattern is not a business

Co-experience is unusually good at acquisition and says nothing about whether you have a company.

Zoom is the instructive version. The loop delivered a scale of daily participation few products reach, and what turned that into a business was that call quality held up once they arrived. Reverse those two and you get a viral loop running ahead of retention.

The failure mode specific to this pattern is subtler. Because recipients convert well, co-experience products post excellent signup numbers. So it goes unchecked, sometimes for years, whether those users come back. The loop keeps the charts green. Then growth flattens, and the team finds it has been pouring cheap signups into a product nobody stays with.

Is the loop actually spinning?

Recipients are supposed to arrive pre-qualified, so they should convert better than cold visitors, and clearly. Compare signup rate for people arriving from something a user shared against organic or paid arrivals. If they convert no better than a stranger off a search result, the loop is not functioning: either the booking page or shared file is not showing them anything worth having, or they were never people who could buy.

The trend that decides whether it compounds is different. Track how many non-users an average active account touches per month and watch the direction, not the level, because that is what moves when you change sharing friction. A falling line with flat signups means user growth is carrying you while the loop quietly dies.

Then time your share flow, and not time to value: time from intent to share to shared. Every second there taxes the cheapest growth you have.

Find your external surface

Start by listing every place your product reaches somebody outside the account: emails it sends, links it generates, files it exports, embeds it renders. The ones worth finding are those nobody has ever thought of as distribution.

Then go and meet one as a stranger would. Sign out, open a shared link on a phone, and see whether the value is obvious before you scroll. That page is selling for you whether or not anybody designed it to, and the single most common omission is that it offers the recipient no visible way in. The moment somebody finishes is the moment they want it, so say plainly, on the screen where they just watched it work, that they can do this themselves.

One thing to settle before you scale any of it: if activation is broken, co-experience widens the leak and improves the dashboard at the same time.

Co-experience only works if your product has an external surface, and most don’t. The pattern that applies to almost everything is embedded virality, and its real interest isn’t the badge: it turns your free tier from a cost you tolerate into a payment method your customers actually chose.

Updated August 2026