← AI Catalyst C3All programsHomeSearch
AI Catalyst C3·Core Session - Week 18·1:42:07

Mentor Session XV: Selling Beats Building - Paul's Referral-Network Platform, Phone-Book Outbound, Give-First Communities, One Use Case Not a Hundred, and 'Know Thyself'

Harshit Host and mentor (presumably Harshit Tyagi, programme director) - opens on the technical-hat vs sales-hat choice, answers every question, closes on focus and 'know thyself' · Paul Berg Participant - asks the first question (0:07-0:25): how to tell which products are saleable before over-investing, then describes his online referral-networking platform for BNI-style groups · Praful Thakkar Participant - 25 years in real estate, BNI and Buffini-network member, founder of the AIC Mastermind community; gives the 'begin with giving' testimony and later raises a cohort 'service piece' idea · Cody Participant - the 'OpenRouter for MCPs' / elastic-web builder from OH XIV; asks how to demo a many-featured product, about an AI 'app store', and about his SkillPort skills marketplace · Sarah Participant - 'don't say yes to everyone' (from a 1990s book, Futurize Your Enterprise); asks that Founder Stack guests talk about their struggles · Rajendra (as heard) Participant - AIGF cohort-1 alumnus with 50-60 learning products; taking CauseOurClaims.com (OpenAI hackathon winner) to production on Azure; organising the Bangalore immersion meetup · Seyaj (as heard) Participant - heading to Web Summit Lisbon (Nov 9-13) with an umbrella company and products heard as 'Smaran' and 'Parkhema'; asks how to be visible at a conference · Vikram Participant - asks what harness/plugins Harshit uses day to day · Shivani Outskill community manager - immersion dates, Town Hall, weekend schedule, close

The short version

  1. Harshit's opener and refrain: now that the building black box is open, pick a hat - technical or sales. 'Building is not going to make you money; selling is.' He has a hundred projects; ninety are useless. Access to people matters more than the playbook: inbound (content, six to twelve months, always running as backup) and outbound starting with your own phone book and WhatsApp history - twenty messages a day, 'do you know someone who would draw value from this?' (0:04-0:12).
  2. Paul's question: how to confirm a product is monetisable before investing too much love. His product is an online alternative to in-person referral groups (BNI-style, ~$1,500 a year, half a morning gone): members, referral passing in a couple of clicks, follow-up and earned-business tracking, one member per industry, private per group. Harshit: be the power user and let people experience it instead of being sold to (the AIC Mastermind trick - invite to a session, they are signed up before they notice); research Skool and Luma; build one resource so valuable you would charge $500 and give it free; charge after two or three months. Praful: begin with giving - seven past clients at a free breakfast grew to forty; $20 a head bought a $20,000 client (0:07-0:32).
  3. Cody's many-featured MCP: Harshit had 45 seconds to pitch a senior Indian official that morning. Pick five end use cases, record one at a time as a Loom, let the customer discover the rest - 'they were selling for me'. Your tool is a building block inside the customer's bigger picture, not the picture. Detach from the codebase for a day and write a business plan; sell with a video (HyperFrames, Nano Banana) before writing code. 'Software is done' - money moves behind the scenes through APIs and MCPs used by coding agents; build vertical MCPs (0:37-0:58).
  4. Read The One Thing (two rabbits, catch neither). Conference visibility: profile the speakers' LinkedIn/X with a coding-agent skill, find the intersection, give people a takeaway - a QR code that hands them their own analysis; the after-party is where networking happens. Harnesses: Superpowers/BMAD matter for production code; for prototypes Harshit dictates pages into Codex and says 'turn this into a skill' whenever an output is good. Ignore term churn - software factory, FDE, vibe coding; the basics are what sessions end up teaching (0:59-1:15).
  5. SkillPort: Vercel's skills.sh works because they own npx and sell cloud; a marketplace drives traffic but you need something underneath to sell. Rajendra: focus on the hackathon winner, talk business not Azure, turn the writing habit into SEO so the product shows up in Perplexity and ChatGPT - 'you're a good lead-magnet guy; the leads need somewhere to go'. Sarah: don't say yes to everyone. Harshit's close: focus has been his written weakness four years running - 'know thyself' (1:15-1:31). Logistics: Bangalore immersion Dec 5 or 12, Town Hall Nov 1, not a demo day; no office hours after the course but community events; weekend = Jarvis session (Sat) and Founder Stack (Sun) (1:31-1:42).

