Product & design teams
Keep product context moving with the work — from research to spec to launch.
The work's already moving
Hops puts your team and your AI agents in one shared place: an @Hop in every space, custom hops for specialized work, and a private assistant of your own.
Marketing & growth teams
Marketing agents draft with the context your team already has.
Sales & customer teams
Walk in with the context behind every account, handoff, and follow-up.
Founders & operators
Keep fast teams and their AI agents on the same page as the company moves.
Product & design teams
Keep product context moving with the work — from research to spec to launch.
Marketing & growth teams
Marketing agents draft with the context your team already has.
Sales & customer teams
Walk in with the context behind every account, handoff, and follow-up.
Founders & operators
Keep fast teams and their AI agents on the same page as the company moves.
Product & design teams
Keep product context moving with the work — from research to spec to launch.
Marketing & growth teams
Marketing agents draft with the context your team already has.
Sales & customer teams
Walk in with the context behind every account, handoff, and follow-up.
Founders & operators
Keep fast teams and their AI agents on the same page as the company moves.
How it works
It all starts in a Space
A Space holds the conversation, the docs, the tables, and the connected tools for one team or one project. Invite people, and ask @Hop to help out with the routine. It's always at your service to help you get things done.
Together
You've got many projects, and can have as many hops as you want. Sales watches the pipeline, finance coordinates A/R and A/P, product tackles pricing. Each one gets sharper the longer it works with its team.
Supervised
A hop only works where you invite it, and sensitive actions stop for your approval before anything happens.
Connected
Threads, docs, tables, files, and the tools your team already uses, together in one place. Your hops work from the same systems your team does.
Meet your hops
One Hop per job
Hops are named, specialized, and scoped to their team. That's how we like calling our AI agents. A few of them, mid hop:
Sales
Drafts the follow-up from the call notes and the account thread. You hit send.
RevOps
Keeps the pipeline table synced with the CRM and flags every deal that stalls.
Marketing
Writes the launch brief from the spec thread and last quarter's campaign doc. On brand, because it read the brand doc.
Finance
Matches receipts to the expense table and lists what is missing before close.
Legal
Redlines the contract against your playbook and flags what moved from standard. You make the call.
Consultant
Runs one Space per client. Deliverables, threads, and status stay current, and clients never cross.
VC
Drafts the deal memo from the intro thread and a web sweep, then keeps the pipeline table current.
Product
Reads the customer thread, updates the spec, and opens the ticket. With your sign-off.
HR
Turns the goals doc and the project threads into review prep for every manager.
A hop is not a lawyer and no legal services are provided. Use responsibly.
The work itself
Not just chat. The actual work.
Hops produce the real artifacts your team lives in, not another chat log to sift through.
Docs
Real collaborative documents. Your hops draft, edit, and comment next to your team, and every agent edit is labeled in version history.
Tables
Typed tables with views that sync to your source systems. Ask a hop to build one from a thread, then keep it current on a schedule.
Automations
Trigger, conditions, action, in plain language. Every Monday at 8, the pipeline summary posts itself. Mention cancellation, and a save draft appears.
Your stack
Your tools and your models
Hops fits into the stack you already have, and works from the same systems your team does.
Your tools
Hops connects to the systems your team already runs on, with read and write permissions you set per tool, per Hop.
Your models
Model agnostic by design. Run the AI models you trust, and bring the coding agents your engineers already pay for when the work turns technical.
Trust
Built to be trusted with real work
Hops is designed so you always stay in control of what your agents see and do.
Visible work
Every hop shows what it read, what it changed, and who asked. Agent actions land in the audit log.
Human control
Drafts wait for review. External sends and sensitive actions stop for approval.
Hard boundaries
A hop can't show you something you couldn't already see yourself. Permissions travel with the Space.
SOC 2 Type IIISO 27001ISO 42001
Support
Frequently Asked Questions
What is Hops?
Hops is multiplayer AI — the AI workspace for teams and agents. Instead of everyone working in their own private chat, your team and a team of specialist agents share memory, context, and visible work in one place.
How is this different from a normal AI chatbot?
Most AI tools are single-player: one person, one assistant, one private thread. Hops is built for how teams actually work — agents understand shared team context, work is visible to everyone, and handoffs between people and agents are clear.
Who are the agents?
Hops comes with a roster of specialist agents — Mira, Hugo, and Atlas — that work alongside your team. Each has its own focus, shares the same memory layer, and hands off cleanly when a task moves between them.
What is the shared memory layer?
Hops keeps a shared memory of your team's context so agents don't start from scratch every time. Decisions, projects, and history stay available to the people and agents who need them — no re-explaining the same thing twice.
How does Hops handle my data and permissions?
You stay in control. Memory, permissions, and sources are explicit — you decide what agents can see and act on, work is visible rather than hidden in a black box, and your data is never sold or shared with third parties.
How do I get access?
Hops is rolling out gradually. Request early access or join the waitlist and we'll reach out as spots open up.
Small hops. Big leap.
Every drafted follow up, every synced table, every brief that writes itself is one small hop. Together they change how the team moves. Early access is open.