Customer Story

How Evergrove Labs made documentation part of the deploy process

Jacob, co-founder and CTO of Evergrove Labs, explains how Ferndesk saves the company about three hours a week and fits doc updates into its deploy process.

Company

Evergrove Labs

Featured

Jacob

Jacob

Co-founder & CTO, Evergrove Labs

Jacob
Key results
  • About 3 hours saved per week
  • Doc updates now run as part of the deploy process
  • Docs stay current without manual editing
"We save about 3 hours per week! This is now a big part of our deploy process."
Jacob
Jacob Co-founder & CTO, Evergrove Labs

About Evergrove Labs

Evergrove Labs builds AI employees for MCOs (managed care organizations). Jacob is the company’s co-founder and CTO.

Jacob knew the manual version

At a previous company, Jacob kept the documentation current by hand.

At a previous company I did this manually, so it’s really great to have something that works autonomously as a founder.

That’s the comparison he’s drawing. Doing it by hand isn’t difficult work, but it comes back with every release, and at a small company it lands on the founders.

Documentation joined the deploy process

Now the docs update as part of shipping.

This is now a big part of our deploy process.

Ferndesk reads the codebase, support tickets and changelogs, so a release is what prompts the help center to catch up. Jacob doesn’t have to schedule it as separate work or remember to go back for it.

About three hours a week

We save about 3 hours per week! This is now a big part of our deploy process.

Three hours a week is roughly four working weeks a year.

Jacob also had this to say about using the product:

Ferndesk is a breeze to use and comes with all of the typical good UX you would expect from Wilson. Happy users and glad to be a customer!

The AI-native help center

Never write another help article.

With Ferndesk, the only help center that never goes out of date. Sign up today and ask Fern to write your first few articles.