Overview
- Help center created from scratch in the first week
- Solo set up in <10 minutes; content generated within 24 hours
- Answers 200+ product questions per month
- Weekly product updates automatically distributed company-wide
How State Affairs wrote 150 articles in under a week, allowing customers to self-serve answers.
Justin Lawson
CRO at State Affairs
Problem
State Affairs is one of the fastest-growing policy intelligence platforms in the market. The team has invested heavily in product, AI, and reporting — but growth began to strain internal communication and support.
"We were moving really fast, but lacked a reliable way to communicate new functionality to customers and internal teams. As tickets increased, it started to drag on our teams."
Documentation was fragmented and treated as a side task across teams, resulting in gaps, outdated content, and no clear ownership.
State Affairs needed to rebuild their help center from scratch. More importantly, they needed a system that could keep documentation accurate as the product evolved, without adding ongoing overhead.
"If you're building fast—especially with AI—you can't rely on manual documentation. It has to maintain itself. There were plenty of tools that could host content. None actually created and maintained it automatically."
Solution
Setup took ~10 minutes, and Solo was live within 24 hours.
State Affairs uploaded ~150 core product concepts. Within a week, Solo generated full documentation for each using the product's codebase. After a light review, everything was published via Featurebase, immediately enabling customer self-service.
"It would have taken 10x the time to manually write even 10% of this."
As the product continues to evolve, Solo automatically updates documentation, removing the need for ongoing manual maintenance.
Impact
Solo quickly became more than a documentation tool; it became the system of record for product knowledge.
"We're shipping so fast that support and sales couldn't keep up."
Today, Solo:
- Answers 200+ product questions per month
- Sends weekly product updates across the company
- Provides a real-time, trusted source of truth for how the product works
- Updates Help Center content without intervention
ROI
The ROI is straightforward.
Without Solo, this work requires:
- Dedicated documentation ownership
- Ongoing release note creation
- Constant internal support for product questions
"Once you quantify the time this replaces, Solo is irrelevant from a cost standpoint."
Overview
- Help center created from scratch in the first week
- Solo set up in <10 minutes; content generated within 24 hours
- Answers 200+ product questions per month
- Weekly product updates automatically distributed company-wide
Problem
State Affairs is one of the fastest-growing policy intelligence platforms in the market. The team has invested heavily in product, AI, and reporting — but growth began to strain internal communication and support.
"We were moving really fast, but lacked a reliable way to communicate new functionality to customers and internal teams. As tickets increased, it started to drag on our teams."
Documentation was fragmented and treated as a side task across teams, resulting in gaps, outdated content, and no clear ownership.
State Affairs needed to rebuild their help center from scratch. More importantly, they needed a system that could keep documentation accurate as the product evolved, without adding ongoing overhead.
"If you're building fast—especially with AI—you can't rely on manual documentation. It has to maintain itself. There were plenty of tools that could host content. None actually created and maintained it automatically."
Solution
Setup took ~10 minutes, and Solo was live within 24 hours.
State Affairs uploaded ~150 core product concepts. Within a week, Solo generated full documentation for each using the product's codebase. After a light review, everything was published via Featurebase, immediately enabling customer self-service.
"It would have taken 10x the time to manually write even 10% of this."
As the product continues to evolve, Solo automatically updates documentation, removing the need for ongoing manual maintenance.
Impact
Solo quickly became more than a documentation tool; it became the system of record for product knowledge.
"We're shipping so fast that support and sales couldn't keep up."
Today, Solo:
- Answers 200+ product questions per month
- Sends weekly product updates across the company
- Provides a real-time, trusted source of truth for how the product works
- Updates Help Center content without intervention
ROI
The ROI is straightforward.
Without Solo, this work requires:
- Dedicated documentation ownership
- Ongoing release note creation
- Constant internal support for product questions
"Once you quantify the time this replaces, Solo is irrelevant from a cost standpoint."