<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by seyyed mohammad Razavi on Medium]]></title>
        <description><![CDATA[Stories by seyyed mohammad Razavi on Medium]]></description>
        <link>https://medium.com/@seyyedmohammadrazavi?source=rss-7f62f6edcdca------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Jdy1OoFn9Cus4bBXzdPvhw.png</url>
            <title>Stories by seyyed mohammad Razavi on Medium</title>
            <link>https://medium.com/@seyyedmohammadrazavi?source=rss-7f62f6edcdca------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:26:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@seyyedmohammadrazavi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[6 Free GitHub Repos to Turn Any Website Into Clean, Structured Data]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/6-free-github-repos-to-turn-any-website-into-clean-structured-data-381e9fe81ba7?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/381e9fe81ba7</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[llm-agent]]></category>
            <category><![CDATA[web-scraping]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 09:48:41 GMT</pubDate>
            <atom:updated>2026-10-14T09:48:41.382Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I run a data company, so believe me on this one: the hard part was never the AI. It’s turning the web’s mess into something a machine can read. Six repos cover the whole territory.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIuQOPP_du6-l6R8VoxKTw.png" /><figcaption><em>From tangled websites and hostile PDFs to rows a machine can actually use.</em></figcaption></figure><p>I run a B2B data company, so take this from someone whose whole business is the problem: the hard part was never the AI.</p><p>The hard part is that useful data refuses to live in convenient places. It lives on websites with no API. In PDFs where the tables have merged cells. In Word documents last touched in 2014. Every AI pipeline, every market analysis, every enrichment job starts with the same unglamorous step: turning that mess into something structured.</p><p>The open-source world has quietly solved this, piece by piece. Six repos cover the whole territory. Here’s the honest tour, including where each one lets you down.</p><h3><strong>1. firecrawl: the default answer (190k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*lVlTULEQln6znDgYkLfm9A.png" /><figcaption><em>Point it at a domain, get back markdown a model actually wants.</em></figcaption></figure><p>If you only remember one name from this article, make it this one.</p><p>firecrawl crawls a website and hands back clean markdown or structured JSON, built specifically for feeding AI pipelines. Point it at a domain; it handles the crawling, the JavaScript rendering, the cleanup. In 2026 it has simply become the default answer to “get this website into my pipeline”, and the star count says the industry agrees.</p><p>The fine print: the open-source core is real, but the frictionless experience leans toward their hosted API, which has a meter on it. Self-hosting works and asks more of you. Know which deal you’re taking before you architect around it. (Housekeeping note: the project now lives at firecrawl/firecrawl; the old mendableai URL redirects.)</p><p>Use it when: websites, at scale, with JavaScript, and you want the problem to just go away.</p><p><a href="https://github.com/firecrawl/firecrawl">https://github.com/firecrawl/firecrawl</a></p><h3><strong>2. markitdown: the universal converter (189k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*-hTa4TCKgL6zGNKarJmpKg.png" /><figcaption><em>One tool, one output format, and it’s the format LLMs read best.</em></figcaption></figure><p>Now the other half of the mess: files. The inbox full of PDFs, decks and spreadsheets that someone wants “in the AI”.</p><p>markitdown is Microsoft’s answer, and its beauty is its narrowness. It converts files and office documents — PDF, Word, Excel, PowerPoint, images, HTML — to Markdown, the one format LLMs read best. It doesn’t try to be a pipeline or a platform. It converts, and it converts well. Most document-heavy projects I know end up with it somewhere in the stack.</p><p>Its limit is depth: complex layouts get flattened, and a gnarly table can come out as mush. When the document’s structure IS the content, you need the next repo. For the other 80% of files, this is the fastest path by far.</p><p>Use it when: ordinary office documents need to become model-readable, today.</p><p><a href="https://github.com/microsoft/markitdown">https://github.com/microsoft/markitdown</a></p><h3><strong>3. crawl4ai: the crawler you fully own (85k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*I51csoiLnSi1i2rJbJVmUg.png" /><figcaption><em>Self-hosted crawling with every knob exposed.</em></figcaption></figure><p>Back to websites, with a different philosophy. Where firecrawl says “let us handle it”, crawl4ai says “here are all the knobs”.</p><p>It’s an open-source crawler built for LLM pipelines: any website into clean, LLM-ready Markdown, with fine control over extraction strategies, caching and browser behavior, running entirely on your infrastructure. For a data team that considers crawling a core competence rather than a chore, that control is the whole point.</p><p>The flip side is that the knobs are mandatory. More configuration, more moving parts, more reading before the first clean page comes out. And a fast-moving project means APIs evolve; pin your versions.</p><p>Use it when: compliance, cost or craft says the crawler must be yours.</p><p><a href="https://github.com/unclecode/crawl4ai">https://github.com/unclecode/crawl4ai</a></p><h3><strong>4. docling: for documents that fight back (68k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*1yfiIj6bNaUspwWuL1w4Rw.png" /><figcaption><em>Tables that span pages, scanned contracts, multi-column reports: its home turf.</em></figcaption></figure><p>Remember the documents markitdown flattens? This is where they go.</p><p>docling parses complex documents and keeps their structure alive: tables that span pages, multi-column layouts, scanned pages, figures. The 200-page regulatory PDF, the financial report where the tables ARE the content, the contract someone scanned slightly crooked in 2019. Where simpler converters lose the structure, docling works to preserve it.</p><p>The cost is weight. It’s a heavier dependency with real models under the hood, so it’s slower per page and hungrier per machine than a simple converter. Running it on documents markitdown could handle is paying freight rates for a postcard.</p><p>Use it when: the simple converter returned mush and the mush mattered.</p><p><a href="https://github.com/docling-project/docling">https://github.com/docling-project/docling</a></p><h3><strong>5. scrapegraph-ai: describe what you want (31k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*0sC6SSUGKFF4sw3iGo_Png.png" /><figcaption><em>A prompt instead of selectors: scraping that survives redesigns.</em></figcaption></figure><p>Every scraper so far still thinks in pages. This one thinks in goals.</p><p>scrapegraph-ai is a Python scraper where you describe what you want in a prompt, and it builds the extraction pipeline as a graph and runs it. No hand-written selectors, which means no 2 a.m. fixes when the target site ships a redesign and every XPath dies. For sites that change constantly, it’s a genuinely different paradigm.</p><p>Two honest costs. Every extraction spends LLM tokens, so at volume the economics need checking against a hand-written scraper that runs free forever. And model-driven extraction is probabilistic: mostly right, occasionally creative. Validate the output; don’t pipe it straight into production.</p><p>Use it when: the site changes faster than you can maintain selectors, and volume is modest.</p><p><a href="https://github.com/ScrapeGraphAI/Scrapegraph-ai">https://github.com/ScrapeGraphAI/Scrapegraph-ai</a></p><h3><strong>6. maxun: no code, no ticket (17k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*PHsrr4-ZvJFbOeP7xcT4yQ.png" /><figcaption><em>Train a robot in clicks; get a spreadsheet or an API out.</em></figcaption></figure><p>Last one, and it’s for a person who’s been missing from this article: the one who doesn’t code.</p><p>maxun turns any website into a structured API without code. You train a robot on a site in a few clicks, and it extracts, automates and monitors, handing back a spreadsheet or an endpoint. The marketer who checks competitor pricing every Monday, the analyst who copies the same table weekly: this is their repo, and it means they stop filing tickets to get data.</p><p>The limits are the usual no-code limits: logins, aggressive anti-bot walls and heavy JavaScript can defeat the robot, and when it breaks, debugging is clicking, not reading a stack trace. Self-hosting it is still a technical afternoon; someone sets it up once so everyone else clicks.</p><p>Use it when: the person who needs the data weekly isn’t the person who writes code.</p><p><a href="https://github.com/getmaxun/maxun">https://github.com/getmaxun/maxun</a></p><p>· · ·</p><p><strong>The map, folded up</strong></p><p>Documents: markitdown first, docling when they fight back. Websites: firecrawl to make it easy, crawl4ai to make it yours. Sites that won’t sit still: scrapegraph-ai. People who don’t code: maxun.</p><p>In B2B, the data you need almost always lives on someone else’s website. I’ve built a company on that inconvenient fact. These six repos are how you stop treating it as an inconvenience and start treating it as a pipeline.</p><p>What’s the one source you still copy by hand every week?</p><p>· · ·</p><p><strong>Want more repos like these?</strong></p><p>I publish breakdowns like this one all the time: the best, fastest-trending repositories on GitHub, what they’re actually good for, and where they fall short. If that’s your kind of reading, two places to get more.</p><p><strong>The Best GitHub Repos Newsletter</strong>, free in your inbox: <a href="https://best-github-repos.beehiiv.com/subscribe">https://best-github-repos.beehiiv.com/subscribe</a></p><p>And our community on Reddit, <strong>r/BestGitHubRepos</strong>: more than 100,000 members and climbing fast, the fastest-growing subreddit of the year. The comments regularly surface great repos before they trend.</p><p><em>All six repositories are free and open source; star counts were read from GitHub on October 11, 2026.</em></p><p><em>Screenshots from the repositories’ GitHub pages.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=381e9fe81ba7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Free GitHub Repos to Run AI on Your Own Hardware, No API Bill Attached]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/6-free-github-repos-to-run-ai-on-your-own-hardware-no-api-bill-attached-811090282747?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/811090282747</guid>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 09:45:07 GMT</pubDate>
            <atom:updated>2026-10-14T09:45:07.828Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The month our API bill crossed four digits, I spent a weekend testing the local stack. Here’s the honest tour: what shines, what hurts, and the order to try it in.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eTvMwcrvpp4FNtLUv60tyw.png" /><figcaption><em>The whole stack runs on hardware you already own. The question is whether you should.</em></figcaption></figure><p>The month our API bill crossed four digits, three people forwarded me the same invoice with three different comments.</p><p>Finance asked if it would grow. Legal asked where the prompts go. An engineer asked the question that stuck: “can’t we just run this ourselves?”</p><p>The answer is yes, and it’s more mature than most teams think. The entire local AI stack is open source and sitting on GitHub. But “can” and “should” are different questions, so this is the honest tour: six repos, what each one shines at, where each one hurts, in the order I’d actually try them.</p><h3><strong>1. jan: the five-minute proof (44k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*a8daDVg-b1YrM0TtttbKpg.png" /><figcaption><em>Download, pick a model, chat. The demo that convinces the skeptics.</em></figcaption></figure><p>Start where the proof is cheapest.</p><p>jan is an open-source ChatGPT alternative that runs 100% offline: download, install, pick a model, chat. No terminal, no YAML, no API keys. It’s the five-minute demo that turns “local AI is a nerd hobby” into “wait, that’s running on my laptop?”</p><p>What it won’t do is serve your team; it’s a personal app, not infrastructure. And your laptop’s RAM decides which models feel snappy and which feel like chess by mail. Treat it as the proof of concept, not the deployment.</p><p>Use it when: you need to convince yourself, or a skeptical colleague, in one coffee break.</p><p><a href="https://github.com/janhq/jan">https://github.com/janhq/jan</a></p><h3><strong>2. open-webui: the screen your team will live in (154k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*FNzHIA0hWunWwRdg3zBI-w.png" /><figcaption><em>Self-hosted chat your team actually enjoys: accounts, RAG, admin controls.</em></figcaption></figure><p>Convinced? Then the next question is what your team actually looks at every day.</p><p>open-webui is a self-hosted chat interface that speaks to Ollama and any OpenAI-style API. Multi-user, access controls, built-in RAG, a plugin system. It looks and feels like the hosted products your team already knows, which matters more for adoption than any benchmark.</p><p>The honest part: you now run a web app. Updates, auth, backups, the occasional breaking change between versions — someone owns that now, and that someone is you. It’s light work, but it’s work that didn’t exist when the vendor did it.</p><p>Use it when: more than one person needs local AI and nobody wants to learn a terminal.</p><p><a href="https://github.com/open-webui/open-webui">https://github.com/open-webui/open-webui</a></p><h3><strong>3. llama.cpp: the engine under everything (130k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*5wRK0fIrKoiWWKemiUe7MQ.png" /><figcaption><em>Plain C/C++, no dependencies. The project that made local inference real.</em></figcaption></figure><p>Behind that interface, something has to actually run the model. Meet the project that made this whole movement possible.</p><p>llama.cpp is LLM inference in plain C/C++ with no dependencies, running quantized models on CPUs, consumer GPUs, laptops, single-board computers. Half this list is built on top of it. Its quantization formats are the reason a 70B model fits on hardware you own.</p><p>The tradeoff is that it’s a power tool. Build flags, quantization levels, GPU offload layers: the knobs give you performance the wrappers can’t, and the knobs are also why most people stay inside the wrappers. You can use it indirectly forever. Touch it directly the day you need the last 30% of speed.</p><p>Use it when: performance tuning starts mattering, or you just want to see the engine without the hood.</p><p><a href="https://github.com/ggml-org/llama.cpp">https://github.com/ggml-org/llama.cpp</a></p><h3><strong>4. LocalAI: the drop-in replacement (49k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*7bPOUAOGTfUl36K6l4383A.png" /><figcaption><em>One OpenAI-style endpoint, many modalities, your hardware.</em></figcaption></figure><p>Now the integration question: you already have apps that speak the OpenAI API. Rewriting them for local models would be absurd.</p><p>LocalAI’s whole pitch is that you don’t. It’s an open-source engine that runs LLMs, vision, voice, image and video models on your hardware, all behind an OpenAI-style API. Point your existing code at a new base URL and most of it just works.</p><p>The honest tradeoff: breadth costs polish. Covering that many modalities means some backends are rock solid and others are clearly younger, and debugging a failing model sometimes means learning which backend it rode in on. For the core LLM path, it’s dependable.</p><p>Use it when: existing OpenAI-API code needs to go local without a rewrite.</p><p><a href="https://github.com/mudler/LocalAI">https://github.com/mudler/LocalAI</a></p><h3><strong>5. vllm: when one user becomes a thousand (93k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*RH8TcqePnqvl5tOvSWCpJw.png" /><figcaption><em>Paged attention and continuous batching: the production answer.</em></figcaption></figure><p>Everything so far serves a person or a team. Serving a company is a different sport.</p><p>vllm is the high-throughput, memory-efficient serving engine built around paged attention and continuous batching. When your internal tool graduates from three users to the whole org, this is how one GPU serves them all without falling over. It’s the production answer, and the industry has largely voted the same way.</p><p>The cost is operational seriousness. It wants real GPUs, real capacity planning, and someone who reads release notes. Deploying vllm for five users is bringing a race car to a school run. Wait until the queue is real.</p><p>Use it when: customers or the whole company are on the other end, and latency is a feature.</p><p><a href="https://github.com/vllm-project/vllm">https://github.com/vllm-project/vllm</a></p><h3><strong>6. exo: the office becomes a datacenter (47k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*2cf-TiPKzkqV8sXpuUjMfw.png" /><figcaption><em>Frontier models pooled across the devices you already own.</em></figcaption></figure><p>And then there’s the one that’s pure frontier spirit.</p><p>exo runs frontier-scale models locally by pooling the everyday devices you already own — laptops, desktops, phones — into one cluster, so no single machine has to fit the model. The first time a model too big for any one of your machines answers from all of them at once, you grin. There’s no other reaction.</p><p>It’s also the most experimental repo here, and it behaves like it: network hiccups matter, heterogeneous devices surprise you, and I wouldn’t put it in front of customers. That’s not what it’s for. It’s for finding out where the ceiling actually is.</p><p>Use it when: curiosity budget, not production budget.</p><p><a href="https://github.com/exo-explore/exo">https://github.com/exo-explore/exo</a></p><p>· · ·</p><p><strong>What I’d actually do</strong></p><p>jan to see it. open-webui plus the engine when the team wants in. LocalAI when existing code needs to follow. vllm when the queue gets real. exo on the weekend, for joy.</p><p>We still use APIs for plenty. But the week legal asks where the prompts go, or the month the invoice doubles again, the answer is no longer a shrug. It’s a stack, and it’s free.</p><p>What would it take for your team to run its first model in-house?</p><p>· · ·</p><p><strong>Want more repos like these?</strong></p><p>I publish breakdowns like this one all the time: the best, fastest-trending repositories on GitHub, what they’re actually good for, and where they fall short. If that’s your kind of reading, two places to get more.</p><p><strong>The Best GitHub Repos Newsletter</strong>, free in your inbox: <a href="https://best-github-repos.beehiiv.com/subscribe">https://best-github-repos.beehiiv.com/subscribe</a></p><p>And our community on Reddit, <strong>r/BestGitHubRepos</strong>: more than 100,000 members and climbing fast, the fastest-growing subreddit of the year. The comments regularly surface great repos before they trend.</p><p><em>All six repositories are free and open source; star counts were read from GitHub on October 10, 2026.</em></p><p><em>Screenshots from the repositories’ GitHub pages.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=811090282747" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Free GitHub Repos That Take You From “I Use ChatGPT” to “I Know How It Works”]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/6-free-github-repos-that-take-you-from-i-use-chatgpt-to-i-know-how-it-works-65cfd46cac52?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/65cfd46cac52</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[llm-agent]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 09:41:12 GMT</pubDate>
            <atom:updated>2026-10-14T09:41:12.226Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Crossing the line between using language models and understanding them doesn’t need a degree. It needs six repos in the right order, and the stubbornness to finish the fourth one.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J2lT2TaVCXPcm8Cnx8MjCQ.png" /><figcaption><em>The whole curriculum, from your first prompt to your first loss curve.</em></figcaption></figure><p>There’s a moment in every AI conversation where the room splits in two.</p><p>Someone asks why the model did something strange, and half the room offers vibes while the other half starts talking about context windows and sampling. The second half isn’t smarter. They’ve just crossed a line the first half hasn’t: from using language models to understanding them.</p><p>I crossed it embarrassingly late, as a marketer running a data company, and it changed what I could build and what I could sell. The entire path is free on GitHub. Here it is in climbing order, with an honest word about each handhold.</p><h3><strong>1. generative-ai-for-beginners: the on-ramp (121k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*w4zN6V1Fpw0pEQhpB7lvDQ.png" /><figcaption><em>Twenty-one lessons that assume nothing. Everyone starts somewhere.</em></figcaption></figure><p>Microsoft’s 21-lesson course assumes nothing: what a token is, how prompts work, how to call a model from code, how to ship a first application without embarrassing yourself. Every lesson pairs a chapter with video and runnable code.</p><p>Its strength is also its ceiling. It’s genuinely for beginners, and it stays there; a developer six months into the field will skim most of it. But if you’re starting from “I’ve used ChatGPT and that’s all”, there is no gentler on-ramp, and the responsible-AI lessons are ones even experienced builders skip at their own cost.</p><p>Use it when: you’re at zero, or you’re bringing a non-technical teammate to one.</p><p><a href="https://github.com/microsoft/generative-ai-for-beginners">https://github.com/microsoft/generative-ai-for-beginners</a></p><h3><strong>2. Prompt-Engineering-Guide: the highest-leverage hour (78k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*S-rprGQt0nldU7uBXNZLSQ.png" /><figcaption><em>The reference book for the one skill that pays off immediately.</em></figcaption></figure><p>Here’s an unpopular opinion: prompting is still the highest-leverage skill per hour invested in this entire field.</p><p>DAIR.AI’s guide is its reference book: few-shot, chain-of-thought, self-consistency, and crucially the papers behind why these work. It’s both a practical manual and a map of the literature, which is rarer than it should be.</p><p>The honest tradeoff: parts of it age fast. Techniques invented for weaker models matter less with every release, and the repo carries some of that history. Read it for the durable patterns and the research instinct, not as a recipe book frozen in time.</p><p>Use it when: today. The payback starts with your next prompt.</p><p><a href="https://github.com/dair-ai/Prompt-Engineering-Guide">https://github.com/dair-ai/Prompt-Engineering-Guide</a></p><h3><strong>3. openai-cookbook: steal the patterns (76k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*2gfAS_mC-zFC0IfSUmhC7A.png" /><figcaption><em>Working code for every pattern you’ll end up needing anyway.</em></figcaption></figure><p>Between understanding prompts and training models sits a practical middle: building things that work. This is the cookbook for that.</p><p>Working examples for RAG, function calling, embeddings, evals, structured outputs. Every one is a pattern you can lift into your own stack, and most translate almost verbatim to other providers’ APIs. I’ve stolen from it shamelessly and so has everyone I respect.</p><p>Obvious caveat in the name: it’s OpenAI’s kitchen. The patterns generalize, the specific API calls don’t always, and the repo won’t tell you when a competitor does something better. Read it for shapes, not vendor choices.</p><p>Use it when: you’re about to write an LLM feature from scratch. Someone already wrote its skeleton here.</p><p><a href="https://github.com/openai/openai-cookbook">https://github.com/openai/openai-cookbook</a></p><h3><strong>4. nanoGPT: the line itself (63k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*XmnxPBds5UE78R22Kb8xZQ.png" /><figcaption><em>Small enough to read in an evening. The night the magic becomes machinery.</em></figcaption></figure><p>This is the repo where the line gets crossed.</p><p>Andrej Karpathy’s minimal GPT training code: small enough to read in an evening, complete enough to reproduce GPT-2 on a cluster, simple enough to train a character-level Shakespeare model on your laptop tonight. That last part is not a figure of speech. Tonight.</p><p>The night I watched my own loss curve go down was the night language models stopped being magic and became machinery. Nothing in the previous three repos does what that one chart does.</p><p>What it demands in exchange: real Python and a tolerance for being confused for an hour or two. It’s minimal by philosophy, so there’s no padding to catch you. The confusion is the course.</p><p>Use it when: the week your team decides to go deeper than the API. This is where borrowed understanding becomes yours.</p><p><a href="https://github.com/karpathy/nanoGPT">https://github.com/karpathy/nanoGPT</a></p><h3><strong>5. llm.c: see what the frameworks hide (31k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*kZ6iWyqNa7lAszMcKUCjuA.png" /><figcaption><em>Training in raw C and CUDA, every gradient written out by hand.</em></figcaption></figure><p>After nanoGPT, one question remains: what does PyTorch actually do when you call loss.backward()?</p><p>llm.c answers it the hard way: LLM training in raw C and CUDA, no framework, every matrix multiply and every gradient written where you can read it. Also Karpathy, and arguably the best systems-level teaching artifact in the field.</p><p>Let me be clear about the con: you will probably never run this, and you don’t need to. It’s the repo you read, slowly, to see the memory layout and the bookkeeping that frameworks politely hide. For most careers it’s optional. For understanding, it’s the final door.</p><p>Use it when: you’ve trained with nanoGPT and want to lose the last of your superstitions.</p><p><a href="https://github.com/karpathy/llm.c">https://github.com/karpathy/llm.c</a></p><h3><strong>6. Hands-On-Large-Language-Models: the book track (29k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*-kmZbDzBKI761IGs53D2PA.png" /><figcaption><em>The O’Reilly book’s code, from the illustrator who taught half the industry.</em></figcaption></figure><p>One honest admission: not everyone learns from repos and confusion. Some people need a book with figures that actually explain things.</p><p>This is the official code for the O’Reilly book by Jay Alammar and Maarten Grootendorst — the same Jay Alammar whose illustrated transformer posts taught half the industry, mine included. Tokenization, embeddings, semantic search, fine-tuning, all as runnable notebooks that mirror the chapters.</p><p>The tradeoff is obvious: the notebooks are companions, and without the book (which costs money) you’re reading someone’s lab without the lecture. Pair them or pick the free path above. Both roads reach the same place.</p><p>Use it when: you want one structured, visual, finishable track instead of six tabs.</p><p><a href="https://github.com/HandsOnLLM/Hands-On-Large-Language-Models">https://github.com/HandsOnLLM/Hands-On-Large-Language-Models</a></p><p>· · ·</p><p><strong>The climb, honestly</strong></p><p>Start with 1. Steal from 3 immediately. The real milestone is 4: one evening, one laptop, one loss curve going down. Everything after that is refinement.</p><p>The room will keep splitting into people with vibes and people with theories. The difference was never talent. It was one stubborn evening.</p><p>Have you had yours yet?</p><p>· · ·</p><p><strong>Want more repos like these?</strong></p><p>I publish breakdowns like this one all the time: the best, fastest-trending repositories on GitHub, what they’re actually good for, and where they fall short. If that’s your kind of reading, two places to get more.</p><p><strong>The Best GitHub Repos Newsletter</strong>, free in your inbox: <a href="https://best-github-repos.beehiiv.com/subscribe">https://best-github-repos.beehiiv.com/subscribe</a></p><p>And our community on Reddit, <strong>r/BestGitHubRepos</strong>: more than 100,000 members and climbing fast, the fastest-growing subreddit of the year. The comments regularly surface great repos before they trend.</p><p><em>All six repositories are free and open source; star counts were read from GitHub on October 9, 2026.</em></p><p><em>Screenshots from the repositories’ GitHub pages.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65cfd46cac52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Free GitHub Repos That Teach You How Databases Actually Work]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/6-free-github-repos-that-teach-you-how-databases-actually-work-a43ee9b4ade0?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/a43ee9b4ade0</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 09:37:46 GMT</pubDate>
            <atom:updated>2026-10-14T09:37:46.865Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A production incident taught me I had used databases for years without understanding them. These six repos fixed that, from one-picture explainers to building my own.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yHsGIKU3KkMdC0pkABQVSA.png" /><figcaption><em>What actually happens between INSERT and the row existing on disk.</em></figcaption></figure><p>For years I used databases the way I use elevators. Press button, arrive at floor, no idea what the cables are doing.</p><p>Then one night a query that had run in 40 milliseconds started taking 11 seconds, in front of customers, and I realized I could not even form a theory about why. The query planner had changed its mind about an index. I didn’t know query planners had minds.</p><p>That night sent me down a path I’d recommend to any engineer: actually learning what the database does. Not to become a DBA. To stop being a passenger. These six repos are that path, from the gentlest pictures to building one with your own hands.</p><h3><strong>1. system-design-101: start with the pictures (90k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*QvEDnsJowySfgj5ejuAkIw.png" /><figcaption><em>One diagram per hard concept. The gentlest on-ramp there is.</em></figcaption></figure><p>Start here, even if it feels too easy.</p><p>ByteByteGo answers each hard question with a single clear diagram: how a SQL statement executes inside the engine, how an index finds your row, how a transaction commits, how caching layers stack. You scroll it like a feed, and what sticks surprises you.</p><p>The limitation is built into the format. One picture cannot carry the edge cases, and real engineering lives in the edge cases. Treat it as vocabulary, not understanding. You’re learning the names of the things you’ll study properly in the next two repos.</p><p>Use it when: you have ten spare minutes and want them to compound.</p><p><a href="https://github.com/ByteByteGoHq/system-design-101">https://github.com/ByteByteGoHq/system-design-101</a></p><h3><strong>2. system-design-primer: fill in the words (373k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*WVuNwYyPe5voHmxNU7G4kQ.png" /><figcaption><em>The repo a generation studied for interviews and kept open at work.</em></figcaption></figure><p>This is the repo a whole generation of backend engineers studied before interviews, then quietly kept open afterward because the content holds up at work. Caching strategies, sharding, replication, consistency models, CAP, all with diagrams and linked deep dives.</p><p>Here’s my test for whether you need it: can you draw “eventual consistency” on a whiteboard, or do you just nod when someone says it? I was a nodder. This repo is where I stopped.</p><p>Two honest caveats. It’s interview-shaped, so it optimizes for breadth over depth. And parts haven’t aged: the trade-off discussions are timeless, some linked articles are not. Read it for the concepts, not the specific tech picks.</p><p>Use it when: the diagrams from repo 1 made you curious what the arrows actually mean.</p><p><a href="https://github.com/donnemartin/system-design-primer">https://github.com/donnemartin/system-design-primer</a></p><h3><strong>3. pgvector: the detour that saves you a system (23k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*VJA_zrNrRzSxizeMe46p4g.png" /><figcaption><em>Vector search inside the Postgres you already run.</em></figcaption></figure><p>A practical detour, because this one has probably already cost you money.</p><p>Every AI feature needs embeddings, and the reflex of 2024–2025 was to buy a separate vector database for them. pgvector is the counter-argument: one extension adds vector columns, distance operators and nearest-neighbor indexing to the Postgres you already run, with the transactions, backups and access control you already trust.</p><p>Where it wins: one less system to operate, your vectors live next to your relational data, and joins between them are just SQL. Where it loses: at very large scale or very high query rates, the dedicated engines still pull ahead, and tuning HNSW indexes is its own small education.</p><p>Use it when: you’re about to add a vector database to your stack. Check first whether you already have one.</p><p><a href="https://github.com/pgvector/pgvector">https://github.com/pgvector/pgvector</a></p><h3><strong>4. tigerbeetle: read how the pros think (17k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*VZA3kwKYkQx-kPTqlLkOHA.png" /><figcaption><em>A database that assumes disks lie. The design docs are the point.</em></figcaption></figure><p>You will probably never run TigerBeetle. Read it anyway.</p><p>It’s a financial transactions database built from first principles for the workload where losing one transaction is unacceptable: deterministic execution, strict serializability, storage design that assumes disks lie. The design documentation is some of the best systems writing on GitHub, and it quietly resets your standards for what a database owes you.</p><p>The con is the same as the pitch: it’s radically specialized. If your problem isn’t double-entry accounting at scale, this is literature, not tooling. But the literature changed how I read every other database’s promises.</p><p>Use it when: you want to see what “mission-critical” looks like when someone means it.</p><p><a href="https://github.com/tigerbeetle/tigerbeetle">https://github.com/tigerbeetle/tigerbeetle</a></p><h3><strong>5. awesome-database-learning: the deep end’s index (11k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*JLv7_SyjOMBuAYU9_OhoqA.png" /><figcaption><em>Papers, courses and talks on internals, mapped by the PingCAP team.</em></figcaption></figure><p>By now a dangerous thing has happened: you’re curious. This repo is where the curiosity goes.</p><p>PingCAP maintains a curated map of papers, courses, books and talks on database internals: storage engines, query optimizers, transaction processing, distributed consensus. It’s the syllabus for the education nobody assigns you.</p><p>Be honest with yourself about the format, though. It’s links, not lessons. A reading list rewards the disciplined and quietly shames the rest of us. Pick one paper, finish it, then come back. Collecting tabs is not studying.</p><p>Use it when: a specific question (“how do optimizers choose joins?”) needs a real answer, not a diagram.</p><p><a href="https://github.com/pingcap/awesome-database-learning">https://github.com/pingcap/awesome-database-learning</a></p><h3><strong>6. build-your-own-x: now build one (552k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*QxwpHB3L2hRcv2IU917sgQ.png" /><figcaption><em>The final exam: write a tiny database with your own hands.</em></figcaption></figure><p>Everything before this was preparation. This is the exam.</p><p>build-your-own-x is one of the most-starred repos on GitHub: step-by-step tutorials for building your own database, Redis, Git, Docker, shell, web server, from scratch, in the language of your choice. The database tutorials are the point here. A toy engine that only does sequential scans will teach you more than a year of using Postgres politely.</p><p>The tradeoff is time. A weekend minimum, honestly more, and tutorial quality varies by author since the repo is an index, not a school. But this is the only repo on the list that converts knowledge into intuition. After you’ve written a write-ahead log, you never again wonder what WAL means in a Postgres config.</p><p>Use it when: you’re ready to stop reading about databases and start arguing with one.</p><p><a href="https://github.com/codecrafters-io/build-your-own-x">https://github.com/codecrafters-io/build-your-own-x</a></p><p>· · ·</p><p><strong>The payoff is quiet</strong></p><p>Pictures, then vocabulary, then one practical win, then taste, then depth, then your own hands. That’s the whole path.</p><p>The payoff isn’t the interview, though repos 1, 2 and 6 contain every backend interview you’ll ever take. The payoff is quieter: the next production incident where the database does something strange, and instead of being a passenger, you have a theory in the first five minutes.</p><p>What’s the database concept you’ve nodded along to the longest without really knowing it?</p><p>· · ·</p><p><strong>Want more repos like these?</strong></p><p>I publish breakdowns like this one all the time: the best, fastest-trending repositories on GitHub, what they’re actually good for, and where they fall short. If that’s your kind of reading, two places to get more.</p><p><strong>The Best GitHub Repos Newsletter</strong>, free in your inbox: <a href="https://best-github-repos.beehiiv.com/subscribe">https://best-github-repos.beehiiv.com/subscribe</a></p><p>And our community on Reddit, <strong>r/BestGitHubRepos</strong>: more than 100,000 members and climbing fast, the fastest-growing subreddit of the year. The comments regularly surface great repos before they trend.</p><p><em>All six repositories are free and open source; star counts were read from GitHub on October 8, 2026.</em></p><p><em>Screenshots from the repositories’ GitHub pages.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a43ee9b4ade0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Free GitHub Repos That Take You From Zero to Production AI Agents]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/6-free-github-repos-that-take-you-from-zero-to-production-ai-agents-44e005b29fe6?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/44e005b29fe6</guid>
            <category><![CDATA[ai-agents-in-action]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 09:34:12 GMT</pubDate>
            <atom:updated>2026-10-14T09:34:12.163Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I watched our first agent demo impress everyone and then die in production. These six repos are the path I wish someone had handed me, in the order that actually works.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aJ_k47p3N3MVfAKKhoL2jA.png" /><figcaption><em>Six stops between a cool demo and an agent you can bill for.</em></figcaption></figure><p>Our first AI agent took two days to build and two months to make trustworthy.</p><p>The demo was easy. It answered questions, called a tool, looked magical in a meeting. Then real users arrived, and everything that worked in the demo started failing in ways no tutorial had warned me about. Wrong tool calls. Confident nonsense. A bill that grew faster than usage.</p><p>Here’s what I know now: the complete path from zero to production agents is already free on GitHub. The problem is nobody tells you the order. People start with theory when they should start with working apps, and they ship to production without ever hearing the word “guardrails”.</p><p>This is the order that works. Six repos, each one earning its place in the story.</p><h3><strong>1. awesome-llm-apps: steal a working app first (140k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*55nK2HTdmPCeC_0OpBDPXw.png" /><figcaption><em>Over 100 working agents and RAG apps, each one small enough to read in a sitting.</em></figcaption></figure><p>Forget theory on day one. Clone something that runs.</p><p>This repo collects more than 100 open-source agents, agent teams, voice agents and RAG apps, built across OpenAI, Anthropic, Gemini and open-source models. Each one is small enough to read whole. Pick the one closest to what you want to build, run it, break it, rebuild it. That loop teaches faster than any course.</p><p>The honest tradeoff: quality varies. Some apps are polished, some are weekend experiments, and a few lag behind the latest model APIs. Treat it as a bazaar, not a textbook. The license is Apache-2.0, so what you build on top is yours to ship and sell.</p><p>Use it when: you learn by doing, or you need a working skeleton for a client demo by Friday.</p><p><a href="https://github.com/Shubhamsaboo/awesome-llm-apps">https://github.com/Shubhamsaboo/awesome-llm-apps</a></p><h3><strong>2. awesome-mcp-servers: give the agent hands (95k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*jOCxWkZk4DMECVHacz5bjA.png" /><figcaption><em>The tool catalog: every system your agent could touch, one list.</em></figcaption></figure><p>At some point your agent has to stop talking and start doing. That transition has a name now: MCP, the Model Context Protocol, the standard way agents touch databases, browsers, file systems and SaaS tools.</p><p>This repo is the master list of MCP servers that exist today. When someone asks “can your agent update our CRM?”, my answer starts with a search through this list. Nine times out of ten, someone already built the connector.</p><p>The catch is the flip side of the same coin: it’s a directory, not a review site. Stars don’t equal security, and an MCP server you hand your credentials to deserves a code read first. Budget an hour of skepticism per server you adopt.</p><p>Use it when: your agent needs to act on real systems and you don’t want to write integrations from scratch.</p><p><a href="https://github.com/punkpeye/awesome-mcp-servers">https://github.com/punkpeye/awesome-mcp-servers</a></p><h3><strong>3. llm-course: now earn the fundamentals (83k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*uyT-LxJ_6uc9Fibrhgy17w.png" /><figcaption><em>The roadmap half the industry quietly studied, with a notebook at every stop.</em></figcaption></figure><p>Here’s where most people start. It’s the wrong first stop, and the right third one.</p><p>Maxime Labonne’s course is the standard self-study roadmap into LLMs: fundamentals, fine-tuning, deployment, almost every stop with a Colab notebook you can run. After two weeks of cloning apps and wiring tools, the theory finally has something to stick to. You’ve seen agents hallucinate; now you learn why.</p><p>Fair warning: it’s a roadmap, not a hand-holding course. There’s no instructor and no forum waiting for your questions. Discipline is on you. And if you skipped straight here from zero, it will feel abstract — which is exactly why it’s stop three and not stop one.</p><p>Use it when: your demos work but you can’t explain why they fail.</p><p><a href="https://github.com/mlabonne/llm-course">https://github.com/mlabonne/llm-course</a></p><h3><strong>4. ai-agents-for-beginners: the structured version (76k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*SGUWceYa97Njrp0jRXCuRA.png" /><figcaption><em>Eighteen lessons from “what is an agent” to running them at scale.</em></figcaption></figure><p>If the previous repo is a map, this one is a guided tour of the same territory, agents specifically.</p><p>Microsoft’s 18-lesson course pairs every chapter with a short video and runnable Python. It covers the design patterns (tool use, planning, multi-agent, metacognition), agentic RAG, memory, the protocols (MCP, A2A, NLWeb), computer-use agents, deployment. Translated into 50+ languages, which matters if English isn’t your team’s first language.</p><p>The lesson I’d read first is the one on context engineering. Most “my agent is dumb” complaints I hear are actually context problems, and almost nobody studies that on purpose.</p><p>The tradeoff: it’s a beginners’ course and it stays one. The samples lean on Microsoft’s stack, and if you’ve been building for six months you’ll skim half of it. Take the lessons you’re missing and move on.</p><p>Use it when: you want structure instead of a map, or you’re onboarding a teammate into agents from zero.</p><p><a href="https://github.com/microsoft/ai-agents-for-beginners">https://github.com/microsoft/ai-agents-for-beginners</a></p><h3><strong>5. RAG_Techniques: past the demo wall (29k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*tVIQ7I1v-huewJpuzTDBXg.png" /><figcaption><em>Where retrieval stops being a demo trick and starts surviving real documents.</em></figcaption></figure><p>Every agent that answers from your data hits the same wall. Demo RAG takes an afternoon. RAG that survives real documents and real users takes technique, and the techniques have names.</p><p>This repo collects them as runnable notebooks: query transformations, reranking, hierarchical indices, self-RAG, dozens more. When our retrieval quality plateaued, the fix was in here, with working code, not in another blog post repeating the word “embeddings”.</p><p>Honest caveat: it’s a reference, not a pipeline. The notebooks show each technique in isolation; stitching five of them into one production system is still your job. And not every technique earns its complexity — measure before you adopt.</p><p>Use it when: users start saying “it answered from the wrong document”.</p><p><a href="https://github.com/NirDiamant/RAG_Techniques">https://github.com/NirDiamant/RAG_Techniques</a></p><h3><strong>6. agents-towards-production: the unglamorous part (21k+ stars)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*NtNKXI2CTV9vLIIxIAv7hQ.png" /><figcaption><em>Evals, guardrails, cost control: the chapters nobody screenshots.</em></figcaption></figure><p>Nobody posts screenshots of their eval dashboard. That’s exactly why this repo matters.</p><p>Same author as RAG_Techniques, same principle: every topic ships with code you can run. But the topics here are the ones that separate a demo from a product: evaluations, guardrails, monitoring, deployment, cost control, security. The two months I spent hardening our first agent were two months inside exactly this material, except I had to find it scattered across twenty sources.</p><p>The con is simply that it’s the youngest repo on this list and the field moves fast; a tutorial written this spring can feel dated by autumn. The concepts hold even when a library version doesn’t.</p><p>Use it when: someone says the words “can we put this in front of customers?”</p><p><a href="https://github.com/NirDiamant/agents-towards-production">https://github.com/NirDiamant/agents-towards-production</a></p><p>· · ·</p><p><strong>The order is the lesson</strong></p><p>Apps first, so you know what good looks like. Tools second, so your agent can act. Fundamentals third, so you understand why things break. Production last, because that’s where agents go to die quietly.</p><p>Two days to build, two months to trust. These six repos don’t change that ratio as much as I’d like. They just make sure the two months are spent learning instead of searching.</p><p>Which stop are you on right now?</p><p>· · ·</p><p><strong>Want more repos like these?</strong></p><p>I publish breakdowns like this one all the time: the best, fastest-trending repositories on GitHub, what they’re actually good for, and where they fall short. If that’s your kind of reading, two places to get more.</p><p><strong>The Best GitHub Repos Newsletter</strong>, free in your inbox: <a href="https://best-github-repos.beehiiv.com/subscribe">https://best-github-repos.beehiiv.com/subscribe</a></p><p>And our community on Reddit, <strong>r/BestGitHubRepos</strong>: more than 100,000 members and climbing fast, the fastest-growing subreddit of the year. The comments regularly surface great repos before they trend.</p><p><em>All six repositories are free and open source; star counts were read from GitHub on October 7, 2026.</em></p><p><em>Screenshots from the repositories’ GitHub pages.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44e005b29fe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Cheapest Customer Is the One You Keep]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/the-cheapest-customer-is-the-one-you-keep-b8753d84e6e3?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8753d84e6e3</guid>
            <category><![CDATA[b2b-marketing]]></category>
            <category><![CDATA[b2b-lead-generation]]></category>
            <category><![CDATA[b2b-marketing-strategy]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 11:07:34 GMT</pubDate>
            <atom:updated>2026-10-11T11:07:34.998Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Episode five of The Signal Tribe’s second season: winter closes the valley, Grum marches east for new friends, and Vela answers with a pot of embers.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*92aHlM8TvXi-6reP8JiqJQ.jpeg" /><figcaption><em>Four fires in a chain across the snow. The tended map is the whole strategy.</em></figcaption></figure><p>Every SaaS dashboard I have ever opened puts new signups at the top and churn somewhere below the fold. Episode five of season two is about that layout choice, forty thousand years early.</p><h3><strong>Winter closes the valley</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9_0CCFI1ZEPXCHTq9_zR4w.jpeg" /><figcaption><em>No new camps to find. Grum points east anyway.</em></figcaption></figure><p>Snow erases every track. There are no new camps to walk to, no fresh prints to read, nothing to prospect. Grum’s answer is the one every pipeline review reaches for when the top of the funnel thins: go louder, go farther. “Then we march east! The east is full of camps we have never met!”</p><h3><strong>The arithmetic of a new fire</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hgSHUYcVFprzTfNtokHceA.jpeg" /><figcaption><em>Ten sticks. One dying spark. The east was full of snow.</em></figcaption></figure><p><strong><em>Ten sticks to start a new fire in winter. One stick to keep an old one burning.</em></strong></p><p>Grum finds out what acquisition costs in a down season: waist-deep snow, wet wood, a spark that dies while he watches. The episode does not argue with him. It just counts the sticks.</p><p>Marketers have run this count for decades, and it lands in the same place every time. Winning a new customer costs a multiple of keeping one you already have. The multiple grows in winter.</p><h3><strong>Vela’s answer weighs two pounds</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i-zG29MTrTE775mERYrPNA.jpeg" /><figcaption><em>She says nothing. She hands Orr a pot of embers.</em></figcaption></figure><p>Vela has barely spoken all season, and she does not start now. She fills a clay pot with embers from the home fire and hangs it from Orr’s shoulder. Orr reads it instantly: “The short paths. Every fire we ever lit.”</p><p>An ember is not a gift. It is a piece of your own fire, carried to someone who already trusts you, so their fire never goes out. That is the difference between a retention program and a discount.</p><h3><strong>Walking the map you already own</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5giMzQRJCvhVKkhZ8g8O3g.jpeg" /><figcaption><em>Short woven lines to known camps, checked. One long dotted line east, crossed out.</em></figcaption></figure><p>The tribe walks its own map. The marsh camp. The feather spring. One ember, one mended trap, one shared meal at every fire they ever lit. No pitch, no pile, nothing to announce. Just proof, at regular intervals, that the relationship is alive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0q21m3yb8mKfi2ODvS3cPA.jpeg" /><figcaption><em>Grum comes home to hot stew. Retention works on rivals-turned-friends too.</em></figcaption></figure><p>Grum staggers home with empty hands and frozen boots, and the marsh cook is waiting at his fire with stew. The episode gives its loudest character the quietest proof: being kept warm is what being a kept customer feels like.</p><h3><strong>What this looks like on a laptop</strong></h3><p><strong>1. Count your sticks honestly.</strong> Put your real acquisition cost next to your real retention cost. Most teams have never written the two numbers on the same page.</p><p><strong>2. Schedule the embers.</strong> A retention touch that depends on someone remembering is not a program. The tribe walks the short paths at regular intervals, not when a renewal is sixty days out.</p><p><strong>3. Carry an ember, not a pitch.</strong> The visit brings something useful with no ask attached: a fixed trap, a shared meal, a piece of your own fire. The moment the visit carries a quota, it stops counting.</p><p><strong>4. Keep one fire for a future friend.</strong> The stew that waited for Grum was not owed to him. Warmth extended before any deal exists is the cheapest pipeline you will ever build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6YZTFjqUt2gbdZKGhMJ7vw.jpeg" /><figcaption><em>Season two, lesson five, carved.</em></figcaption></figure><p>Next quarter, before anyone proposes marching east, try reading the carving first: feed the fires you lit.</p><p>Which customer of yours got an ember from you this month, and which one only ever hears from you at renewal?</p><p><em>The Signal Tribe is a daily animated series from the team at CUFinder. This </em><a href="http://cufinder.io/buying-signals?utm_source=medium&amp;utm_medium=organic&amp;utm_campaign=signaltribe&amp;utm_content=s2e05"><em>episode</em></a><em>:</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7bzFh2_VbZ4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2F7bzFh2_VbZ4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7bzFh2_VbZ4%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/89411431ff7819125f7024d92ddde34e/href">https://medium.com/media/89411431ff7819125f7024d92ddde34e/href</a></iframe><p><em>All artwork from the episode. Characters and valley by our studio.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8753d84e6e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When a Rival Undercuts You, Do Not Blink]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/when-a-rival-undercuts-you-do-not-blink-25e56ef34797?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/25e56ef34797</guid>
            <category><![CDATA[b2b-lead-generation]]></category>
            <category><![CDATA[buying-signals]]></category>
            <category><![CDATA[b2b-marketing]]></category>
            <category><![CDATA[lead-generation]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 11:04:01 GMT</pubDate>
            <atom:updated>2026-10-11T11:04:01.872Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Episode four of The Signal Tribe’s second season: a rival tribe arrives with gift piles twice as tall, and Grum wants a bidding war.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YvSnixzgW4gEc_A49hYcPg.jpeg" /><figcaption><em>The chief holds up one small honeycomb against a mountain of gifts. That is the whole argument.</em></figcaption></figure><p>The scariest email I get as a founder is not a churn notice. It is a customer forwarding a rival’s offer with the subject line “thoughts?”. Someone is promising them more, for less, and now there is a number on the table that I am supposed to beat.</p><p>Episode four of season two is about that email, forty thousand years early.</p><h3><strong>The pile that is twice as tall</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fXEw3qGNJXSjRGydWoBK7Q.jpeg" /><figcaption><em>Friendly banners. Enormous piles. Orr stops mid-step.</em></figcaption></figure><p>The eastern tribe finds the feather tribe’s spring, the one Vela’s people spent a whole season earning. They are not hostile. They are generous, which is worse. Their gift piles are twice the size of anything the valley has ever laid on the flat stone.</p><h3><strong>Grum calls for a bidding war</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YaU96_ND07BEbbeSRDw-nQ.jpeg" /><figcaption><em>The gift mountain grows. The storage racks behind it empty.</em></figcaption></figure><p>Grum’s answer is the answer every sales floor reaches for first: “Double our gifts! Triple them! Bury their pile in ours!” And the episode gives the rebuttal in one frame: behind the growing gift mountain, the tribe’s own storage racks emptying, with winter clouds coming over the ridge.</p><p><strong><em>A gift war has one rule. Whoever wins the pile loses the winter.</em></strong></p><p>That is a margin lesson carved in meat and firewood. Match a discount with a deeper discount and you can win the deal while losing the quarter, and the next quarter, because the new price is now the price.</p><h3><strong>The question nobody panicking thinks to ask</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JK0uO4fF7xTh2chRMwREHw.jpeg" /><figcaption><em>Their pile is bigger. Why are you still here?</em></figcaption></figure><p>Orr does the thing I wish every account manager did on undercut day: he walks to the customer and asks the honest question. “Their pile is bigger. Why are you still here?”</p><p>The feather chief’s answer is the heart of the episode. The easterners bring the same pile to every camp. You brought honeycomb the summer our bees died. The big pile is generic by definition, because generosity at scale has to be. The small bundle was specific, and specific is what trust remembers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*csREBSTDoOvzKt1ozTAHaQ.jpeg" /><figcaption><em>The same pile to every camp, or many small right things to one camp.</em></figcaption></figure><h3><strong>Deepen, do not discount</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ECHV408BMuv8ik-hrLZ4Kw.jpeg" /><figcaption><em>Winter fat before the first snow. Fish traps mended while they eat.</em></figcaption></figure><p>The tribe’s response to the rival is the quietest competitive move of the season. No bigger pile. They bring winter fat before the first snow, because they know this camp’s winters. They mend the fish traps while they eat, because they noticed the traps. Service in the places a pile cannot reach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1F_oTE4SsbUedjU-ezyi4Q.jpeg" /><figcaption><em>The eastern pile, respectfully covered. The old fire, warm.</em></figcaption></figure><p>The episode ends with the eastern pile neatly covered by a hide, respected and unopened, and one eastern figure walking home along the ridge, thoughtful rather than angry. The valley does not humiliate its rival. Season arcs being what they are, I suspect we have not seen the last of the zigzag banners.</p><h3><strong>What the founder notebook says</strong></h3><p>The lesson carved on the tablet is <strong>the oldest fire beats the biggest pile.</strong> Into the undercut playbook:</p><p><strong>1. Ask the chief question first.</strong> Before matching any offer, ask the customer why they are still with you. Their answer is your actual differentiation, in their words. Defend that, not the price.</p><p><strong>2. Count the full cost of the gift war.</strong> The discount you give to keep one account becomes the benchmark for every renewal that hears about it. Whoever wins the pile loses the winter.</p><p><strong>3. Outspecific them, not outspend them.</strong> A rival at scale must be generic. Your winter fat is whatever you know about this customer that they cannot: the integration nobody else built, the quirk of their workflow, the summer their bees died.</p><p><strong>4. Leave the rival their dignity.</strong> Markets are long. The eastern tribe walks home unbeaten and unburned, and that is on purpose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h_Yhe09q91H0Yt_futQynw.jpeg" /><figcaption><em>Season two, lesson four, carved.</em></figcaption></figure><p>Next time a forwarded offer lands with “thoughts?”, try answering with the chief’s question instead of a counter-discount.</p><p>What is the one specific thing you do for your best customer that no rival at scale could copy?</p><p><em>The Signal Tribe is a daily animated series from the team at CUFinder. This </em><a href="http://cufinder.io/buying-signals?utm_source=medium&amp;utm_medium=organic&amp;utm_campaign=signaltribe&amp;utm_content=s2e04-article"><em>episode</em></a><em> (82 seconds):</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Faqph-mG4AqY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2Faqph-mG4AqY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Faqph-mG4AqY%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/82146a1e58c86d31e276bd2c41a51a5e/href">https://medium.com/media/82146a1e58c86d31e276bd2c41a51a5e/href</a></iframe><p><em>All artwork from the episode. Characters and valley by our studio.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25e56ef34797" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Deal Is One Resignation Away]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/your-deal-is-one-resignation-away-c91c29d9d987?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/c91c29d9d987</guid>
            <category><![CDATA[b2b-marketing-strategy]]></category>
            <category><![CDATA[buying-siglans]]></category>
            <category><![CDATA[b2b-lead-generation]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 08:50:26 GMT</pubDate>
            <atom:updated>2026-10-11T08:50:26.372Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Episode three of The Signal Tribe’s second season: Orr carries the tribe’s finest goods to a friendly camp and comes home with all of it.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kJP1NO1oDwmOgsk79w1V8Q.jpeg" /><figcaption><em>Vela says nothing. She snaps a thread, and hands him the rope.</em></figcaption></figure><p>The deal was ours. Champion loved us, pricing approved, start date on the calendar. Then my one contact took three weeks of leave, and when she came back the budget had a new owner, and the new owner had never heard of us.</p><p>Episode three of season two is about that deal, and about every deal that lives or dies on one person’s calendar.</p><h3><strong>The visit that went nowhere</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IaPUtiWNFB18wDZCztjXJg.jpeg" /><figcaption><em>A full carrying frame, a friendly camp, and nobody who knows him.</em></figcaption></figure><p>Orr goes back to the marsh valley carrying the tribe’s finest goods. The visit should be easy: the tribes are friends now, the first trade went beautifully. Except Orr knows exactly one person at that camp, the lattice elder, and she is away in the reed beds.</p><p>What follows is the politest failure in the series so far. Nobody is hostile. People wave. And nobody trades, because to everyone but one absent woman, Orr is a stranger with a large backpack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aay5je0fgSPfXEZD1HF7LA.jpeg" /><figcaption><em>Even Grum is impressed, for the wrong reason.</em></figcaption></figure><p>He waits until dusk and carries every item home again, to Grum’s genuine awe: “Even I have never carried this much home!” It is the funniest line in the episode, and it is also exactly what a stalled pipeline looks like. Full load, friendly account, nothing moving.</p><h3><strong>The lesson without words</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NmETeuLdwln8NTAhC34CdA.jpeg" /><figcaption><em>A snapped thread. A braided rope. Nothing else needed saying.</em></figcaption></figure><p>Vela has been nearly silent all season, and this episode is why that arc exists. She does not explain the failure. She hands Orr a single reed thread and snaps it. Then she hands him a three-strand rope, and lets him pull.</p><p><strong><em>One friendship between two camps is a single thread. Three friendships woven across is a rope.</em></strong></p><p>A single thread snaps when one person is away, or tired, or promoted, or gone. Not because anyone did anything wrong. Because thread is thread.</p><h3><strong>The braided visit</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mZF2kDklTUUuHm6plr048g.jpeg" /><figcaption><em>The weaver meets their weaver. The fisher meets their fisher. Grum finds the cook.</em></figcaption></figure><p>The remedy is structural, not heroic. The next visit is not one hunter with a bigger backpack. The tribe’s weaver meets their weaver and they disappear into basket patterns. The fisher meets their fisher over a trap design. And Grum, in the season’s warmest running gag, finds the marsh camp’s cook, and the two of them are inseparable by sundown.</p><p>Peer meets peer. Nobody is selling. Three real friendships form in an afternoon because each pair actually has something to talk about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V6P8ChpuWP-HixsRtd_phA.jpeg" /><figcaption><em>The elder’s staff, planted and absent. The trade, thriving anyway.</em></figcaption></figure><p>The payoff frame is my favorite composition of the season: at the next full moon the elder is away again, her staff planted upright to say so, and the trade around it does not even slow down.</p><h3><strong>What the founder notebook says</strong></h3><p>The lesson carved on the tablet is <strong>a rope is more than one thread.</strong> Into a pipeline review:</p><p><strong>1. Count the names, not the sentiment.</strong> For each open deal, count the people on their side who would answer your message within a day. One is a thread. The CRM says “strong champion”; the thread says one resignation from zero.</p><p><strong>2. Braid peer to peer.</strong> Your engineer talks to their engineer, your CS lead to their ops person. Introductions between peers hold because both sides get value; a second thread spun by the seller alone is still the seller’s thread.</p><p><strong>3. Multithread while it is sunny.</strong> Orr’s failed visit happened after a successful trade. The time to meet the weaver and the fisher is during the honeymoon, not during the renewal panic.</p><p><strong>4. Let Grum find the cook.</strong> Not every connection needs a business case. Some of the strongest threads in an account are two people who simply like each other. Leave room for that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NhqkqAms2ri5Rkl4aKTRKg.jpeg" /><figcaption><em>Season two, lesson three, carved.</em></figcaption></figure><p>Orr ends the episode with the rope coiled over his shoulder, and Vela ends it the way she has ended every episode this season: having taught the most important lesson without raising her voice, or using it.</p><p>Your three biggest open deals: how many people on their side would answer you tomorrow?</p><p><em>The Signal Tribe is a daily animated series from the team at CUFinder. This </em><a href="http://cufinder.io/buying-signals?utm_source=medium&amp;utm_medium=organic&amp;utm_campaign=signaltribe&amp;utm_content=s2e03-article"><em>episode</em></a><em> (78 seconds):</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBedHudAqph8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2FBedHudAqph8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBedHudAqph8%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e6911f04516e66a63f4c3b3dbdf02c64/href">https://medium.com/media/e6911f04516e66a63f4c3b3dbdf02c64/href</a></iframe><p><em>All artwork from the episode. Characters and valley by our studio.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c91c29d9d987" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Cold Outreach Is Not Cold]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/the-best-cold-outreach-is-not-cold-1e5473e720d8?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e5473e720d8</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[b2b-lead-generation]]></category>
            <category><![CDATA[lead-generation]]></category>
            <category><![CDATA[buying-signals]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 08:33:51 GMT</pubDate>
            <atom:updated>2026-10-11T08:33:51.617Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Episode two of The Signal Tribe’s second season: the tribe owes a stranger valley a visit, and Grum wants to arrive loud.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kswqGXCGeIMf7Yj1Q1Fl1w.jpeg" /><figcaption><em>Everything the strangers left behind, laid out and read like evidence.</em></figcaption></figure><p>The first cold email I ever sent took me four minutes to write and got me a reply that took four seconds to read. It said “unsubscribe.” The hundredth one took me forty minutes, because I spent thirty-six of them reading about the company first. That one booked a meeting.</p><p>Episode two of season two is about those thirty-six minutes, forty thousand years early.</p><h3><strong>This time, we are the strangers</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYlu6bGqX0YVnvoZ1S_GdQ.jpeg" /><figcaption><em>The diamond-lattice token: an address, if you can read it.</em></figcaption></figure><p>Last episode, strangers from an unmapped valley walked into camp already trusting the tribe, because a mutual friend had carried the tribe’s story east. Now courtesy demands a return visit. Three ridges east, to a camp nobody in the valley has ever seen, carrying gifts for people nobody has ever met.</p><p>The role reversal is the whole premise. For nine episodes the tribe read signals that came to them. A return visit means being the signal, in somebody else’s valley, where you are the unknown spear at the cold fire pit.</p><h3><strong>Grum packs everything</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GXTLZW4fzzQ5r6sLyrmlEw.jpeg" /><figcaption><em>More gifts means more welcome. The carrying frame disagrees.</em></figcaption></figure><p>Grum’s plan is Grum’s plan: take everything, arrive loud, give it all, hope. It is spray and pray with a carrying frame, and the episode gives it exactly one inset drawing as a rebuttal: a petroglyph of a loud stranger at a camp edge, greeted by three raised spears.</p><p><strong><em>A loud stranger at an unknown camp is how spears get raised.</em></strong></p><p>Every unsolicited message lands as exactly that: a stranger, loud, at the edge of someone’s camp. The question the receiver asks is never “what are they offering.” It is “did this person do any work before walking in.”</p><h3><strong>Reading the leavings</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KcU5G3b4PXY7_WuTXzUAAw.jpeg" /><figcaption><em>The token, the basket, the reeds, the furs, the emptied honey bowl. Five objects, five sentences.</em></figcaption></figure><p>Orr does what Vela would do, which is the quiet engine of this season: he lays out everything the strangers left behind and reads it like ground. A reed basket means a marsh valley. Fine furs given freely mean they have plenty. And the honeycomb bowl they emptied to the wax means the one thing they want and cannot make.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8T2vrv4oPUBLehS7EPbdAA.jpeg" /><figcaption><em>Every object is a sentence.</em></figcaption></figure><p>Nothing in that pile is secret. The strangers were not hiding their marsh or their missing bees. The information sat in plain sight from the moment they visited. Somebody just had to treat it as information.</p><h3><strong>The arrival done right</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hIF_suPggmtN8Og2Doduvg.jpeg" /><figcaption><em>Their sign, drawn first. Spears bundled and grounded. Honeycomb in hand.</em></figcaption></figure><p>The party crosses the third ridge carrying honeycomb, because that is the one thing the hosts want and cannot make. Orr draws the strangers’ own lattice sign at the camp edge, announcing themselves in the hosts’ language, and the spears go down in a bundle before anyone comes out.</p><p>The welcome is immediate. Not because the gift was expensive, but because every detail said: we know who you are, we learned your signs, we came for you specifically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SKht972AaX2abKHSUTEtHQ.jpeg" /><figcaption><em>First trade with the fourth tribe. Grum attended. The drum stayed quiet.</em></figcaption></figure><h3><strong>What the founder notebook says</strong></h3><p>The lesson carved on the tablet is <strong>know the valley before you walk it.</strong> Off the parchment and into an outbound review:</p><p><strong>1. The research is already lying around.</strong> The prospect’s website, job posts, tech stack, funding notes, reviews. Like the reed basket, none of it is hidden. Enrichment is just reading the leavings systematically instead of heroically.</p><p><strong>2. Lead with their honeycomb, not your inventory.</strong> Grum wanted to bring everything. The party brought one thing, chosen because the evidence said it was wanted. One relevant line beats a feature list every time.</p><p><strong>3. Speak in their signs.</strong> Drawing the lattice mark first is writing the subject line in the prospect’s vocabulary, not yours. Their words for their problem, found in their reviews and job posts.</p><p><strong>4. Ground the spears visibly.</strong> No pressure mechanics on a first touch. No false deadlines, no triple follow-up in week one. The bundled spears are what made the open hands possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ksn3L0GgHywHR5TVyeBnIA.jpeg" /><figcaption><em>Season two, lesson two, carved.</em></figcaption></figure><p>The episode ends with a first trade at a new fire, a marsh valley added to the map stone, and Vela once again watching from the background, saying nothing, because nothing needed saying.</p><p>Before your next cold sequence goes out: can you name the honeycomb, for each of the first ten accounts on the list?</p><p><em>The Signal Tribe is a daily animated series from the team at CUFinder. This </em><a href="http://cufinder.io/buying-signals?utm_source=medium&amp;utm_medium=organic&amp;utm_campaign=signaltribe&amp;utm_content=s2e02-article"><em>episode</em></a><em> (80 seconds):</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnKmevVYheNU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2FnKmevVYheNU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FnKmevVYheNU%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/eaddc206fe1922140d63355294232de0/href">https://medium.com/media/eaddc206fe1922140d63355294232de0/href</a></iframe><p><em>All artwork from the episode. Characters and valley by our studio.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e5473e720d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Strangers Who Already Trusted Us]]></title>
            <link>https://medium.com/@seyyedmohammadrazavi/the-strangers-who-already-trusted-us-7771c1036125?source=rss-7f62f6edcdca------2</link>
            <guid isPermaLink="false">https://medium.com/p/7771c1036125</guid>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[b2b-lead-generation]]></category>
            <category><![CDATA[b2b-marketing-strategy]]></category>
            <category><![CDATA[b2b-marketing]]></category>
            <dc:creator><![CDATA[seyyed mohammad Razavi]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 08:26:36 GMT</pubDate>
            <atom:updated>2026-10-11T08:26:36.796Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Season two of The Signal Tribe opens with a mystery: three strangers from an unmapped valley walk into camp and head straight for the trading stone.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cvYsJKGvO5FFH0uzM0Burg.jpeg" /><figcaption><em>Dawn. Strangers nobody has met. And they know exactly where the flat stone is.</em></figcaption></figure><p>The best lead I ever got introduced itself with the words “a friend of mine uses you.” I didn’t run an ad for that lead. I couldn’t have. There is no campaign setting for someone else’s dinner conversation.</p><p>Season two of The Signal Tribe opens on exactly that mystery, forty thousand years earlier. Season one taught the valley to read signals, qualify prey, map new ground, and count what matters. Season two starts with something stranger: customers who arrive already sold.</p><h3><strong>The arrival that should be impossible</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AERglMR4felOPMiNyyxicA.jpeg" /><figcaption><em>They walk in confidently, carrying gifts, and set them on the flat stone. The right stone.</em></figcaption></figure><p>At dawn, three strangers nobody in the valley has ever met walk into camp. They are not cautious. They do not scout from the ridge the way the feather tribe once did. They walk straight to the flat trading stone, the one Vela established two friendships on, and set down full baskets as an opening gift.</p><p>Think about what that means. First contact in this series has always been slow: a found spear in episode five, an empty feast in episode six, a silent trade in episode seven. Trust was built one careful laying at a time. These strangers skipped all of it.</p><h3><strong>The wrong explanation arrives first</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z5y3VYkizQIeg60aUqkNjQ.jpeg" /><figcaption><em>Orr traces the route: three ridges east. No drum carries three ridges.</em></figcaption></figure><p>Grum, of course, has a theory. “They heard my drums! Even sleeping, the drums work!” It is the marketer’s oldest reflex: when a lead appears, credit the loudest thing you did recently.</p><p>Orr, who has become the valley’s methodical one, checks the map stone instead. The strangers’ valley sits three ridges east. Sound does not travel three ridges. Whatever brought them, it was not volume. I have run this exact meeting. The deal closes, the channel report says “direct,” and everyone with a budget claims the credit. The honest answer is usually the one Orr finds.</p><h3><strong>The feather knot</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pqxDL33f-nMUVXJ5C-UsZQ.jpeg" /><figcaption><em>Three feathers on the stranger chief’s staff, tied the feather tribe’s way.</em></figcaption></figure><p>Vela sees it first, because Vela always sees it first. Tied to the stranger chief’s staff: three feathers, knotted in the feather tribe’s distinctive way. The same three feathers Orr has worn in his topknot since episode seven.</p><p><strong><em>We never walked to them. Our name did.</em></strong></p><p>The feather chief, the valley’s first real friend, had carried the story east. Fire by fire, telling whoever sat down: there is a tribe past the ridges that trades fairly, lays goods on a flat stone, and asks nothing first. The strangers did not need convincing because someone they trusted had already done the convincing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gqSnSkfmZtJxnbWEVMKJGg.jpeg" /><figcaption><em>A drum’s sound dies at the first ridge. A story crosses three, fire by fire.</em></figcaption></figure><p>The episode’s field-guide diagram puts it plainly: a drum’s sound rings die at the first ridge. A story passed hand to hand crosses three ridges and keeps walking long after you sleep. Marketers call this a referral, and it is the oldest channel there is.</p><h3><strong>You cannot beat it into existence</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QwmR1HmgUxb8RMBRq5RN7g.jpeg" /><figcaption><em>Grum reaches for the drum. Orr stands in the way.</em></figcaption></figure><p>Grum’s instinct, on learning the news, is to thank the strangers with the great drum. One ceremonial concert, for old times’ sake. Orr physically stands between Grum and the drum, and delivers the episode’s second lesson: we send them home so glad they came, their fires tell the next valley.</p><p>That is the whole mechanics of word of mouth in one sentence. You cannot run a referral the way you run a campaign. You can only earn it, guest by guest, and let it walk. The moment you grab the drum to amplify it, you are back in episode two, emptying the valley.</p><h3><strong>What the founder notebook says</strong></h3><p>The lesson carved on this episode’s tablet is <strong>a friend’s word beats a thousand drums.</strong> Here is how it reads off the parchment and into a pipeline review:</p><p><strong>1. Audit your source column honestly.</strong> When a deal arrives warm, find the actual fire it started at. “Direct traffic” is almost never direct. Someone talked.</p><p><strong>2. Treat every current customer as a future channel.</strong> The feather chief was episode nine’s rekindled friendship. The tribe nearly let that fire go out. The strangers exist because it didn’t.</p><p><strong>3. Spend on the goodbye, not the announcement.</strong> The tribe loads the departing strangers with its finest goods, because the send-off is what their fires will describe. In SaaS terms: the offboarding, the handover, the last renewal conversation. That is the story that travels.</p><p><strong>4. Never interrupt a referral with a drum.</strong> No “we noticed you were referred, book a demo” sequence within the hour. Let the borrowed trust breathe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VqsgMnVCFf9EdslfwuDwGw.jpeg" /><figcaption><em>The strangers leave east, loaded with the camp’s finest. Their fires will tell the next valley.</em></figcaption></figure><p>The strangers leave at dusk, east along the ridge trail, and they leave something behind on the flat stone: a small carved token with a diamond-lattice mark. A fourth tribe’s sign. Orr keeps it, and season two has its first open thread.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NfrzEd1hEeQhYFwYlh5Mdw.jpeg" /><figcaption><em>The season two tablet: eleven stones now, one set slightly apart.</em></figcaption></figure><p>Vela watched the whole episode from the far background, saying almost nothing, because Orr no longer needed her to say it. That silence is its own season-two thread, and I am not going to spoil where it goes.</p><p>What does your source column say about your last three closed deals, and do you actually believe it?</p><p><em>The Signal Tribe is a daily animated series from the team at CUFinder. The </em><a href="http://cufinder.io/buying-signals?utm_source=medium&amp;utm_medium=organic&amp;utm_campaign=signaltribe&amp;utm_content=s2e01-article"><em>season two</em></a><em> premiere (84 seconds):</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FGNF6cgZOEqQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2FGNF6cgZOEqQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FGNF6cgZOEqQ%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a6b18c58d4be401e5acd1ebe88df075c/href">https://medium.com/media/a6b18c58d4be401e5acd1ebe88df075c/href</a></iframe><p><em>All artwork from the episode. Characters and valley by our studio.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7771c1036125" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>