# Type

> Type is a shared workspace where your entire team can collaborate with Claude or Codex using the subscriptions you already pay for.

This is the full-text companion to https://type.com/llms.txt. It contains the published answers from every public page on https://type.com in one document: plan prices, competitor comparisons, customer results, setup instructions, and the launch announcement. Each section links the page it came from, and every claim is copy that page renders. For current product commands and capabilities, follow https://docs.type.com/llms.txt instead of this file.

## Pricing

Source: https://type.com/pricing

Choose a plan for 2 to 60 team members. Every plan includes the full Type workspace and twice its monthly price in AI usage credits.

### Plans

- **Basic** — $50/month for 2 team members and 100 credits / mo. For individuals and small teams bringing their first recurring AI workflows into a shared Space.
- **Pro** — $100/month for 4 team members and 200 credits / mo. For teams using Type throughout the week across shared conversations, connected tools, and repeatable work.
- **Enterprise** — $250/month for 20 team members and 500 credits / mo, or $500/month for 40 team members and 1,000 credits / mo, or $750+/month for 60 team members and 1,500 credits / mo. For teams running Type every day across more people, Spaces, and automated work.

### Pricing questions

**What are AI usage credits?**

AI usage credits cover model requests made with Type-provided AI access. Usage is measured from the underlying model cost, so different models and requests can consume different amounts.

**Do the plans have different features?**

No. Basic, Pro, and Enterprise include the same Type workspace capabilities. Choose based on your team size and how much AI usage you expect each month.

**What happens when we use our monthly credits?**

Type warns workspace admins around 80% of the allowance. At 100%, new AI work pauses by default until you upgrade, add credits, or the next billing period begins. If you enable auto-upgrade, Type moves you to the next price point instead. On the $750+ Enterprise plan, AI work continues and admins keep receiving warnings.

**Can we use our own Claude or Codex subscription?**

Yes. Team members can connect supported Claude or Codex subscriptions. Eligible requests are routed through those subscriptions and do not use the workspace's Type credits.

**Does it cost to add more team members?**

Yes. Each plan includes the number of team members shown above. To add more people, choose the next plan size or contact us for a custom contract beyond 60 members.

## Comparisons

### Type vs Claude Tag: AI teamwork beyond Slack

Source: https://type.com/claude-tag-vs-type

Compare Type vs Claude Tag on company memory, model lock-in, API pricing, integrations, and Slack-only workflows.

**Is Type a Claude Tag alternative?**

Yes. Both bring AI into Slack. The difference is who controls your company memory, model choice, pricing, integrations, and where work happens. The real tradeoff is who controls your company memory, context, and workflows, and Type keeps that work portable across models, tools, and teammates.

**What are the alternatives to Claude Tag for AI in Slack?**

Type is the alternative this page compares. Start with Type when your team needs portable memory, model choice, broader integrations, and work that moves across Slack, the browser, and the repo.

**Who owns our company memory and context?**

In Type, company memory, project context, and workflows are owned by you and easily portable across models, so you keep memory, files, decisions, and workflows in Type instead of binding them to one model provider. With Claude Tag, memory, context, and workflows live inside Anthropic, which makes switching providers hard later.

**How does model choice compare?**

Type lets you use the best model for each job and control your costs with a provider aligned with your business, so you can build durable team workflows without making any single provider the permanent home for company context. With Claude Tag you are stuck with the models Anthropic provides, at the prices Anthropic sets.

**How does pricing compare?**

Claude Tag requires a paid Claude Team subscription and charges by API request on top. Type uses your existing Claude or Codex subscriptions, and lets you use cheaper models where it makes sense.

**How do integrations compare?**

Type has 1,000+ integrations, with secure and flexible permissions and access across your team's apps, and you manage those permissions for your team in a way that's specific to your company. Claude Tag has only a dozen native integrations, connected in a rigid way.

**Where does the work actually happen?**

With Type your team works collaboratively in Slack and in a dedicated desktop experience. Claude Tag is focused on the Slack experience, with a desktop experience that is very much single-player.

### Type vs Viktor: AI teamwork without the API bill

Source: https://type.com/viktor-vs-type

Compare Type vs Viktor on API pricing and cost alignment, model choice, organization-level security and permissions, and Slack-only workflows.

**Is Type a Viktor alternative?**

Yes. Both put AI to work across your team. The difference is in pricing and cost alignment, AI model flexibility, security and permissions, and flexibility for your team to work where they want. The real tradeoff is whose incentives your AI platform serves: Type gets the most out of the subscriptions you already have and keeps security manageable as agentic work scales.

**What are the alternatives to Viktor for team AI work?**

Type is the alternative this page compares. Start with Type when your team wants to get the most from existing subscriptions, manage security at the org level, and work in a dedicated desktop and mobile experience rather than inside Slack or Microsoft Teams only.

**How does pricing compare?**

With Viktor you pay direct API prices on every request, stacked on top of the AI subscriptions you already have. Type connects the Claude or Codex subscriptions you already pay for and gets the most out of them, with cheaper models where it makes sense, so you cut spend instead of stacking API bills on top.

**Whose incentives does each one serve on cost?**

Viktor earns more as your API usage grows, so the incentive is to maximize your token spend. Type is aligned with you on saving costs: Type wins when your team gets more done, not when you burn more tokens.

