Cooperly vs Fellow

Cooperly is for founder-led companies whose decisions no longer fit in one meeting. Fellow records, summarises and organises meetings and 1:1s; Cooperly follows the commitments made in threads and tasks between meetings, and keeps the owner visible to the team.

30 days free. No card.

Old rule

If it matters, it was said in a meeting.

New rule

Track promises in the threads and tasks where they’re made.

A great meeting note covers the forty minutes people spent in the room. The handoff that broke last week was agreed in a Slack thread on Tuesday. Cooperly reads where those agreements happen and keeps the owner in view after the call.

  1. Read what the work already shows

    Decisions, commitments and blockers already sit in Slack channels, ClickUp chat and Asana tasks. Cooperly proposes them as team facts; the team lead confirms each one.

  2. Ask only what tools can’t tell

    Profiles, Pulse and Fundamentals add how people work, what feels stuck and which agreement needs another conversation.

  3. Your agents prepare. People decide.

    ChatGPT, Claude and your other approved tools read the picture through MCP. The team agrees the owner and the next step.

Fellow vs Cooperly: features and fit

Cooperly is built for founder-led companies before management becomes an HR programme. Compare that job with the one Fellow is designed to do.

Starting point

Cooperly
Commitments and handoffs across chat, tasks and notes.
Fellow
Starts with the calendar: each meeting gets an agenda, notes and a recap. Cooperly starts with who owns the work after the meeting.

Sources

Cooperly
Slack channels, ClickUp chat and Asana task text; meeting notes and retros you upload.
Fellow
Records Zoom, Meet and Teams meetings and links them to calendar events. Cooperly reads conversation outside meetings, where many decisions now happen.

1:1s

Cooperly
Coop Profiles and recent team facts prepare a specific conversation.
Fellow
Keeps 1:1 agendas, talking points and previous notes. Cooperly adds how both people work and which commitment is at stake.

Action items

Cooperly
An owned roadmap step the team revisits.
Fellow
Captures action items and pushes them to Slack or task tools. Cooperly keeps the agreement and checks it against the next Pulse.

Human check

Cooperly
A lead confirms each proposed fact before it counts.
Fellow
Notes are summarised automatically from the recording. Cooperly asks a lead to confirm what becomes a team fact.

People context

Cooperly
Profiles, Pulse and Fundamentals.
Fellow
Context comes from what was said in meetings. Cooperly adds working preferences and current team signals.

AI access

Cooperly
MCP for ChatGPT, Claude and other approved clients; read-only by default, Claude and Codex write after a confirmed preview.
Fellow
MCP on paid plans gives Claude, ChatGPT and others recaps, transcripts and action items. Cooperly’s MCP carries the team picture: owners, facts, profiles and agreements.

Best fit

Cooperly
Founder-led teams of 10–50.
Fellow
Describes itself as designed for mid-sized and enterprise teams, including regulated industries. Cooperly is built for the company that has just outgrown the founder’s view.

Price shape

Cooperly
£240/year up to 10 people, £948/year for 11–50.
Fellow
Per user: Team $7, Business $15 each month on annual billing. Cooperly’s price is fixed for the team size.

Why choose Cooperly as a Fellow alternative?

Start with the job you need the system to do.

The decision happened in a thread.

Cooperly

Cooperly reads Slack channels and task comments, where a lot of small decisions are made between calls. It proposes them as facts and the lead confirms them.

Fellow

Fellow records meetings and turns them into transcripts, summaries and action items. A decision made in chat on Tuesday is outside that record; Cooperly picks it up there. Source for The decision happened in a thread.

Choose Cooperly when ownership breaks between meetings. Choose Fellow when the main problem is losing what was said in meetings.

A better 1:1 starts before the agenda.

Cooperly

Cooperly gives the lead both people’s working profiles and the commitments between them, so the 1:1 is about the handoff that actually broke.

Fellow

Fellow’s 1:1 tools suggest talking points and summarise previous 1:1s. Cooperly adds the working context those notes do not hold. Source for A better 1:1 starts before the agenda.

Choose Cooperly when the 1:1 needs team context. Choose Fellow when you need a dependable agenda and notes for every meeting.

The deadline moved in a Slack thread on Wednesday.

The call ended with a clear action item. By Wednesday, a Slack thread had moved the deadline and nobody updated the owner. Cooperly catches the change in the thread, the lead confirms it, and the team re-agrees who owns it.

