Hops Opens Shared AI Workspace After 2,500-Team Early Access

More than 2,500 teams tested Hops in early access before the collaborative AI workspace opened to the public on November 10, 2026. The launch touches a decision many HR and operations leaders now face: whether AI belongs in individual chat windows or inside the shared documents, workflows and permissions that govern how teams actually work.

Hops, built by For Good AI and led by founder and CEO Andrew Filev, places AI agents into shared team documents, reusable work methods and custom apps. Filev previously founded Wrike, which was acquired for $2.25 billion, and the same team develops Zencoder's AI coding agents.

Why the founder thinks productivity gains stall

Filev's premise is that faster individual output has not produced matching company-wide gains. In his conversations with founders and executives of established companies, most estimate their organizations move only 10% to 20% faster than a year earlier — far short of the 2x improvement individual AI tools would suggest.

He draws a direct parallel to earlier workplace technology: "The PC era didn't pay off when PCs got faster. It paid off when they were networked. I believe AI will follow the same path."

What changes for day-to-day team work?

In Hops, people and the agent work together in shared chats, documents, tables and decks. When someone asks the system to draft or revise material, it writes directly into the shared file, so participants work from one version instead of shuttling AI output between private chats and team documents. The product page describes live editing, with AI document edits visible in version history.

Three capabilities stand out for people-operations teams:

• Reusable skills. A team can save a working method — instructions, context and format — as a skill. The knowledge owner controls access and can update it. Hops cited its own marketing lead, who taught the system the company's voice so a salesperson could request a customer email written straight into a shared document.
• Custom apps. If a team lacks a tool, it can describe an application and have Hops build and run it inside the workspace using the same data and permissions. Hops connects to more than 2,000 apps, including CRM and cloud-storage tools.
• Embedded operations. Hops reports that 30 engineers and a fleet of AI agents rebuilt its collaboration stack in a year. The company now runs its own CRM, support desk, IT requests and project tracking in the product, and employees can ask about leave policy and receive an answer linked to the handbook.

How do permissions and pricing work?

Under the permission model, Hops will not use a file the requester cannot open. If an answer draws on information others in the thread cannot see, the reply is held until the requester approves it. External sends and sensitive changes also wait for human approval, and administrators can restrict which teams use connected tools or set them to read-only.

Pricing is consumption-based rather than per-seat. The pay-as-you-go plan includes 5,000 free credits at $0 per user per month, with top-ups of 20,000 credits for $20. Teams draw from a shared balance, administrators can set per-teammate spending limits, and purchased credits stay valid for 12 months. Chat, documents and collaboration do not consume credits; consumption depends on the model, information read, tools used, number of steps and output length.

Enterprise plans add the full integration library, SSO, SCIM and audit controls, security review, custom terms and the option to bring an API key. Hops says it does not use customer data to train models.

What does early adoption show?

Discern Security CEO Sai Venkataraman said in the launch release that his sales and marketing teams use Hops for pipeline reviews, event and website-prospect follow-ups, and campaigns. He added that the product replaced tools including Slack and Jira at his company.

The public opening turns Hops's early-access period into a broader adoption test. Shared skills and permission controls aim to make AI output reusable without widening access to underlying information, while credit pricing ties heavier automation to consumption. The open question is whether teams will move enough recurring work into the workspace for shared methods to close the company-level gap Filev described as lagging.