I'm building a SaaS and noticed I spend hours daily answering questions about API integration, authentication, error handling - stuff that's all in the docs but unread by users.
The documentation exists. It's clear (I think). But people still reach out with: 'How do I get my API key?', 'What does this error mean?', 'Can you explain this feature?'
I'm researching this problem and would love to hear from other developers/founders:
How much time do you spend answering questions already covered in your docs?
What's worked for you to get people to actually read documentation?
Is this just part of the job?
Survey link: https://aicofounder.com/research/bpFw8fS
Curious to hear your experiences!
Top comments (0)