Engineering notes / Muhammad Kashif
Ship Ugly, Sell Specific: What I Copied From a Million-Dollar Month
Blake Anderson went from broke to roughly a million dollars a month in eighteen months with three ChatGPT-powered apps. I do not need his revenue to learn from his playbook. I need the pattern: stand where a cultural tre…
Ship Ugly, Sell Specific: What I Copied From a Million-Dollar Month
By Muhammad Kashif · Draft · AI automation & cybersecurity builder, Pakistan
Blake Anderson went from broke to roughly a million dollars a month in eighteen months with three ChatGPT-powered apps. I do not need his revenue to learn from his playbook. I need the pattern: stand where a cultural trend meets a tech shift, ship something people already want to screenshot, and explain the product in one line.
Here is how I translate those notes into builds I would actually attempt from Pakistan.
RizzGPT / Plug AI: intercept a behavior people already do
The product idea is almost insultingly simple: screenshot a chat, get a suggested reply. It works because dating anxiety plus always-on messaging was already a habit. The model did not create the habit. It inserted itself into it.
When I look for ideas now, I ask: what do people already photograph, forward, or paste into a notes app in a panic? That is the wedge. A five-minute pitch that needs slides is usually dead on arrival — the notes call this the one-liner test. If I cannot say the product in one sentence, I do not open the builder yet.
Umax: make the output shareable on purpose
Umax rates a selfie across twenty-plus traits and suggests improvements. People shared the screenshots. Those screenshots became free ads. Revenue stepped from about a hundred thousand a month toward half a million as the loop compounded.
For builders, the lesson is distribution baked into the artifact. I now ask whether the default output of a tool wants to be posted. A private PDF report rarely spreads. A vivid, slightly competitive scorecard might.
Cal AI: remove a tedious habit instead of adding a dashboard
Cal AI does photo-based calorie tracking. It wins by deleting friction, not by adding charts. That is the product taste I want in automation work too: if the workflow needs a training manual, it is probably not ready for non-technical users.
The playbook I wrote on my whiteboard
Find an obsession or an insecurity people already talk about. Build fast and ship ugly. Obsess over distribution. Be specific when you prompt the builder — vague prompts create vague products.
The notes also point at Claude Code-style builders as the start of a no-code (or low-code) stack, with starter ideas like an AI data logger. My version of “ship ugly” is a private beta for three friends, not a polished landing page for nobody.
How I would run a thirty-day attempt
- Write ten one-liners. Kill anything that needs a paragraph of context.
- Pick the line that intersects a trend I can see in local chats — freelancing, exam prep, small-business invoicing, family group-chat chaos.
- Build a thin slice with ChatGPT or Claude Code: one screen, one magic moment, one shareable output.
- Give it to ten people. Measure whether they return without me nudging them.
- Only then spend time on branding.
Prompting the builder like a product spec
The notes stress specificity when prompting the builder. My template is narrow: who the user is in one sentence, the single action on the first screen, the output they can share, and what we are explicitly not building in version one. Claude Code-type tools respond better to that than to “make an AI app for students.”
I also time-box the ugly ship to seventy-two hours. If there is no tap-able demo by then, the one-liner was probably wrong — not the model.
When I borrow the Cal AI lesson for B2B, I look for paperwork people hate: expense photos, contract clause highlights, screenshot-to-ticket for buggy portals. Same removal of tedium, different market.
What I refuse to copy
I will not copy dark patterns around body image or dating pressure just because they monetize. The mechanism — habit intercept, shareable output, ruthless specificity — transfers to healthier domains. An automation that screenshots a confusing bank SMS and explains the fee in plain language uses the same shape without the same harm.
Million-dollar months are rare. Clear one-liners and ugly ships are available every week.
None of this requires a million-dollar month. It requires a one-liner you believe, a seventy-two-hour ugly build, and the discipline to measure return visits before you polish the logo.