# Pushcast — Launch-Day Social ## X / Twitter thread **Post 1 — hook variants (lead with C):** - **Variant A (benefit):** I built a tool that turns every git push into marketing. Connect a repo, it reads your code, and drafts your launch posts — you approve them in one screen. It's called Pushcast and it's live today. 🧵 - **Variant B (question):** Every marketing tool asks for your landing page URL. But the truth of what you built lives in your repo — so why is nothing reading it? That's the whole idea behind Pushcast, live today 🧵 - **Variant C (story/identity) — ✅ lead:** I can ship software. I freeze at the blank tweet box. So I built the thing I needed: it reads my repo, figures out what my product actually does, and writes the marketing I keep avoiding. Launching Pushcast today 🧵 **2/** Most marketing tools start from a landing page or a paragraph you have to write — marketing copied from marketing. Pushcast starts from the codebase: the ground truth of what your product actually does. **3/** Connect a repo (read-only). It walks the code *in memory*, runs a secrets denylist, and discards raw file contents. What it keeps is a "Product Brain" — your features, integrations, ICP — where every claim cites the exact file it came from. Code is read, not stored. **4/** From that Brain it generates the stuff I hate doing: positioning, landing copy, a Product Hunt package, social threads, an email sequence, a 30-day calendar. Specific to what I built — not generic template copy. **5/** Then it stays on. A webhook classifies each push; user-facing changes become drafted posts. Marketing becomes a 10-minute weekly review, not a second job. Nothing posts without me — draft by default, autopilot only per channel when I flip it. **6/** The recursive part: this thread, Pushcast's positioning, and its launch kit were generated by Pushcast, from Pushcast's own code. I'm customer zero of my own tool. **7/** It's early and honest about its edges. If you can ship but can't get anyone to look — let it read one of your repos. Free to see what it finds → [link] --- ## LinkedIn A year of watching good products sink because nobody knew they existed taught me something: solo developers don't have a marketing problem, they have a translation problem. The truth of what they built lives in the repo — and no marketing tool reads it. So I built Pushcast. You connect a repo, it reads the code to understand your product (storing facts, never your code — that part is enforced in the codebase, not promised on a page), and it generates your positioning and a full launch kit from what you actually shipped. Then every push becomes drafted posts waiting in a ten-minute weekly review. You approve; nothing goes out on its own. It's launching today, and it's dogfooding itself — its own marketing runs through its own pipeline. If you've ever shipped something you were proud of and then watched it disappear, I'd love for you to try it on one of your repos. → [link] --- ## Reddit drafts (do not auto-post) > ⚠️ DRAFTS ONLY. Reddit autoposting is account suicide. Post by hand, from an account with history, following each subreddit's self-promo rules, and disclose you're the maker. One-click copy only. ### r/SideProject (or r/indiehackers) **Title:** I built a tool that reads your repo and writes your marketing — launching today, would love your brutal feedback I'm a solo dev and I made this for myself, so mods/forgive the self-promo. The problem: I can build anything but I'm useless at marketing, and every tool wanted a landing-page URL instead of looking at what I actually built. Pushcast connects to a repo (read-only), reads the code *in memory* — secrets denylist first, raw code discarded — and builds a "Product Brain" where every feature cites the file it came from. Then it generates positioning + a launch kit, and turns each push into drafted posts you approve in one screen. Code is read, not stored (it's enforced in the Mapper). It's dogfooding itself — its own launch kit was generated by itself. Genuinely want to know where it's wrong or thin. Happy to let it read one of your repos and show you the Brain. ### r/devtools (or r/programming for the privacy-architecture angle) **Title:** How we made "your code is read, not stored" an architectural guarantee, not a privacy-policy line Maker here. The hardest objection for a repo-connected tool is "what happens to my code." Our answer is structural: the Mapper streams files in memory, runs a gitleaks-style denylist before anything reaches a model, extracts structured facts + file paths, and discards the raw bodies — nothing code-shaped is persisted or sent to a model. Happy to talk through the stream-and-discard boundary, the denylist ruleset, or the short-lived GitHub token model.