At a glance, three clicks deep

Skim here first: the closed row is the glance, open is the study card with the key points and timestamps, and the ↓ link drops to that concept's full write-up below.

01Pick the sales hat: phone-book outbound, inbound as the slow backup, and 'access to people' over playbooksMonetising AI skills is a sales problem solved first through existing relationships (phone book, WhatsApp),…0:04:00›

Monetising AI skills is a sales problem solved first through existing relationships (phone book, WhatsApp), with content-driven inbound as the slower parallel track.

Technical hat vs sales hat; executives sell and hire engineers to scale (0:05)

Inbound: content and brand, 6-12 months, always running as backup (0:10)

Outbound: phone book and WhatsApp history; 'do you know someone who would draw value from this' (0:10-0:11)

Twenty messages a day; shameless and consistent (0:11)

Generic solution (RAG) applied to a reachable vertical; cold email at $50-100/month underperforms (0:11-0:12)

↓ Full write-up of this concept

02Paul's referral-network platform: show the value as its power user, research Skool and Luma, and lead with a $500-worth free resourceValidate and sell a community/tool product by running your own community on it, letting prospects experienc…0:07:00›

Validate and sell a community/tool product by running your own community on it, letting prospects experience value before any pitch, and front-loading a free resource worth paying for.

Paul's product: virtual referral groups (20-30 members, one per industry, real-estate/finance nodes), referral passing and tracking, tenancy per group; no competitor found (0:12-0:17)

Harshit: be the power user; showcase value, don't sell - AIC Mastermind sign-up trick (0:18-0:19)

Luma for meetups; don't charge at first; get members using it daily (0:20-0:21)

Research Skool, Luma and peers for ideas and uniqueness (0:22, 0:24)

Build a resource you would charge $500 for and give it away; monetise after 2-3 months (0:22-0:23)

Paul's next steps: enticement video, 5-10-person pilot per group, subscription (0:21-0:22)

Praful: begin with giving; the signal that you want business is felt and kills fragile relationships (0:25-0:30)

↓ Full write-up of this concept

03Demo one end use case, not the platform: Harshit's 45-second pitch, the Loom that makes customers sell for you, and detaching from the codebaseMake a broad tool legible by choosing five concrete end use cases for named customers, demonstrating one at…0:37:00›

Make a broad tool legible by choosing five concrete end use cases for named customers, demonstrating one at a time, and positioning the tool inside the customer's problem rather than as the product.

Two-minute pitch to a senior official done in 45 seconds - lead with the core (0:40)

Firecrawl MCP: one thing, easy to trust; Glued: one use case recorded as a Loom, customers sold the rest (0:41-0:42)

Five end use cases, named customers, even at the cost of TAM (0:43)

Tool as building block inside the bigger picture; a directory page for the rest (0:45, 0:47)

No app store coming; APIs and MCPs behind coding agents are where money moves; vertical MCPs (0:50-0:51)

'Connect everything to your tool' is a wrong assumption below OpenAI/Anthropic credibility (0:52-0:53)

Detach from the codebase; one day of business-plan brainstorming; sell with a video first (0:55-0:57)

↓ Full write-up of this concept

04The One Thing, 'don't say yes to everyone', and know thyself: focus as the recurring weaknessProgress on monetising comes from choosing one product, one segment and one channel and declining the rest,…0:59:00›

Progress on monetising comes from choosing one product, one segment and one channel and declining the rest, including customers who are not yours.

The One Thing: two rabbits; Praful brings copies (0:59-1:01)

Sarah: don't say yes to everyone - not your market, not your bucket (1:27-1:28)

Harshit: focus is his written weakness four years running; 'know thyself' (1:28-1:31)

↓ Full write-up of this concept

05Being visible at a conference: profile the speakers with a coding-agent skill, give a takeaway, and go to the after-partyPrepare for a conference by profiling who will be there with an agent, tailoring one demo to the intersecti…1:01:00›

Prepare for a conference by profiling who will be there with an agent, tailoring one demo to the intersection, and designing a takeaway people can scan.

Agent skill: read speakers' LinkedIn/X, find the intersection with your product (1:03-1:04)

