Exploring a simpler way to handle document approvals in small teams
I’m exploring a small SaaS idea around document approvals for small teams.
In many teams I’ve worked with, approvals happen over email, WhatsApp,
and shared drives. It works until something goes wrong — then there’s
no clear record of who approved what or when.
I’ve built a basic working version and I’m now trying to validate:
- Is this a real problem for small teams?
- Who feels this pain the most?
- What would make a tool like this actually useful?
Not selling or launching yet — just looking for honest feedback
before going further.
Would love to hear your thoughts.
Congrats on the launch, looks solid. How are you currently thinking about acquiring early users and gathering feedback?
Thanks for the thoughtful question 🙌
Right now I’m focusing on validating the problem more than scaling . I’m starting with content-driven discussions around document approval chaos (email chains, WhatsApp version confusion) and trying to engage small firms to understand their current workflows.
My goal in this phase is to get a few early beta users, observe how they use it, and refine the workflow experience before pushing for broader acquisition.
Still experimenting with positioning and would love any suggestions
That’s a smart approach. Validating the problem first usually saves a lot of time later.
Since you're already starting conversations around document approval chaos, one thing that can help is joining discussions in communities where people complain about messy approval processes (email chains, version confusion, etc.). Those threads often surface people who are perfect early beta users.
I help founders find and engage in those conversations in a structured way so they can attract the right early users while validating the problem. If you’d like, I can share a quick idea on how I’d approach it for your niche.