Most Upwork proposals fail because freelancers answer what the client wrote, not what they actually need.
A client writes: "I need a dashboard."
What they mean: "My team is making decisions with bad data and I need it fixed fast."
I built a tool that tries to detect this gap — reads the job post, finds the real pain point, then writes a proposal around that.
It's MVP stage. No idea if it actually works in real scenarios or if I'm just solving a problem that doesn't exist.
Would anyone who does freelancing be willing to try it and tell me honestly what's broken?
Link: https://proposal-os-ruby.vercel.app
Abdul Razzaque
Posted on
I built an MVP that detects what clients actually need from job posts — not what they wrote
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (1)
Interesting angle — reading between the lines of job posts is a real skill. The next layer of this problem is the client's behavior history: a well-written job post from a client who habitually doesn't pay is still a bad project. Have you thought about combining brief analysis with client reputation signals?