Pricing

Credits are a unit of Coco's effort. Every action shows its cost up front, so you always know what the work is worth before you approve it.

Coco prices the work, not the seat. Every action shows its credit cost up front. About 8 credits to enrich a dozen contacts. About 32 credits to send 5 outbound emails. About 25 credits to research and shortlist a target list. The free Hobby tier comes with 1,000 credits a month, no card required. The Founder tier is $40 a month for 5,000 credits plus à la carte top-ups when you need more. Team pricing is custom: pooled credits across the team, shared memory, admin audit trail. Whatever tier you start on, you see the credit cost of every workflow before you approve it.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Three tiers — Hobby, Founder, Team

Hobby — $0 a month, forever. 1,000 credits a month, no card, no commitment. Three tool connections (pick from the integrations list — HubSpot, Gmail, Apollo, whatever your stack uses most). Community support. All core capabilities are available: research, drafting, follow-up automation, CRM hygiene, meeting prep, list segmentation, lead routing. Hobby is the tier most teams evaluate on. It's also a fine permanent home if your volume is light and you only need Coco for a couple of recurring workflows.

Founder — $40 a month, "most teams." 5,000 credits a month plus à la carte top-ups when you need more. Unlimited tool connections. Scheduled runs and watchers — Coco can kick off a workflow on a cadence (weekly target-list refresh, daily CRM hygiene sweep) or in response to a state change in a connected tool (new HubSpot contact, deal stage move, calendar booking). Custom voice training on outreach: Coco learns your tone, your phrasing patterns, your typical structure, and the words you'd never use, so drafts come back closer to what you'd write yourself. This is the tier most active GTM teams settle on once they've outgrown the free allotment.

Team — custom, for GTM teams of three or more. Pooled credits across the team rather than per-user allotments — usage flexes with where the work is heaviest each month. Shared memory: shared ICP definitions, shared playbooks, shared voice templates. Admin audit trail for the GTM lead or RevOps owner to see what's running, who approved what, and where credits are going. SOC 2 (in progress) and DPA available on request. Dedicated onboarding for the first workflows you want to ship across the team. Team starts at three users and scales from there; ask for a quote at the size and motion you're at today.

CTAs: Hobby starts at the signup page with no card. Founder is a one-click upgrade once you've hit your free limit (or any time before). Team is a conversation — email hello@joinco.co.

What 1,000 free credits actually gets you

The hardest question for any credit-priced product is "how much work does a credit actually do?" Here's the answer in concrete output. With 1,000 credits a month, Coco can deliver roughly:

• ~80 account research briefs — single-account deep research with funding history, hiring signals, public commentary, and an ICP-fit assessment, about 12 credits each.
• ~150 outreach drafts or follow-ups — first-touch cold emails, LinkedIn notes, follow-up replies in your voice, about 4–6 credits each.
• ~300 CRM records cleaned or enriched — duplicate merges, missing-field fills, lifecycle-stage updates, about 1–3 credits per record.
• ~25 target-list or design-partner searches — full ICP-anchored shortlist runs (build the candidate set, score fit, rank, and surface the top 5–10), about 25–40 credits each.
• ~20 meeting prep packs — pre-meeting brief with attendee context, account history, suggested talking points, and post-meeting follow-up draft, about 8 credits each.
• ~15 workflow checks or routing fixes — pipeline health sweeps, follow-up gap audits, lead-routing rule fixes, about 25–60 credits each depending on scope.

Those numbers don't add to exactly 1,000 because real teams mix workflows. The point is that 1,000 credits is enough free work per month to evaluate Coco properly on real GTM jobs before you spend a cent. You can run the design-partner search, draft some outbound, clean a few hundred CRM records, and sweep your follow-up gaps inside the free allotment.

When 1,000 credits stops being enough — usually within the first month or two of active use — the upgrade to Founder costs less than the hourly rate of the work it replaces.

Why credits, not seats

Seat pricing was designed for passive software. You pay $X per user per month, more users pay more, the cost of the tool scales with headcount. The model holds together because the tool is a productivity layer — each user gets the same value from access, and access is the unit of value.

Coco isn't a productivity layer. It's doing work. The value isn't access; it's output. Charging per seat for an AI co-worker would price the work backward — a five-person team paying for five seats whether they ran one workflow a month or a thousand. Some teams would massively overpay; others would underpay until the tool became unprofitable to maintain. Either way, the price wouldn't track the work.

Credits track the work. One credit, one unit of Coco's effort. A draft costs what a draft costs whether the team that bought it is solo or fifty people. Heavy weeks cost more than light weeks. Cheap workflows stay cheap; expensive workflows show their cost up front. The plan card you see before approving any run displays the credit estimate so you can decide whether the work is worth running before it runs. That's the difference between credit-based pricing and a seat tax with a credit cap bolted on: with Coco, credits aren't a usage limit on top of a seat. They're the pricing itself.

Two more compounds: pooled credits across the Team tier mean a five-person team isn't paying five times as much as a one-person team for the same workload. And credits scale with output — if your motion changes (more outreach, less CRM cleanup), pricing follows. See the credits-vs-seats deep dive for the longer argument.

How credit costs are estimated

Credit costs map to discrete units of work Coco does. The rough scale:

• Reasoning, plan-building, and drafting are usually a few credits each. A drafted outreach email is about 4–6 credits. A drafted follow-up reply is about 3–5 credits. A drafted LinkedIn message is about 2–4 credits.
• Research per account is about 5–12 credits depending on depth. A quick fit-check is the low end; a deep brief with funding, hiring, and public commentary is the high end.
• Enrichment runs about 1–2 credits per record on average. Sometimes less for a basic lookup, sometimes more if Coco has to chase a contact across multiple sources.
• Meeting prep is about 8 credits per brief. Pre-meeting context plus a draft follow-up template.
• CRM hygiene is roughly 1–3 credits per record depending on how much enrichment or reasoning the record needs. A duplicate-merge proposal is about 1 credit; a deep cleanup pass is at the higher end.
• Multi-step workflows (research + draft + queue) sum the per-step costs and show the total. The design-partner pipeline mentioned on the how-it-works page — research 10 companies, find contacts, draft 5 personalized first-touches — totals about 132 credits.

Estimates land within about 20% of actual cost on most workflows. If a run looks like it will materially exceed its estimate, Coco pauses and asks before continuing rather than burning credits silently. Unused credits roll over for 30 days: long enough that a slow week doesn't punish you, short enough that the pricing stays honest.

Buying extra credits

Founder tier supports à la carte top-ups when you blow past your 5,000-credit monthly allotment. Top-ups stack on top of the base allotment and follow the same 30-day rollover window. There's no markup on volume. The per-credit price stays flat across top-up packs.

Team tier negotiates volume pricing for the pooled allotment. If your team consistently runs heavy workflows (high-volume enrichment, recurring multi-step campaigns), the Team conversation includes pricing for the actual volume rather than a per-user calculation. Email hello@joinco.co and we'll work the math against your usage pattern.

Phase 2 — a free CRM and marketing automation suite, native to Coco

Coco doesn't require a CRM to be useful. Connect what you have — Gmail and a spreadsheet is enough to get started, and most teams come in with HubSpot or Salesforce already configured. But if you don't already have a stack you love, we're not going to push you to go buy one before you can use the product.

Phase 2 includes a free CRM and marketing automation suite native to Coco, built around the same approval-first model. Contact and company records. Pipeline tracking and lifecycle stages. Email sequencing and campaign execution. Quoting and invoicing. Forms, lists, and segmentation. Marketing automation tooling. Routing, workflow logic, and follow-up automation. The native suite gives Coco shared context to operate with more precision when you're not bringing your own CRM.

The model: start by connecting the tools you already use. Grow into the native system when you're ready. Phase 2 is on the roadmap; the timing is set by customer pull, not by an artificial release date.

What you don't pay for

A few costs that surprise people when they evaluate Coco against other AI tools:

• No per-integration fee. All the integrations Coco supports today — HubSpot, Salesforce, Gmail, Calendar, Apollo, LinkedIn, Clay, Outreach, Slack, Notion, Calendly, ZoomInfo, plus the orchestration set — are part of every tier, including Hobby. There's no $X-per-month-per-tool tax on top of credit pricing. See the integrations hub for the full list.
• No seat charge for view-only collaborators on the Team tier. A GTM lead who wants to read the audit trail and review approvals doesn't pay a seat fee. Active operators (people approving runs, handing Coco goals, editing drafts) count toward the team allotment.
• No fee for re-running a workflow you've already approved. If you approve a recurring CRM-hygiene sweep on Monday and it runs again Tuesday, you pay only for the credits the actual work consumes — not a per-run platform fee.
• No markup on third-party API costs. When a workflow spends against a connected API (Apollo enrichment, ZoomInfo lookup, etc.), that cost comes out of your credit balance at unit cost — no platform margin on top.

The principle: pay for the work Coco does. Pay once. See the cost before you approve.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Frequently asked questions

Do unused credits roll over?

Yes — 30 days. The goal is fair evaluation, not punishment for a slow week. If you're on Founder, unused credits from the current month stay available for the next 30 days; usage debits the oldest credits first. Hobby tier credits also roll within the same window but reset if you upgrade tiers.

Can I cap monthly spend?

Yes — Founder and Team tiers support soft caps (alert at threshold) and hard caps (block new workflows once the cap is hit). The cap is configurable per-account on Founder and per-team on Team. Hobby is naturally capped at the 1,000-credit monthly allotment.

Why is the Founder tier called "Most teams"?

Because most active teams use 3,000–8,000 credits a month — Founder is the closest fit for that range. Teams running lighter usage often stay on Hobby permanently; teams running heavier usage usually move to Team for the pooled-credit and audit-trail benefits. The naming is descriptive, not aspirational.

Is there a free trial of Founder?

Hobby is the free trial. The 1,000 credits a month give you enough room to evaluate Coco properly across multiple workflows before you spend anything. Upgrade to Founder when you outgrow it — usually within the first month or two of active use.

Do credits expire if I cancel?

Credits don't carry over after a cancellation. They're tied to active tier billing, so if you pause or downgrade, you lose the unused balance from the previous tier. Re-subscribing starts a fresh allotment under the new tier's terms.

Can I share credits across my team?

Pooled credits are a Team tier feature. Hobby and Founder are per-user — each user has their own allotment. Team tier shares one pool across all active operators, which means a five-person team running mixed workloads usually comes out cheaper than five Founder seats.

What if a workflow's actual cost exceeds the estimate?

Workflows have a cost ceiling. If a run looks like it will materially exceed its plan-card estimate, Coco pauses and asks before continuing — rather than burning credits silently. You can approve the overage, edit the plan to fit the original estimate, or stop the run entirely. The plan card is the contract; surprises are caught at the gate. See the security page for how cost ceilings tie into the broader audit trail.

Get started

Connect one tool. Hand Coco one concrete piece of work this week. Watch the plan card, approve the first run, and see what the credit cost actually feels like against the value of the output.

Try Coco for free → · 1,000 credits free · no card · ~2-min setup

Or book a walkthrough → if you'd rather talk through pricing against your specific volume first.