Recap from Call #1 — Thu 4 Jun
For anyone who couldn’t make it, here’s what we covered and where things are heading.
Four of us showed up live — and that turned out to be exactly the right number to actually talk to each other. (Law of two feet: the people who came were the people who needed to be there.)
Where the collective stands
The first milestone is simple: get 10 people through the four courses, which unlocks the path to the Claude Certified Architect certification.
| ~33 |
27 |
21 |
1 |
| said they want to take part |
have accounts |
have started the course |
finished all four (+3 close behind) |
Live updates (~15 min) on the progress tracker.
On top of that: we now have Anthropic partner portal access. The track is real and moving.
What drew people to Claude
We went round the group on what brought each of us here and what we want Claude to help with. A few threads stood out:
- Claude Code is badly named. Several of us use it for almost everything except writing code by hand — designing systems, blueprints, reports, PDFs, presentations, analysing spreadsheets. The “Code” label undersells how versatile it is.
- It’s a sparring partner, not just a tool. Feed it rich context (e.g. recorded client conversations), then design from blueprint to production with it alongside you.
- It’s the strongest model for serious work. Folks who’ve used Gemini and others kept landing back on Claude for the heavy lifting.
- It needs a skilled hand. The power-tool analogy came up: incredibly capable, but it lacks common sense. Point it badly and it creates a mess. Skill still matters.
There’s also room for people who don’t live in the terminal — Cowork is a more natural entry point for project management and knowledge work, and I’d love to see a Cowork-focused corner of the community grow.
learn together, build together.
What the collective should be
The phrase that landed best: learn together, build together — borrowed from a 10,000-person collective one of our members founded in Morocco on exactly that motto.
The value people are looking for:
- The people and their insights — different perspectives (governance, sovereignty, project management, architecture) colliding usefully.
- A network that could later turn into project teams and real business opportunities.
- A catalyst effect — someone shares a feature, a repo, a problem, and it propels everyone forward faster than going solo.
Ideas we want to try
- Opt-in member profiles / a directory — who you are, where you are, what you’re building, so people can find each other.
- Weekly cadence — who joins, joins; transcript summaries sent out so nobody falls out of the loop.
- Member spotlight — a rotating 2–3 minute slot to present something you built or are passionate about.
- “New this week in Claude Code” — a standing segment, since features drop constantly.
- Crowdsourced agenda — suggest and vote on topics so the calls stay relevant.
Join in
- Our LinkedIn page is up — come say hi and connect.
- The forum is the place to introduce yourself and keep the conversation going between calls.
- Propose topics for the next call or suggest things we could help facilitate at fider.claude-collective.com.
If you’ve started the courses, keep going — we’re genuinely close to that 10-person milestone. And if you haven’t introduced yourself yet, drop a quick post: who you are, where you’re from, and what you’re working on.
See you on the next call.
