Abstract
Burner has a real user base, a 4.3★ lifetime rating, and 8,053,675 installs, but recent reviews repeatedly complain about immediate trial charges, cancellation confusion, unreliable calls and texts, poor support, and unexplained account closures; the gap is real, but a solo builder is entering regulated, abuse-prone telecom, not a normal CRUD app.
Background
Burner: Second Phone Number sells disposable US/Canada phone numbers for SMS, calls, voicemail, auto-replies, VPN, personal info protection, reverse lookup, and related privacy features. The store listing says the app is free, while its own fine print says burners are free for a trial period only and users should review pricing before purchasing.
What it does
Gives users a second number they can use for calls, SMS, voicemail, privacy, boundaries, classifieds, job searches, business calls, and temporary identity separation.
What changed
Recent reviewers describe trust-breaking billing around the trial, duplicated or unexpected charges, post-update contact and message problems, missed calls, and harder-to-reach support.
Why it is soft
A competitor does not need more privacy bundles; it needs boring reliability, plain pricing, clean cancellation, and business-safe continuity for people who depend on the number.
Strengths
Burner is not a strawman: some long-time users still praise the privacy value, call clarity, setup, VPN bundle, yearly plan value, and usefulness as a work or marketplace number. The hardest thing it has already built is trust at scale — 8,053,675 installs, a recognizable brand, and users who have kept numbers for years.
Real use cases
Reviews mention job searches, business lines, online marketplaces, avoiding spam, privacy, overseas networking, carrier disputes, and protecting a real phone number.
Habit lock-in
Several angry reviewers say they used it for years or rely on the number for work, which means switching is painful even when the app disappoints them.
Some service recovery
A few updated reviews say issues were fixed or support gave thorough instructions, so the incumbent can still recover unhappy users.
Market gap
The complaints cluster around trust more than features. The most common theme is billing and trial confusion, followed by core communication reliability; support and account continuity turn those bugs into perceived business risk.
Trial and billing trust
Many reviewers say they were charged immediately, charged after canceling, charged twice, or shown a trial that did not behave like a free trial.
Calls and messages failing
Users report calls going to voicemail, missed notifications, dropped calls, outgoing texts not delivered, message delays, VoIP problems, and lag in the Android app.
Support and cancellation
The support complaints are harsh because users are paying for a number they may depend on, yet say they cannot reach anyone, get refunds, or stop charges cleanly.
Continuity and missing basics
A smaller but important group wants group SMS, web access, easier device switching, better login privacy, number portability, and less surprise account enforcement.
Wife no longer is locked out of her app. However, calls she receives go immediately to voicemail without ringing, resulting in many missed calls. Not good, as she uses this number for work.
Subscribed several times. Mostly had problems with answering calls but never with billing. I decided to go with $59.99 yearly subscription which came with 3 days free trial. Downloaded app, picked up number as usually and subscribed. When I opened app I was asked to pick up number again and pick up either monthly or yearly plan. I was also billed immediately, no 3 days trial. Canceled immediately. Looks that I am out of $60 and there is no way to contact anyone. Trying to dispute with bank.
- Make pricing impossible to misunderstand. No hidden trial cliff, no surprise plan screen after number selection, and a visible cancel link before the user pays.
- Compete on reliability, not feature sprawl. Ship one paid line with SMS, calling, voicemail, delivery state, and notification diagnostics before adding VPN, lookup, video, or identity extras.
- Treat the number as business-critical. Add exportable message history, clear account-status warnings, a human escalation path, and a documented policy for closures.
Build complexity
Estimated, not derived: one developer, part-time, no funding, no team, and no paid acquisition. This is hard for a solo builder because the product depends on paid telephony infrastructure, number inventory, fraud controls, app-store policy, support, and reliability monitoring.
| Workstream | Weeks |
|---|---|
| Android app: onboarding, inbox, calls, SMS, voicemail | 5.0 |
| Telephony provider integration and number lifecycle | 4.0 |
| Billing, cancellation, receipts, plan-state clarity | 2.5 |
| Abuse prevention, verification, logging, account review flow | 2.5 |
| Reliability monitoring, notification diagnostics, delivery states | 2.0 |
| Play listing, support docs, QA across Android devices | 2.0 |
| Total | 18.0 |
Expected revenue
Estimated, not derived: assume a transparent $8/month single-line subscription, no paid acquisition, and slow store-led growth because a new telecom app starts with no reviews and must screen abuse. The month-12 figure is gross MRR before telephony, support, refunds, and tax effects.
| Month 12, monthly | ||
|---|---|---|
| Installs | 1,200 | |
| Activated | 480 | 40% |
| Retained after first month | 220 | 18% |
| Paid | 100 | 8% |
| Revenue | $800 |
Biggest challenges
The hardest part is not the inbox UI; it is earning trust while running a telecom service alone. A second-number app attracts spam, scams, 2FA edge cases, refund disputes, and angry users whose business number may stop working at midnight.
Telephony dependency
Calls, SMS, number availability, deliverability, and short-code behavior depend on providers and carrier rules the solo builder does not control.
Abuse and compliance
Disposable numbers invite bad actors, so account closures, verification, logs, and appeals must be designed before growth arrives.
Support load
Billing and missed-call tickets are urgent; part-time support can quickly become the product’s bottleneck.
AI angle
There is no strong AI moat here. AI can help write support macros, classify failed-call logs, summarize tickets, or flag likely abuse, but it does not materially solve number provisioning, carrier deliverability, call reliability, billing trust, or regulatory risk.
Useful assist
AI ticket triage could make a solo operator faster at spotting repeated billing or notification issues.
Not decisive
The market gap is operational trust, not language generation; AI should not change the build-time or revenue estimate.
Conclusion
Skip it. The complaints expose a clear opening for a transparent, reliable second-number app, but a part-time solo builder is taking on telecom infrastructure, fraud, support, and carrier dependency for a modest month-12 revenue target.
18 weeks
Time to v1
$8/mo
Single-line subscription
$800
Revenue at month 12
Telecom ops
Fact that decided it