Position
DriveD
ReasoningR
ConnectionC
CapacityCa
1Punch

default gear, shows under stress first

1

Drive 1 · Punch

Takes responsibility, makes decisions, holds boundaries, and moves things forward. In a team, this gives leadership, speed, and crisis stability.

Priya Dawson
Priya Dawson

Priya Dawson

Product Manager

2

Reasoning 1 · Punch

Speaks in conclusions, models, arguments, and criteria. In a team, this gives clarity and intellectual direction.

Adrian ColeJulian Park
Adrian Cole

Adrian Cole

Team Lead

Julian Park

Julian Park

Engineer

2

Connection 1 · Punch

Sets the tone, reads the room, and influences atmosphere. This brings energy, emotional presence, and engagement.

Serena HoltFelix Mercer
Serena Holt

Serena Holt

Designer

Felix Mercer

Felix Mercer

Front-End Developer

0

Capacity 1 · Punch

Strongly notices resources, body, money, conditions, comfort, and capacity. This brings realism and sustainable limits.

No members
2Foundation

strong, steady, process-oriented

1

Drive 2 · Foundation

Helps the team agree on responsibility: who leads, who decides, who owns what. This prevents chaos and power struggles.

Adrian Cole
Adrian Cole

Adrian Cole

Team Lead

2

Reasoning 2 · Foundation

Thinks well with others, asks questions, builds shared criteria, and creates common understanding.

Priya DawsonFelix Mercer
Priya Dawson

Priya Dawson

Product Manager

Felix Mercer

Felix Mercer

Front-End Developer

0

Connection 2 · Foundation

Naturally hears people, bridges positions, and keeps conversations human. Valuable for feedback, conflict, and difficult conversations.

No members
2

Capacity 2 · Foundation

Naturally makes the environment workable: rhythm, comfort, tools, operations, and practical stability.

Serena HoltJulian Park
Serena Holt

Serena Holt

Designer

Julian Park

Julian Park

Engineer

3Sensitive

cares, doubts, needs kind feedback

2

Drive 3 · Sensitive

Sensitive to pressure, public challenge, humiliation, or status games. Use one-to-one conversations, pauses, and small confidence-building steps.

Serena HoltFelix Mercer
Serena Holt

Serena Holt

Designer

Felix Mercer

Felix Mercer

Front-End Developer

0

Reasoning 3 · Sensitive

Sensitive around competence, reasoning, and whether the argument is clear enough. Give examples, preparation time, and safe wording.

No members
1

Connection 3 · Sensitive

Sensitive to tone, reactions, public comments, and emotional judgement. Feedback about tone should be private and gentle.

Julian Park
Julian Park

Julian Park

Engineer

2

Capacity 3 · Sensitive

Sensitive to fatigue, workload, money, and practical chaos. Use predictable rhythm, soft pacing, and clear resource templates.

Adrian ColePriya Dawson
Adrian Cole

Adrian Cole

Team Lead

Priya Dawson

Priya Dawson

Product Manager

4Background

follows, keeps it simple

1

Drive 4 · Background

Does not naturally want to carry leadership or push decisions. Give clear tasks, deadlines, and success criteria.

Julian Park
Julian Park

Julian Park

Engineer

1

Reasoning 4 · Background

Prefers a ready-made model, checklist, or decision structure instead of building complex reasoning from scratch.

Serena Holt
Serena Holt

Serena Holt

Designer

2

Connection 4 · Background

Does not naturally hold the emotional fabric of a conversation. Give simple scripts for opening, closing, and asking for feedback.

Adrian ColePriya Dawson
Adrian Cole

Adrian Cole

Team Lead

Priya Dawson

Priya Dawson

Product Manager

1

Capacity 4 · Background

Does not naturally want to think much about logistics, schedule, or physical resources. Use checklists, budgets, and weekly plans.

Felix Mercer
Felix Mercer

Felix Mercer

Front-End Developer

