Why we built Kanvis.

You already know how this goes. You spend an evening rewriting the same two pages so some piece of software will let them through. You swap a word, move a date, cut the thing you were proudest of because it didn’t fit. You send it. Nothing comes back. Not a no, just nothing.

Somewhere in that silence, a person who would have liked you never saw your name. And the rejection was never the hard part. The hard part is that what got judged was a page of formatting, and you weren’t in the room to say otherwise.

The part people miss is that it’s just as bad on the other side. The person hiring didn’t build this funnel for fun. They’ve got 250 documents and an afternoon, so they skim each one for a few seconds and hope. They’re guessing too. Everyone here is making an expensive decision on almost no information, and everyone knows it.

Plenty of people have noticed this problem. Most attempts to fix it go wrong at the business model, not the technology. The moment a job seeker can pay to be seen, you’ve started selling the thing you were supposed to be measuring.

So we made the awkward decision first and built afterwards. Candidates don’t pay us. Not for a boost, not for a badge. Hiring teams do. That means the product has to be good enough that a company will pay for the shortlist, which is a lot harder to build than a premium tier. We’d rather have that problem.

You also get the people who build it. If you tell us something’s wrong, the person reading your message is the person who changes the product, usually that week.

The whole approach comes down to one swap. Stop asking people to squeeze themselves into a document, and let them talk instead.

You talk for about five minutes. No forms, no templates. You say what you did and what it took, and it gets written down properly, with every line tied to the moment you said it.

Your page answers when you can’t. You get a page at kanvis.me with your name on it. When someone opens it at eleven at night and wants to know whether you’ve really shipped something at scale, the page answers them from your own record, with the evidence attached.

The first interview actually happens. Apply through Kanvis and you get a real first conversation about the role. It’s run by AI, and we say so up front. The hiring team then reads what you actually said instead of guessing from a file.

That line matters more than anything else on this page. Every score Kanvis produces is worked out the same way for everyone who applied, and the AI gets no say in it. That’s what makes it a system you can question rather than one you just have to accept.

Both sides are live and people are being hired through it. So what follows is a direction, not a promise.

Next up is depth. An interview that gets better at drawing out the things a document can’t hold, and a page that remembers what it learned about you from one application to the next instead of asking again. After that, reach. This problem isn’t specific to one country, one language or one kind of work, and the answer shouldn’t be either.

The long-term version is the one worth writing down, because it’s what we’d want to be held to. A world where sending a résumé is the odd choice. Where the normal way to be considered for a job is a page that already knows what you’ve done, can be asked about it by anyone, and costs you nothing to keep.

That’s a long way off. We’d rather say it out loud anyway.