BOOM! Got my first sale even without an MVP
I was saying I’m gonna give people 10 free leads and then ask $30 for the next 10. But while falling asleep, I came up with the idea that $30 for 10 “potential” customers is too much, so I changed the price to $10.
I gave free leads to 8 people. So far I offered the next batch to 2 of them, and 1 bought it that same day. 2 views on the payment page, 1 sale hahaha
While giving people their leads, I was often asked if I used some tool to find them. So for me it means it’s time to start building the MVP and crush the market hehe.
The other 6 are still in the process. Will post every Thursday about the current product stage, so you’ll see how many of them pay.
Do you remember how you felt after your first sale?
@lakix0@tryCasi congrats on going live! send them the direct review link, it’s your App Store link with ?action=write-review at the end. it opens straight to the review screen, way more people finish it than when they have to find the button
@jyriso ha, fair catch, but Sequo is closed now, so no testimonials coming. for the next one I’ll start collecting from the first tester, and Testimoon is on my list
@itsthedonhashim every time something changes. at the end of each task the agent adds a line if it made or changed a decision, with the why, and I cut anything that’s no longer true. it stays short because old decisions get replaced, not piled up
@Sakshar2303 one idea for a next step: claims about things outside the repo, like “env var added” or “webhook updated”. that’s where most of my false “done” came from, and nothing in git can prove those. even just flagging them as “unverifiable, check by hand” would help
@SereneDesiree ha, Reddit loves a pivot. the trivia thing could still be useful as a hook though, “unlock your apps with trivia” is an easier first try than “make your own flashcards”, and then people stay for the study part
@Domlokyn my bad then, might depend on the region. in that case I’d reply in the Resolution Center and ask them to quote the exact guideline and what change would pass. Apple also runs “Meet with Apple” review sessions on the developer site from time to time, worth checking if one is open
@jscnjay honestly that’s the right kind of cave man. I let the agent write the migration, then read it and run it myself. it’s the one place where 2 extra minutes is always worth it
@imhstark same channels for me. how do you find the right people on X, searching for posts where they describe the problem, or replying under bigger accounts? that part takes me the most time
@GioStrives congrats on getting it live. now that real testers are on it, I’d set up a daily database backup before anything else. on a VPS nobody does it for you, and it’s the one thing you can’t fix later
@matt_teeixeira traffic was my hardest problem too. what finally worked was replying to people who already had the problem, not posting about the product. it’s slow, but every conversation compounds
@AlexTolson91 a cheap guardrail: a tiny check after deploy that loads the homepage and fails if the tracking ID isn’t in the HTML. build passing tells you nothing about what’s actually on the page
@yashagl that one hurts. if Polar lets you respond to the dispute, send usage logs showing he actively used the paid features both months. that’s the evidence banks look at, and it wins more often than people think
@Mr_Swiftly agree, average position gets misleading as you rank for more. I’d look at which of those long tail pages bring sign-ups and write more like those. 53 clicks is small enough to check them by hand
@karumatendai since they keep asking for the video, I’d add a short screen recording and a two-line description to the review notes before submitting. it often skips that first rejection round
@WalterAIBuilder what works for me is a tiny daily minimum, like one bug or one reply, so the bad days still count. the sprints still happen, but the minimum keeps the crash from turning into a week off