Small prototype or video for that one thing; QR-code takeaway (1:04-1:05)

After-parties are where networking happens; Telegram QR and selfie-notes culture (1:05-1:06)

↓ Full write-up of this concept

06Harshit's working harness: dictate pages into Codex, 'turn this into a skill', spec-driven kits only for production code, and ignoring term churnReserve spec-driven harnesses for production code;1:07:00›

Reserve spec-driven harnesses for production code; for prototypes, dictate freely and convert good outputs into skills on the spot.

Custom dev harness + simple automations; Codex Max plan; deletes harnesses often (1:08)

Superpowers/BMAD = production engineering with tests and review (1:10)

'Turn this into a skill' after any output you love; 15-20 projects (1:08-1:09)

FDE = consultant x PM x engineer; term churn vs basics (1:13-1:15)

↓ Full write-up of this concept

07SkillPort and the hackathon winner: a marketplace needs something to sell underneath; a lead magnet needs somewhere to leadMarketplaces and lead magnets are traffic mechanisms;1:15:00›

Marketplaces and lead magnets are traffic mechanisms; they pay only when a product and an offer sit beneath them.

skills.sh works for Vercel because of npx and cloud revenue; have a business first (1:16-1:19)

Praful: the platform is the value; 'service piece' for cohorts (1:19-1:21, 0:58)

Rajendra: pick the hackathon winner; V5 to V20 endurance; business language not tech (1:22-1:25)

Writing habit -> SEO/AEO for Perplexity and ChatGPT; lead magnets need a destination (1:25-1:26)

↓ Full write-up of this concept

08Programme logistics: Bangalore immersion Dec 5 or 12, Town Hall Nov 1, no demo day, no office hours after - community events insteadEnd-of-programme calendar and format as stated on 8 October 2026.1:31:00›

End-of-programme calendar and format as stated on 8 October 2026.

Immersion Dec 5 vs 12, Bangalore; founders, interviews, networking; not a demo day (1:31-1:35)

Town Hall Nov 1; no office hours after; community events continue (1:38-1:40)

Founder Stack guests asked to share struggles (1:35-1:37)

Weekend: Jarvis (Sat), Founder Stack (Sun) (1:41)

↓ Full write-up of this concept

The concepts in full

01

Pick the sales hat: phone-book outbound, inbound as the slow backup, and 'access to people' over playbooks

0:04:00

A hundred projects, ninety useless. They give pleasure; they do not pay. The deal that paid last week was a voice agent - a market he had written off.

Harshit frames the moment: the building black box is open, so decide whether you wear the technical hat or the sales hat; executives wear the sales hat and hire engineers to scale what they prototype. He thought voice agents were commoditised, then signed one last week because the buyer had seen three vendors demoing recordings and his team had customised for the buyer's marketplace. The lesson is not the playbook but access: who do you already reach? Inbound (LinkedIn, social, brand) works in six to twelve months and should always run in the background. Outbound starts in your phone book and WhatsApp history: pass your idea through everyone you have chatted with, not as a pitch but as 'do you happen to know someone who would draw a lot of value from this?' - they answer as the customer or they connect you. Twenty messages a day, build the list, bake the habit, repeat next week; you have to become 'that sort of shameless person'. A generic capability (RAG, a chatbot, a voice agent) becomes saleable when applied to a vertical you can reach. Paid email outbound at $50-100 a month gives poor results by comparison.

Worked example · from the session

Voice agents 'were done' - until a marketplace client who was interviewing three vendors a week chose the customised one.

Why it matters

Everything else in the session - Paul's platform, Cody's MCP, Rajendra's products - comes back to this: who can you reach, and are you asking?

02

Paul's referral-network platform: show the value as its power user, research Skool and Luma, and lead with a $500-worth free resource

0:07:00

Paul has built the online version of the Thursday-morning referral breakfast. Harshit's answer: don't sell it to the group - run the group on it.