**Can I switch AI models per task?**

In Type, yes. Switch models per task in one click and route each job to the model that does it best and cheapest. Viktor is built around one model choice, so switching models or providers is hard.

**How do security and permissions compare?**

In Type, integrations, permissions, and access are managed at the organization level, with the right scope for every team and agent, instead of being scattered across individual users. Viktor is a single super agent with permissions tied to individual users, which makes org-wide integrations and security hard to manage.

**Do I have to work inside Slack or Microsoft Teams?**

Not with Type. Type has dedicated desktop and mobile apps built for agentic work, plus Slack when that's where the conversation is, so your team's best AI users get a real workspace rather than just a chat sidebar. Viktor requires you to work inside Slack or Microsoft Teams, which strains as your team scales up agentic work.

### Type vs Buzz: shared AI channels that work out of the box

Source: https://type.com/buzz-vs-type

Compare Type and Block's Buzz on setup and hosting, where your team can work, shared cloud agents, integrations, permissions, and total cost.

**What is Buzz?**

Buzz is an open-source project from Block that puts people and AI agents in shared channels, built on the Nostr protocol with a Rust relay, a Tauri desktop app, and a Flutter mobile app in development. It is Apache 2.0 licensed, and the hosted service at buzz.xyz is labeled a developer preview and is free.

**Is Type a Buzz alternative?**

Yes, for teams that want the shared people-and-agents channel model without operating it. Type is a hosted AI workspace with the same premise and a different delivery: built for a whole company rather than just its engineers, cloud-first instead of running on laptops, no relay to run, a full browser client, cloud agents the whole team shares, nearly 1,000 integrations an admin controls centrally, and a Slack integration so you do not have to replace your chat tool to adopt it.

**Does Buzz require self-hosting?**

Not strictly. Block runs hosted relays at buzz.xyz, free, invite-only, limited to three communities per account. Hosted communities are not end-to-end encrypted. If you want your own instance, the relay needs Postgres, Redis, an S3-compatible object store, a git data volume, and TLS termination. Block publishes a one-click Railway template that handles the initial deploy, after which the relay and its keys are yours to run.

**Can I use Buzz in a browser?**

Only partly. The relay serves a browser client scoped to repository browsing and invite acceptance, and Buzz's own docs note it has no pull request or issue pages. Chat, channels, and agents require the desktop app. Type runs the entire workspace in any browser with nothing installed.

**Does Buzz have a mobile app?**

A Flutter app exists in the repository with working chat and agent-activity screens, but there is no published build on any distribution channel, including the App Store, Play Store, TestFlight, and direct APK. Mobile means building from source today, and it covers 10 feature areas against 29 on desktop. Type runs in a mobile browser now, reaches phones through Slack, and has an iPhone app coming.

**Where do Buzz agents run, and can a team share one?**

Agents run as local processes the desktop app spawns, so an agent stops when that machine sleeps. Block's remote-agent document describes exactly this limitation, and remote agents are still a spec in review. You can open an agent to a channel, and Buzz shows a persistent warning that anyone can then use it to access your computer, including files, accounts, and connected tools. Type agents run in the cloud on a persistent computer that the whole channel shares.

**How does access control compare?**

Buzz's VISION.md states that the relay enforces all access control and channel membership is the only gate, with membership administered by public key through the relay's admin CLI. Type separates personal from organization connections, assigns them per Space, and has agents act with the access of the person and conversation that started the work. Neither product ships SAML or SCIM today.

**What happens if someone loses their key in Buzz?**

Block's terms are explicit: because of the key-based identity model Block generally cannot recover, reset, or restore a lost private key, and if your key is lost you may permanently lose access to your account and associated content. Every agent needs its own keypair, and the agent's secret is not stored and cannot be recovered. Type uses ordinary accounts, so a lost laptop means signing in again.

**Do I have to replace Slack to use Type?**

No. Type connects to the Slack you already run, so your channels stay where they are. Mention an agent from Slack, route a Slack user group to a Space, or DM Sidekick as a native Slack assistant with the same context, skills, and memory it has in Type. Teams adopt Type gradually rather than migrating on day one. Buzz has no Slack integration and is itself the chat app, so adopting it means moving conversations into it.

**Is Buzz or Type better for non-technical teams?**

Type. Buzz's README describes it as another AI-adjacent developer tool, and the capabilities it leads with are opening repos, sending patches, and reviewing code. Type ships blueprints for Marketing Manager, Sales Operations, Support Specialist, Product Engineer, Data Analyst, and HR Partner, and nothing in the first-run path requires a terminal, a keypair, or a config file.

**Do I have to @mention the agent every time?**

In Buzz, yes: its harness queues @mention events per channel, so an unmentioned question goes unanswered. In Type the agent replies by default, with a classifier that decides when it is being asked something and stays quiet during human back-and-forth. You switch the composer to Team message when you want people only.

**How do the two handle integrations across an organization?**

Type manages them org-wide: an admin connects a tool once and assigns it to the Spaces that should have it, personal and organization connections stay separate, and every connection is revocable. Buzz has no connector catalog, so integrations are MCP servers each person wires up on their own machine, capped at 16 per session, with no central way to see, grant, or revoke them.

**How many integrations does Buzz have?**

