We built this because we ran too many sessions that lost momentum between the agenda doc and the room. The tool is the bridge we wished we had.
This platform started as an internal tool for a team running agile ceremonies at scale. The problem was not that facilitators did not know how to run sessions. They did. The problem was that the logistics of preparation, the live board, and the follow-through all sat in three different tools and none of them talked to each other.
The first version was a retro builder wired to a Firestore board and a Vertex AI function. It ran its first session in a single afternoon. The feedback was simple: the prep time dropped, the close summary was actually accurate, and the action items got done. Those three things are not complicated. They just require the tool to stay in the loop for the whole session, not hand you a document and walk out.
We stripped out everything specific to the original team's infrastructure, made the platform tenant-portable, and opened it. The method library is hand-curated. The AI co-facilitator runs four modes that map to how facilitation actually works. The self-host option means a company with strong data policies can adopt it without a procurement negotiation.
The brand name is still being chosen. The product is not. It works, and teams are using it. This is what it is.
Founder name TBD
Replace with founder details once the brand is confirmed
These are not aspirations on a wall. They show up in how the product is built.
Good facilitation first
The method library is curated by facilitators, not by what is easy to automate. The AI recommends methods that actually work; it does not just fill in the nearest template.
Your data stays yours
We designed the self-host path before we designed the SaaS pricing. A team's retro notes and planning discussions are candid. They belong inside the team's boundary, not an external vendor's database.
Method over magic
The AI explains its reasoning. You can see why it chose a method, push back, and adjust. We want facilitators to get better at their craft by using the tool, not to hand the decisions over.
Built to expand, not to bloat
Agile ceremonies are the first slice. The architecture is designed to add workshop families without rebuilding. We add a new type when the method library for it is ready, not when the roadmap says so.
Free to try. No card required. If it does not make your next session better, nothing is owed.