Paul asks how to tell which products are saleable before investing too much love, then describes the one he thinks is: US networking groups of 10-30 people meet weekly in person to pass leads (the famous national one costs about $1,500 a member a year, with rules, and the morning is gone); his group meets online 8:30-9:30 and he has built the website that runs it - member contact information, referrals passed in a couple of clicks, follow-up and earned-business tracking, one member per industry, anchored by the real-estate agents and finance people who are the referral nodes. It has made his own group more effective and organised; he found no direct competitor; he plans a tenancy model so each group is private, and sees high-performing real-estate agents across Connecticut as the obvious buyers. Harshit's questions: what does it do, have you shown them, are there competitors? Then the strategy: be the power user of your own product and let people experience the value rather than be sold to - the way Praful's AIC Mastermind invites you to a session and you are signed up before you notice; the way Harshit gave away a resource playlist that was really a blog sign-up. Organise the meetups through it (he names Luma, luma.com); don't charge at first; get them 'stuck in the interface' chatting and scheduling. Research Skool, Luma and similar community platforms for ideas and to see whether the wheel is unique (he types a list into chat). Create one resource so valuable your own mind says 'I'd charge $500 for this' - and give it free as the offer; money comes after two or three months. Paul's plan in response: a video to entice people to a sample session, a trial with five to ten cohorts per group, then the per-group subscription. Praful adds the real-estate version of the same rule: 25 years of give-first.

Worked example · from the session

Praful's breakfast: seven or eight past clients, free meal, no business talk, grew to forty; $20 a head produced a $20,000 client because every guest was asked to bring only people who would value the service.

Why it matters

It is the first time Paul's own product has been critiqued live on the programme, and the advice is specific: experience before pitch, community-platform research, a give-first offer, revenue later.

For your projects

This is Paul's own validation checklist from the session: (1) run the Connecticut group on the platform and record the video from real use, not a demo; (2) benchmark against Skool and Luma before pricing - Harshit's doubt was whether the wheel is unique; (3) write the give-first asset (a referral-group playbook or template worth $500) as the lead magnet for real-estate 'nodes'; (4) pilot with 5-10 people per group free, charge per group after 2-3 months; (5) the outreach list is the phone book - agents and finance people Paul already knows - at twenty messages a day. Praful offered an offline conversation (0:30) and his AIC Mastermind WhatsApp group.

03

Demo one end use case, not the platform: Harshit's 45-second pitch, the Loom that makes customers sell for you, and detaching from the codebase

0:37:00

'You have two minutes.' He used forty-five seconds, on the one thing that mattered. Cody's product has a hundred things.

Cody is building a giant MCP - 'OpenRouter for MCPs' - that other bots can plug into, and cannot get it tested or trusted outside hackathons; bots hit login walls and take website claims as fact. Harshit's diagnosis: too many features, no legible use case. That morning a senior Indian government official gave him two minutes with no introduction; he pitched the core in forty-five seconds. Firecrawl's MCP is easy to trust because it does one thing. For his own many-featured MCP (Glued) he picked one end use case - a performance marketer reallocating campaign budget between Instagram campaigns - recorded himself doing it, sent the Loom, and customers started asking 'can it also do...?' and selling the rest to themselves. So: list the five most important end use cases, define the customers even if it shrinks the TAM (there are no users yet), record them one by one, and test whether each is a real pain. Position the tool as a building block in the customer's bigger picture ('today we build a real-estate listing directory - the data comes through Firecrawl') rather than the picture itself. Keep a directory page for everything else. Cody's instinct to let 50-100 Outskill learners build verticals on it is 'a lot going on' - eliminate. On his AI-app-store question: there will be no app store; software is being quashed and money is made behind the scenes by APIs and MCPs that coding agents call (ElevenLabs, Higgsfield), so build vertical MCPs for specific audiences. On the 'check my balance, am I good for the holiday' agent: nobody connects their bank, travel and everything to your tool until you are OpenAI or Anthropic - a wrong assumption. On a JSON-schema capability registry: too low level; 'your head is in the codebase'. Prescription: one day, no code changes, brainstorm with AI in the same project on the single segment to pivot around, write the business plan. He sold a university vice-chancellor with a HyperFrames/Nano Banana video of a product that did not exist yet.

Worked example · from the session

One Loom of the budget-reallocation use case did what a twenty-feature tour could not: prospects asked for features he had not mentioned.

Why it matters

The most transferable advice of the session for anyone with a platform-shaped product.

04

The One Thing, 'don't say yes to everyone', and know thyself: focus as the recurring weakness

0:59:00

