Lab, samples

Sample automations.

Three go to market workflows I designed and built for a B2B software startup. They run on Claude, a few tools the team already had, and GitHub Actions. A person stays in the loop wherever judgment matters. Client names and data are removed.

01   Content pipeline

A week of content, two decisions.

Built

Sunday night, Claude proposes five blog ideas from keyword gaps, competitor moves and customer pain points, checked against memory files for the brand, the personas and the keywords so nothing repeats. Marketing picks two.

Monday afternoon, Claude writes each pick in full, straight into its Notion page: the post with its SEO details, three LinkedIn versions and a five-slide carousel PDF. Marketing approves, and a daily GitHub Actions job turns approved posts into site pages and opens a pull request. It runs without anyone’s laptop open.

Sunday nightClaude: 5 ideasNotionStatus: IdeaPick twoMarketingMonday 4pmPost, 3 LinkedIn, carouselApproveMarketingDaily jobGitHub ActionsPull requestClaude CodeSlack pingReady to mergePublishedOn the site

Scroll sideways to see the whole diagram.

Where a person decides

Where the person steps in

  • Pick two of five ideas

    Nothing gets written until a person chooses.

  • Approve before anything ships

    Edit in Notion, then approve. Publishing only follows approval.

Built withClaude, Notion, GitHub Actions, Claude Code, Slack.

02   Outbound engine

Four tracks, two human touches.

Built, ready to switch on

Every weekday morning Claude pulls fifty new leads, scores them on title, company fit, technology and intent, and enrolls the best into one of nine sequences by role. When a known company visits the website, a short warm sequence starts the same day, by email and LinkedIn.

Every two hours Claude reads the replies, sorts them into interested, later, no and out of office, and drafts an answer from approved templates. Claude never sends: a person reads each draft in Slack and sends it. On Fridays Claude scores every sequence, retires what is not working, promotes what is, and writes a fresh angle for each retired message.

Weekdays, 8amTrack 1Claude scores 50 leadsTitle, fit, tech, intentEnroll the best9 sequences, by roleSummary in SlackSite visitTrack 2Claude checks and routesSkips anyone in a sequenceWarm sequenceEmail and LinkedInStarts the same dayEvery 2 hoursTrack 3Claude sorts repliesInterested, later, no, awayDrafts an answerFrom approved templatesA person sends itReviewed in SlackFridays, 3pmTrack 4Claude scores sequencesRetire or promoteWrites a new angleNot a rewordA person approvesAbout five minutes

Scroll sideways to see the whole diagram.

Where a person decides

Where the person steps in

  • Send every reply yourself

    Drafts arrive in Slack. A person reads, edits if needed, and sends. Usually zero to five a day.

  • Approve new copy on Fridays

    About five minutes. Pausing and promoting sequences is already done.

Built withApollo, Claude, HeyReach, RB2B, Slack, a Notion message library, GitHub Actions. About $300 to $450 a month in tools and API, before people time.

03   Daily LinkedIn brief

Thirty seconds of LinkedIn a day.

Ran every weekday

At 7:07 every weekday morning, a GitHub Actions job runs Claude Code. It searches the news on five industry topics, reads the top articles in full, and checks every link so nothing broken reaches the founder. Claude picks the three that fit the company’s positioning and drafts a comment on each in the founder’s own voice.

The founder gets one email with three cards and a share button on each. The brief follows a weekly rhythm, a video prompt on Tuesdays and a personal story on Thursdays, and every two weeks it nudges for something more human.

Weekdays, 7:07GitHub ActionsSearch the newsFirecrawlCheck linksBroken ones outClaude picks 3Drafts commentsOne emailShare buttonsFounder postsAbout 30 seconds

Scroll sideways to see the whole diagram.

Where a person decides

Where the person steps in

  • Tap, tweak, post

    The founder chooses what to share and in what words. About thirty seconds a day.

Built withGitHub Actions, Claude Code, Firecrawl, Resend.

Want one of these running in your stack, under your name? Tell me what your team does by hand every week.

cassandra@instinctai.io

Or use the form.

Instinct AI LLC, Tulum, Mexico