Your Calendly Link Is Doing Your Parlei's Job

You sent a Calendly link. The recipient clicked it. They're meeting you in twenty minutes. The Calendly page lists three meeting types, your photo, a one-line bio, and a button. They book the meeting and close the tab.

Somewhere between the click and the booking, they did something Calendly never asked them to do. They tried to figure out who you are.

They scrolled the Calendly about-page hoping for context. They Googled your name in another tab. They opened your LinkedIn while booking. They formed an opinion based on whatever they could scavenge. By the time the meeting starts, that opinion is fixed.

You sent a link to a scheduling tool. They used it as identity infrastructure.

---

Calendly is not identity infrastructure. Calendly is a scheduling tool. Twenty years of product development have made it very good at scheduling and only incidentally able to host an "about" surface that gets used as identity infrastructure by default.

The about surface exists because somebody on the Calendly product team correctly noticed that visitors to a Calendly link want to know who they're meeting with. The team added a one-line bio field and a photo. That was the right product call for the moment. The right product call has aged badly.

A one-line bio on a Calendly page is doing infrastructure-grade work with note-card-grade affordances. The visitor wanted twenty things and got two. The visitor wanted a brief and got a postage stamp.

---

Imagine the prospect about to take a discovery call with you. They have eight minutes between meetings. They click your Calendly link to confirm the time. They land on the page. The page says "Discovery call — 30 minutes — Lise Richards, founder at Parlei." That's it. They book. They close the tab.

They are now walking into the call with no context other than your name and your one-line bio. The advantage you had — that you'd been in their inbox, that they'd seen your Substack, that a friend had referred them — is gone the moment they see the Calendly page, because the Calendly page is the most recent context they have on you. Recency wins.

You walk into the call selling. They walk in evaluating from scratch.

This is the second-order cost of using a scheduling tool as identity infrastructure. The cost isn't the bad about-page. It's the lost momentum every meeting you book.

---

The steel-man is fair. Calendly is one of the best-functioning tools in the modern professional stack. The product team that built it should be celebrated. Asking Calendly to be a Parlei would be asking it to do something it wasn't designed to do, and dilute its core function in the process.

So don't ask it. Ask Parlei to do that job, and let Calendly do scheduling.

The pattern works the way every well-staffed organization works: each tool does the thing it's specialized for, and the orchestration layer above them routes the visitor by what they came for. Calendly schedules. Parlei recognizes. Each one is better at its job than the other one would be.

---

The shift here is small in description and large in consequence. Stop sending the Calendly link as a standalone identity artifact. Send the Parlei link first. The Parlei link routes the recipient by what they came for — I'm prepping for our meeting, I want to schedule something, I want to know more before I book — and serves Calendly as the result of the I want to schedule path, not as the entry point.

The recipient gets the brief they were trying to scavenge for. The brief is shaped to the meeting type. The Calendly link is exactly where it was; it just isn't the entry point anymore. The roles match the responsibilities again.

---

Use Calendly for what Calendly is for. Use Parlei for what Calendly was being asked to do by accident.

Your Calendly link is doing your Parlei's job. Stop making it.