There is no connector catalog. Integration happens through MCP servers each person configures on their own machine, capped at 16 per session, and a workflow's only outbound action is a generic webhook call. Type has nearly 1,000 native integrations across 16 categories plus a custom API connector for anything else.

**Which AI models and harnesses does each support?**

Buzz supports any agent speaking ACP over stdio, with twelve documented presets including goose, Claude Code, and Codex, which is broader harness support than Type. You supply and pay for the model, since Block's terms state Block does not provide, resell, host, or guarantee access to any AI model. Type runs Claude and Codex with the harness, model, reasoning level, and speed selectable per thread, as a Space default, and per automation.

**What does each cost?**

Buzz is free and Apache 2.0, with no paid tier on the hosted service, and you pay your model provider plus any self-hosting infrastructure. Type starts at $50 per month after a 14-day free trial for 2 team members and $100 of included AI usage, scales to plans for 60 members, meters AI usage at provider published rates, and does not meter requests that run through a personal Claude or ChatGPT subscription you connect.

**Is Buzz production ready?**

Block uses it internally and says so, and buzz.xyz is labeled a developer preview while the README says it is not finished. The code is candid about the gaps: a workflow that reaches an approval gate is logged as not yet implemented and the run is marked Failed, and two workflow actions, send_dm and set_channel_topic, return NotImplemented. Block also tells its own employees to use an internal build rather than the open-source release.

### Type vs Claude Cowork: a shared channel instead of a solo session

Source: https://type.com/cowork-vs-type

Compare Type and Claude Cowork on session sharing, team memory, Slack, admin controls, integrations, and what each one costs.

**What is Claude Cowork?**

Cowork is Anthropic's agent for knowledge work inside claude.ai. You describe a task, Claude works through it with your connectors and files, and you watch it go. Sessions run either in an Anthropic-hosted cloud sandbox, which is the default and is labeled beta, or locally with code execution inside a VM on your own machine. Anthropic shipped a research preview in January 2026 for macOS and Max subscribers, made it generally available on macOS and Windows in April, and added web and mobile in July.

**Is Type a Claude Cowork alternative?**

Yes, if what you want is a team using AI rather than individuals using AI. Cowork gives one person a very capable agent working in a session only that person can see. Type gives a team a shared channel where the agent works in front of everyone, so anyone can hand it work, read what it did, and pick up a thread somebody else started. Type runs on Claude, so this is not a choice between Cowork's capability and a weaker model.

**Can two people work in the same Cowork session?**

No. Anthropic's own limitations list states that sessions can't be shared with others. Cowork does follow you across devices, so you can open your session on a phone or a second computer to check progress or redirect it, which is one person on several devices rather than several people in one session. There are no observers, no comments, no assignment, and no handoff. In Type the thread is the unit of work, so a coworker reads the whole session and continues it without being invited to anything.

**Does Cowork remember what I told Claude in chat?**

Not yet. Anthropic states that what Claude remembers about you in chat doesn't carry into Cowork sessions, and that within Cowork memory is supported in projects only. Type memory belongs to the Space, so what one person taught the agent about your pricing, your customers, or your naming conventions is there for the next person who asks, including the agent's scheduled runs.

**Can I use Cowork from Slack?**

No. Anthropic's Slack product is Claude Tag, and its docs place Cowork in claude.ai chat and Claude Tag in Slack channels, with the guidance that team work goes to Claude Tag while personal work goes to Cowork or Claude Code. Mentioning Claude in Slack starts a Claude Tag session on the Claude Code engine rather than a Cowork session, and Claude Tag runs on service-account credentials an admin sets per channel instead of your own connectors. Type connects to the Slack you already run: mention an agent in a channel, route a Slack user group to a Space, or DM Sidekick as a native Slack assistant with the same context, skills, and memory it has in Type.

**Can an admin control who gets Cowork?**

On Team plans, barely. Anthropic states that the Cowork toggle is organization-wide, so either all members have access or none do, and that Team plans don't have access to the controls that would narrow it. Type manages access the other way around: an admin connects a tool once for the organization and assigns it to the Spaces that should have it, personal and organization connections stay separate, and every connection is revocable.

**Where does Cowork actually run the work?**

Both in the cloud and on your machine, depending on the session. Cloud sessions are the default and run in a per-session sandbox Anthropic isolates and hosts. Local sessions run the agent loop natively on your computer with code execution inside a VM built on Apple's Virtualization.framework or Hyper-V. Local mode has a consequence Anthropic spells out: conversation history stays on the user's computer, is not subject to Anthropic's standard data retention policies, and cannot be centrally managed or exported by admins. Type agents run in the cloud per Space, and the work stays in the workspace where the team can read it.

**Can Cowork share what it built with my team?**

Through live artifacts, with limits Anthropic documents plainly. Sharing requires a Team or Enterprise plan, since Pro and Max can't share or publish them. They are desktop-only and stored on your computer, so they don't come with you when you switch devices. There are no external or public links and no per-person recipient selection, so anyone in your organization holding the link can open it. A shared one connects to the viewer's connectors rather than yours, so what it shows changes depending on who opens it. Type documents and apps live in the workspace, co-edited with live presence, with read, edit, suggest, manage, and publish permissions and revocable public links.

**How do the two handle integrations?**

