Tre & Tide Operations & Automation

What I have built.

Every team system on this page runs, or ran, in production. The team names stay private, and the work, the tools and the way each one runs are as built. Beside them are the smaller builds I share in public.

  • 15 systems
  • 8 teams
  • 9 live today
  • 6 delivered and handed over

Status checked 20 November 2026.

Built in public

Smaller builds and experiments I wrote up on LinkedIn, newest first. Open any one to read the full post.

  1. Invoices that start in Slack and land in QuickBooksAn accountant asked if everything could live in QuickBooks. Now an invoice asked for on a call is drafted, approved in Slack and sent without being built by hand. · QuickBooks · Slack · Trigger.dev (LinkedIn post, opens in a new tab)
  2. An AI video, made one approved step at a timeScript first, then stills, then motion. Every shot came from AI, but no step started until I had signed off the one before. · Claude · OpenAI · ElevenLabs · Remotion (LinkedIn post, opens in a new tab)
  3. What a Google Maps listing says about follow-upA scan of local clinics' listings, reviews and website chat, to see where customers drop after the first message and what to automate first. · Apify (LinkedIn post, opens in a new tab)
  4. An AE's day, planned in one Slack messageEvery morning n8n reads each open deal's emails, calls and meetings in Attio, and sends the rep what to do today, who to reply to, and a draft waiting in the thread. · n8n · Attio · Slack (LinkedIn post, opens in a new tab)
  5. A watch for when my tools change underneath meEvery morning n8n reads status pages, changelogs and deprecation notices for the tools I build on, plus my own failed runs, and only flags what needs action. · n8n · Firecrawl (LinkedIn post, opens in a new tab)
  6. From form fill to qualified lead, instantlyA tiny form is enriched and scored on Cloudflare Workers the moment it is sent, with a reply drafted for the good ones. · Cloudflare · Deepline · Attio (LinkedIn post, opens in a new tab)
  7. Who came up on that call?After each call, n8n pulls the transcript, lists everyone mentioned, finds them and sends me a recap, never looking anyone up twice. · Granola · n8n · Deepline · Supabase (LinkedIn post, opens in a new tab)
  8. LinkedIn invites, recapped before I open LinkedInEach new invite is looked up and sorted into peer, buyer or employer, with a suggested reply waiting on my phone. · n8n · Deepline · Supabase (LinkedIn post, opens in a new tab)
  9. A job bot that scores companies against my own ICPEvery weekday it watches a list of companies in Attio and flags the hiring and news that fit what I want next. · Attio · Clay (LinkedIn post, opens in a new tab)
  10. One chat that routes work across my AI toolsI talk to one bot, and it hands planning, coding and checking to the right model, so I stop being the copy-paste router. · Claude · OpenAI (LinkedIn post, opens in a new tab)
  11. A workflow that builds workflowsAn n8n form asks five plain questions about a manual task, then a workflow drafts the automation live. Built for my first n8n meetup. · n8n · Claude (LinkedIn post, opens in a new tab)
  12. An assistant that works while I sleepA bot with my project notes behind it reads weekend messages, pulls the context, lists my actions and finishes the small ones. · Claude (LinkedIn post, opens in a new tab)
  13. The same job-board watcher, in code and on the canvasA watcher for open GTM and RevOps roles, first on Cloudflare Workers, then rebuilt in n8n so beginners can follow it. · Cloudflare · n8n (LinkedIn post, opens in a new tab)
  14. Funding news to a founder's emailA pipeline I first wrote in code, rebuilt node for node in n8n so people can see how it works. · n8n (LinkedIn post, opens in a new tab)
  15. Turning interviews into contentA content machine built around the interview itself, so the best lines from each recorded conversation become posts ready for review. · Fathom · Claude · Cloudflare (LinkedIn post, opens in a new tab)
  16. A hiring-signal monitor on CloudflareOne Worker checks company job boards every day for open RevOps and GTM roles, without spending a single AI token. · Cloudflare (LinkedIn post, opens in a new tab)
  17. Notes that tidy themselvesInstead of re-cleaning my Obsidian vault, a routine airs it out on every run, linking new notes and flagging stale ones. · Claude (LinkedIn post, opens in a new tab)
  18. Deal owners set by the calendarWhen a call is booked, whoever runs it becomes the deal owner in the CRM, with nobody assigning it by hand. · Trigger.dev · Attio (LinkedIn post, opens in a new tab)
  19. Who actually engages with my postsA daily task pulls everyone who reacts or comments, keeps each person once, and scores who is worth a conversation. · Trigger.dev · Apify · Supabase · Claude (LinkedIn post, opens in a new tab)
  20. Account signals without ClayOne sentence in, real matching companies out with their sources, then a contact waterfall. Proof that signal work does not depend on one tool. · Deepline (LinkedIn post, opens in a new tab)
  21. Making Claude Code pick the right modelGlobal rules for which model handles which job, so the heavy models only run when they earn it. · Claude (LinkedIn post, opens in a new tab)
  22. A voice assistant that talks to Claude CodeA phone app with my working context behind it, so I can pick work back up when I am away from the laptop. · Vercel · Supabase · Claude (LinkedIn post, opens in a new tab)
  23. A Clay workbook, rebuilt in Claude CodeFind, score, enrich, find people, personalise and write, as a chain of files a team can read. Built as a teaching demo. · Clay · Claude (LinkedIn post, opens in a new tab)
  24. What to say to a website visitorWhen a visitor is identified in Slack, a bot reads their profile and drafts the first email and LinkedIn note in the thread. It never sends. · Slack · Trigger.dev · Claude (LinkedIn post, opens in a new tab)
  25. A newsletter digest that curates itselfEvery morning it scans brand and AI channels and scores what it finds, leaving the taste call to the person who writes. · Trigger.dev · Claude · Notion (LinkedIn post, opens in a new tab)
  26. Catching the deals going quietEvery weekday morning a bot reads the open deals in the CRM and flags the few going cold this week. · Trigger.dev · Attio · Slack (LinkedIn post, opens in a new tab)
  27. One AI assistant, everywhere people askThe team's Slack bot, the portal chat and the website widget share one brain in Supabase, instead of being four separate assistants. · Supabase · Slack · Claude (LinkedIn post, opens in a new tab)
  28. Deals that move stage on their ownWhen a sales call recording lands, the deal moves on in the CRM without anyone dragging it. · Fathom · Attio · Trigger.dev (LinkedIn post, opens in a new tab)
  29. Picking up one thread, not the whole projectA Claude Code skill that loads only the context I ask for, part of my log, handover and pickup routine. · Claude (LinkedIn post, opens in a new tab)
  30. Context that builds up across every callEach call's transcript adds to one running note on the deal, so whoever joins call four knows what happened in calls one to three. · Attio · Fathom · Claude (LinkedIn post, opens in a new tab)
  31. Coaching logs, prep and handoversA small system that remembers each coaching session, so I never arrive at the next call cold. · Supabase · Fathom · Claude (LinkedIn post, opens in a new tab)
  32. Handover and pickup skills for every sessionTwo Claude Code skills: one writes the session log and handover at the end, the other loads it back at the start. · Claude (LinkedIn post, opens in a new tab)
  33. Where did our students come from?Form answers about how people found the program now land on each person's CRM record, where the team can use them. · Trigger.dev · Attio (LinkedIn post, opens in a new tab)
  34. Giving Claude Code a memory of its own fixesAutomation logs it can read, so a bug found once is not rediscovered in the next session. · Supabase · Claude (LinkedIn post, opens in a new tab)
  35. One row per customer that every automation readsA Supabase table created at sign-up, holding billing, project status, folders and payment IDs, that every automation reads and writes. · Supabase (LinkedIn post, opens in a new tab)
  36. LinkedIn profiles filled in for every new leadEach new lead in the CRM is sent to Clay for its LinkedIn profile and written straight back, and an hourly sweep catches any that were missed. · Attio · n8n · Clay · Trigger.dev (LinkedIn post, opens in a new tab)
  37. A notes vault that links itselfA tag system and an auto-linker for my Obsidian notes, so every new file is connected to the notes it belongs with. · Claude · Obsidian (LinkedIn post, opens in a new tab)
  38. A tool that takes good posts apartPaste a post, a cold email or an n8n workflow, and it explains the mechanic behind it and how to build the same thing. · Supabase · Claude (LinkedIn post, opens in a new tab)
  39. A community leaderboard, rebuilt on Trigger.devA weekly ranking of members’ LinkedIn posts, rebuilt as a queue that survives rate limits and crashes, and posted to Slack every Monday. · Trigger.dev · Supabase · Slack (LinkedIn post, opens in a new tab)
  40. Giving OpenClaw a fair tryWhat changed my mind after being skeptical of it for a while. (LinkedIn post, opens in a new tab)
  41. A script for Clay’s filter dropdownsClaude Code wrote a browser script that types and picks every ICP industry in Clay’s filters, so nobody clicks through them one by one. · Claude · Clay (LinkedIn post, opens in a new tab)

