Happy Friday before a long weekend!
Requirements generation is a commodity
When I started Glossa a year ago, it was novel and valuable to generate high-quality requirements. (Remember when everyone was using Fireflies for meeting notes?)
Now, nearly everyone I talk to is generating initial requirements or user stories from conversations (with varying levels of success) by using copy-paste and Claude, NotebookLM, or Copilot.
That’s where most people stop on their own - once you need team collaboration, you need a tool like Glossa (requirements evolve as discovery continues, multiple people work on the same project and need a shared source of truth, projects need to be consistent across practitioners to preserve margin).
Internal collaboration is the tip of the iceberg, though. As we look ahead, we’re thinking a lot about the place where working with people is even harder: collaborating with clients.
Our existing client portal - where clients can upload documents, answer questions, and review requirements and user stories - is the foundation. But client interactions and interfaces are not limited to that set of use cases: demo feedback, UAT, training and adoption are all points of friction today.
What else would you want to see in Glossa’s client portal to help make your partnership with your client seamless and strategic, rather than snarled in admin?
What We Shipped This Week & What's Coming Next
This week:
See the impact of each meeting - Every conversation is important, whether you’re learning new requirements, getting basic questions answered, or confirming decisions you’ve already made. Now, you can see the impact of each file on your project in summary form: how many (and which) requirements, outcomes, user stories were created, which discovery questions were answered, and which existing requirements were updated. Check it out on the new Recent Activity section on your project dashboard.
Smarter category-to-outcome mapping - If you've mapped a parent category to a business outcome, child capabilities inherit that outcome automatically. This makes mapping simpler and easier to digest at a glance.
Better CSV export - Now better formatted, to make export/import into downstream tools simple and seamless (thanks for this one, Patrick!)
Coming next:
Workflow diagrams - We are finalizing the visualization and would love your feedback. Which of these 4 options do you prefer?
MCP - get requirement richness where you already work, whether that's Claude, Salesforce, or somewhere else
Weekend Request
Who runs your sprint demos? How do you prep for them, and how much detail do you go into?
If you tell me a bit more about how things work for you, I’ll share some early ideas :)
Also: See you at Dreamforce! Reach out if we haven’t already put a time on the books.
Have a great long weekend!
- Ali