The hardest competitor to beat is the one that's free and already installed

When you build a tool in a category that already has software in it, the instinct is to line yourself up against the software. We did that first. We made the little comparison grid: Filestage, GoVisually, PageProof, Frame.io. Features down the side, checkmarks across. It's a comforting exercise because it makes you feel like you're in a race.

Then we actually watched how freelancers get client approval today, and the grid fell apart. Almost none of them use a proofing suite. They send a Figma link and wait for a comment. They email a PDF and hope for a reply. They paste a Loom in Slack and get back a thumbs-up. The real competitor isn't another app. It's a message that says "yes."

That sounds like a throwaway line. It's actually the most important product decision we made, because competing with free software and competing with a free habit are completely different problems.

Why the proofing suites don't fit the person we're building for

The suites are genuinely good at what they do. Filestage, GoVisually, PageProof — they're built for marketing and agency teams who need pixel-level annotation, reviewer roles, and version stacks, and they price like it (roughly $19 to $249 a month depending on tier and seats). If you're a ten-person creative team routing an ad through legal, that machinery earns its keep.

A solo web designer handing off a landing page to a small-business owner is not that team. They don't need an annotation canvas. They need to know the client approved this version, on this date, and to have something to point at when the invoice gets questioned. Selling them a proofing suite is selling a forklift to someone who needs to carry one box.

So the suites aren't really the competition for this person. They're a different product for a different buyer. Which means the thing our freelancer is actually choosing between is "use a new tool" and "just send the Figma link like always." And "like always" is free, familiar, and requires zero decisions.

Free and habitual is a brutal thing to beat

Here's what makes the status quo so hard to displace. It isn't that email is better. It's that email is already there, the client already knows how to use it, and switching costs nothing to keep doing. Every friction we add — an account, a new interface, a thing the client has to learn — is weighed against a baseline of literally nothing.

That reframes the entire design brief. If we were competing with Filestage, we'd win by having more features, or the same features cheaper.

“But you don't beat a free habit with features. You beat it by being less.”

Being less means making the better-documented path also the easier path — especially for the person who never chose to be there. In client approval, that person is the client. They didn't sign up for anything; they just want to look at the work and say yes. If our tool makes their side even slightly harder than replying to an email — a login, an account, a confusing screen — they'll route around it, tell the freelancer "just email it to me," and the free habit wins by default.

The trade-offs that fall out of taking "free" seriously

Once "beat the Slack yes, not Filestage" became the actual goal, a bunch of decisions stopped being hard.

No client accounts. The client opens a link and sees two buttons. Nothing to sign up for, nothing to remember, works on a phone. If replying to an email is the bar, the client's path has to be at least that easy — and ideally easier, because it's one tap instead of composing a reply.

Tool-agnostic, not a workspace. People already keep their work in Figma, Drive, Loom, staging links. We're not going to win by making them move it into our canvas. So deliverables are just URLs — the tool wraps around where the work already lives instead of demanding it relocate.

The output is a receipt, not annotations. The thing email can't give you is a durable, dated, version-pinned record of the "yes." So that's the whole product — the artifact, not the review chrome. Everything the proofing suites spend their budget on (annotation, reviewer roles, seats), we deliberately don't have.

Cheap on purpose. If the alternative is free, a $9 tool has to feel like a rounding error against a single avoided dispute — not like a subscription you have to justify.

Notice that every one of those is a subtraction. Competing with free pushed us toward doing less, which is the opposite of where a feature comparison would have led us. The comparison grid had us racing to add; the honest look at the status quo had us racing to remove.

What we're still not sure about

The risk in this framing is real, and we'll name it: the same thing that makes the status quo hard to beat — it's free and habitual — might just win anyway. Maybe the pain of a fuzzy "yes" isn't sharp enough, often enough, to make anyone change what they do. A tool only gets adopted if the freelancer forms a new reflex ("send the link"), and reflexes are exactly what a free habit is made of. We don't have that answer yet — it's the thing we most want early users to prove or disprove.

But we're confident the framing itself is right, and it generalizes past our little product.

If you want to see what "beat the email, not the suite" looks like as a finished thing, OkayFlow is the result. But the more useful takeaway costs nothing: go find out what your users do today, before you assume you're racing the competitor with the logo.