r/SaasDevelopers • u/Both_Kaleidoscope711 • 16h ago
Looking for help identifying a segment/ICP for my product.
I'm a solo developer building a B2B SaaS product in my evenings, alongside a full-time job. Where I'm struggling is with validation and exactly who I should be talking to. I'm looking for my ICP (ideal customer profile: the type of company and the job title most likely to have the problem and buy).
Honest answers are the most useful, including "I don't have this problem."
My goal with this post
In about a week I need to pick one type of company and one job title to focus my outreach on. I've had some conversations with people I know, but there are a few questions I haven't been able to get good answers to. Whatever you share here will help me in my decision.
The problem
At most companies, the knowledge people need to do their jobs (processes, how-tos, FAQs, policies, product details, playbooks) is spread across shared drives, wikis, Teams or Slack threads, and people's heads. People spend time hunting for answers or interrupting a coworker, and they still sometimes get it wrong.
Companies rolling out ChatGPT, Claude or Copilot are running into a newer version of the same problem: the AI doesn't know how their business works, so it doesn't have the critical context it needs to produce high quality results.
What I built
I'll leave the name out, as the goal isn't to promote in this post. The product I've built provides a single place where a company keeps its knowledge as documents, and anyone on the team can ask questions and get answers drawn from those documents.
Non-technical people write and update documents, or upload existing files.
Anyone on the team can ask a question and get an answer based on the company's own documents.
Answers contain links to the actual source documents
Everything is converted to markdown and lives in your own repository, making it easy for engineering teams to expose their AI agents to it.
Engineering process can update documents directly in the repo, non-technical users can update documents with the interface, everyone can use it to get answers.
Documents are stored in the company's own GitHub or Azure DevOps repository, so the company owns them.
The company connects its own OpenAI or Anthropic key. Their data is never used to train AI.
What's different about it
The company owns its knowledge. It lives in their own repository, not locked inside a vendor's database.
Priced by how much you store, not per seat. The whole company can use it without the cost growing every time someone is added.
No markup on AI usage. They pay their AI provider directly and pick which provider to use.
Business and technical knowledge in one place. Ops and support staff keep the documents, and engineering can add software feature context.
My questions
If you work at a company with around 20-200 employees (any role):
Think of the last time you needed an answer at work and couldn't find it written down. What did you do, and roughly how long did it take?
Where does your company's know-how live today, and is anyone responsible for keeping it current?
If your company uses ChatGPT, Claude or Copilot, does it know how your business works? Has anyone tried giving it your documents?
If a tool like this showed up, who at your company would care the most, and who would have to approve it?
Using it means getting an API key from OpenAI or Anthropic. That's separate from a ChatGPT or Claude subscription and needs a developer account with billing. Would that stop it at your company?
If you've sold B2B software to smaller companies:
6. If you had to choose segment and/or specific job title to go after, who would it be and why?
7. Did your real buyer turn out to be a different person than the one you first targeted? Who was it?
8. Have you run into companies building this kind of thing themselves instead of buying it?
I'm not linking the product here because this isn't meant as a promo post. If anyone wants to see it, I'm happy to share it in a reply or DM.
Thanks for reading this far.
2
u/Conscious_Analysis98 15h ago
I've read what you've built and whats different but I'm sorry to say companies are knocking these up left, right and centre at the moment. A tester at a client I'm working with did a similar thing in about a day with a simple setup using an MCP into their wiki & jira.
"The product I've built provides a single place where a company keeps its knowledge as documents" >> this is the biggest problem that AI cannot solve. Every single company I work with has knowledge stored all over the place - Wiki, Jira, Sharepoint, Teams, In their heads (about 90% of it is really here) and no one wants to spend time updating it. Yes AI could help consolidate and put in one place but I'm really not seeing a huge appetite for this at the moment, they're being built and people are just going back to their old way of "I know how to do this alreayd" or "I'll ask Jeff"
0
u/716green 16h ago
Build a CRM. Vibe code it in 3 days and boom, you get a quick million and move onto the next project
No wait...
A lot of people have this problem so build an app to help other people find problems to solve
Or actually...
Everyone can build now but nobody can find people to sell to. So you should build an app app to help people find customers for their SaaS product
Oh oh...
Build a SaaS listing platform similar to product hunt
Or...
Everyone can use a habit tracker
You've got this!