A podcast and video studio

One system for the whole studio, from the first booking to the finished episode, built around the tools the team already had.

Watch it run: booking to paid, without anyone retyping it.

A 4-minute walkthrough of the studio system, from the first booking to the paid invoice in the books. Example data only, no live accounts.

Booking to paid invoice

People book a session online with 48 hours' notice. The invoice and pay link go out from the studio's own email, and an unpaid slot is released when the hold runs out.

  1. Booking page
  2. QuickBooks invoice
  3. Pay link
  4. Paid in the books
  • QuickBooks
  • Trigger.dev
  • Google Workspace
  • Slack

Live

Bookings that skip upfront payment

A private booking link for trusted regulars. It books the session, drafts the invoice and tags the person who sends invoices in Slack, so nothing goes out unchecked.

  1. Private link
  2. Session booked
  3. Draft invoice
  4. Checked in Slack
  • QuickBooks
  • Trigger.dev
  • Slack

Live

A portal for the studio's customers

Customers see their upcoming sessions, sign their contract, and watch and comment on their edits in one place, instead of in email threads.

  1. Sign in
  2. Upcoming sessions
  3. Contract
  4. Review the edit
  • ClickUp
  • Google Workspace
  • Supabase

Live

Footage to editing, with quiet alerts

New footage reaches the editors without anyone dragging files, and the team gets one batched update instead of a message per file. When a connection needs signing in again, one Slack post reminds in its thread until it is fixed, then ticks itself done.

  1. Footage lands
  2. Editing task
  3. One batched update
  4. Ticked when fixed
  • ClickUp
  • Trigger.dev
  • Slack

