Every formal invitation used to arrive with a second, smaller card tucked inside it: the reply card. Pre-printed, pre-addressed, already stamped. Accepts with pleasure. Declines with regret. A line for a name, perhaps a box to tick for the fish.
Nobody who designed those cards was thinking about user experience, but they understood it perfectly. The biggest predictor of whether a guest replies is how much effort replying takes. So the host does all the work in advance and leaves the guest exactly one thing to do. No one has ever been asked to create an account on the couple’s website to say yes to the chicken.
Cross-company software has spent years doing the opposite.
One bit of information, wrapped in a funnel
When two companies work together, much of what one side needs from the other is small. Will you take this on? Is this what you needed? Can we go ahead? The answer is often a single bit — yes or no — plus, if it’s no, a sentence about why.
And to get that single bit, we ask the other company to adopt our tool. Find the invitation under everything else in the inbox. Create an account. Confirm an email address. Pick a password. Find the project. Find the thing. Then answer.
Each step is small. Together they’re a funnel, and every funnel leaks. The client who never quite gets around to logging in isn’t being difficult. They’re being rational: they work with a dozen vendors, every one of whom would like them in a portal, and their week has no room for a dozen portals. So the project quietly falls back to email, and the shared workspace becomes a record that only one side keeps.
We’ve argued before that unlimited people is the point — a joint workspace is only as good as the share of both companies actually in it. Pricing was the first barrier to take down. The login was the next.
Meet them where the question already is
So as of today, the other company can answer a Beevyl handoff straight from the email that asks.
When one side proposes a handoff, the people on the receiving side get an email that says what’s being handed over, by whom, by when, and what “done” means. Under it are two buttons: Accept and Return. Accept, and the handoff is theirs to deliver. Return, and they say why — we can’t start until the final brand voice guide lands — and the proposing side knows exactly what’s missing.
No account. No password. Nothing to install. If the person was invited to the workspace but never joined, answering also accepts the invitation, and the team roster shows them as Joined via email. If they ever want the full app, they can set a password later. Plenty of people never will, and that’s fine.
The reply card never asked anyone to join anything. It just made the answer the easiest thing in the envelope.
The button that isn’t one click
The obvious way to build this is a magic link: click Accept in the email, and the handoff is accepted. We didn’t build it that way, and the reason is worth knowing even if you never touch Beevyl.
Most corporate mail passes through a security product — Microsoft Defender’s Safe Links, Proofpoint, Mimecast — and many of them open the links in a message before a person does, to check where they lead. A link that acts the moment it’s opened gets acted on by the scanner. Build a one-click Accept, and somewhere a robot is accepting work on behalf of someone who hasn’t read the email yet.
So the button in a Beevyl email opens a page. Opening it changes nothing; the page can be loaded any number of times, by anyone or anything. It shows the handoff, says who you’re answering as, and offers one button. The answer happens only when a person presses it. One click to open, one tap to confirm: a single extra tap, in exchange for the whole sign-in, sign-up and find-the-thing path — and a guarantee that a scanner’s visit leaves nothing behind.
A credential the size of one question
The link is the credential, so it’s built to be small. Each email carries links signed for the one person it was sent to, good for that one handoff and those two answers, for fourteen days. The footer says so in plain words: the buttons in this email act as you — please don’t forward it. An expired link doesn’t strand anyone; the page offers to email a fresh one to the same address, for as long as the handoff is still waiting on them.
None of this makes it a lesser kind of answer. It runs through the same rules as the app — someone who can’t accept a handoff in the app can’t accept it from an email either — and it lands in the same places: the activity feed both companies read, and the audit trail underneath, each marked via email. The proposing side’s confirmation names who accepted, and that it came from the email. Accountability that depends on remembering a password was never really accountability.
Email that minds its manners
Making the inbox a place where work gets done meant taking the emails themselves seriously, so we rebuilt them while we were there.
Every email about a handoff — or a decision, a blocker, a task — now takes the item and the workspace as its subject and lands in the same conversation as the others about it, instead of arriving as one more “You have a new notification”. Headings say what happened. Buttons say what they do — Accept, Review and sign off, Open the task — and open the exact item rather than the front page. Every email carries a plain-text copy with the links written out, for mail apps that strip buttons.
And we turned the tracking off. No pixels reporting when you opened something, no click tracking rewriting links through someone else’s domain — which, for links that act on your behalf, would have been exactly the wrong place to send them. We don’t know if you opened our email. The only thing we measure is whether the question got answered.
The easiest thing in the envelope
Accept and Return are the first two answers you can give from an email. They won’t be the last: most of what one company needs from another is a small, clear question, and each of them deserves a reply card.
The principle underneath is older than software. If you need someone’s answer, do the work of asking well. Put the question where they already are, make the answer one gesture, keep a faithful record of it — and then get out of the way.