Loading page…
A mobile profit calculator for drivers who need to know what a load really pays after costs.
3 paying users · about 200 downloads in six months
“Distribution first, code second” is the right lesson for a niche calculator that already has a clear user.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Pavlo spent two weeks riding in a truck to see drivers’ work firsthand, then built Truck Driver Helper around a practical question: what is the real profit on a load? Drivers may be paid as a percentage of a load or by the mile, and a simple total can hide costs. The app began as 33% Truck Driver Helper before the name and design changed to cover more pay arrangements. Pavlo used AI coding tools and shipped a React Native and Expo app with Supabase, RevenueCat, and an admin panel. Publishing took three weeks, including a subscription rejection and fixes. After about six months, the app had around 200 downloads, three paying users, and $15 in monthly revenue. Running costs were about $58 a month, so it did not yet cover itself.
Use the two-week ride-along as an acquisition advantage: keep speaking with drivers in the places where they already compare loads, fuel costs, and pay. Ask owner-operators to walk through a recent settlement and show which calculation they do by hand.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Pavlo reports the downloads, paying users, revenue, prices, and costs in the video. They are founder-reported and unaudited; the app’s store dashboard and financial accounts are not independently shown.
Truck Driver Helper’s revenue snapshot is recurring: three paying users paying about $5 each produced $15 a month. That means the first dollar comes from a driver choosing to pay for repeated load calculations, not from an ad impression.
The potential flywheel is a driver using the tool before accepting a load, saving the result, and returning when the next offer arrives. As the history becomes useful, the app can show how different pay arrangements and costs affect take-home profit.
At about 200 downloads over six months, three paying users, and $15 MRR, Truck Driver Helper has a very early signal. The creator estimates that about 14 paying users would cover the roughly $58 monthly cost, leaving 11 more payers to reach break-even.
Truck Driver Helper estimates a driver’s actual profit from a load. It needs to handle at least two common pay structures identified in the product story: a percentage of a load or payment per mile. The original 33% name was too narrow because drivers also use other arrangements, so the product broadened its framing. Pavlo also built an admin panel to see signups, active users, and paying accounts. Planned extensions included voice-based load entry, an owner-operator mode, fuel tracking, and better reports. Those ideas should remain secondary to an accurate, understandable core calculation. A driver needs to know which inputs were used and what the result means before trusting it during a real workday. The product is a decision aid for individual drivers, with a possible later path into owner-operator workflows.
Truck Driver Helper uses subscription revenue. The transcript gives a typical price of about $5 a month, a 15% app-store share, and about $4.25 net per subscriber. With three paying users, reported MRR was $15. The creator estimated monthly operating costs at about $58 when servers and AI tools plus Apple’s annual developer fee were included, and calculated that roughly 14 subscribers would reach break-even. This leaves little room for paid acquisition at the current scale. Price around recurring value such as saved loads, fuel records, and reports, but keep the calculation itself easy to try. Avoid hidden pricing and measure conversion after a driver completes a real calculation. The next business milestone is a sustainable acquisition loop, not a higher list price unsupported by usage.
Pavlo used React Native and Expo for the iOS and Android app, Supabase for data, RevenueCat for subscriptions, and an admin panel for analytics. Apple charged $99 per year and Google $25 one time; servers and AI tools cost about $50 monthly, which the creator summarized as roughly $58 a month including Apple’s fee. Store submission took three weeks overall. Apple rejected the app over subscription disclosures and a missing reviewer test account, and the founder spent 10 days fixing the submission. The numbers show that a small calculator still carries platform and operating overhead. Make subscription terms visible, maintain a reviewer account, and test purchase flows before submission. The React Native implementation helped one person serve both phone platforms, but distribution and retention remain the costliest problems at this scale.
Copy the founder’s strongest move: learn a workday from the inside, then define the calculation around a real decision. Change the launch sequence by validating a channel before expanding the product. Talk to drivers and dispatchers, publish a clear store page, and create demonstrations around a realistic load. Build the cheapest trustworthy calculator first, then add fuel, saved reports, or voice entry only when users ask for them. Use the specific employment patterns in trucking as an advantage; do not market it as a generic finance app. Ask drivers to verify calculations against their settlement documents and label assumptions. The case suits a developer who can access trucking communities and handle app-store operations. It is less suitable for someone who expects the stores alone to deliver customers.
Our read: the core risks are store discovery, trust in the profit calculation, and low revenue per individual subscriber. New apps start without reviews and can sit low in search; an incorrect estimate could also affect a driver’s decisions. Make every assumption visible and let users correct cost inputs. Platform submission and subscription rules create operational work, while low paid conversion limits the amount available for marketing. A fleet product could raise contract value, but it would introduce different buyers and longer sales cycles. Keep claims conservative, protect financial and trip data, and do not imply that the app guarantees profitability. The current $15 MRR is useful evidence of willingness to pay, but it is not proof that the business covers costs or has found a repeatable channel.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,435 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click