Gleo is Beach's system of work. Not a system of record: not a CRM, not a document archive, not a place where finished work goes to be filed away. Gleo is where work gets designed and delivered, day to day.
At Beach, every quest we run lives in Gleo. So do the quests we help our customers build and deliver for themselves. It is the operating layer between philosophy and practice: the place where The Beach Loop actually turns.
System of work, not system of record
Most enterprise software captures what happened. Gleo supports what is happening: the exploration, the alignment, the progress, and the evidence that makes the next campfire worthwhile.
A system of record tells you the deal closed. A system of work helps you understand why it closed, what was learned, and what quest comes next. The Beach Way lives in that second category. Gleo is how we operationalise it.
How we use Gleo
Beach runs on Gleo. Playbooks structure our client engagements. Phases mark periods of focused work. Sessions are where we gather for sensemaking. Activities move quests forward. Artefacts, tasks, and open questions capture what we discover along the way.
Teams, roles, stakeholder maps, and charters define who guides the journey and who is learning through participation. Gleo is not something we sell separately from how we work. It is how we work, made visible and repeatable.
How customers use Gleo
Gleo is also how we enable customers to build and deliver their own quests. Service companies, portfolio teams, and transformation programmes use Gleo to run playbook engagements with structure while preserving room for exploration.
The Beach Way provides the language. Gleo provides the scaffolding. Customers do not need to adopt our metaphors wholesale, but the mapping is deliberate: every concept in this handbook has a counterpart in Gleo, so teams can move from reading to running without translation loss.
The mapping
The Beach Way remains platform-independent. Gleo terminology stays accessible and generalised. The mapping below connects the two without collapsing them:
- Quest
- Playbook
- Expedition
- Phase
- Campfire
- Session
- Activity
- Activity
- Trail
- Artefacts, Tasks and Open Questions
- Landmark
- Landmark
- Guide, Smith and Apprentice
- Teams with roles, stakeholder maps and charters
Gleo, Forge, and the workshop
Gleo runs the quest. Forge hosts what gets built. Hammer compiles the content. Each serves a different layer: work orchestration, deployment, and build.
A team might sensemake in a Gleo session, capture trails as artefacts, then ship a landing page to Forge. The handbook describes the philosophy. Gleo is where it happens. The tools are how it ships.
Learn more at beach.io/products/gleo.