Here's a question most agency owners don't think to ask: how many of your late approvals are actually caused by your approval tool?
Not by the client being busy. Not by the deliverable needing more work. By the simple fact that your client has to create an account, remember a password, and log in to a platform they use once a month — just to click "Approved."
That friction is invisible to you. But it's very real to your client.
The login tax
Every time you send a client a deliverable to review through a platform that requires a login, your client has to:
- Find the email with their login credentials (if they even remember signing up)
- Navigate to the platform (what was the URL again?)
- Enter their password (wrong password, try again)
- Click "Forgot password" (because they definitely forgot it)
- Wait for the reset email (check spam folder)
- Set a new password (must include uppercase, number, and a hieroglyph)
- Finally log in and find the deliverable
- Now they can actually review the work
That's eight steps before your client even looks at what you made. Is it any wonder they "haven't gotten to it yet"?
What happens in practice
We've talked to hundreds of agencies about their approval workflows. The pattern is remarkably consistent.
Day 1: You finish the deliverable, upload it to your client portal, and send a notification. You feel productive.
Day 2: Nothing. The client got the email but didn't recognize the platform name. They flagged it to deal with later.
Day 3: You send a follow-up. "Just checking if you had a chance to review the homepage mockup!" The client opens the email, clicks the link, hits a login screen, tries their usual password. It doesn't work. They close the tab.
Day 5: You send another follow-up. This one is more urgent because the project timeline is slipping. The client finally resets their password, logs in, and approves in 30 seconds. The actual review took half a minute. The access friction took five days.
Five days lost. Not because the client was difficult. Because the software was.
The magic link approach
Here's how it works without a login barrier:
- You create a project and add your client's email
- Your client receives an email with a secure link
- They click the link
- They're in. Immediately. No signup, no password, no account
That's it. The link is unique, cryptographically secure, and expires after a configurable period. It's the same authentication pattern used by Slack, Notion, and dozens of other modern platforms.
When you send a new deliverable, your client gets an email notification with a link directly to that deliverable. They click it, see the work, and approve or request changes. The entire interaction takes 60 seconds.
The numbers
We don't have peer-reviewed academic studies on client approval friction (if only). But here's what we've observed across agencies using TryApprove:
- Average time to first client action (magic link): Under 24 hours
- Average time to first client action (login required): 3-5 business days
- Completion rate for onboarding steps (magic link): ~85%
- Completion rate for onboarding steps (login required): ~40-50%
The difference isn't subtle. It's the difference between a project that stays on schedule and one that drifts for a week every time you need client input.
But isn't a magic link less secure?
This is the first question people ask, and it's a fair one.
Short answer: no. Magic links are actually more secure than passwords for this use case.
Here's why:
- Passwords get reused. Your client uses the same password on every platform. If any one of those platforms gets breached, their password is compromised everywhere. Magic links are single-use tokens — there's nothing to breach.
- Passwords get shared. "Hey, can you log in and approve this? My password is taco123." We've all seen it. Magic links are tied to a specific email address and can't be transferred meaningfully.
- Magic links expire. Even if someone intercepted a link (unlikely over HTTPS), it expires after a set period. A password sits in your client's browser forever.
- No credential storage risk. Your platform doesn't need to store password hashes, which means there's no password database to be targeted.
Slack, Notion, and Medium all use magic links for authentication. Your clients are already using this pattern daily — they just don't think about it.
The client's perspective
Put yourself in your client's shoes for a minute. They work with three agencies — a design agency, a content agency, and a development agency. Each uses a different platform:
- Agency A uses Filestage (login required)
- Agency B uses GoVisually (login required)
- Agency C uses TryApprove (magic link)
For agencies A and B, your client has to maintain two separate accounts with two separate passwords for platforms they barely use. Every time they need to review something, it's a minor interruption that requires cognitive effort.
For Agency C, they click a link in their email. That's it. No context-switching, no password management, no friction.
Which agency do you think gets faster feedback?
What this means for your business
Faster approvals don't just feel better. They have real business impact:
Projects stay on schedule
When a client takes 5 days to approve a deliverable instead of 1, your entire timeline shifts. If you have 4 approval checkpoints in a project, that's potentially 16 extra days of delay — an entire month of timeline slip caused purely by access friction.
You bill faster
Invoices tied to milestones get sent sooner when those milestones are hit on time. A project that should take 4 weeks but stretches to 6 because of slow approvals delays your revenue by 50%.
Your team stays productive
Nothing kills creative momentum like context-switching. When a deliverable sits in approval limbo, your designer either idles (expensive) or starts something new and has to context-switch back when the feedback finally arrives (also expensive). For more on managing this, see our guide to stopping the feedback chase.
Client satisfaction goes up
This sounds counterintuitive — clients don't think about approval software. But they do think about how easy it is to work with you. When your process is frictionless, clients attribute that smoothness to your agency, not your tools. Their experience is: "I click a link, I see beautiful work in a portal with our brand, I approve in one click. This agency has their act together."
How to implement this
If you're currently using a login-based approval tool and want to switch to magic links, here's the path:
Option 1: Use TryApprove
TryApprove was built from the ground up with magic links as the primary client authentication method. There's no login option because we believe it's the wrong pattern for this use case.
When you create a project:
- Your client receives a portal link via email (automatically)
- Every time you add a new task or deliverable, they get notified (automatically)
- Every time they need to review something, they click the link (no password)
The portal shows your logo, your colors, and your brand. The client sees their contracts, questionnaires, deliverables, and invoices — all in one place.
Option 2: Build your own
If you have development resources, you can implement magic link authentication in your existing workflow. The basic approach is:
- Generate a unique, cryptographically random token for each client session
- Send the token as a URL parameter via email
- Validate the token server-side when the client clicks the link
- Set a session cookie with an appropriate expiration
- Invalidate the token after use (or after expiration)
But honestly, if you're building client-facing approval workflows, you're better off using a tool designed for it rather than building authentication infrastructure from scratch.
The bottom line
Every login screen between your client and their "Approve" button is a wall. It might be a small wall. But small walls add up to big delays.
The best client experience is the one with the fewest obstacles. Magic links remove the biggest obstacle most agencies don't even realize they have.
Your clients don't want another account. They want to click a link and do the thing.
Give them that.
