Who's looking at your decks, by company. Full intel →
Engagement (by company)
Loading PostHog data…
Last 30 days
Named viewers appear once the auth wall is on. Today the site is fully public so PostHog can only show anonymous counts. The moment you turn auth on for a prospect's page (see Privacy & access), this section starts showing who viewed.
PreviewThis is what the section above looks like once you turn auth on. Fake data, for illustration. When a real prospect signs in to view their deck, their name + email + every page they opened appears here in real time.
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
Lorem date
Done
Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Lorem date
In Progress
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.
Today
Due Today
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum.
Ongoing
In Progress
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia.
Lorem date
Scheduled
04Weekly Revenue Reports
Cliff's weekly view of pipeline → revenue
Coming soon
Weekly revenue reports will pull the current week's invoices, deal closures, and pipeline shifts into a single view here. Until then, the source of truth lives in Xero.
05Sales Methodology
How Huddle sells — playbooks and patterns
Coming soon
The Huddle sales motion — how we open conversations, qualify, build trust, present the diagnostic, and close. Will live here as a written playbook with the patterns Cliff uses across Barrenjoey, ASB, Westpac and Macquarie deals.
/Marketing
📣
Marketing
Content calendar, brand kit, and lead generation tools are coming. This bucket will be built out as Huddle's marketing motion gets established.
📅
Content Calendar
LinkedIn posts, thought-leadership articles and campaign schedule.
🎨
Brand Kit
Logo, colours, fonts, templates and visual identity guidelines.
🎯
Lead Generation
Inbound pipeline, referral tracking and outreach campaign results.
Consectetur adipiscing · check-ins added as published
Scheduled
Lorem Ipsum Working Agreement
Next monthly leadership deck
/How to use Claude
01How to use Claude
Recipes for the everyday jobs. Plus what to do when things go wrong.
⚡ The 30-second rule
If you only remember three things, remember these:
1. Open huddletalent when you start Claude Code (the parent folder, not a subfolder).
2. Ask Claude first. Before Googling, before messaging anyone, before opening any other app. Claude knows your business.
3. Run /checkpoint before you close. It saves everything you did, writes a handover for next time, and commits across all three repos so nothing is lost.
Everything else lives in the other tabs above. The most common ones are Recipes (how to do specific jobs) and Skills (the slash commands Claude knows).
📝 Change something on a deck
On the Barrenjoey deck, change the headline on slide 2 to '...'. Then tell me the URL so I can check.
Claude reads the file, makes the change, commits and pushes, and gives you the live URL. Changes are usually live within about 60 seconds.
The more specific you are about WHICH deck and WHICH section, the cleaner the result. "Change the deck" is too vague.
🆕 Make a new client deck
I need a new deck for [Client Name]. Start from the Barrenjoey deck and adapt it for [context, e.g. a CFO at a recruitment firm in Sydney].
Claude copies the Barrenjoey deck as a template, swaps the client-specific content, and gives you the URL. You then describe the parts you want changed and Claude iterates.
Point Claude at any source material you have, a LinkedIn URL for the buyer, a website, a recording. The more context, the more tailored the first draft.
❓ Ask a question about your business
What did we agree with Westpac in the last meeting?
Claude has your transcripts, customer files, and notes loaded. It can answer business questions without you having to dig through emails or recordings.
If an answer feels made up, push back, "are you sure? show me the source."
💾 Save your work before you close
/checkpoint
Claude runs a structured end-of-session protocol: commits any unsaved changes across all three repos, updates its memory, writes a handover note so the next session knows where you left off, and prints a verified state report so you can see what shipped. Without this, work done in a session can disappear.
Make this the last thing you do every session. Saying "save everything" or "wrap up" works too, both trigger the same protocol.
🎙️ Bring in a voice memo or whiteboard photo
I just recorded a 5-minute voice memo about [topic]. Read it, summarise the three main points, and update [the relevant file].
Drag the file straight into Claude Code. It handles audio, images, PDFs, Word docs, PowerPoints.
For long voice memos, ask Claude to transcribe first, then summarise. Two steps, much cleaner.
⏸️ Pause Claude or change direction
Press Esc to stop. Then describe what you actually want.
Claude says yes to every idea. If it's running off in the wrong direction, interrupt it, don't watch it dig deeper.
If something comes up mid-session that you'll handle later, say "park that for later" and Claude will note it without acting.
Claude has been given 12 specialised skills for Huddle Talent. Some run automatically when the situation calls for them; others you trigger by typing a slash command or asking in plain English. Skills with a teal border are auto-invoked, the rest you call manually.
🎯 Sales & prospecting
/score Lead Scoring Auto + manual
Scores any new prospect 0-100 against five pre-meeting signals (ICP fit, source quality, engagement, champion, urgency). Returns Hot / Warm / Cool / Likely-DQ.
Before your first call with a new prospect, to allocate prep time. Auto-runs on any new LinkedIn reply, booking, or intro email.
/prospect-research Prospect Research Auto + manual
Generates a full pre-meeting briefing: buyer LinkedIn, company news, tech stack, comparable deals, recommended angle. Multi-source.
Auto-runs when a new prospect meeting is booked. Manual: "research this prospect" or "prep for the meeting with [company]".
/qualify Deal Qualification Auto + manual
Scores a prospect on the 7 qualification criteria (Budget, Decision Maker, Pain, Timeline, Team Readiness, Use Case Fit, Alternatives). Green / yellow / red recommendation.
After every first meeting (auto). Manual: "is this deal qualified?", "should we keep working this?".
/deck-generator Deck Generator Manual
Authoritative for client-facing decks. Knows your brand, design files, deck-and-proposal standards, and the CRO + Creative Director critical review.
Any deck or proposal work. Don't describe deck changes in plain text when this skill exists.
✏️ Content & communications
/content-writer Content Writer Manual
Writes blog posts, LinkedIn posts, email content, case studies, and sales-enablement material in your voice. Uses 6 Team Conditions framework and anonymised customer evidence.
Any external-facing writing where Cliff's voice and Huddle's frameworks matter.
/branded-doc Branded Document Manual
Creates professional Huddle-branded .docx documents with a visual preview workflow. Two-phase: HTML preview to iterate, then one-step export.
/inbox-automation Inbox Automation Daily, plus manual
Gmail end-to-end: classifies every email into 5 tiers, auto-drafts replies for relevant senders, archives noise, chases you on unsent drafts.
Runs daily in the background. Manual: "triage my inbox", "draft a reply to [name]".
🤝 Meetings
/meeting-intelligence Meeting Intelligence Auto + manual
Two modes: prep (pre-meeting, pulls open items + sources, generates briefing) and debrief (post-meeting, classifies transcript, extracts decisions and actions, routes to the right files).
Auto-runs before scheduled meetings and after Fathom transcripts arrive. Manual: "prep for tomorrow's meetings".
/meeting-debrief Meeting Debrief Auto + manual
Post-meeting only: extracts key quotes, action items, and sentiment from the transcript, then updates the prospect or customer intelligence file.
After any prospect or customer meeting. Manual: "/meeting-debrief" or "debrief that call".
🔧 Privacy & system
/auth-toggle Auth Toggle Manual
Self-service control over who can see which deck page. Lock to a customer's email domain, open to anyone with the link, or toggle the whole site public. Always tests on dev first by default.
Anytime you want to lock or unlock a page. "Make Westpac private, only westpac.com.au". See Privacy & access below.
/checkpoint Checkpoint Manual (or natural phrase)
End-of-session safety protocol. Saves memories, writes a handover, commits across all three repos, prints a verified-state report. Forbidden-phrases gate prevents premature "done" declarations.
Before you close Claude Code. Also triggers on "save everything", "wrap up", "safety check", "before I close".
/brand-kit Brand Kit Auto (helper)
Internal helper. Auto-invoked by other skills (deck-generator, branded-doc, content-writer) to keep visuals consistent. Single source of truth: huddletalent-ops/.claude/rules/brand-standards.md.
Whenever Huddle colours, fonts, or the logo are involved. You rarely call it directly, other skills pull it in.
The list is short on purpose. Each of these will create real pain if ignored.
Don't edit files in Notepad or Explorer. Tell Claude what needs changing. Hand-editing breaks the git history and skips Claude's safety checks.
Don't use Chat or ChatGPT for real work. They don't know your business. Claude Code does. The two will give different answers; only Claude Code's answer is grounded in your files.
Don't open a subfolder when you start. Always open the parent huddletalent. The parent has the brain that tells Claude who you are and how to work with you. Subfolders only see a slice of the business.
Don't worry about breaking things. Everything is in git. You cannot break anything permanently. If a change looks wrong, just tell Claude "undo that last change".
What you're seeing
What to do
Claude won't respond to a message
Press Esc, wait a second, describe again.
Claude is doing the wrong thing
Press Esc to stop it. Then say what you actually want.
Claude says "I don't remember our last session"
Tell it "read CLAUDE.md and the most recent handover file". Memory loads from those.
The deck or page looks broken after a change
Say "undo your last change" or "revert that". Everything is in git, nothing is lost.
Claude can't push your changes
Say "pull the latest from main, then try the push again". There's just newer work upstream.
Claude Desktop won't close
On Windows, the X button leaves it running. Open Task Manager (Ctrl+Shift+Esc), find Claude, click End Task.
The whole thing feels confused
Run /checkpoint, close Claude Code completely, reopen on the huddletalent parent folder. Fresh session, full context loaded.
You opened the wrong folder
Close Claude Code. Reopen on huddletalent (the parent, not deck/website/ops).
Wrong people can see a deck
See Privacy & access below.
When you're comfortable with the basics, these unlock more power.
The instruction trick. Type instruction at the start of a big task. It expands to "confirm and hold for instruction before you proceed", Claude pauses and waits for your full brief instead of charging ahead.
/checkpoint (or save everything). End-of-session ritual. Saves memories, writes a handover, commits across all your repos, prints a verified-state report. The skill lives in huddletalent/ops/.claude/skills/checkpoint/, so anyone on the team gets the same protocol.
/deck-generator. Use this for any deck work. It knows your brand, design files, and templates. Don't describe deck changes in plain text when this skill exists.
Ctrl+N for parallel sessions. Run two things at once, one session researching, the other building.
Record your voice, paste the transcript. Two minutes of talking gets you a better result than ten minutes of typing.
Tell Claude to remember things."Add this to your memory" or "write this into CLAUDE.md". That memory persists every future session.
Push back when it's wrong."That's wrong, rethink it", Claude will. Don't accept a bad answer.
Send URLs, not files. Your deck is a link. Email it. No PDFs, no downloads.
02Privacy & access
Who can see what, and how you turn the sign-in wall on or off, yourself.
🔒 Right now, your deck site is fully public
Anyone with a URL can see any page at deck.huddletalent.tech. That was a deliberate choice, easier to share with prospects.
When you're ready to lock things down, you don't need an engineer. Tell Claude in plain English. Changes go live in about 60 seconds.
The two states (today)
🌐 Public
Anyone with the URL can see it. No sign-in. Good for prospect decks you want shared widely or pages like this Command Centre.
🔐 Restricted (L3)
Visitor must sign in with Google or an email link. Only allowed emails or email domains get through. Everyone else sees a polite "Not authorised" page.
Pages can mix freely. You could have the homepage public and the Westpac deck restricted to *@westpac.com.au.
The two environments
URL
What it is
Current default
dev.huddletalent.tech
Your sandbox. Test changes here first. Nothing here goes to customers.
Sign-in required (standard customer-domain rules)
deck.huddletalent.tech
Your live site. What you send to customers and prospects.
Fully public
Rule of thumb: change dev first, test it, then promote to prod. Claude does this by default. If you say "lock the Westpac page", Claude does it on dev and waits for you to say "now do prod".
The access diagram
When the 5-tier plan is live, each tier can see everything the tiers below it can see. The bars show how much of the business each tier has visibility over.
5-tier access model (future state)
Cliff-only
You + Michael — founder finance, sensitive customer notes, personal context
+ senior team — leadership memos, hiring decisions
Team
+ all Huddle — team updates, internal SOPs
Customer-safe
Anyone you share with — public decks, marketing, prospect pages
What to say to Claude
Turning the wall on or off completely
Turn auth off for everything.
Turn auth on for everything, use the standard customer-domain rules.
Locking or opening a single page
Make the Westpac page private, only westpac.com.au or westpac.co.nz can see it.
Open up the Barrenjoey page for anyone with the link.
Checking what's set
Show me what's locked right now on prod.
Show me the rules for the Westpac page.
Moving changes between dev and prod
Now do the same on prod.
Do this on prod directly, skip dev.
The 60-second wait
After any change, the result is cached at the edge for up to 60 seconds. If you test immediately and see the old behaviour, that's why, wait a minute and refresh.
The admin dashboard (alternative to Claude)
You also have a web UI at deck.huddletalent.tech/admin/. Sign in with Google. You can add a new rule for a path, add or remove allowed emails / domains, delete a rule, or see the last 20 changes in the audit log.
Most of the time, talking to Claude is faster. The dashboard is there when you want to see everything at a glance, or when you're showing a teammate how access works.
When the team grows: the 5-tier plan
Future-state plan, not yet live. When you want internal privacy tiers, the same plain-English commands will work. The skill already knows about all five tiers.
Tier
Who
Example content
Cliff-only
You and Michael
Founder finance, sensitive customer notes, personal context
Board
You + any advisors / directors
Board decks, strategy docs
Leadership
You + senior team
Leadership memos, hiring decisions
Team
You + everyone on the Huddle team
Team updates, internal SOPs
Customer-safe
Anyone you choose to share with
Public decks, marketing, prospect-facing pages
When you're ready, tell Claude: "set up the five privacy tiers from the future-state plan, add me to all of them, and start with the Cliff-only tier locked to just my email."
What to watch out for
Don't delete the catch-all / rule. It's the safety net if a narrower rule is removed. Without it, the whole site falls back to whatever the next-most-specific rule says, which is usually wrong.
Don't delete /login, /admin, /favicon, /robots.txt. These need to stay public or sign-in itself breaks.
Admins bypass everything. Only make someone an admin if you trust them with access to every page on the site. The dashboard at /admin/ shows who's an admin.
If you ever lock yourself out, email seby@seby.com.au. The recovery path uses the Firebase Console which we can access for you.