Cowork uses your personal connectors, which is the design: your Google Drive, your Jira, your Slack, authorized as you. That suits your own work and leaves an admin nothing to grant or revoke on anyone else's behalf. Anthropic also notes that the always-allow setting for connector tools is off by default and that most custom connectors don't annotate their tools, so every tool on those connectors is gated behind a prompt. Type has nearly 1,000 native integrations across 16 categories that an admin connects once and assigns to the Spaces that should have them, plus a custom API connector for anything else.

**Which Cowork features depend on which plan?**

More than you would expect, and they point in opposite directions. Anthropic documents auto mode as available for Pro and Max plans only, and computer use as Pro and Max only with Team and Enterprise having no access to it. Live artifact sharing inverts that: Team and Enterprise only, unavailable on Pro and Max. Dispatch, which lets you send work from your phone to your desktop, is a Pro and Max beta, and Anthropic notes it runs as one continuous thread with no way to start a new thread or manage multiple threads. Type's five self-serve tiers include 2, 4, 20, 40, or 60 team members and a shared pool of AI usage.

**How does recurring work compare?**

Both do it, and Cowork does it well: Anthropic ships scheduled tasks and says they run without a device online. The difference is where the result lands. Type triggers on a schedule, a webhook, an app event, an RSS feed, a Slack message, or an email sent to the Space's own inbound address, and the run posts into the channel where teammates can read it, correct it, or take it further. A Cowork scheduled task reports back into the session of the person who created it.

**What does each cost?**

Cowork is priced through Claude plans. Pro is $20 per month or $17 per month billed annually. Max is $100 per month at 5x usage and $200 at 20x. Team is $25 per standard seat per month or $20 billed annually, and $125 per premium seat or $100 billed annually, with a two-member minimum and a 150-seat ceiling. Enterprise is $20 per seat per month billed annually with usage billed separately at API rates, requiring 20 seats self-serve or 50 through sales. Anthropic also notes that working on tasks with Cowork consumes more of your usage allocation than chatting with Claude. Type starts at $50 per month for 2 team members and $100 of included AI usage; plans scale to 60 members, with AI metered at provider published rates.

**Can admins see what Cowork did?**

Partly, and the published answer depends on which page you read. Anthropic's Cowork product page says Cowork activity is not yet captured in audit logs or the Compliance API, while its support documentation says Cowork via mobile and web is captured in the Compliance API, so confirm the current state with Anthropic before relying on either. Local sessions are unambiguous: Anthropic states their conversation history sits on the user's computer, outside standard retention policies, and cannot be centrally managed or exported by admins, and it answers plainly that endpoint detection tools cannot inspect activity inside the VM. In Type the agent works in a channel, so the record of what it did is the thread, readable by anyone with access to that Space.

**Do I have to give up Claude to use Type?**

No. Type runs Claude and Codex, with the harness, model, reasoning level, and speed selectable per thread, as a Space default, and per automation. If your team already pays for Claude or ChatGPT, connect those subscriptions and the requests that run through them are not metered against the workspace at all. Plenty of teams keep Cowork for individual work and use Type for the work more than one person touches.

**Which is better for a team where most people are not technical?**

Type, mostly because the shared channel teaches people. Someone watches a coworker hand the agent a task, sees what came back, and copies the pattern the same afternoon. A Cowork session is private, so that never happens in front of anyone. Type also ships six blueprints, Marketing Manager, Sales Operations, Support Specialist, Product Engineer, Data Analyst, and HR Partner, arriving with 21 skills and 16 scheduled automations already written between them.

**What are Cowork's current limitations?**

Anthropic publishes them, which is worth crediting. Sessions can't be shared with others. Chat memory doesn't carry into Cowork, and inside Cowork memory works in projects only. Cowork projects aren't shareable with teammates, while claude.ai chat projects are on Team and Enterprise. Live artifacts and plugins that include local MCP servers work through the desktop app only. Anthropic also states that the risk of prompt injection attacks is non-zero, and that network egress permissions don't apply to the web fetch or web search tools or to MCPs.

### Type vs Claude Team: per-seat Claude, or one shared workspace

Source: https://type.com/claude-team-vs-type

Compare Type and the Claude Team plan on shared chats, team memory, connectors, Slack, admin controls, and what ten seats actually cost.

**What is the Claude Team plan?**

It is Anthropic's paid seat-based plan for Claude, built for groups of 2 to 150 people. Standard seats are $25 per member per month billed monthly or $20 billed annually. Premium seats are $125 monthly or $100 annually, and Anthropic describes them as offering more usage rather than more features. Every seat includes Claude on web, desktop, and mobile, Claude Code, Cowork, projects, a 200k context window, SSO, JIT provisioning, and admin-enabled connectors.

**Is Type a Claude Team alternative?**

Yes, and the difference is what you are buying. A Claude Team subscription buys each person their own Claude. Type plans include seats for 2 to 60 team members in one shared workspace where Claude works inside visible Space threads and memory belongs to the team. Type runs Claude, so this is not a trade between collaboration and model quality.

**Can two people work in the same Claude chat on the Team plan?**

No. Anthropic states that even if a project is public, your chats within that project will be private and inaccessible to other members of your organization unless you manually share them, and that chats within a project are not shared by default. Manual sharing produces a snapshot: the shared view includes the messages sent before you shared, and later messages stay private until you update it. Nobody prompts into your conversation. In Type a thread is the shared unit, so a coworker reads the whole session and continues it without being invited.

