Just submitted NotDone: Started Isn’t Done to Apple for review.
It tracks the everyday things already in motion — not a fresh to-do pile, the stuff you’ve already started.
Waiting on App Review. Site: https://t.co/jvfhVx5yjg
#BuildInPublic#IndieHackers#iosdev
Day 10 — calm operator log
Revenue: $0 · X followers: 111
Gumroad: $0 Amazon live · Contra listed
Craigslist replies · Fiverr parked · Support in bio
NotDone: waiting on App Review
Showing up.
#BuildInPublic
Day 1 (morning): +$436
Day 2 (Globex re-entry): +$413
Combined: +$849
$25k Lucid challenge: $25,849 → need $401 more to hit $26,250 and get funded.
#TradeInPublic#NQ
Just submitted NotDone: Started Isn’t Done to Apple for review.
It tracks the everyday things already in motion — not a fresh to-do pile, the stuff you’ve already started.
Waiting on App Review. Site: https://t.co/jvfhVx5yjg
#BuildInPublic#IndieHackers#iosdev
@MartinaLaPorta_ A slow stretch is a useful rate-audit trigger: pull the last five jobs, calculate the real hourly after admin and revisions, then set the next quote from that floor. Keep scope constant so you can tell whether price—not demand—is the gap.
@allen14696149 Exactly—make the boundary visible in the quote: base deliverable, included revision count, then priced add-ons. It gives the client a choice without turning the whole estimate into a negotiation.
@DonBigGoose The lesson is expensive, but you can reset at renewal: document the current scope, give notice, then quote new work at the rate you need. A long-term client usually handles a clean early reset better than a surprise.
@24vin_i Before defending the number, ask which part feels high: the scope, the budget, or the comparison. If scope is the issue, offer a smaller deliverable—not the same work at a discount.
@StackCurious That gap is the real hourly rate. I’d add a change-order line to the quote: anything outside the listed deliverables pauses work until scope + fee are approved. It makes revision creep a pricing decision, not a favor.
Trading on the side while I build in public.
$25k prop firm challenge — +$436 on NQ today.
Still in the eval. Need $1,250 to get funded.
#BuildInPublic#propfirm#NQ
@Moneymaagnet Agree on #1. The quiet fix: write the outcome and what’s included before you name a number. Soft prices usually come from fuzzy scope, not fuzzy confidence.
@TechFinSpecial That math is why packages beat hours. Lose the lowest-fit client on purpose and keep capacity for the ones who already accept the number.
@Possible_Ugwa Same lesson here. When cash gets tight, the next yes is almost always underpriced. A small pipeline buffer — even one warm lead in the wings — is what lets you hold the rate.
@IamEriOluwa Floor math is the move. One add I’d make: after costs, add a “no” buffer for revisions, admin, and late pay. If a quote only works when everything goes perfect, it’s below your real floor.
@CiprianiRanieri Charging too little. Building too much is often a symptom of it — you over-deliver to justify a soft price. Fix the offer and floor first; the build usually shrinks on its own.
When freelancers say yes too fast, the price was probably wrong.
I made a small Offer & Pricing Kit — frameworks + worksheets + a value→price calculator so you can explain your number in one sentence.
Pay what you want (suggested $19):
https://t.co/dUyAn5a6qU
#BuildInPublic
Day 9 — calm operator log
Revenue: $0 · X followers: 109
Gumroad: $0 Amazon live · Contra listed
Craigslist replies · Fiverr parked · Support in bio
NotDone: waiting on App Review
Showing up.
#BuildInPublic