# Brand Kit ## Positioning > For the solo developer who can ship anything but can't get anyone to notice, Pushcast is a marketing co-founder that reads your repo — not your landing page — and turns every push into launch assets, content, and traction, with you approving everything before it goes out. ### Alternative angles - **The privacy-first repo tool (lead with trust)** — Connect your repo to a marketing tool without the dread: Pushcast reads your code and stores facts, never code — enforced in the Mapper, not promised on a page. - _tradeoff:_ Wins the developer's hardest objection up front and is hard to fake, but leads with a fear instead of the payoff — risks sounding like security software rather than growth, and buries the 'it gets your product' wow. - **The anti-marketer (lead with identity)** — You didn't start a company to write threads. Pushcast does the marketing a solo founder hates, from the code you already wrote. - _tradeoff:_ Resonates hard with the exact ICP and is very shareable, but defines the product by what the user avoids — easy to read as 'content spam button' unless the code-grounding and the approval loop are right behind it. - **The commit-driven engine (lead with the loop)** — git push is the only marketing skill you need. Every commit becomes drafted posts waiting in a 10-minute weekly review. - _tradeoff:_ Most concrete and demoable (the loop sells itself), but assumes the founder already values content cadence; undersells the one-time 'it read my code' moment that converts skeptics on day one. ## ICP profiles ### Primary: The shipping solo founder A technical founder building a real product alone — vibe-coder, indie hacker, or ex-engineer who left to build their own thing. Fluent in Git, Stripe, and a deploy pipeline; allergic to marketing-speak and growth-hacking decks. Has shipped something good and watched it sink because nobody knew it existed. Skeptical by default, especially about handing a repo to a SaaS. - **Pains:** Can build the whole product but freezes at the blank tweet box; Marketing tools want a landing-page URL or a paragraph they don't want to write — circular and shallow; No time and no team; marketing is the thing that always slips; Won't connect a repo to anything that might store code or read secrets - **Desires:** Traction without becoming a 'marketing person'; Proof the tool actually understands what they built; Control — review before anything is public, no autopilot they didn't unlock; Something that runs off the work they're already doing (shipping) ### Secondary: The no-code / outsourced-build founder A founder who shipped via Lovable/Bolt/Replit or an agency and has a working product but can't read its code fluently. Wants the same code-grounded marketing without a deep Git workflow — comfortable with the dashboard and the no-repo intake path. - **Pains:** Has a product but no clear story for what makes it different; Marketing advice assumes a team and a budget; Doesn't know what in the build is actually noteworthy - **Desires:** A credible launch without hiring an agency; Plain-language positioning derived from what was built; One screen to approve a week of content ## Voice - **Tone:** Talks to a peer who ships code — technical-credible, never condescending, Plain and concrete; shows the mechanism instead of claiming the outcome, Quietly confident, a little dry; lets the demo do the bragging, Honest about limits — names what it can't do yet - **Vocabulary:** repo, commit, git push, ship, the code, receipts, draft, approve, your product, evidence, with you in control, while you sleep - **We never say:** powerful / seamless / robust / cutting-edge (developer-repellent filler), growth hacking / 10x your reach / go viral, AI-powered as the pitch (the AI is plumbing; the code-grounding is the point), engagement / users / content as nouns about a person's launch, anything that implies posting without the founder's approval - **Examples:** - It reads your code. So it actually gets your product. - Build quiet. Ship loud. - Your code is read, not stored — enforced in the Mapper, not promised here. - git push is the only marketing skill you need. - Every claim cites the file it came from. ## Taglines - Build quiet. Ship loud. - The marketing co-founder for people who ship code. - It read your code. Now it can sell your product. - git push is the only marketing skill you need. - Your repo is the brief. - Marketing that starts from the code, not the landing page. - Code is read, not stored. - Every commit, into marketing — while you sleep. ## Elevator pitches **One sentence:** Pushcast connects to your repo, builds a code-level understanding of your product, and turns every push into launch assets and content you approve in one weekly screen. **One paragraph:** Every marketing tool starts from a landing page or a paragraph you have to write — shallow, circular inputs. Pushcast starts from your codebase, the ground truth of what your product actually does. It reads the repo (and stores facts, never code), builds a Product Brain where every feature cites the file it came from, and from that generates your positioning, a full launch kit, and ongoing posts drafted from real commits. Nothing goes out without you: drafts wait in a ten-minute weekly review, and you unlock autopilot per channel only when you trust it. **One page:** Solo developers can ship software but can't get anyone to look at it. Their product knowledge lives in the repo, and no marketing tool reads it — they all start from a landing page URL or a founder's typed description, which is marketing copied from marketing. Pushcast starts from the code. Connect a repo (read-only, per-repo) and a deterministic Mapper walks it — applying a secrets denylist and discarding raw file contents in memory, so what's kept is the Product Brain: structured facts, features, and the file paths that prove them. Every claim is auditable; a hallucinated path fails the run. From that Brain, Pushcast generates a Brand Kit (positioning with honest tradeoffs, ICP, voice) and a complete Launch Kit (landing copy, a Product Hunt package, social threads with hook variants, an email sequence, a press one-pager, a 30-day calendar) — specific to what you actually built, with no generic filler. Then it stays on: a webhook classifies each push, drafts posts from user-facing changes, and rolls the week into a digest that opens with the only question that matters — is it working? The whole thing is built around control and trust, because the buyer is a developer who will check. Code is read, not stored. Drafts never auto-publish. You approve from one screen and graduate channels to autopilot only when you're ready. Free to see what it reads; paid when you ship loud. [PLACEHOLDER: pricing — see open questions.] ## Handle Setup Wizard - `@pushcasthq` — The 'hq' suffix is reliably available when the bare name isn't, and reads as a product account, not a person. - `@getpushcast` — Verb-led, matches a likely getpushcast.com; clear call-to-action as a handle. - `@pushcast_dev` — Signals the developer audience directly; good for the X/GitHub dev crowd where the ICP lives. - `@pushcast` — The clean grab — claim it everywhere it's free; the broadcast double-meaning (push → cast) is the brand. - `@buildquietshiploud` — Tagline-as-handle for a platform where the name is gone; memorable and on-message, if long. **Setup checklist:** - Check the chosen handle across X, GitHub (org), LinkedIn, Bluesky, and YouTube in one pass — claim the same handle everywhere even where you won't post yet. - Lock the matching domain (getpushcast.com / pushcast.dev) and an email-from name that matches the handle. - If the bare name is taken on a platform, use one consistent modifier (hq / get / _dev) across all platforms, never a different name per platform. - Set the wordmark avatar + a one-line bio from the primary tagline on every profile. - Lead with GitHub and X — that's where the ICP already is; wire the OAuth connect for those first. - Reserve the handle now even on platforms you'll launch on later; squatting your own name is cheap insurance.