Two rabbits run past. Chase both and you catch neither. Harshit has written 'focus' on the first page of his year-end review four years running.

Praful recommends The One Thing (Gary Keller - the real-estate book with the domino stack and the two-rabbits opener, about 120 pages, one sitting) and will bring ten copies to Bangalore. Harshit admits the same pattern: sign a deal, then chase the next one instead of delivering; decide at New Year to focus on YouTube, get distracted by whatever turns up. Sarah's version, from a 1997 book on the new internet (Futurize Your Enterprise): don't say yes to everyone - people outside your target market fall into someone else's bucket; saying yes to all comers got her into ugly situations in the website business and the rule applies to AI work now. Harshit's close for the cohort: with so many playbooks learned, the phrase everything leads to is 'know thyself' - people who know themselves get answers from inside; people who don't have things happen to them. Pause, let others run in directions that are not your race, look sideways.

Worked example · from the session

Harshit's year-end diary: four Decembers in a row the weakness written down is focus.

Why it matters

The session's theme in one line - elimination, not addition.

05

Being visible at a conference: profile the speakers with a coding-agent skill, give a takeaway, and go to the after-party

1:01:00

Everyone at the crypto conference had their QR code on their lock screen. The networking happened at 8 pm, not in the hall.

Seyaj is taking an umbrella company with several products to Web Summit Lisbon (Nov 9-13) with a demo day and VCs present, no pricing decided. Harshit does not attend many conferences but describes what he did for C4: build a skill/automation on the coding agent that reads the speakers' (and attendees', if listed) LinkedIn and X profiles - recent posts, the problems they discuss - and finds the intersection with your product, then make a small hacky prototype or video for exactly that. Give people something to take away from a two-minute conversation: a QR code that drops their own analysis onto their phone. From a Dubai crypto conference: the day sessions were half-empty, the after-party was where it happened; everyone shared contacts by Telegram QR, took a selfie with you and typed a note so they remembered who you were. Brainstorm forward: a QR tied to a dictation device that transcribes the conversation and sends a summary into the chat right there.

Worked example · from the session

Scan this and your conference-specific analysis appears - that is a reason to remember the booth.

Why it matters

A concrete pre-conference workflow built from tools the cohort already has.

06

Harshit's working harness: dictate pages into Codex, 'turn this into a skill', spec-driven kits only for production code, and ignoring term churn

1:07:00

He has used Superpowers and BMAD. For most of his work he rambles two or three pages into Codex and says 'turn this into a skill' when the output is good.

Vikram asks what base harness Harshit runs (Superpowers, Graphify and the like). Answer: he keeps deleting harnesses; one custom harness for deep development, otherwise simple automations, all on Codex on the Max plan. Spec-driven development kits (Superpowers, BMAD) are for software engineers with something already in production that must not break - planning, testing, review, refactor - and he uses them when adding a feature to a live product. For proof-of-concept work he dictates at length, corrects, and whenever he loves an output he says 'turn this into a skill: how we iterated, what I don't want (bloated scripts, em dashes)', and the next time he asks for a script the skill applies itself; 15-20 projects run this way. On the flood of terms - software factory, 'JEV' (an encoder/decision API the labs had internally), vibe coding, forward-deployed engineering (FDE: consultant + product manager + engineer, Palantir hires MS CS + MBA; not every engineer can hold a C-suite conversation) - stop obsessing: the terms are good for session titles, but the sessions end up teaching the same basics. 'There comes a time when you should stop listening and focus on one thing.'

Worked example · from the session

'This script looks great - we should always write scripts like this, no bloat, no em dashes. Turn it into a skill.'

Why it matters

A low-ceremony way to accumulate reusable skills without a framework.

07

SkillPort and the hackathon winner: a marketplace needs something to sell underneath; a lead magnet needs somewhere to lead

1:15:00

Vercel's skills.sh exists because Vercel owns npx and sells cloud. What does your marketplace sell?

