ReadMe (YC W15) Raises 9M Series A from Accel and Y Combinator

Post by harrisonjackson » Thu, Aug 29, 2019, 3:12 AM UTC

choward wrote: post #19

harrisonjackson wrote: post #12

Earlier quoted context omitted.

Did you go to the products page? Not questioning what you said at all just curious how deep you dug (obvs apex should have the info you were missing), but as someone that is pretty familiar with their offering and someone that has hosted api docs and sdk documentation through other sources their copy and marketing is on point for me - and the marketer/founder in me wants to know where the disconnect happened for you.

Yes. It was pretty much the first thing I read actually. It makes a little more sense after a re-read. I still have no idea why there are snippets of code at the top telling me how to make a POST request. Anyway, I'm a developer, so when I evaluate something I'm very focused on "how do I use this for real in production and how much pain is it going to cause me?" So what I usually do first thing is go look for the doc…

Post by paggle » Thu, Aug 29, 2019, 5:45 AM UTC

bretpiatt wrote: post #16

bg0 wrote: post #13

[you're right]

$100 is 1/50th of a $5,000 per month employee. From looking at your business from the website in your profile it feels like high quality API docs could speed up many members of the team. It's hard to evaluate situations from the outside so I could also be totally off. At Jungle Disk we consume a ton of tools and they are all easily positive ROI. Good people are hard to find and expensive vs. SaaS subscriptions.

Post by guptaneil » Thu, Aug 29, 2019, 2:07 PM UTC

gkoberger wrote: post #10

choward wrote: post #9

I've read pretty much everything on the site and between the high level marketing speak and generic wireframes, I have no idea what it does or what problem it actually solves. There's even a link if you hover over about that says "Learn about why we exist". I thought for sure that would have something, but it's just a list of all the employees. It looks like the only way to figure out what it actually does is to sign…

Hey! We do API documentation, plus a bunch of other tools. All the logos are click-able (for example: https://developers.intercom.com/ ) if you want an example. So, basically, we sit at developer.whatever.com, and take care of everything from reference guides to marketing pages to tutorials to support forums. If you have any more questions or feedback, feel free to email me at greg@readme.io! We're always updating th…

Post by mobee » Thu, Aug 29, 2019, 5:01 PM UTC

gkoberger wrote: post #5

sytse wrote: post #4

Earlier quoted context omitted.

Congrats on the raise. Interesting to use to API logs to provide better debugging and support. Can you give an example?

Thanks Sid! Let's say you get back an error. We've made it so the API creator can link in the response to a unique page in the docs, where they'll see their actual API log. They can see exactly what the server saw and returned, replay the request, and more. If an error code is returned, the API creator can write out what the error means and how to fix it. If that's not enough, they can open a support ticket on ReadMe…