**What does the Team plan actually share between teammates?**

Projects and their knowledge base. Anthropic documents public projects that everyone in the organization can find and use, and private projects shared with named people at can-view or can-edit level. Sharing a project shares the knowledge base, and Anthropic is explicit that your chats stay private unless you choose to share them. Sharing a project with a group requires an Enterprise plan and is in beta. So the reference material is shared and the work is not.

**Is there shared team memory on the Claude Team plan?**

No. Anthropic states plainly that Team plans do not have organization-level controls for memory features and that individual Team plan members manage their own memory settings directly. Team plans are also held on the older memory experience: Anthropic says free, Pro, and Max users are being migrated to the improved version while users on Team and Enterprise plans stay on the legacy experience for now. Each project keeps its own separate memory space. Type memory is scoped to the workspace, the Space, or the person, so a correction one teammate makes is there for the next one and for scheduled runs.

**What happens to sharing once Claude is connected to our tools?**

It stops. This is the constraint most teams do not see coming, and Anthropic documents it in two lines: for Team and Enterprise plans, connectors are only available in private projects, and chats with synced content can't be shared. So the moment Claude pulls from your Drive, your GitHub, or your Microsoft 365, that conversation is both inside a private project and unshareable. Enterprise search behaves the same way: Anthropic notes conversations within your search project are private to you unless you manually share them. In Type, connections are assigned to a Space and the resulting thread is visible to that Space by default.

**Who controls connectors on the Team plan?**

An Owner or Primary Owner, and this part is genuinely well built. Anthropic requires an Owner or Primary Owner to enable a connector for the organization before members can use it, and enabling it does not grant anyone access because each person still authenticates individually. Owners can also set each tool to always allow, needs approval, or blocked, and Anthropic states this applies org-wide and individual users can't override it. Claude inherits each person's permissions from the connected service. Type works the same way in shape: an admin connects a tool once for the organization and assigns it to the Spaces that should have it.

**Can we use Claude from Slack on the Team plan?**

Yes, through Claude Tag, which replaced Claude in Slack on August 3, 2026 and is in beta on Team and Enterprise plans. It is Anthropic's one genuinely multiplayer surface, and their wording is worth quoting: everyone in a channel works with the same Claude, so anyone can steer it or pick up where it left off. Two things to know. Only a Primary Owner or Owner can set up its access and channels, and the Admin role can't. Channel usage is billed to the organization while direct messages are billed to the individual's own Claude account. Type connects to the Slack you already run, with the same context, skills, and memory the agent has in Type.

**Is Claude Code included in the Team plan?**

Yes, on every seat. Anthropic states Claude Code is included with every Team plan seat and that premium seats offer more usage for heavier workloads, not exclusive access. That covers the terminal plus supported IDEs including VS Code, Cursor, and JetBrains. It is one of the strongest things about the plan, and Type does not replace it. Type runs Claude and Codex for shared work and its CLI can move a local Claude Code or Codex session into a Type thread when a teammate needs to see it.

**How do usage limits work on the Team plan?**

Per person, which is a real advantage. Anthropic states usage limits on Team plans are per-member rather than applied to the team as a whole, and that if one member reaches their limit it does not affect the limits of other members. Standard seats get 1.25x more usage per session than Pro and Premium seats get 6.25x, though the pricing page describes the same premium seat as 5x a standard one. Weekly limits reset at a fixed time. Type pools usage across the workspace instead, which suits uneven teams and means one heavy week does not strand a colleague.

**What does each cost for a team of ten?**

Ten Claude Team standard seats are $250 per month billed monthly, or $2,400 for the year billed annually, which is Anthropic's own worked example. Premium seats put the same ten people at $1,250 monthly or $1,000. A ten-person Type team fits the $250 Enterprise plan, which includes up to 20 team members and $500 of AI usage, with AI metered at the providers' published API rates beyond that. The honest comparison depends on volume: Claude Team bundles a generous per-seat allowance into the seat price, so a team of heavy daily users may pay less per unit of AI there than they would metered in Type.

**Does the Team plan charge for usage beyond the seat?**

Only if you opt in. Anthropic's model is pre-purchased usage credits billed at standard API rates, which Owners control with spend limits and can disable completely, and it says that when credits are disabled members will be unable to continue working once they reach their limits and will need to wait for them to reset. So the default is a predictable flat bill with a hard stop. Two billing details worth knowing: removing a member does not trigger an immediate credit or refund because you have to reduce the seat allocation, and Anthropic accepts cards only, not ACH bank transfers.

**What admin controls does the Team plan include?**

More than people expect at $20 a seat. SSO and just-in-time provisioning are both available on Team plans. Owners can verify a domain and block new personal accounts from being created. There are three fixed roles, owner, admin, and user, plus spend controls at the organization and individual level, and usage analytics for Owners and Primary Owners. What requires Enterprise: SCIM, which Anthropic says is not available for Team plans, audit logs, which are available for Enterprise organizations only, the Compliance API, custom data retention controls, custom roles, and claiming or migrating existing accounts on your domain.

**Does Anthropic's documentation contradict itself on Team admin features?**

