Comment by davecyen
3 days ago
Very needed! I’ve worked on platform teams and API docs were always rushed last second to push out a release—-but in many ways they are the product.
Another pain point was creating guides/examples for integrating 3rd party tools. Could be worth exploring
For sure. It can be challenging to inculcate a culture of treating docs as a product, but since great docs can drive revenue growth and bad docs can increase churn, it's a very important mindset.
In terms of creating guides/examples for third-party tools, do you have a particular use-case in mind? e.g. if you're something like Zapier with hundreds of connections?
Re: 3rd party integrations, think glue code for enterprise platforms (I previously worked on the developer platform at Shopify).
For example, a guide to integrate Shopify's Storefront API with Sanity CMS. These are usually a marketing/product thing more than developer docs... and almost always become obsolete after the next release and forgotten about.
Would've loved to generate a bunch of these guides and then automatically keep them up-to-date with code examples, and help serve both purposes for growth and developer docs.
Yes, absolutely! Someone mentioned a similar situation where they had 100+ integration-specific landing pages in webflow (mostly for SEO) that became stale within months.
Definitely would love to pick your brain more about this if interested. prithvi@gopromptless.ai
Have any of your customers provided case study information that would imply some reduction in churn or an increase in inbound leads or sales?
Yeah, great question! The earliest quantitative measurements people make are around how much time is being saved, but people are also measuring deflection rates in AI support chatbots (better docs => better support), which is strongly correlated with CSAT scores. Measuring reduction in churn or increased inbound takes several months to prove out, and we just haven't been around that long :)
We'll definitely be posting some case studies in the coming weeks, though!