Hop Studios pilot

Welcome to Maater

Hop is the reference pilot - shared operational knowledge next to Basecamp, with AI that can actually see the work. You are a tester shaping the product, not a customer with an SLA.

What Maater is for Hop

The place for work specs, meeting notes, client context, and chat grounded in real Basecamp todos. Basecamp stays the task authority. Maater holds the enriched context agents and teammates reuse.

Your first 15 minutes

1. Accept your workspace invite (check spam if missing) and set a password.
2. Enable the Hop Studios workspace chip so Browse is not empty.
3. Connect Basecamp (recommended) under Settings.
4. Open one client or internal doc; ask chat a question about it.
5. File feedback with the Flag tool or /pilot-feedback when something is wrong or delightful.

Rollout order

• Travis - leadership path and doc QA
• Gil - next developer onboard (approved)
• Chris - after Gil is stable (PM / client-facing validation)
• Tammy, Elena - later wave

Rowan sends invites when it is your turn. Web-only is fine; Cursor + MCP is optional for developers.

Developers

• Ingest a Basecamp todo URL via the command palette to refresh a work spec.
• Ask Rowan for the Cursor extension VSIX and hosted MCP connect steps.
• Materialized docs sync beside the client repo - that is the intended daily loop.

Links

• App - flownotes.space (pilot host until domain cutover)
• Mobile beta (Expo Go QR) - phone preview; no Expo account needed for the QR
• Public changelog
• Sovereignty / BYOK path

Full internal onboarding guide lives in the Hop workspace after you log in (hop-studios/flownotes-pilot/hop-studios-pilot-onboarding-guide.md).

Open Maater Not on the pilot? Request access