Demo Team is a compact, high-capability core team for a messaging product inside a very large company. The team’s shape is strongest in Reasoning, with Drive and Connection both present, and a lighter but still useful amount of Capacity. In simple terms, this is a team that can think clearly, make decisions, and build sensible product steps. It is well suited to solving hard product problems, setting criteria, and moving work forward without too much noise. That is a strong base for both goals: raising AI-assisted coding to 70% and growing the product to strong monthly revenue growth.
The team is, however, small and functionally concentrated. Reasoning-heavy teams often produce good answers, but they can become too internal, too cautious, or too debate-driven if the operating model is not clear. This matters because messaging products need speed, customer empathy, fast experimentation, and reliable execution at scale. Adrian Cole, Priya Dawson, and Julian Park give the team strong structure and decision quality. Serena Holt and Felix Mercer add user sensitivity and collaboration, which protects the team from becoming too dry or purely technical.
Overall, this is a thoughtful, serious, and promising team, but not yet a fully balanced business unit. It can achieve the goals if you lead it with clear decision rules, tighter commercial focus, and stronger delivery rhythm. Without that, the team may build well, but monetise too slowly.

  1. Read the profiles

    Read both people’s working profiles.

  2. Check what changed

    Check the commitments that changed since the meeting.

  3. Re-agree the owner

    Agree the owner again and keep it on the roadmap.

Give the same trusted context to the AI tools your team already uses.

Cooperly makes selected profiles, signals, goals and agreements available through MCP. Use that context in ChatGPT, Claude or another approved client while Cooperly keeps the permissions. Claude changes Cooperly only after you confirm a preview. AI helps with preparation; people keep the judgement.

Context Cooperly gathers

Team Pulse
Coop Profile
Fundamentals
Team memory

Cooperly

People Context Layer

Team-scopedPermissionedYou approve changes

The AI tools you already use

Claude

Claude chat and code access

ChatGPT

Contextual chat and commands

AI Agents via MCP

Linear, Notion, and compatible clients

When to choose Cooperly

Cooperly follows decisions and commitments made between meetings. Fellow records, summarises and organises the meetings and 1:1s themselves.

Choose

Cooperly

  • Decisions happen in chat and tasks as often as in meetings.
  • 1:1s need context on how both people work, alongside last week’s notes.
  • You want a flat price for the whole team.

Choose

Fellow

  • Most decisions happen in meetings and you need them recorded.
  • You need agendas, transcripts and action items for every call.
  • You work in a regulated industry and need meeting records.

Fellow vs Cooperly pricing

Your plan stays flat as your team grows.

One flat price for this team size. Full Cooperly access included: up to 10 people at the Teams rate, then up to 50 people across five teams at the Company rate.

30people
1011–50 people: £948/year50

Cooperly

For Companies

£948/ year · For Companies

£2.63per person / month equivalent

Fellow

Business

≈£3,991/ year

Calculated for 30 people

Keep people context and the review rhythm connected across several teams as the company grows. Up to 5 teams, up to 50 people. MCP and approved integrations are included.

This uses Fellow Business at $15 per user each month on annual billing, because Team caps AI notes per user. Team is $7. Fellow says MCP connections are available on paid plans. Cooperly includes MCP and integrations in both team-size plans.

Official Fellow pricing

Fellow is priced per user for meeting coverage. Cooperly is one company price for the team picture, whoever attends the meetings.

Prices checked .

USD estimates use the 4 September 2026 reference rate (£0.7391 per $1), rounded only for display. Taxes and optional add-ons excluded. Rate source

Questions about Cooperly and Fellow

Cooperly replaces a different part of the job: following commitments and ownership between meetings. If you need recordings and transcripts, keep a notetaker and add Cooperly for the team picture.

Cooperly accepts meeting notes, 1:1 notes and retros you upload, and proposes facts from them for the lead to confirm. It does not record meetings itself.

Cooperly connects to Claude, ChatGPT and other approved clients through MCP, and Fellow publishes its own MCP. Your AI client can use meeting recaps from one and owners, facts and profiles from the other. Cooperly access is read-only by default.

Use Cooperly with Claude

Cooperly gives each person a working profile to explain how they communicate and decide, and a Pulse to say what feels stuck. The lead reads it before the 1:1 starts.

Cooperly pricing: Up to 10 people: £240/year (£20/month billed yearly). 11–50 people: £948/year (£79/month billed yearly). MCP and approved integrations are included in both team-size plans. Fellow Business is $15 per user each month on annual billing, so 30 users cost $5,400 a year.

Compare prices at your headcount

Cooperly is run by the founder and team leads. A lead confirms facts and prepares conversations; nobody administers a programme.

Keep the owner in view after the call, wherever the plan changes next.

Try Cooperly with a real team.
30 days free. No card.