RamenClub Outreach Report
27 founders. 81 cold emails.
Source: ramenclubhq.slack.com — 1,512 messages analyzed.
Generated March 29, 2026
How this was built
Captured the full RamenClub Slack workspace via HAR file. Extracted and analyzed 1,512 messages across 10 channels. Identified founders actively shipping, their stated pain points, traction signals, and what help they were explicitly or implicitly asking for. First 8 prospects were cross-referenced against public web presence to verify emails and social handles. Remaining 19 were built entirely from Slack data alone — product names, URLs, and pain points pulled directly from their messages.
"2026 is my year of marketing." Launched on ProductHunt + Show HN. Has law firm and competitive intel users. Doing ICP demo calls. Needs to turn early traction into a repeatable pipeline.
Use Changeflow's own technology to monitor prospects' websites for buying signals — new job listings, fundraise announcements, product launches — and auto-draft a personalized cold email the moment a trigger fires. His product sells itself. Build the automation in 48h.
Email 1Day 1using changeflow to sell changeflow
Hey Steve, Saw the Show HN post for Changeflow. The compliance monitoring angle is solid — law firms are a great ICP. Quick thought: what if you monitored your own prospects' sites for buying signals (new job listings, funding posts, product launches) and auto-drafted a personalized outreach when one fires? Meta, I know. But I can build that workflow in a day. Worth a chat? Alexis
Email 2Day 6one thing that could double your demo conversions
Hey Steve, One thing I've noticed with monitoring tools: the hardest part isn't convincing people monitoring is useful — it's showing them *what to monitor*. A "Trigger Templates" gallery — pre-built setups for "competitor raises funding", "prospect posts a job listing", "regulation page gets updated" — gives new users an instant win on signup. Happy to pull that together if you want to test it. Alexis
Email 3Day 14last one
Hey Steve, Not chasing. Just leaving this here: I built a community intelligence tool last week that mined 1,500+ Slack messages to surface warm leads with full context. Same principle as Changeflow but for social data. If the "year of marketing" thing gets stuck, I'm around. Alexis hello@alexisbouchez.com
"Running migration scripts to production. Recording 4-minute launch videos." Building alone, big vision. StrawPage just hit 1M users in the same "easy websites" space.
Set up Palmframe on Hyperclay before launch so real user reactions are captured from day one. Plus: propose a "Hall of Fame" gallery (sorted by file size vs. app complexity) as a viral mechanic. StrawPage grew through shareable examples. Hyperclay's one-file constraint is a meme-able superpower.
Email 1Day 1your launch is closer than you think
Hey David, Found Hyperclay through a community I'm in. The portable self-contained HTML app idea is genuinely interesting. Saw you're in launch prep (migration scripts, launch videos). One thing that makes a launch stick: having a feedback loop ready *before* people arrive. I built Palmframe for exactly this — contextual reactions in real time. Worth adding before launch? I'll set it up for you for free. Alexis (@frenchfounder)
Email 2Day 5the StrawPage angle
Hey David, StrawPage (also "make websites easily") just hit 1M users. Growth was almost entirely community-driven — people sharing wild examples. Hyperclay's one-file constraint is a meme-able superpower. The person who builds the most insane app in a single 50kb file wins the internet for a day. A "Hall of Fame" gallery on your site — sortable by file size and app complexity — could be your StrawPage moment. Happy to build it. Alexis
Email 3Day 13last message
Hey David, Last one. The Palmframe offer stands whenever you're ready. One honest thought before the PH launch: "Hyperspace Systems LLC" doesn't match the fun, portable energy of Hyperclay. First impressions matter more than you'd think. Good luck with the launch. Alexis hello@alexisbouchez.com
"Got a recruiting lead to try amor.dev with his team — might be the first $1k/yr plan." Also building Elmo (brand monitoring in LLMs). Switching analytics infra, wrestling auth decisions across multiple products.
Elmo monitors how brands appear in LLM outputs. But brands are also discussed in Slack communities and Discord servers — often with more buying intent than LLM mentions. Alexis just built a Slack extraction layer. Natural $99/mo Elmo add-on. Same signal layer could make Amor smarter too: engineers signaling stack transitions in communities = real-time intent data vs. historical GitHub commits.
Email 1Day 1Elmo but for Slack communities
Hey Jared, Elmo for LLM brand mentions is the right idea. But here's what I think is worth more right now: brands also get mentioned in paid Slack communities and Discord servers — way more actionably than in LLMs. I just built a tool that extracts brand mentions, sentiment, and context from Slack workspaces. Surfaced 8 warm outreach targets from 1,500 messages in a day. This is a natural $99/mo add-on for Elmo. Interested in building it together? Alexis
Email 2Day 7amor.dev + real-time intent data
Hey Jared, Different angle on Amor: the best engineer candidates are already signaling in communities — "just moved from Postgres to Clickhouse", "shipping with the new Claude API". Real-time intent vs. historical commit analysis. Monitoring those community signals and surfacing them in Amor would make it dramatically more powerful. The extraction layer I built does exactly that. Might be worth 20 minutes. Alexis
Email 3Day 14ok last one
Hey Jared, No more emails after this. Unsolicited: on the auth decisions — Better Auth is the right call for multi-product if you control the infra. Saved me weeks vs. Clerk. The community monitoring angle still stands if Elmo's roadmap goes there. Alexis hello@alexisbouchez.com
"I acquired Topical Map AI 6 months ago. Spent the first few months fixing significant technical debt — broken auth, credit system exploits, AI hallucinations. Now looking for someone to own growth: affiliate, content/SEO, paid acquisition, B2B outreach. Open to equity split, rev share, or hybrid."
Direct response to her explicit ask. Alexis proposes himself as technical growth partner: build the free "Quick Topical Map" tool for top-of-funnel capture, set up a Webflow/Framer integration (huge market of designers who want content strategy), and establish a white-label track for SEO agencies. Revenue share on new MRR generated.
Email 1Day 1growth partner for topicalmap.ai
Hey Megan, Saw your post looking for a growth partner for Topical Map AI. 2,500 SEO professionals is a solid base to build from. I'm Alexis — software engineer, been building and shipping products for a few years. Genuinely interested in the partnership model you described. The technical debt work you did — auth rewrite, credit system, hallucination fixes — that's the kind of foundation that can actually scale. I'd like to hear more about where you want to take it. 30-minute call? Alexis (@frenchfounder)
Email 2Day 6three distribution ideas for topicalmap.ai
Hey Megan, Whether we work together or not, three things I'd try: 1. Free "Quick Topical Map" tool (limited clusters, no signup) — top-of-funnel SEO traffic, converts to paid 2. Webflow/Framer integration — designers want content strategy without touching a CMS 3. White-label access for mid-sized SEO agencies — recurring revenue, low acquisition cost Happy to build any of these on a test basis before committing to anything. Alexis
Email 3Day 14last message on the partnership
Hey Megan, Not following up again after this. I genuinely think Topical Map AI has the right ingredients: real users, clean tech, clear ICP. The growth partner role you described is exactly the kind of work I do well. If the timing is right — hello@alexisbouchez.com. Alexis
"Taking a few months off to build PythonStarter — a Python and Flask starter kit for vibe coders. Built with Claude Code." Journalist background, 40K+ Medium views, 10K X followers. Launch date: first week of March.
Write a ranking comparison post ("Best Python starter kits for indie hackers 2026") that goes live the same day as the Product Hunt launch. PythonStarter ranks first. Drives long-tail SEO traffic after the PH noise fades. Secondary: Daniel's journalist background is a superpower for developer tools — he can write docs that actually get read. Help him leverage that.
Email 1Day 1your PH launch + one SEO move
Hey Daniel, Saw you're launching PythonStarter on Product Hunt. Good timing — the vibe-coding wave has a lot of non-technical founders suddenly needing a Flask stack that just works. One move that helps PH launches: a ranking blog post live the same day. "Best Python starter kits for indie hackers 2026" — I'll write it, PythonStarter ranks first (because it should), and it drives long-tail traffic after the PH noise fades. Free. I'm building content in this space anyway. Alexis (@frenchfounder)
Email 2Day 5the journalist angle
Hey Daniel, Going from journalist to developer is a superpower for selling a developer tool — you can write. Most starter kits fail not because of code quality but because the docs read like a README. Your 40K Medium views prove you know how to explain things. "Build your first SaaS in a weekend with PythonStarter" on Medium, cross-posted to dev.to. I can review the technical accuracy if you want a second pair of eyes. Alexis
Email 3Day 13last one
Hey Daniel, Last email. The SEO post offer stands — whenever you launch. Small flag: "getpythonstarter@gmail.com" as your public contact for a paid product looks early-stage to a buyer. Worth setting up daniel@pythonstarter.com before the PH launch — 10 minutes, looks 10x more serious. Good luck. Alexis hello@alexisbouchez.com
"Built it after realizing invisible hours were eating my income. Quick calls becoming 90 minutes, revisions nobody scoped, endless back-and-forth." Freelancer workspace for time tracking, projects, clients, payments.
Build an open-source MCP server for Trackora so freelancers can log time, create invoices, and check project status directly from Claude Code — without leaving their coding environment. The tool that caused the billable time gets used to log it immediately. Zero-friction = dramatically better adoption. Alexis open-sources it, Trackora gets distribution through the Claude ecosystem.
Email 1Day 1Trackora + Claude Code = zero-friction time tracking
Hey Ahmed, Trackora solves a real problem. But there's a gap: most developers are in their editor or Claude Code all day, and switching to a browser to log time is the exact friction that kills adoption. I can build an MCP server for Trackora in a weekend — freelancers could log hours, check project status, and generate invoice drafts without leaving their coding environment. I'll open-source it. You get distribution through the Claude ecosystem. Worth exploring? Alexis
Email 2Day 6the invisible hours thing hits different now
Hey Ahmed, The "invisible hours" framing in your copy is really good. Knowing you're working unprofitably without realizing it is a visceral hook. One expansion: a "Profitability Audit" feature. Analyze past projects, surface which clients and project types were actually profitable. Upsell: "you're losing $X/month on these types of projects." Adds $20-30/mo justification immediately. Happy to help spec it. Alexis
Email 3Day 14last one from me
Hey Ahmed, Not following up again. The MCP server — I'll build it whether or not we work together. If you want Trackora's API in scope rather than me reverse-engineering the public interface, I'm at hello@alexisbouchez.com. Good luck. Alexis
"Got my first trackable referral from ChatGPT yesterday — this is the start, it should compound from here." 13 years across 6 B2B SaaS companies. Building: social studio, competitive analysis, alternative posts, bottom-of-funnel features.
Build a live competitive intelligence pipeline that feeds into Oleno's context: monitor what competitors' content is gaining traction, what topics the community is actively discussing, what questions prospects are asking right now. Oleno generates content — ContentSignal tells it what's worth generating today. Transforms Oleno from "AI that writes" to "AI that writes what will win."
Email 1Day 1a data pipeline idea for oleno.ai
Hey Daniel, Oleno's positioning is sharp — "content operations, not content tools." 13 years in B2B SaaS means you know the GTM motions. One thing that could sharpen Oleno's output: live competitive signal. I can build a pipeline that monitors what your users' competitors are publishing, which topics are trending, what communities are actually talking about — and routes that context into Oleno's AI. Your product generates content. My pipeline tells it what content is worth generating right now. Worth 20 minutes? Alexis (@frenchfounder)
Email 2Day 7the ChatGPT referral is just the start
Hey Daniel, The ChatGPT referral you mentioned — first one, 46 days after indexing — is worth doubling down on hard. "Content that ranks in LLMs" is the new SEO play, and most of your ICP doesn't know this yet. A post from you on "how to make your B2B content appear in ChatGPT answers" would rank for a real query and pull in exactly the right people. I can help research and draft it if that would be useful. Alexis
Email 3Day 14last one
Hey Daniel, Last email. The competitive signal pipeline — I think it's worth building regardless. If you want to see a prototype before committing to anything, I'll put one together. Alexis hello@alexisbouchez.com
Building an LLM evaluation platform. Dogfooding his own product. Needs distribution in the Claude Code / developer ecosystem where prompt engineering is actually happening.
Build an open-source MCP server that integrates Promptfast evaluations directly into Claude Code workflows. Developers run evals without leaving their terminal. With "eval-as-you-build" mode, evals fire automatically when a prompt file changes — catching regressions immediately instead of post-launch. First eval tool natively in the Claude ecosystem is a serious distribution advantage.
Email 1Day 1promptfast + claude code = eval that actually gets used
Hey Ben, LLM eval platforms have an adoption problem: developers know they should be running evals, but leaving their workflow to do it kills it. I can build a Promptfast MCP server so Claude Code users can run evals without leaving their terminal. First eval tool natively in the Claude ecosystem would be a real distribution advantage. I'd open-source it. You get the Claude Code community as a channel. Interested? Alexis
Email 2Day 6eval-as-you-build
Hey Ben, One angle worth thinking about: "eval-as-you-build" rather than "eval-before-deploy." What if Promptfast caught prompt drift in real time as you iterated — a background mode that surfaces regressions the moment you change a prompt file, not when you remember to check a dashboard? The MCP integration makes this natural. Happy to prototype it if that's directionally right. Alexis
Email 3Day 14last one
Hey Ben, No more emails after this. I'll build the Promptfast MCP server either way — it's a gap in the Claude ecosystem. If you want the API in scope rather than me reverse-engineering the public interface, I'm at hello@alexisbouchez.com. Alexis
"Runner up at the hackathon (I'll take that!). Managed to snag $2500 in OpenAI credits." Building Bub — an MCP server with smooth OAuth flow for claude.ai. Also building hackweeks.com (remote hackathon platform). Rebuilding the landing page to better reflect what they do.
Bub is an MCP server with proper OAuth — exactly what claude.ai users need. But most developers don't know it exists. Alexis writes a "How to connect Bub to Claude in 2 minutes" tutorial, submits it to the Claude community and relevant developer communities, and sets up Palmframe on the landing page to capture feedback from people who land and don't convert.
Email 1Day 1bub MCP + the distribution gap
Hey, Saw the hackweeks.com landing page update. The MCP server with OAuth for claude.ai is a genuinely useful thing — but most people won't know to look for it. I can write a "connect Bub to Claude in 2 minutes" tutorial and submit it to the places Claude developers actually hang out. Short build, real distribution. Interested? Alexis (@frenchfounder)
Email 2Day 6the $2500 credits angle
Hey, The hackathon runner-up story + $2500 in OpenAI credits is actually a good marketing hook — "I built this at a hackathon and it worked well enough to win second place." If you document the Bub build process (what worked, what didn't, how long the OAuth took to get right), that's a dev.to / Hacker News post that sells the product better than any landing page. Happy to help write it. Alexis
Email 3Day 14last one
Hey, Last email. The tutorial offer stands — hackweeks.com or the Bub MCP, happy to help with either. One thought: if Bub doesn't have a feedback widget yet, Palmframe (palmframe.com) takes 5 minutes to add and captures exactly the kind of "I almost signed up but..." signal that's hard to get otherwise. Alexis hello@alexisbouchez.com
"Finally able to talk money with my second early adopter. We agreed on $1100 for the AI agent-based solution." Restructured from coding agent to agent framework. Recorded intro video. IMAP integration complete. Building SolidJS + Tailwind GUI for agent workflow planning.
Nocodo is solving a real problem (AI agent framework for no-code platforms) and has early revenue to prove it. But nobody outside the community knows it exists. Alexis writes a detailed "How Nocodo works" technical deep-dive — the kind of content that gets shared in AI/developer communities and turns into warm inbound. The intro video is a great raw material.
Email 1Day 1nocodo case study — $1100 deal, real story
Hey, Saw the second early adopter close at $1100. That's real traction with a real story behind it. The problem is nobody outside your community knows about it. A "here's what Nocodo actually does, here's who's paying for it" case study — written for the AI developer crowd — would be a meaningful distribution push. I can write it. Your intro video + the early adopter story are great raw material. Interested? Alexis (@frenchfounder)
Email 2Day 7agent frameworks are about to get crowded
Hey, The agent framework space is about to get a lot more competitive. The window for "first to be known" is open right now. One thing that would help: getting Nocodo into the "how I built X with Y agent framework" conversation on X and Hacker News. Developers who are evaluating frameworks pay attention to those posts. Happy to help draft one. You'd review it for accuracy, I'd handle the writing and submission. Alexis
Email 3Day 14last one
Hey, Last email. The case study offer stands. One thought: the IMAP integration you shipped is actually a differentiator — most agent frameworks don't have native email. Worth calling that out loudly in your positioning. Alexis hello@alexisbouchez.com
"Made the decision to move forward with shipping Parallel Agents as a freemium VSCode extension." Also launched agent-worktree-trace (tracks files changed by AI agents). Building Flocker (real-time agent observability dashboard). Job hunting in parallel. Building in London.
Three distinct tools (Flocker, Parallel Agents, worktree-trace) with no discoverability. Alexis writes a "How I track my Claude Code agents" post featuring all three tools, submits to Hacker News / dev.to / X, drives GitHub stars and VSCode Marketplace installs. The audience is exactly right — Claude Code developers who want visibility into what their agents are doing.
Email 1Day 1acyc.ai + the discoverability gap
Hey, The agent-worktree-trace extension and Flocker dashboard are genuinely useful — I can see exactly what problem they solve. The gap: Claude Code developers who need this don't know it exists yet. I want to write a "How I track what my agents are actually doing" post featuring your tools. Publish to Hacker News + dev.to + X. I do the writing, you get the GitHub stars. Worth doing? Alexis (@frenchfounder)
Email 2Day 6freemium VSCode extensions need this
Hey, For freemium VSCode extensions, the path to paid is: useful → visible → trusted → paid. You have "useful." The gap is "visible." A strong presence in the Claude Code community channels (Discord, Slack, Reddit r/ClaudeAI) — not spammy, genuinely helpful posts that mention the extension — is what moves people through that funnel. I can help set that up. Happy to draft the first few posts. Alexis
Email 3Day 14last one
Hey, Last email. Genuinely think the tooling you're building at Acyc.ai is the right bet. Agent observability is going to be a real category. If you want help with the developer awareness piece when the job hunting stabilizes, I'm at hello@alexisbouchez.com. Alexis
"ACTUALLY SECURE platform to interact with your remotely running Claude Code sessions from your phone." Open-sourced seamless-claude (background context compaction) and claude-code-timelog. EU infrastructure, pgBackRest backups, Wazuh HIDS. SOC2-minded.
The "ACTUALLY SECURE" framing is a strong differentiator — especially for regulated industries (fintech, healthcare, legal) where running Claude Code on unmanaged infrastructure is a compliance risk. Alexis helps write the compliance-first narrative: what Bothy does differently, what risks it eliminates, and why "secure" matters more than "easy" for this buyer. Gets Bothy in front of CTOs and security-conscious engineering leads.
Email 1Day 1bothy.ai + the enterprise angle
Hey, The "ACTUALLY SECURE" positioning for Bothy is smart — and underused. There's a whole segment of engineering leads who can't use standard AI coding tools because of compliance requirements. Fintech, healthcare, legal. They're actively looking for exactly what you're building, but they won't find it unless you speak their language. I can help write a compliance-first landing page variant (SOC2-readiness, EU data residency, audit trail). Worth a conversation? Alexis (@frenchfounder)
Email 2Day 7seamless-claude + the missing narrative
Hey, The seamless-claude open-source project is genuinely useful (background compaction is a real pain). But the GitHub README is doing all the work — there's no "here's why I built this, here's the problem it solves" story. A 500-word "how I stopped context window anxiety from ruining my Claude Code sessions" post would get 10x the GitHub stars. Happy to help write it from the README + your notes. Alexis
Email 3Day 14last one
Hey, Last email. The EU secure infrastructure angle for Bothy is a real competitive moat — most Claude Code tools are US-hosted and don't care about GDPR. Worth making that much louder in your positioning. If you want help thinking through the enterprise GTM at some point, I'm at hello@alexisbouchez.com. Alexis
"Wake up to my project being on the front page of Hacker News. The API ran out of credits due to the traffic surge." 71 messages, most active shipper. 25+ projects. Featured in TechCrunch, Engadget, Gizmodo. Built emojistime.com, pulsefeedback.io, "Things AI Say."
The HN front page hit proved the demand is real — but the API credit failure means the traffic converted to nothing. The fix isn't bigger credits, it's a viral loop: rate-limited free tier that works even when the paid tier is down + a "share your result" mechanic that turns HN visitors into organic distributors. Alexis designs the rate-limiting + sharing architecture.
Email 1Day 1waking up to HN front page then running out of credits
Hey Steven, That HN front page moment with the API credits running out — brutal timing. But also: it confirmed the demand is real. The fix isn't bigger API credits. It's a rate-limited free tier that works even when everything else is down, plus a "share your result" mechanic that turns that traffic into something permanent. I can help design that system. The emojistime traffic could compound instead of just spike. Alexis (@frenchfounder)
Email 2Day 6the 25 projects thing
Hey Steven, Building 25+ projects is impressive but also means none of them get the distribution they deserve. One thing that helps: a personal hub that cross-links all your projects and builds cumulative SEO. "Steven Irby's internet lab" or whatever — the kind of page that makes journalists say "this person is prolific" and link to everything at once. You've already been in TechCrunch, Engadget, Gizmodo. A few well-placed links to that hub would do more than individual product launches. Happy to help build it. Alexis
Email 3Day 14last one
Hey Steven, Last email. The rate-limiting / viral loop offer stands for whichever project gets the next HN hit. One thing I'd flag: pulsefeedback.io and Palmframe (which I built) are solving adjacent problems from different angles. Might be worth comparing notes at some point. Alexis hello@alexisbouchez.com
"Finished building Custom rules. Created 2 new landing pages with different value propositions. Created 3 X lists for accounts to engage with consistently to help build my audience on X." FT backend engineer, chronic "shiny object syndrome."
The best marketing for a tool that grows X audiences is using that tool publicly and documenting results. Alexis proposes a 30-day "XreplyAI in public" experiment: use XreplyAI to grow Alexis's own X account, document the results weekly, publish. Provides social proof from a real user + distribution through Alexis's audience. No paid spend, no ads — just demonstrated value.
Email 1Day 1use xreplyai to sell xreplyai
Hey, XreplyAI is a tool that grows X audiences. The best way to sell that is to demonstrate it growing a real X account — publicly. I want to use XreplyAI on my own account for 30 days and document the results weekly. If it works (and I think it will), I publish the results and drive you qualified signups. If it doesn't, you get honest feedback from a real user. I'll write the posts. You get the case study. Worth trying? Alexis (@frenchfounder)
Email 2Day 6the two landing pages thing
Hey, Running two landing page variants is the right instinct. One thing that would sharpen the test: adding a feedback widget (Palmframe or similar) to capture *why* people don't convert, not just how many. Conversion rate tells you what's happening. In-page feedback tells you why. The why is what you actually need to improve the copy. Happy to help set that up if useful. Alexis
Email 3Day 14last one
Hey, Last email. The 30-day public experiment offer stands. One thing: the "shiny object syndrome" admission you made in the community — building XreplyAI is actually an antidote to that if you focus it. The X audience you'd build while using your own tool becomes the distribution channel for everything else you make. Alexis hello@alexisbouchez.com
"Been grinding on this one for a while, feels great to have it out in the wild." Building AdApt (rewrites sponsor ad copy to match newsletter voice — ~50% improvement in click rates), Diet Tracker (PDF/Excel reports for dietitians), HeyPost Chrome extension, Newsletter Growth Playbook audit service.
AdApt is the most interesting of the products — 50% improvement in sponsor ad click rates is a strong claim with a clear B2B buyer (newsletter operators who run paid sponsorships). The problem is reaching them. Alexis uses community intelligence to identify the top 50 newsletter operators actively running sponsors and builds a targeted cold sequence specifically for them.
Email 1Day 150% better click rates — that's a real claim
Hey, AdApt's "50% improvement in sponsor click rates" is a genuinely strong claim. The problem is the newsletter operators who need it most probably haven't heard of it. I just built a community intelligence tool that identifies warm leads from Slack communities and Discord servers. I can run it on the newsletter/creator communities and surface the operators who are actively running sponsors + complaining about ad performance. That's your first 50 targeted prospects. Interested? Alexis (@frenchfounder)
Email 2Day 6the newsletter growth playbook angle
Hey, The Newsletter Growth Playbook audit service you launched — that's actually a great AdApt distribution channel. Clients who come for the audit and discover their sponsored content is underperforming are a natural AdApt upsell. Packaging it as "audit + fix" (audit finds the problem, AdApt fixes it) would make the ROI obvious and the upsell frictionless. Happy to help write the combined pitch. Alexis
Email 3Day 14last one
Hey, Last email. The prospect list offer stands for AdApt whenever you want to run the outreach. One thought: you've got 4 products across different verticals. The energy is there — but a single "newsletter tools" positioning for all of them (Diet Tracker is the odd one out) might compound better than running them separately. Alexis hello@alexisbouchez.com
"I'm a senior developer based in London. I currently work for NYSE, but I build loads of little side projects." Shipped: in-voice.co.uk (web freelancer invoicing), webdevherts.co.uk, MarketHours (macOS menu bar app showing when global markets are open/closed). Asking about macOS self-distribution — never done it before.
macOS self-distribution without App Store is hard to get right — pricing, discovery, licensing, updates. Alexis builds a Gumroad/Paddle listing for MarketHours with proper indie app metadata + submits it to the communities where traders and finance folks hang out (FinTwit, Reddit r/algotrading, finance Discord servers). The NYSE background adds credibility.
Email 1Day 1markethours + the trader community angle
Hey, MarketHours is a genuinely useful macOS app for traders — knowing when markets are open without checking multiple sites is a real pain. The self-distribution question you asked: the trick is not to try to find all traders everywhere, but to go deep in one community first. r/algotrading on Reddit is 400k+ people who care about exactly this. A "I built this for myself, here it is" post there would do more than any App Store listing. Happy to help write and submit it. Alexis (@frenchfounder)
Email 2Day 7the NYSE angle is underused
Hey, "Built by a developer who works at NYSE" is actually a strong credibility signal for a finance app. It means you understand real trading workflows — not just the surface level stuff. That context should be front and center on MarketHours's landing page and in every community post. Right now it's invisible. Happy to help rewrite the copy with that angle. Alexis
Email 3Day 14last one
Hey, Last email. The community distribution offer stands for MarketHours. One thing worth knowing: Paddle (for macOS licensing + payments) has much better global pricing flexibility than Gumroad for a tool that traders worldwide would use. Alexis hello@alexisbouchez.com
"Completed first pass at redoing my marketing site with 53 programmatic SEO pages and a perfect lighthouse score." Got Reddit scraping APIs working with captcha solving. Building a free tools directory for SEO. Asking about affordable keyword research tools.
Browsable creates scraping APIs by reverse-engineering webpages. The most valuable marketing for this is showing developers exactly how to use it for high-demand use cases. Alexis writes 3 technical tutorials: "Scrape LinkedIn profiles with Browsable", "Scrape Amazon product data in 5 minutes", "Scrape Reddit for market research." These rank for high-traffic developer queries and are natural link magnets.
Email 1Day 1browsable + three tutorial ideas that would rank
Hey, Browsable's 53 programmatic SEO pages is smart. But the highest-traffic developer queries for scraping tools aren't about the tool — they're about the target. "How to scrape LinkedIn with [tool]" gets searched thousands of times a month. So does Amazon, Reddit, Twitter. Three tutorials targeting those queries specifically would drive more qualified traffic than 53 generic pages. I can write them. You'd review for technical accuracy. Interested? Alexis (@frenchfounder)
Email 2Day 6the reddit scraping timing is perfect
Hey, Getting Reddit scraping working with captcha solving right now is good timing — Reddit's API crackdown made scraping much harder and a lot of developers are looking for alternatives. A "how I scrape Reddit in 2026 (without the API)" post would hit HN and r/selfhosted pretty well right now. The Browsable use case writes itself. Happy to draft it from your implementation notes. Alexis
Email 3Day 14last one
Hey, Last email. The tutorial series offer stands. One thought: keysearch.co is fine for surface-level keywords but Ahrefs is worth it once you're seeing real traffic from the programmatic pages. The long-tail data quality difference is significant. Alexis hello@alexisbouchez.com
"We now deliver 20 scroll-stopping ads for ecommerce brands in 48 hours. Money back if ads don't outperform your current best within 14 days." Using Claude Code: sales transcripts → quotes → CSV → Figma → launch in 30 mins. Beauty industry ecommerce background (L'Oréal).
Copixel's Claude Code workflow (transcripts → CSV → Figma → ads in 30 mins) is a genuinely novel production system. Packaging it as an open-source Claude skill demonstrates technical depth, gets shared by the Claude Code community, and positions Copixel as the agency that actually knows how to use AI — not just claim to. Alexis formalizes and publishes the workflow.
Email 1Day 1that claude code workflow deserves more attention
Hey, The sales transcripts → quotes → CSV → Figma → launch in 30 minutes workflow you described — that's a genuinely novel production system for an ad agency. Most AI ad agencies just say "we use AI." You can show exactly *how*. Packaging that workflow as an open-source Claude skill would get shared in the Claude Code community and position Copixel as the agency that actually understands AI production. I can help formalize and publish it. Interested? Alexis (@frenchfounder)
Email 2Day 6the L'Oréal credibility signal
Hey, "Beauty industry ecommerce background including L'Oréal" should be on the Copixel homepage above the fold. It's the exact signal beauty brands need to trust an AI ads agency. Right now most ad agencies look the same. The L'Oréal / beauty expertise differentiator makes the ICP obvious and the conversion easier. Happy to help rewrite the positioning copy with that front and center. Alexis
Email 3Day 14last one
Hey, Last email. The Claude skill packaging offer stands. One thing: the money-back guarantee is strong but the 14-day window is short for B2B. Ecommerce brands often need 30 days to test properly. Might be worth revisiting that framing. Alexis hello@alexisbouchez.com
"One of my biggest and earliest customers turned off the auto-drafting feature a couple of weeks ago. I reached out and didn't get a response. I dreaded they were planning to leave." HubSpot Marketplace listing approved. Describes watching behavioral signals before a customer churns.
The scenario described is exactly the nightmare — a big customer goes quiet, turns off a key feature, stops responding. Palmframe embedded in the product would have caught the signal earlier: in-product feedback showing dissatisfaction before the feature got turned off. Alexis sets up a Palmframe-based early warning system — micro-surveys triggered by engagement drops, feature disablement, or login frequency changes.
Email 1Day 1the customer who turned off auto-drafting
Hey, The story you shared about your biggest customer turning off auto-drafting with no explanation — that's the kind of thing that's easy to miss until it's too late. I built Palmframe (palmframe.com) specifically for this: a feedback widget that captures in-product signals before users disengage. Triggered on feature disablement, session drops, anything you want. You'd have known something was wrong a week earlier. Happy to set it up for you. Alexis (@frenchfounder)
Email 2Day 6HubSpot Marketplace + in-product feedback
Hey, Congrats on the HubSpot Marketplace approval — that's a real distribution channel. One thing worth doing before the traffic picks up: instrumenting your onboarding with feedback checkpoints. HubSpot users who install and don't activate in 72 hours are almost never coming back. Catching them before they churn (even a single "what's missing?" prompt) changes the math. Palmframe takes 5 minutes to add. Happy to help with placement strategy. Alexis
Email 3Day 14last one
Hey, Last email. The Palmframe offer stands. One thing I've been thinking about since you shared that story: the customer who doesn't respond is scarier than the customer who complains. At least the complainer is still engaged. The DHH trick you mentioned for LLM feedback is smart. Works for real humans too — framing helps. Alexis hello@alexisbouchez.com
"Launched contentboo.st V2 beta in stealth mode. Validating with private demos and handling onboarding manually. Just landed my first client at [price]." Simplifying onboarding experience. Architecture rebuilt to handle multiple clients. $636 MRR.
Manual onboarding is the bottleneck. Every new client requires hands-on time, which caps growth at founder bandwidth. Alexis builds a proper self-serve onboarding flow — in-product setup wizard, contextual help, automated check-ins — so ContentBoost can scale from 1 client to 10 without adding hours. Palmframe tracks where people get stuck.
Email 1Day 1manual onboarding is the growth ceiling
Hey, Manual onboarding made sense for validation. But $636 MRR with a V2 means you're ready to scale — and you can't do that if every new client needs a demo call and a hand-holding session. I can build a self-serve onboarding flow for ContentBoost: in-product setup wizard, automated check-ins, feedback capture for people who get stuck. Turns onboarding from founder-time into product-time. Worth building together? Alexis (@frenchfounder)
Email 2Day 7the gov proposal angle
Hey, You mentioned working on a gov proposal alongside ContentBoost. Government contracts are a meaningful revenue diversification if the procurement process isn't too slow for your timeline. One thing that helps: a "how ContentBoost handles enterprise compliance" one-pager. Government buyers need to understand data handling before they'll move forward. Happy to help write it if the proposal is still live. Alexis
Email 3Day 14last one
Hey, Last email. The self-serve onboarding build offer stands. One thing: the "getting back on Twitter" entry in your logs — worth it. ContentBoost is a marketing tool. The founder being visible on marketing channels is credibility for the product. Alexis hello@alexisbouchez.com
"I founded bullet.to, a minimal iOS/Android/web planner back in 2020 and went full time on it 2 years ago. Living remote in Thailand." Switched from Notion marketing brain to Claude-based. Planning AI features for Q1. Deployed new markdown rich text editor. Redesigning onboarding screens.
"Minimal planner adds AI that doesn't bloat the experience" is a compelling product story that Notion and other productivity tools can't tell because they're already too complex. Alexis helps write the AI features launch narrative — specifically targeting the "anti-Notion" community who moved to Bullet for simplicity and will care deeply about how AI is added.
Email 1Day 1minimal planner + AI = a story nobody else can tell
Hey Hamish, "Minimal planner adds AI without becoming bloated" is a narrative that Notion, Obsidian, and every other productivity tool can't tell right now — they're all going bigger, not smaller. You've been building since 2020, gone full-time, and you're still minimal. The AI features you're planning for Q1 are actually a major story if framed right. I can help write that launch narrative. Worth a conversation? Alexis (@frenchfounder)
Email 2Day 6the Thailand remote angle
Hey Hamish, The "solo founder, fully remote in Thailand, full-time on a minimal planner for 2 years" story is genuinely interesting to the Indie Hackers / bootstrapper crowd. A "2 years in, here's what I've learned" post would drive real traffic to Bullet and build the kind of trust that converts better than any ad. You've got the story — it just needs to be written. Happy to help draft it from a conversation. Alexis
Email 3Day 14last one
Hey Hamish, Last email. The AI launch narrative offer stands. One thought: the "flutter rich text editors are all buggy" problem you solved for Bullet — that's worth a dev.to post on its own. Other Flutter developers have the same problem and would appreciate the solution. Alexis hello@alexisbouchez.com
"Talk To HR is an HR system that runs purely in Slack or Discord that you just talk to. No portals, no logins, no forms." Building with wife Emily. Features shipped: monthly UK payroll agent, versioned employment contracts, Slack interactive elements, Google Calendar sync for leave.
The ICP is precise: UK startups with Slack, 10-50 employees, no dedicated HR person yet. Alexis builds the targeted prospect list (recently funded UK startups, LinkedIn + Companies House data) and writes a cold email sequence specifically for this buyer — "you're using Slack for everything, HR shouldn't be different." First 50 prospects + sequences delivered.
Email 1Day 1talk to hr + the UK startup ICP
Hey Adrian, Talk To HR's ICP is actually very precise: UK startups that run on Slack and haven't hired an HR person yet. That's a targetable list. I can build it: recently funded UK startups (Companies House + LinkedIn), 10-50 employees, Slack-heavy. First 50 prospects with context + a cold sequence written specifically for this buyer — "you're using Slack for everything, HR shouldn't be different." Worth doing? Alexis (@frenchfounder)
Email 2Day 6the UK payroll differentiator
Hey Adrian, The UK payroll agent you shipped is a meaningful differentiator — UK payroll is genuinely complex (PAYE, NI, pension auto-enrolment) and most HR tools either don't do it or do it badly. That feature should be front and center in your positioning for UK startups. "HR in Slack, including proper UK payroll" is a sentence that no US-built HR tool can honestly say. Happy to help rewrite the landing page copy around that. Alexis
Email 3Day 14last one
Hey Adrian, Last email. The prospect list offer stands. One thing worth noting: the "built with my wife" angle is actually a trust signal for HR software. Buying HR tools requires trusting the people behind them. A founder story on the homepage would help with that. Alexis hello@alexisbouchez.com
"I work in CRO/AB Testing/Experimentation at a Fortune 150. Out of my own necessity I built this B2B software for both me and my analyst. I have not done any B2B marketing at all. I'm not sure which strategy is best — ABM? LinkedIn outreach?"
Atticus has Fortune 150 CRO expertise but has never done B2B sales — he literally said so. Alexis uses community intelligence to identify the 10 ideal customers for Growthlayer (growth-stage startups $500k-$5M ARR with A/B testing needs, currently using spreadsheets or basic tools), writes personalized outreach for each, and delivers a "B2B cold outreach 101 for CRO tools" playbook.
Email 1Day 1growthlayer — your first 10 ABM targets
Hey Atticus, You said you have no idea which B2B marketing strategy to start with. The answer for Growthlayer specifically is ABM — you have a precise ICP (companies running experimentation with an analyst, probably $500k-$5M ARR) and it's a small enough list to do manually. I can identify the first 10 ideal targets from community data + LinkedIn and write personalized sequences for each. It's how you get from "built this for myself" to "first paying customers." Worth doing? Alexis (@frenchfounder)
Email 2Day 6the Fortune 150 angle
Hey Atticus, "Built by someone who runs experimentation at a Fortune 150 company" is a powerful credibility signal for Growthlayer. The target buyers are growth teams who want enterprise-grade experimentation at startup prices. That context should be prominent in your positioning. Right now it's buried. A "why I built this" page that leads with the Fortune 150 background would convert better than a generic features list. Happy to help write it. Alexis
Email 3Day 14last one
Hey Atticus, Last email. The ABM list offer stands. One thing: the "anti-guru" post you mentioned writing is actually a good Growthlayer marketing move. The people who hate growth gurus are exactly the people who'd pay for a serious CRO tool built by a practitioner. Alexis hello@alexisbouchez.com
"Signed up three dental clinics to pilot the v1 of some patient intake software (name TBD it's so early) in exchange for actual real money, baby steps." Led product design at Cado Security through acquisition by Darktrace. Asking about backend architecture decisions to minimize future rework.
3 paying dental clinic pilots is remarkable early traction — most founders can't get one. But "name TBD" at the pilot stage means the naming/positioning problem needs to be solved before they accidentally build toward the wrong market. Alexis offers a naming + positioning workshop: patient intake vs. practice management vs. dental CRM — each is a different buyer, different price point, different sales motion.
Email 1Day 1three paying dental pilots before you have a name — that's the dream
Hey, Three dental clinic pilots paying actual money before you've even named it — that's genuinely impressive traction. The "name TBD" is actually a problem you should solve now, before you build further. Patient intake vs. practice management vs. dental CRM are three different buyers, three different prices, three different sales motions. The wrong positioning will mean you attract the wrong customers even if the product is right. I can help work through the naming + positioning quickly — a 60-minute call and a one-pager. Worth it before you go further? Alexis (@frenchfounder)
Email 2Day 7the Darktrace acquisition credibility
Hey, The "led product design at Cado Security through acquisition by Darktrace" background is meaningful for a healthcare SaaS. Security + compliance expertise is exactly what healthcare buyers need to feel before purchasing. That credibility should be in your pitch from day one. Dental clinics are increasingly worried about patient data security (GDPR in EU, HIPAA in US). Your background lets you address it credibly. Happy to help work that into your pitch deck. Alexis
Email 3Day 14last one
Hey, Last email. The naming/positioning offer stands whenever you're ready. On the architecture question you asked about — the answer for healthcare is almost always "handle compliance first, optimize later." Multi-tenant data isolation, audit logs, and encryption at rest are not things you want to retrofit after your 10th clinic. Happy to think through the specific decisions if useful. Alexis hello@alexisbouchez.com
"Shipped a lander for my new project www.clipform.io (vibe coded on and off for the last 6 months). A user that first did a free trial 2.5 years ago has just signed up — PMF in sight?" Using Remotion + Claude Code to build a social media marketing skill. Based in Hoi An, Vietnam.
The Remotion + Claude Code social media production workflow Clipform has built is actually a great open-source Claude skill waiting to happen. Formalizing and publishing it as a skill drives discovery from the Claude Code community — developers and marketers who see the skill see Clipform as the tool that made it. The 2.5-year trial conversion also proves there's latent demand that just needs activation.
Email 1Day 1the 2.5-year trial signup is a signal worth chasing
Hey, A user who signed up for a free trial 2.5 years ago finally converting — that's a strong signal. It means the problem they signed up to solve didn't go away. It means your solution finally matched their moment. The question is: how many more are like them? I can help build a re-engagement sequence targeting everyone who ever touched Clipform but didn't activate. They're warm — they just need the right prompt. Interested? Alexis (@frenchfounder)
Email 2Day 6the remotion + claude code workflow
Hey, The Remotion + Claude Code social media production workflow you've been building — that's a genuinely interesting technical approach. Most social media tools don't use programmatic video at all. Packaging it as an open-source Claude skill and publishing it would drive discovery from the Claude Code developer community. They'd find the skill, see what Clipform does, and convert. Distribution with zero ad spend. I can help formalize and write the skill documentation. Would that be useful? Alexis
Email 3Day 14last one
Hey, Last email. Both offers stand — re-engagement sequence + Claude skill documentation. The Hoi An setup sounds nice. The remote-while-building thing + a finally-converting old trial user + a product you've been vibe coding for 2.5 years feels like a good moment. Alexis hello@alexisbouchez.com
"My goal is to figure out a GTM strategy as well as a working sales/pricing model. I'm trying to reach out more and more to potential clients now." Spent 3 years building RecordRanks — a sports competition organization and ranking platform, live as cubingcontests.com (speedcubing). Just finished a massive backend rewrite. First ever paying customer just signed; deploying in May. Full-stack Next.js + self-hosted Supabase. Moving from Warsaw to UK.
RecordRanks' real distribution unlock is federations — one national federation adopts it and every club beneath it converts automatically. The speedcubing proof (cubingcontests.com) is a working case study nobody has packaged yet. Five angles worth exploring: (1) Federation outreach pipeline — identify 10 national federations most likely to adopt, write tailored pitches; (2) Pricing model design — free-for-clubs / paid-for-federations tiered structure; (3) Landing page rewrite — currently speaks to developers, needs to sell to competition organizers; (4) Community distribution — speedcubing forums, chess clubs, table tennis Discord servers, each a warm channel; (5) Case study package — turn cubingcontests.com into a professional federation pitch deck with metrics.
Email 1Day 1recordranks + the federation angle
Hey Deni, Congrats on the first paying customer — that's genuinely the hardest one. There's a distribution angle RecordRanks has that most GTM approaches miss: sports federations. If one national federation (speedcubing, table tennis, chess, whatever) mandates your platform, every club beneath them converts automatically. You don't sell 50 clubs — you sell one federation. cubingcontests.com is your proof it works. That's a case study waiting to be written. I can help identify the 10 most-likely federations to approach, write the pitches, and package the case study. Interested? Alexis (@frenchfounder)
Email 2Day 6the pricing model question
Hey Deni, The GTM + pricing question you raised — here's the frame I'd use: Free for small clubs (under 100 competitors). Paid for federations and larger organizations. The free tier builds grassroots adoption; federations see their member clubs already using it and the upgrade is a natural ask. It also means your sales motion is simple: you're not selling 50 clubs one at a time, you're selling one federation at a time. The backend rewrite you just finished is actually a re-engagement hook — "we rebuilt everything, we're now federation-ready" is a real reason to go back to anyone who said no before. Happy to work through the full pricing structure. Alexis
Email 3Day 14last one
Hey Deni, Last email. The federation pipeline offer stands whenever you're ready. One thing: your landing page currently reads like a developer wrote it for other developers. Competition organizers and federation directors don't care about "self-hosted Supabase" — they care about "results are live in minutes, rankings update automatically, records are tracked forever." Same product, different words. That rewrite is a one-day job and probably moves conversion more than anything else right now. Alexis hello@alexisbouchez.com
"I'm currently building Tibbie, a pay-as-you-go social media scheduler. I've also built a few WordPress plugins, including one acquired by Automattic." "I'm more developer than designer." Looking for feedback on social scheduling UX — asking the community what they love/hate about their current schedulers.
"More developer than designer" is an honest admission that's also a clear gap. Alexis does a 2-hour UX review of Tibbie's key flows + sets up Palmframe to capture ongoing user feedback. The pay-as-you-go model is a genuinely interesting differentiator (subscription fatigue is real) — the design just needs to communicate that value clearly.
Email 1Day 1tibbie UX review — developer-to-developer
Hey Daniel, "More developer than designer" — same. The problem is that with a social media scheduler, the UX *is* the product. If scheduling a post feels awkward, people churn regardless of how clean the code is. The pay-as-you-go model is genuinely differentiated. Most social schedulers have subscription fatigue baked in. But that story needs the UX to tell it. I can do a 2-hour UX review + set up Palmframe for ongoing user feedback. Worth it? Alexis (@frenchfounder)
Email 2Day 6the automattic acquisition story
Hey Daniel, "Built a WordPress plugin that Automattic acquired" is actually a meaningful trust signal for Tibbie — it means you know how to build tools people use at scale, and you know what quality looks like. That story should be on Tibbie's about page. Especially for WordPress users who are already in your world via Autoblue. The continuity of "Daniel builds tools WordPress people love" is a strong narrative. Happy to help write it. Alexis
Email 3Day 14last one
Hey Daniel, Last email. The UX review offer stands. One thing: the community question you posted about what people love/hate in social schedulers — that's actually a great Tibbie marketing move. Synthesizing the responses into a "we built Tibbie to fix exactly these things" post would be genuine product marketing. Alexis hello@alexisbouchez.com