Cody asks whether to continue SkillPort, a skills marketplace. Harshit: Vercel released skills.sh in a day because anything installed through npx registers there automatically and the real business is cloud services; directories and marketplaces bring traffic, but the next step is selling something, so first have the underlying business, then the marketplace - otherwise you will spend months chasing listings and make nothing, and people will compare you with skills.sh. Praful disagrees on framing (the platform itself is the value) and wants to fold it into a 'service piece' he is designing for cohorts (shared infrastructure to remove individual usage struggles) - to be discussed in the AIC Mastermind. Rajendra has 50-60 learning products and one he means to monetise, CauseOurClaims.com (OpenAI hackathon winner, going production-grade on Azure with domain testers). Harshit: focus on the one you are passionate about - V5 may fail, V20 may succeed; it is endurance; and stop talking tech - nobody cares about Azure vs AWS, only 'this customer had this problem, I solved it'. Use the habit of writing and sharing as automated SEO: daily posts on specific problems people search for in Google, Perplexity and ChatGPT so the product shows up; 'you're a very good lead-magnet guy - the leads need somewhere to go'.

Worked example · from the session

A skills directory with nothing to sell underneath is traffic without a till.

Why it matters

Two learners, one rule: a funnel needs a product at the bottom.

This idea elsewhereparallelOrganic Sales on AEO
08

Programme logistics: Bangalore immersion Dec 5 or 12, Town Hall Nov 1, no demo day, no office hours after - community events instead

1:31:00

It is not a demo day. It is founders on stage, Harshit interviewing them, and networking until 11 pm.

The Bangalore immersion will be December 5 or 12 (Abhishek's message said 12; Harshit is trying for the 5th; decision within 48 hours); it runs from about 10 am to late, with founders invited, Harshit interviewing them, an after-party - nothing like the AIGF demo day at the Google office. Rajendra asks for a plan early (last time 25 people met the day before) and mentions a Jagriti Yatra idea. Town Hall is November 1, the last scheduled session. The 'Shekhar' (as heard) evals session was running in parallel today; recordings of it are not provided for now. After the course there are no office hours, but sprint and community events continue. An advanced Catalyst is not planned; Harshit may run a separate forward-deployed-engineering programme for software engineers. Sarah asks that Founder Stack guests talk about struggles, not just wins; Harshit will brief this weekend's guest. Weekend: Jarvis session Saturday, Founder Stack Sunday. Side notes: ElevenLabs hackathon group forming; Dubai AI Festival Oct 26-27.

Why it matters

Dates and expectations for the last month of the cohort.

Tools referenced

ToolCoverageMomentContext
Firecrawlexplained0:41:00One-thing MCP as the trust example
Loomexplained0:42:00Record one use case, send it
Codexexplained1:08:00Harshit's daily agent on the Max plan
Superpowersexplained1:07:00Spec-driven harness, production work only
Vercelexplained1:17:00skills.sh as the marketplace example
Lumamentioned0:20:00Meetup platform suggested for Paul's groups
Skoolmentioned0:22:00Community platform to research
OpenRoutermentioned0:44:00'OpenRouter for MCPs' positioning
HyperFramesmentioned0:57:00Video that sold before code existed
Telegrammentioned1:05:00QR contact sharing at crypto conferences

Action items

    Resources mentioned

    Resources
    • docThe One Thing (Gary Keller)
    • docFuturize Your Enterprise (1997)
    • docHarshit's list of community platforms to research (typed into chat)
    • docCauseOurClaims.com

    Extraction notes

    This page was built from an auto-generated transcript, which garbles product and people's names. Those were corrected silently in everything above and logged here for transparency. The warnings flag claims that were true on the recording day but change fast.

    Transcript corrections applied

    The transcript saysThe trainer actually means
    icky guyikigai
    school.com / dooma.comSkool.com and Luma.com (community and meetup platforms)
    AIC mastermind.comAIC Mastermind - Praful Thakkar's community
    Prayful / Praful TakkarPraful Thakkar
    Buffini / brand buffiniBrian Buffini's coaching network
    Jeff / jevAn unnamed frontier-lab release ('JEV', as heard) whose invites the group shared; also an encoder/decision API Harshit mentions - unresolved
    Kodi / CodyCody (participant)
    fire crawlFirecrawl
    GluedHarshit's own MCP product (as heard)
    be madBMAD (spec-driven development kit)
    Sugar / ShekharOutskill's head of engineering who ran the evals sprint (name unverified)
    Harshit VadiparathyThe Saturday 'Jarvis' session instructor as announced; spelling unverified
    Smaran / ParkhemaSeyaj's product names, unverified

    True on recording day — verify before relying