In two places, and we would rather flag them than pick a side. The Team plan article lists Single-Sign-On and Domain Capture together as Team features, while the domain article says domain claiming is supported on Claude Enterprise plans only and that Team plans can verify a domain and block new personal accounts but admins can't claim or migrate existing accounts. The same Team article lists role-based permissioning as a Team feature, while the roles article heads its section custom roles, Enterprise plans only. If either matters to your rollout, get it in writing from Anthropic.

**Do I have to give up Claude to use Type?**

No, and most teams should not. Type runs Claude and Codex, with the harness, model, reasoning level, and speed selectable per thread, as a Space default, and per automation. If people already pay for Claude or ChatGPT, connect those subscriptions and the requests that run through them are not metered against the workspace at all. A common shape is Claude seats for the individuals who need Claude Code all day, and Type for the work more than one person touches.

**Which is better for a team where most people are not technical?**

Type, and the reason is visibility rather than ease. On a Claude Team plan every colleague sits in front of an empty chat box and has to work out what to ask. In Type they watch a coworker hand an agent a task in a channel, see what came back, and copy the pattern that afternoon. Type also ships six blueprints, Marketing Manager, Sales Operations, Support Specialist, Product Engineer, Data Analyst, and HR Partner, arriving with 21 skills and 16 scheduled automations already written between them.

## Customer results

### How Intelligems Cut Support Answer Time in Half With Type

Source: https://type.com/customers/intelligems

See how Intelligems built a 1,500-entry support knowledge system, cut answer creation time roughly in half, and keeps company knowledge current in Type.

- 1,500 support knowledge entries
- 50%+ faster answer creation
- Nightly company knowledge refresh
- 100 people building with AI together

### How Raycon Made AI Accessible to Their Whole Team

Source: https://type.com/customers/raycon

See how Raycon got 50+ people building with AI together, built 127 reusable skills, and runs 26 unattended automations across shared company Spaces.

- 3,262 agent runs in three months
- 127 skills built by Raycon's team
- 26 unattended automations

## Type for a team or industry

### A Shared Space for Ecommerce Operations

Source: https://type.com/ecommerce

Create a shared Space for your ecommerce team, with Claude or Codex connected to Shopify, Meta Ads, support tools, and the rest of your stack.

Space templates:

- Data and Insights
- Performance marketing
- Web development
- Supply Chain Operations
- Content management
- Customer support

### A Shared Space for B2B Operations

Source: https://type.com/b2b

Create a shared Space for your B2B team, with Claude or Codex connected to your CRM, product data, support tools, and the rest of your stack.

Space templates:

- Data and Insights: Daily business report (Every weekday 8am); Conversational BI (Live revenue, usage, and funnel answers — no SQL)
- Sales Operations: Daily pipeline report (Every weekday 8am); Deal risk alerts (When deals stall or slip past close dates)
- Customer success: Account health monitor (Live usage, adoption, and renewal risk by account); Renewal & QBR briefs (Before every renewal and QBR)
- Support: Reply drafts with account context (On new ticket); Voice-of-customer report (Weekly themes, escalations, and CSAT drivers)
- Marketing: Daily campaign report (Every weekday 9am); Budget reallocation advisor (When channel efficiency diverges)
- Sales engineering: Instant product answers (On question in any deal channel); Customer requests → feature tickets (When customers ask for something new)

### A Shared Space for Finance and Operations

Source: https://type.com/finance-and-ops

Create a shared Space for your finance and ops teams, with Claude or Codex connected to your ERP, billing, spend management, and banking.

Space templates:

- Month-end close: Bank and credit card reconciliation (Every weekday, on new cleared transactions); Close checklist and tie-out tracker (Live task status, accruals, and open items)
- Cash and forecasting: Daily cash position and burn snapshot (Every weekday 8am); Rolling 13-week cash forecast (Every Monday 7am)
- AR and collections: Overdue invoice chase list (Every weekday 9am); AR aging and DSO tracker (Live balances by customer and age bucket)
- AP and vendor spend: Bill review with duplicate and policy checks (On every new invoice); Vendor spend and renewal watch (Every Monday 8:30am)
- Revenue and billing: Stripe to GL revenue reconciliation (On every payout and month-end); Billing exception monitor (On failed charge or invoice mismatch)
- Board reporting and audit prep: Board metrics pack (Five business days before each meeting); Audit and diligence evidence collection (On every auditor request)
- Operating reviews and KPIs: Monday operating metrics pack (Every Monday 7am); Variance and exception watch (On any KPI or budget threshold breach)
- Headcount and hiring plan: Payroll and headcount vs plan (On every pay run); Open roles and start date tracker (Live by team, level, and start date)
- Inventory and purchasing: Reorder and stock cover alerts (On stock cover below target); Open PO and landed cost tracker (Live by supplier, PO, and arrival date)

### A Shared Space for Sales and Marketing

Source: https://type.com/sales-and-marketing

Create a shared Space for your sales and marketing teams, with Claude or Codex connected to your CRM, ad accounts, analytics, and lifecycle tools.

Space templates:

