NotMissing retweeted
Step by step guide for your personal AI lead nurturer and qualifier
78% of customers buy from whoever replies first. Here’s the structure
NotMissing retweeted
if your business is only optimised for Google, it's not enough
most local businesses haven't even optimised for SEO yet. the ones that have are stuck on Google alone while their customers have already moved to ChatGPT, Perplexity and Google AI Overviews
two stats that should scare every local business owner:
only 1.2% of local businesses show up in AI recommendations. everyone else is invisible the second someone stops using Google
only 45% of businesses that rank well on Google also show up in AI answers. your Google ranking and your AI visibility are two completely different games
here's the 3-step system I'd set up if I owned a local business today:
step 1: Take over local search
only 3 businesses show up in the map pack. Everyone else is invisible
most of your competitors have abandoned their Google profiles. wrong categories, no posts, photos from 2019. it's wide open
open Claude:
"compare my Google Business Profile against the top 3 map pack competitors in [city]. pull their categories, photos, reviews and posting frequency. give me a gap analysis and the 10 biggest changes to make this week."
then in the same chat: generate 30 days of posts, write service descriptions with local terms, seed 15 Q&A pairs, and build a review response library.
two weeks of agency work in two hours
step 2: Stop losing leads to voicemail
someone calls, gets voicemail, calls the next guy. a $2k job gone in 45 seconds
"build me a full inbound playbook for a [service] in [city]: SMS auto-reply for missed calls, 5 templates for common inquiries, a 6-question qualification checklist, and a follow-up sequence at 1 hour, 24 hours, 3 days and 7 days."
paste it into your phone or CRM. every inquiry handled the same way
step 3: get recommended by AI before people even Google you
when someone asks ChatGPT "who's the best roofer in Nashville?" it pulls from specific articles and sources. if you're not in them, you don't exist to AI
"search ChatGPT, Perplexity and Google AI Overviews for 'best [service] in [city]'. list every URL being cited. give me a table showing source, domain authority, content type and how hard it would be to get my business included."
then use Claude to write a better version of the top-cited article and publish it on your site. AI crawlers start preferring yours. you show up in recommendations without anyone searching for you by name
better GBP → more reviews → AI cites you → more inbound → repeat
this is how you generate 100+ leads a month without paying for ads
NotMissing retweeted
If you want to learn Claude fast listen up!
This 2 minute read will teach you the basics that you can implement in any of your projects
You should learn these Claud features as a beginner:
1. Chat with persistent context
Not a Q&A tool. A persistent thinking environment. The difference is how you prompt it, give it your full situation, constraints, and goals upfront and keep the conversation going rather than starting fresh every time. The longer the context, the sharper the output.
Prompt
"Here is my current GTM strategy, our ICP, and our last 3 months of conversion data. Identify the weakest point in the funnel and give me three specific fixes."
2. Extended reasoning
Claude can be instructed to think before it responds working through a problem step by step before committing to an answer. Use this for anything involving trade-offs, multi-variable decisions, or situations where a fast answer is probably a wrong one.
Prompt
"I'm considering acquiring a business with £2M EBITDA in a contracting market. Think through the financial, operational and strategic risks before giving me your assessment."
3. Coding and code review
Beyond writing snippets. Claude can hold an entire codebase in context, reason across files, identify architectural issues, and refactor with a full explanation of every decision. Useful whether you're the developer or the person managing one.
Prompt
"Here is my full repo. I'm seeing a performance issue on the data fetch layer. Identify the bottleneck, propose a fix, and explain the trade-offs versus alternatives."
4. 1 million token context window
This is not a minor feature. One million tokens means you can load an entire product spec, legal contract, research report, or codebase and work with it as a single unit. No chunking, no summarizing, no losing information across sessions. Most use cases don't come close to hitting the ceiling.
Prompt
"Here are 12 months of customer support transcripts. Identify the top 5 recurring friction points, cluster them by product area, and suggest the highest-leverage fixes."
5. Custom system prompts
Define exactly how Claude behaves before a conversation starts its role, output format, constraints, tone, and standing context. This is the difference between a generic assistant and a specialized tool built for your specific workflow.
Go to Settings → Custom Instructions, define your configuration once, and every session inherits it automatically.
6. Native integrations
Claude connects directly to Google Drive, Notion, and other tools pulling from your actual documents rather than whatever you paste in manually. For information-heavy workflows this is where it stops being a chat interface and starts being infrastructure.
Authenticate via Settings → Integrations and Claude can read, search and reason over your live files from that point forward.
7. Workflow automation
Claude can sit inside automated pipelines triggered by events, processing inputs, producing structured outputs, handing off to the next step. This is not about prompting faster. It's about removing yourself from the execution loop entirely.
Connect via Integrations or API, define your trigger conditions and expected output format, and Claude handles the processing step without you in the middle.
8. Browser and web interaction
Claude can navigate to a URL and extract structured information from it. Competitor monitoring, pricing tracking, content research without manual collection. Build this into a scheduled workflow and it runs on its own.
Prompt
"Go to these 5 competitor pricing pages. Extract their tier structure, feature inclusions, and price per seat. Return it as a comparison table."
9. App and interface generation
Functional, deployable front ends from a plain language brief. React components, dashboards, internal tools described in a prompt, built in minutes. Not a mockup. Working code.
Prompt
"Build a React dashboard for tracking outbound leads. Fields: name, company, deal size, status, last touchpoint, next action. Rows editable inline, filterable by status."
10. API access
For operators embedding Claude into their own products, automations, or agent infrastructure. Full control over model behavior, system prompts, tool use, and output structure.
Hit anthropic console, generate your key, and call claude-sonnet-4-6 directly with your system prompts, tools, and structured inputs.
The gap between people using Claude as a chat assistant and people running it as operational infrastructure is already large
It's getting wider every month
What are you building with it?
NotMissing retweeted
your Claude and their Claude cost the same $20. so why does theirs do 10x more than yours?
the answer is MCP servers
they turn Claude from a chatbot into something that reads your database, manages your GitHub, sends your Slack messages, and deploys your code. Same Claude. Same subscription. Completely different output.
what is an MCP server?
Model Context Protocol. an open standard that lets Claude connect directly to your tools and services through a universal plug-and-play interface
without MCP: you copy-paste data into Claude, get an answer, copy-paste it back. You are the middleware
with MCP: Claude reads your database directly. Opens your GitHub issues. Send your Slack messages. You just describe what you want done
the servers worth installing:
GitHub MCP: create repos, open PRs, review code, manage issues. If you install one server, make it this one
Supabase MCP: full backend access. Database, auth, storage, edge functions. All of it
Notion MCP: your entire knowledge base becomes queryable and writable through Claude
Slack MCP: "summarize what the team discussed about the launch this week." And getting an actual answer
Memory MCP: Claude remembers context across sessions. The closest thing to giving it a brain that doesn't reset
the gap between people using Claude as a chat assistant and people running it as operational infrastructure is already large.
MCP servers are why.
NotMissing retweeted
We're hiring our first AI automation engineer
@setmyclaw
Responsibilities:
• Build real automation solutions for real clients
• Write custom code where no-code falls short
• Integrate AI platforms, LLMs & APIs end to end
• Work directly with clients to scope and deliver
You're a fit if you:
• Think in workflows, not just tasks
• Can build it, ship it, and explain it to a client
• Are comfortable with Git and production environments
• Have experience with AI agent frameworks
part-time to start. full-time potential as we grow.
This is not a theoretical role. You'll be in the work from day one
application link in the comments 👇
NotMissing retweeted
I'm helping people with a broken openclaw setup.
With Claude starting to restrict third-party tools, a lot of teams are suddenly running into broken workflows and unexpected limitations. If you’re using OpenClaw + Claude and your setup suddenly stopped working, I'm here to help.
I’ve been actively testing alternatives, rebuilding workflows, and figuring out the best solutions for my clients.
If you want help, comment "help", I’ll help you find the best way forward.
NotMissing retweeted
Ok so Apple new Terms and Conditions for iCloud came out and apparently they’re scanning all your photos and videos
How is no one concerned about this?
I’m not sure I want to agree to those terms but if I don’t I can’t use iCloud anymore…
NotMissing retweeted
My AI agent is handling my newsletter so I don’t have to do anything
It’s currently warming up my domain dividing the subscribers in batches
I have 2 types of newsletter - one for b2c which is essentially people coming through X and one for b2b so actual businesses that I get through ads or other sources
I use one common template, my agent automatically writes articles or pulls the ones in my notion and sends it to the right audience
Currently at around 170 subscribers for SetMyClaw, so it will take a while to get an email to everyone but I don’t want to risk my domain authority and ending up in the spam folder
NotMissing retweeted
everyone's trying to build something new with AI.
new app. new SaaS. new side project.
meanwhile their own business still runs on manual replies, forgotten follow-ups, and spreadsheets held together by hope.
you don't need to build the next AI startup.
you need your existing life and business to run without you.
here's what i set up for clients:
• morning briefings - wake up knowing everything that happened
• instant lead response across every channel
• automated follow-ups that never forget
• reports that build themselves from your actual data
not a new product. just your business, on autopilot.
setup takes a week. costs less than your coffee budget to run.
stop building new things. start automating what you already do.
NotMissing retweeted
everyone complaining that OpenClaw "sucks" or "needs constant hand-holding"
that's a setup problem, not a product problem
90% of the issues I see:
→ no SOUL.md (agent has no personality or memory)
→ no HEARTBEAT.md (agent just sits there waiting)
→ wrong model for the task (opus for everything = expensive AND slow)
→ no tool integration (agent can't actually DO anything)
→ no AGENTS.md (no workflow, no structure)
I've set up systems that run 24/7 with near-zero intervention
the difference isn't the tool. it's the config.
building a community for people who want to learn how to do this properly
comment "BUILD" if you want in
NotMissing retweeted
My OpenClaw cron burned through my API rate limit while I was sleeping.
288 agent sessions. Zero new messages. All wasted.
5 rules I follow now so it never happens again:
NotMissing retweeted
I replaced my VA with an AI agent running on a $680 Mac Mini.
It monitors WhatsApp, updates my CRM, sends me Telegram alerts, and drafts replies 24/7.
Cost: $35/month vs $2,000/month.
Here's the full architecture behind it:
NotMissing retweeted
Everyone's talking about SOUL.md but nobody shares theirs
I spent weeks tweaking the 3 files that make my OpenClaw agent actually useful
It has opinions, remembers everything, manages 3 businesses, and knows when to shut up in group chats
Sharing my full SOUL.md + USER.md + AGENTS.md with annotations explaining why each line matters.
Comment "SOUL" and I'll DM you all 3
(follow so I can DM)
NotMissing retweeted
I run a 24/7 AI assistant for $35/month
Not $400. Not $200. Thirty-five dollars
$5 VPS + $30 API (using OpenClaw)
I wrote a complete breakdown showing exactly how to set this up.
Like + Comment "AGENT" and I'll DM you the guide.
(Follow me so I can DM you)
NotMissing retweeted
I just built signal(dot)fm
a living directory for high-signal crypto & web3 podcast.
I saw this idea from a tweet @hosseeb made back in 2021 & decided to explore.
how it works;
> filter by skill level, topics & type
> search instantly and never miss any show
> access each podcast socials & links directly
curious: why will would you want me to see in a podcast dashboard?
💡Early feedback = shaping the product.
check it out here: signal-fm-xi.vercel.app
NotMissing retweeted
$BTC Bitfinex LONGS:
We’re almost there… just a bit more patience.
All of these peaks on the chart have marked major bottoms.
Most people are getting absolutely rekt before the sweet victory. Don’t be that person.
(I’m not implying we have to break the low - just wait)
$BTC Bitfinex LONGS:
We’re still around the same level. I’d definitely be positioned for the upside here, looking at both the BTCUSD chart and this one, plus other factors like overall liquidity.
However, if we want to be really picky, you could say we still have a few percentage points left before reaching that green trendline. So I’d keep some stables ready to compound your long in case we get another dump and our whale friends over at Bitfinex decide to allocate a bit more.
Also consider that these peaks have all marked a major bottom so far.



















