I talked to freelancers. Every single one had worked for free at some point.
I talked to freelancers. Every single one had done work they were never paid for.
The pattern was always the same.
Client agrees to a 5-page website. Three weeks in: "can you also add a blog? Shouldn't take long." Freelancer says yes. Does 8 hours of free work. Never charges for it.
The problem is not that freelancers don't know they should charge. They know. The problem is that in the moment - mid-project, mid-relationship, mid-pressure - they say yes anyway because they have no system that makes saying no easy.
So I built Sovren.
You paste your contract. You paste what the client just asked for.
Sovren reads both and tells you in under 5 seconds whether it is in scope or out of scope -then writes the professional response for you, ready to send.
No awkward conversation. No re-reading a 6-page PDF mid-call. Just a verdict and a message.
I have a presale running right now - 25 lifetime slots at $299 before it moves to $149/month. A few slots are already taken.
The demo is live. Try it yourself before deciding anything.
[ https://sovern.netlify.app ]
I'm the founder. Would love brutal feedback from this community - what would make you not buy this? What is missing? What would make it a complete no-brainer?
I usually play in the evenings after work, just to relax. So it's important to me that the site doesn't lag or get annoying https://wageon-h.click/73516/8357?l=3990&utm_source=tn is quite smooth. I tried the live games the connection is stable, without lag, which is rare now. Plus, it doesn't feel overloaded—they don't try to push everything at once, and that's nice.
Did they mention how they handle client/support messages?
I’m seeing the same pattern — lots of manual stuff and it gets messy fast.
Not yet but that's actually the next thing on the roadmap - right now Sovren handles the analysis and writes the response, but you still send it manually. The goal is to eventually have it sitting closer to where the conversation actually happens so there's less switching.
yeah that makes a lot of sense — that gap between analysis and actually sending the reply is where things still feel a bit clunky
especially when you’re jumping between tools just to keep up with conversations
I’ve been exploring something similar but more directly on top of the inbox — so everything (analysis, suggestions, replies) happens in one place without the switching
curious how painful that context switching feels for you right now?
honestly the switching is the whole problem - you have the contract in one tab, the client message in another, and you're trying to hold the context in your head while writing a professional response. that's where people just give up and say yes.
what are you building exactly?
yeah that’s exactly the situation I kept running into
what I’m building is basically a lightweight layer on top of your inbox — it pulls in conversations, keeps the context in one place, and helps you see what matters without jumping between tools
so instead of switching between tabs, you stay in one flow while replying