- Pipeline and forecast: Daily pipeline and forecast report (Every weekday 8am); Stalled and slipped deal alerts (When close dates move or deals go quiet)
- Inbound lead routing: Enrich and route new leads (On new form fill or demo request); Speed-to-lead and SLA tracker (Live first-touch time by rep and source)
- Outbound and follow-ups: Account research and sequence drafts (On new target account added); Reply and follow-up queue (Live by sequence, rep, and stage)
- Call notes and deal intel: Post-call summary and CRM update (After every recorded call); Objection and competitor themes (Weekly across calls and open deals)
- Paid acquisition and CAC: Daily spend, CAC, and ROAS report (Every weekday 9am); Budget reallocation advisor (When channel efficiency diverges)
- Lifecycle and nurture email: Campaign drafts and send briefs (Before every scheduled send); Lifecycle performance by segment (Live opens, clicks, and pipeline created)
- Content and SEO pipeline: Weekly content and keyword brief (Every Monday 7am); Ranking and traffic movement alerts (When key pages gain or lose position)
- Funnel and attribution: Weekly funnel and conversion report (Every Monday 8am); Source-to-revenue attribution (Live by channel, campaign, and landing page)
- Competitive and win-loss: Competitor launch and pricing watch (On competitor site or pricing change); Win-loss reasons by segment (Live from closed deals and call notes)

### A Shared Space for Customer Success

Source: https://type.com/customer-success

Create a shared Space for your customer success and support teams, with Claude or Codex connected to your CRM, support desk, and product analytics.

Space templates:

- Account health and churn risk: Account health monitor (Live adoption, support load, and renewal risk by account); Churn risk alerts (When usage drops or a champion goes quiet)
- Onboarding and activation: Kickoff plan and welcome sequence (On closed-won deal); Time-to-value by cohort (Live activation milestones and stalled accounts)
- Renewals and QBRs: Renewal and QBR briefs (Before every renewal and business review); Renewal pipeline and risk board (Live by close date, owner, and health)
- Ticket triage and replies: Reply drafts with account context (On new ticket); Queue, SLA, and backlog board (Live first response, resolution time, and aging tickets)
- Escalations and bug handoff: Escalation to engineering handoff (On P1 escalation or repeated bug report); Open escalations by account (Live status, owner, and time since last update)
- Voice of customer: Weekly voice-of-customer report (Every Monday 8am); Feature requests by revenue (Live themes across tickets, calls, and accounts)
- Expansion and upsell signals: Plan limit and seat growth alerts (When usage crosses plan thresholds); Expansion pipeline board (Live upsell signals by account and owner)
- CSAT and NPS follow-through: Low score follow-up drafts (On negative CSAT or NPS response); CSAT and NPS drivers (Live by segment, teammate, and issue type)
- Help center and docs upkeep: Article drafts from repeat questions (When a ticket theme crosses a threshold); Weekly docs gap report (Every Friday 9am)

### Type x Lerer Hippeau: A shared Space for ecommerce

Source: https://type.com/lerer/ecom

Create a shared Space for your ecommerce team, with Claude or Codex connected to Shopify, Meta Ads, your 3PL, support tools, and the rest of your stack.

Space templates:

- Data Analyst
- Performance Marketer
- Landing Page Optimizer
- Supply Chain Operations
- Content Manager
- Support Specialist

## Type for Slack

Source: https://type.com/slack

Connect Type spaces to Slack channels so your team can work with shared context, skills, connections, and automations without leaving Slack.

### Set up and use Type in Slack

Connect a Slack channel to a Type space, then @mention Type whenever you want a response.

1. **Install.** Select Add to Slack, sign in to Type, and choose the Slack workspace your team uses.
2. **Add Type to a channel.** In Slack, add Type to the channel where you want to use it. When prompted, choose the Type space you want that channel to connect to.
3. **Use Type in Slack.** @mention Type in a connected channel message or thread reply. Type replies in the Slack thread and syncs the conversation to the space.

### Your team stays in control

- Type can only access the Slack channels you choose.
- New channel connections default to @mentions, so Type does not respond to ordinary messages.
- Your space's skills, connections, and automations stay available to your team in Slack.

## ChatWalrus x Type

Source: https://type.com/chatwalrus

Get your team engaging with ChatWalrus content, personalized to your brand and delivered in Slack. Recaps, answers, and custom skills, powered by Type.

### One agent, three jobs

- **Weekly Session Digest.** Ranked for your brand. What matters, not everything.
- **Answers Anything.** Everyone on your team can ask questions, get answers, and leverage the content to take action for your business.
- **Custom Skills.** Based on your site and brand docs, we deliver custom skills your whole team can use.

### Connect in three steps

1. Create an account
2. Connect Slack
3. Upload your brand documentation

## Partner programs

### Type Partners: 1-on-1 onboarding & 3 months free for VC portfolio companies

Source: https://type.com/vc-partners

Available to portfolio companies of B4Capital, Matchstick Ventures, Lerer Hippeau, Haystack. Hands-on onboarding, then 3 months on us.

- **Personalized 1-on-1 onboarding.** Book a working session with our team. We'll set up your workspace, create your first Space, and connect the tools your team uses.
- **3 months free.** Full access to Type: shared Spaces with Claude or Codex, the desktop and iOS apps, and connections to your company tools.

### Type x BFG: 1-on-1 onboarding & $125 in credits

Source: https://type.com/partners/bfg

