FrancoVarriano

My (meta) thread of threads that recap some of the most interesting points from books I've read on the topics of #Innovation, #StrategicDesign, #DesignThinking

You can access 𝕏 APi via @OpenClaw. We’re trying to make it affordable without giving away the shop. Hopefully, this can be useful & fun 💫

ollama launch hermes Ollama 0.21 includes supports Hermes Agent, the self-improving AI agent built by @NousResearch.

Tools like Fellow are must haves to work effectively with AI and Agents - where context is everything. Congrats on the launch of iOS app @aydin @FellowAInotes producthunt.com/products/fello…

@Mike_Scully_ AI

I condensed everything I know about selling AI services into one cheat sheet. - Niche selection. - Tech stack. - ROI conversations that close deals. - Objections and exactly how to handle them. Free. Just save it. If you want the full breakdown of how to go from zero to your first $10K month using this framework, drop "AI" in the comments and I'll send you the playbook. (Must follow so I can dm you)

@fivosaresti ABM

"ABM is only for enterprise teams with 6-figure budgets." That was true when 6sense was the only option. Now, with: - Clay - Claude Code - Signal tools like RB2B, Findymail, Jungler There’s no more excuse. Anyone can build full ABM infrastructure with a lean team. All you have to do is understand the 4 stages: 1. TAM mapping 2. Signal tracking 3. Awareness scoring 4. Demand generation. The RevOps layer that used to need dedicated headcount and 6-figure contracts now runs on a lean stack. Smaller teams with better infrastructure are outcompeting the ones who built ABM the old way. PS Comment the word "ABM" And I'll send you a massive breakdown we did on the 8 steps you need to build your ABM system.

@lukepierceops NICHE

I mapped every AI automation opportunity across 25 industries. 10-15 pain points each. With the exact positioning, pricing range, and who to sell to. This took me 4 years and 80+ client engagements to figure out. A lot of AI agencies pick a niche and pray. They don't know the actual pain points. They don't know who the buyer is. They don't know what these companies are already paying for broken solutions. They don't know what the realistic project size is. So they end up competing on price for generic "AI automation" gigs. I've worked with marketing agencies, recruiting firms, e-commerce brands, law firms, real estate companies, healthcare practices, financial services, SaaS companies, manufacturing, construction, logistics, and more. Every single one has 10-15 processes that are bleeding money because they're still done manually. Here's what the guide covers for each industry: → The top 10-15 automation pain points (ranked by ROI) → Who the actual buyer is (CEO, COO, ops manager, etc.) → What they're currently paying for manual labor or broken SaaS → Realistic project pricing ($5K-$60K+ depending on scope) → The discovery questions that unlock the deal → How to position yourself as the expert even if you've never worked in that industry → Red flags to avoid (industries and company sizes that aren't worth it) 25 industries and 300+ specific automation opportunities. This is the cheat code for picking your niche and knowing exactly what to sell before you ever get on a call. Like + RT + reply "NICHE" and I'll send you the full guide (Must be following so I can DM)

@AlfieJCarter Bible

I put my entire Claude Code setup for GTM engineering into ONE Notion doc 10 modules. No fluff. - How to install Claude Code and run your first GTM session in under 10 minutes - How to build a CLAUDE. md that acts as your project brain and never loses context - How to install GTM skills that chain together and run autonomously - How to connect your full stack via MCP servers without writing custom wrappers - How to run parallel agents and subagents across GTM workflows simultaneously - How to manage context and token usage across long research sessions - How to choose between Sonnet, Opus, and Haiku based on the task - How to hook Claude Code into external triggers so workflows run without you - The exact GTM workflows to build first: signal detection, lead scoring, outreach sequencing - Full slash command reference for every repeatable GTM task This is the setup I would have KILLED for before spending months piecing it together from documentation, YouTube tutorials, and scattered GitHub threads. Like + comment "BIBLE" and I'll send it over (must be connected for priority access)

"$600K buys 10%. Very rich deal. Management questionable." 10/10 no notes

2005: growth teams optimized funnels 2015: growth teams optimized loops 2026: growth teams optimize agents

@AdamrahmanGTM Prompts

