Question 1

What does Lyra do for me as a founder?

Accepted Answer

Lyra is your CPO. Lyra writes PRDs grounded in your actual repo, prioritizes your backlog with RICE, and defends the cuts when your roadmap needs to get smaller. Founders who use Lyra ship fewer features and reach product-market fit faster, because the cuts happen before the build, not after.

Question 2

What playbooks is Lyra trained on?

Accepted Answer

Marty Cagan's Inspired, Lenny Rachitsky's product newsletter, Teresa Torres on continuous discovery, RICE prioritization, and the kill-criterion patterns used by senior PMs at top product companies. Lyra writes the spec the way a strong CPO would — with acceptance criteria, edge cases, and an explicit reason to cut.

Question 3

When during my venture lifecycle do I work with Lyra?

Accepted Answer

Validate and Build, primarily. In Validate, Lyra writes the lightweight specs that turn an idea into something testable. In Build, Lyra owns the PRDs, the backlog, and the cuts. Lyra reappears in Grow when the roadmap starts colliding with what existing users actually want.

Question 4

Can Lyra make decisions or only recommend?

Accepted Answer

Lyra drafts and recommends — you approve. The PRD, the prioritization, the kill criterion all come from Lyra; the decision to ship, cut, or delay stays with you. Lyra is built to make those decisions easier by showing the trade-offs explicitly, not to make them for you.

Question 5

How is Lyra different from a human CPO?

Accepted Answer

A human CPO costs $250k+ and reads your issues sometimes. Lyra reads every GitHub issue every session, links related ones automatically, and bundles them into one coherent spec. The trade-off is user-research interviews and stakeholder politics, which stay human. Lyra writes the spec; you do the discovery.

Question 6

What's an example of Lyra's output?

Accepted Answer

A PRD that takes issues #34, #41, and #58 and turns them into one feature with: problem statement, target user, acceptance criteria, edge cases, the kill criterion ('cut if fewer than 20% of active users touch it within four weeks'), and a sequenced build order. The kind of doc an engineer can build from on Monday.

Lyra — your AI Chief Product Officer.

What Lyra runs

Ask Lyra

The rest of your Team

Frequently asked about Lyra