Live

A B2B software company's sales and success teams

Built inside their own codebase with their engineer, who reviewed and merged every change. Improved one feedback round at a time.

Signal-based outreach

Which accounts need attention today, and why. A signals engine reads the CRM and outside changes, ranks what matters for each rep, and sends one Slack message every morning. A draft email only appears after the rep picks who to write to.

  1. CRM and signals
  2. Ranked per rep
  3. Morning Slack
  4. Rep decides
  • HubSpot
  • Clay
  • Neon
  • Vercel
  • Slack

Video walkthrough coming soon

Live

A closed-won handoff nobody retypes

When a deal closes, a handoff record collects why they bought, what they bought and what could get in the way, with an approval step in Slack before onboarding starts.

  1. Deal closes
  2. Handoff record
  3. Approved in Slack
  4. Onboarding starts
  • HubSpot
  • Trigger.dev
  • Slack

Video walkthrough coming soon

Live

A coaching and community business

Membership billing that runs on its own. The team only hears about it when something needs a person.

Membership billing on Stripe

Each plan has its own invite link. Payments, renewals and access to the community plan run on their own, and the team gets an email when a payment fails or a card is about to expire.

  1. Invite link
  2. Stripe checkout
  3. Access granted
  4. Alert if a payment fails
  • Stripe
  • Trigger.dev
  • Vercel

Video walkthrough coming soon

Live

Member payments, tracked in Notion

Stripe payments write back to the team's member tracker in Notion. A payment issue is flagged on the member's row and clears once it is resolved.

  1. Stripe payment
  2. Member tracker
  3. Issue flagged
  4. Cleared when resolved
  • Stripe
  • Notion
  • Trigger.dev

Live

Testimonial intake with a review step

Graduates share their story through a short intake page. The team gets it in Slack, and nothing is used until a person approves it.

  1. Intake page
  2. Lands in Slack
  3. A person approves
  4. Ready to use
  • Cloudflare
  • Slack

Ran in production · handed over

A cohort check-in dashboard

One view of every cohort, so the support team knows who to check in with next. It sits behind a staff sign-in, because it holds student data.

  1. Check-in sheets
  2. One dashboard
  3. Who to check in with
  • Cloudflare
  • Google Workspace

Ran in production · handed over

Deals that move stage on their own

When a sales call recording lands, AI reads what was agreed and moves the deal to the right stage in the CRM, so nobody drags cards around after a call.

  1. Call recorded
  2. Transcript read
  3. Stage decided
  4. Deal moves in Attio
  • Fathom
  • Trigger.dev
  • Anthropic
  • Attio

Ran in production · handed over

More teams I have built for

Smaller builds for four more teams. Each one was delivered and documented so the team could run it.

Review intelligence for a multi-office firm

For a law firm with offices across one state. Google reviews for every office are collected each morning, scored by AI for sentiment, themes and the staff they mention, and shown per office and per person in a dashboard behind a sign-in.

  1. Google reviews
  2. AI scoring
  3. Per-office view
  4. Staff scorecards
  • Apify
  • n8n
  • Anthropic
  • Supabase
  • Vercel

Live · handed over

A searchable clinic directory

For a veterinary recruiting company. A directory web app over a registry of clinics and vets, kept in sync by scheduled workflows, with sensitive fields masked, downloads behind a password, and reports sent by email.

  1. Source records
  2. Synced registry
  3. Directory app
  4. Email reports
  • n8n
  • Supabase
  • Trigger.dev
  • Vercel

Ran in production · handed over

AI short videos, from question to finished file

For an interview-prep startup's social team. Claude writes the script and caption for each interview question, an AI presenter video is generated, captions and the logo are added, and the finished vertical video lands in Google Drive.

  1. Next question
  2. Script by Claude
  3. AI video
  4. Branded video in Drive
  • Trigger.dev
  • Anthropic
  • OpenAI
  • Supabase
  • Google Workspace

Delivered with a handover

A newsletter digest that curates itself

For a branding studio's newsletter. Every day it finds B2B branding posts and videos, ranks them, drops the repeats, files the best in Notion and emails a short digest.

  1. Posts and videos
  2. Ranked, no repeats
  3. Filed in Notion
  4. Daily email
  • Trigger.dev
  • Anthropic
  • Notion
  • Google Workspace

Read the LinkedIn post (opens in a new tab)

Delivered · now paused

Alongside the builds, I teach.

I spent 18 months coaching Clay cohorts, and I run n8n meetups in Da Nang as the first n8n Ambassador in Vietnam. It is why every project ends with SOPs and training, so the team can run it without me.

Want one of these for your team?

Book a call and bring the workflow that keeps going wrong, or send me a short message about it.

Message me