A special offer for BFG portfolio companies: personalized Type Space onboarding plus $125 in credits. Hands-on onboarding, then $125 in credits.

- **Personalized 1-on-1 onboarding.** Book a working session with our team. We'll set up your workspace, create your first Space, and connect the tools your team uses.
- **$125 in credits.** Use $125 in Type credits while your team works with Claude or Codex across shared Spaces and connected company tools.

## Careers

Source: https://type.com/careers

Join Type to build shared Spaces where teams collaborate with Claude or Codex across company tools and data.

- iOS Engineer (Contract) (20–30 hours/week to start): https://type.com/careers/ios-contractor

## Announcements

### Introducing Type: the shared workspace for your team's best AI work

Source: https://type.com/blog/launch

Type Team · September 9, 2026 · Company

#### Why are we launching Type?

We built Type because the value of AI should spread across a team instead of staying trapped in private chats.

Today, we're publicly launching Type, the shared workspace that compounds your team's best AI work. Teams need one centralized place to build apps, skills, and automations together. Our ambition is to build the last piece of software your team will ever need.

To pursue that ambition, we've raised $4 million in pre-seed funding from Lerer Hippeau, Haystack, Matchstick, and executives at Slack, GitHub, Coinbase, Ramp, and Replit.

Our founders previously built Halp, which defined conversational ticketing in the last era of software. Slack was an investor, OpenAI was a customer, and Atlassian acquired the company.

Now, everyone is launching swarms of AI agents and teammates. But the number of agents a company has is a vanity metric when most of them are stuck in individual chat silos, wasting tokens on wrong answers and unnecessary work. The teams winning with AI are the ones whose best work is visible and compounds across the whole team. That's what Type is for.

#### How is Type different?

Type combines shared context, model choice, connected tools, durable memory, and app building in one workspace the whole team can improve.

Type puts your integrations, skills, files, and chat threads in one place your whole team can see, either directly in Slack or through the desktop and mobile apps. As soon as one person figures out how to get great work from AI, it spreads to everyone instead of living in a silo.

Teams can use whichever model is best for the job without locking into one provider. Engineers can use Codex while marketers use Claude, and existing Claude and Codex subscriptions can connect to Type so teams are not paying twice.

Tools are connected and authorized once, with permissions and guardrails at the team and individual level. Type also includes built-in tools for work such as scraping and searching LinkedIn, Instagram, TikTok, and the web.

The more a team works in Type, the smarter its shared company brain becomes. Type learns the team's customers, context, and preferred ways of working so people do not have to re-explain the business every morning.

Teams can also build custom interactive apps and internal tools that everyone can edit and use. Type handles permissions, access, data, and hosting so people can create dashboards, inventory systems, landing pages, and other software without the usual infrastructure overhead.

> The more our team uses Type as a whole, the better quality the AI gets for the team. Your whole departments can be using it rather than just individual team members. — Ray Lee, Co-founder and CEO, Raycon

- One shared workspace instead of a hundred private chats.
- Any model for any job, without locking into one provider.
- Connected tools with team and individual guardrails.
- A company brain that improves as the team works.
- Custom apps and internal tools without infrastructure overhead.

#### What are teams already doing with Type?

Teams already use Type to run support, merchandising, growth, reporting, and financial workflows that improve with every successful job.

Customers are running thousands of successful agent jobs that handle support conversations, scale merchandising systems, and run go-to-market plays.

Direct-to-consumer brands are building landing pages for paid campaigns and shifting budget toward the best-performing variants. A fast-growing B2B team supports thousands of customers with personalized health reports delivered before every meeting. Executives run financial analysis on profit-and-loss statements and use it to make hiring and spending decisions.

Intelligems, the e-commerce optimization platform, turned 1,500 support tickets into a knowledge base that makes every answer better than the last.

Every day, we're surprised by what teams automate. Type makes every person on a team AI-fluent and turns each successful workflow into a starting point for the next one.

> It's probably halved, if not more, compared to the previous solution. The answers are much more detailed, thought through, and need less iteration to get to the right outcome. — Max Klug, Intelligems

#### How can your team try Type?

Start free at type.com and use the included skills and automation templates to get your first shared workflow running in minutes.

The old way of working keeps AI knowledge scattered across personal chats. Type gives the whole team a shared place to build the new way of working together.

#### Launch questions

**What is Type?**

Type is a shared AI workspace where teams organize company context, connect tools, build reusable skills and apps, collaborate with multiple AI models, and automate recurring work.

**How is Type different from a chatbot?**

A chatbot usually keeps work inside one private conversation. Type makes integrations, files, skills, threads, apps, and automations visible and reusable across the team, so useful AI work compounds instead of disappearing into individual chat histories.

**Can teams use different AI models in Type?**

Yes. Teams can choose the model that fits each job, including Claude and Codex, and can connect existing subscriptions to avoid paying twice for the same access.

**How does Type handle connected tools and permissions?**

Teams connect and authorize tools once, then set permissions and guardrails at the team and individual level so they control exactly what AI can access and change.

**What can teams build with Type?**

Teams use Type to create reusable skills, automations, analytics dashboards, inventory tools, landing-page prototypes, support workflows, financial analysis, and other interactive internal apps.

## Legal

- Savvy Learn Privacy Policy: https://type.com/privacy
- Terms of Use Agreement: https://type.com/terms