Each one links to the original source, says what was reported, and lists the limits.
89 workflows
A newsletter post gives a nine-step sequence and six prompts to find the outcome clients buy, standardise repeatable parts, design three package tiers, price by value and build a productized service.
A founder connects five MCP servers to Claude Code, each acting as an SEO analyst, market researcher, technical auditor or product analyst, with the prompts he uses, including a weekly rage-click report.
A newsletter writer has Google Analytics and Search Console email six CSV reports each Monday, and a Claude skill compares the week to the last and saves a visual report and the raw data to a dated folder.
An MIT-licensed plugin of Claude Code skills that guides a founder from an idea scorecard and competitor matrix through MVP scope, pricing strategy, go-to-market and a pitch deck outline, saving each output to a project folder.
A paid newsletter post explains two prompts and a workflow for designing a landing page with Claude Design, matching your brand, then handing the design to Claude Code to build.
A creator used Claude Design to build a brand system and landing page from her existing copy, Claude Code to build the assessment site, and an email tool to send profile-specific sequences.
A developer says a SaaS with only welcome, reset and receipt emails lost users after a day, and a Claude Code command planned and built six lifecycle sequences that check app state between sends.
A paid newsletter tutorial uses one prompt to define activation milestones and then prompts for a welcome email and follow-ups at days 3, 7, 14 and 30 to move new customers toward activation.
A newsletter author describes a small services business that classifies enquiries, drafts a first reply and tags the owner in Slack, with human review and fixed follow-up rules, cutting handling time per lead.
A framework for choosing a first AI automation by its worst-case outcome, connecting an inbox read-only, watching the first twenty runs, and naming who verifies output before widening the agent's permissions.
A solo developer describes an hourly support agent on a spare computer that classifies emails, replies to what it can answer from an instruction file, and forwards everything else to the founder.
A solo automation engineer lists seven n8n workflows for agencies, from CRM-triggered onboarding to proposal reminders, with AI used for inbox triage and content repurposing drafts.
A step-by-step build of a Claude Code subagent that, given a post or topic, gathers search trends and search results and writes a research brief with keywords, snippet opportunities, competitor gaps and a suggested title and slug.
A newsletter writer built a coding-agent workflow that starts from his own Search Console queries, checks demand and competitors through a keyword tool, and labels each idea as write, update, expand, test or ignore.
A freelancer's guide to the business side of building document chatbots for small clients: discovery call, a small free demo, a one-page scope, testing, handover and monthly support.
An AI engineer describes a retrieval-augmented chatbot deployed for one client with over 500 PDFs, with the chunking and retrieval choices, and reports 94% answer accuracy against 61% for plain GPT-4.
An automation engineer describes an n8n workflow that pulls analytics, search and ad data each Friday, has Claude write a plain-English comparison with the prior week, and emails clients a Google Doc.
An agency owner replaced a $15,000 developer quote by learning React from a course, then using AI mainly for debugging, to build a keyword research and content brief SaaS with paying customers.
A product manager describes building a macOS image-search app and its website with Cursor and an AI assistant, and the hosting, packaging and signing work that took far longer than the code.
A deliberate experiment built a 60,000-page site with a small OpenAI model for about $10 and recorded that AI crawlers requested it far more than Googlebot. The author expects it to be deindexed.
A public repo documents a content site's SEO system: scripts that split human from machine search queries, judge rewrites against untouched control pages, and guard against traffic drops.
An architecture write-up of three niche directory sites whose content is generated by Claude Haiku, rebuilt nightly, kept small and linked to primary sources, in a six-month experiment on whether such sites can rank.
A paid newsletter post says a prompt reverse-engineered from replied-to emails produced 167 replies and 43 meetings from 500 sponsorship cold emails, with each prompt version tested on 40 prospects.
A step-by-step build that tags each open-text survey response with themes, sentiment and a churn signal using a cheap Claude model, alerts on risky ones, and emails a weekly summary of themes.