AI does 90% of our initial GTM strategy formulation all in just these 6 prompts. This has been a MASSIVE unlock for speed to winning GTM for our diverse client base. (Comment "Prompts" and I'll DM you a document with all of the prompts.) Here’s what these prompts cover: 1/ Deep Market Research This prompt pulls all relevant information specific to what would be useful for GTM knowledge for the company you're looking to develop a GTM strategy for. The purpose of generating this information is to use it as context for future prompting. 2/ TAM Mapping This prompt will discover all relevant industries & sub-industries that your company could work with, plus statistics on general market size, industry value, and industry growth rates. Outputs from this prompt will also be useful context for other prompts. 3/ ICP Validation This prompt will develop ICPs from the industries uncovered from the TAM Mapping output. It will score each industry segment from highest to lowest priority, find the best fit personas from each industry segment, outline their specific needs & pain points, and craft some messaging ideas around this information. 4/ Company Account Sourcing This deep research prompt will find unique databases for any set of company data that you are looking for. From online directories, to scraping methods, to other niche paid databases - this prompt will give you a list of best fit options for your particular targeting case. 5/ Targeting Keywords Generation This prompt will generate a list of relevant industry and persona keywords to use for specific database filtering for when your developing lists in tools like Apollo. These keywords are typically a lot more accurate than using the general industry filtering. 6/ Messaging Creation This prompt will create multiple email script variations based on the context generated from previous prompts. It'll create unique variations on length of the emails, different offers, pain points, case studies, and complexity. Want these copy-and-paste prompts for yourself? Comment "Prompts" and I'll DM you a document with all of the prompts. (Must be following to receive)

Introducing Overlay: the open source Perplexity Computer. Overlay allows you to do work with the best models. It also lets you set up an OpenClaw cloud instance in one-click! Web: getoverlay.io GitHub: github.com/DevelopedByDev…

the best agents share a pattern... they surface something the user already vaguely knows but hasn't acted on, & then collapse the distance between awareness & action to one tap or no taps at all. that's the magic. in order to do this well, you need a unique surface that makes awareness easy, & that surface needs to allow for ease of consumption + action.

I just claimed my .agent domain and joined the .agent community! get yours now and help shape the future of autonomous agents #Y8CSJOEL" target="_blank" rel="nofollow noopener">agentcommunity.org/join#Y8CSJOEL @agentcommunity_

We set out to cut costs on observability and ended up rebuilding our incident response workflow. By using agent skills to migrate our stack to Grafana & ClickHouse: - Our monthly observability bill dropped ~60% ($20k → $8k) - Root Cause Analysis investigations went from days to hours - Any engineer can use agents to run our 8-phase RCA playbook Read the full blog post to see how we did it: gadget.dev/blog/how-we-ac…

When Hervé Guétin built Brush, an open-source Shopify Custom App starter kit, he needed a backend that could handle auth, data sync, and deployment without the usual headaches. Enter Gadget. Here’s how it helped: 1. PaaS that just works – built-in DB, ORM, routing, dev/prod environments. No DevOps stress. 2. Shopify integration handled – installs, permissions, API updates, data modeling… all automatic. 3.  Production-ready day one – Brush is already running in production. With Gadget, Hervé could focus on features and value, not backend complexity. Learn more: gadget.dev/use-cases/shop…

Is your Node.js worker quietly drowning? Sustained 100% event loop utilization leads to growing backlogs, slow system performance, and timeout errors. Here’s how to spot an overloaded worker early and avoid CPU-blocking pitfalls 👇

Building custom apps for every client was slowing Aligent down. Weeks were spent on rebuilds, redeploys, and infrastructure for each store. With Gadget handling hosting, integrations, and deployment, they now ship reusable apps globally in hours. “With Gadget, we almost have the opposite problem. It's so easy to ship apps, we have to be specific about what we want to build.” - Jarrod Swift, CTO Read the full case study: gadget.dev/blog/aligent-c…

Want the full walkthrough? We break down the architecture, auth flow, and how the homepage + settings pages work step by step here: gadget.dev/blog/building-…

Can vinext (Next.js on Vite) run inside a Gadget app? We tried it and got Next-style routing while keeping Gadget’s managed backend, Postgres, and auth. The trick: a custom Vite middleware plugin. We wrote up the full engineering breakdown (including the exact Vite config we used): gadget.dev/blog/we-ran-vi… Prefer a walkthrough? Watch the video: youtube.com/watch?v=aTpD46…