Abstract
FAX App turns a phone into a fax machine — scan, send, receive — with 3.1M+ installs and a 4.5★ lifetime average. Recent reviews describe being billed a full subscription after a confirmed cancellation, a "free" pitch that gates the first real send behind payment, and faxes that don't go through even after a charge — real, but fixable with honest per-use pricing.
Background
Marketed by some partners as a free way to send an occasional fax, FAX App: Send Faxes from Phone instead pushes most first-time senders straight into a subscription.
What it does
Scans a document with the phone camera or imports a file, then sends or receives it as a fax without a physical machine or phone line.
What changed
Reviewers describe the app dropping a simpler credit-based, pay-per-fax option in favor of weekly/monthly/annual subscriptions, and continuing to bill after a cancellation email is already confirmed.
Why it is soft
The lifetime 4.5★ average and multiple reviewers who return to the app "several times" whenever they next need to send a fax show occasional, real demand for the core function — the backlash is about billing, not whether faxing-by-phone is useful.
Strengths
Even critical reviewers confirm the core function works — the pattern is people coming back specifically when they next need to fax something, which is exactly the low-frequency, high-intent use case a pay-per-use competitor should target.
Works when billed fairly
Reviewers who paid once and weren't over-charged describe it as simple and effective for an occasional fax need.
Repeat, intent-driven demand
Multiple reviews describe re-installing and paying again each time a new fax need comes up — proof this is a recurring, if infrequent, need rather than a one-off download.
I've had this app several times, pay for it & install it when I knew I would be sending alot of faxes, cancelled & needed it again. Works great & simple to use. The only reason I gave a 4 is bc I cancelled the app last week & they still tried to bill me for it.
Market gap
The recurring complaints, grouped into named clusters, most-common first:
Billed after a confirmed cancellation
The dominant cluster: subscriptions that keep charging after a cancellation email is already in hand, with reviewers told to fight it out with Google Play instead of the developer.
"Free" gates the actual send
Several reviewers arrived expecting a free service — in one case pointed there directly by their bank's own instructions — only to hit a paywall the moment they try to send.
Faxes fail to go through
A smaller but serious cluster: paid faxes that never reach the recipient, with no refund and no clear status on why the send failed.
warning! used the trial to fax a few papers to disability determinations, and none of them went through. I tried 3 separate times. after 4 days, I canceled the service. today, I woke up to them charging me for a full year of service AFTER I CANCELED 3 DAYS AGO! (i still have the cancelation email).
TD Bank says this is Free Fax for TD Bank disputes. App even says so in one of its first paragraphs in its description but then it starts asking for payment, a subscription when you are hitting send!
- Make cancellation actually stop billing, immediately. No further charges once a cancellation is confirmed — this is the single most-repeated complaint above.
- Price per fax, not by forced subscription. The reviews above describe an infrequent, intent-driven need — a subscription fights that pattern instead of fitting it.
- Show a clear delivery status and auto-refund a failed send. A charge for a fax that never arrived is the fastest way to turn a first-time user into a 1-star review.
Build complexity
Estimated, not derived: one developer, part-time, no funding and no paid acquisition. The sending itself is bought from an existing fax-gateway API, so the build is mostly billing and reliability, not fax infrastructure.
| Workstream | Weeks |
|---|---|
| Fax-gateway API integration (send/receive) | 1.5 |
| Document scan + cloud file import | 1.0 |
| Honest per-fax billing, working cancel | 1.5 |
| Delivery status tracking + auto-refund on failure | 1.0 |
| Total | 5.0 |
Expected revenue
Assumes $1.99 per fax (first send free to prove it works), reached without paid acquisition — this is a smaller, more occasional-use category than most, so the estimate stays modest.
| Month 12, monthly | ||
|---|---|---|
| Installs | 20,000 | |
| Activated (sent one free trial fax) | 8,000 | 40% |
| Sent a paid fax that month | 1,000 | 5% |
| Revenue | $2,500 |
Biggest challenges
Not the app itself — delivery reliability depends on a third-party gateway a solo builder doesn't control, and the category itself is a shrinking, narrow-intent niche to reach without paid acquisition.
Reliability isn't fully in your hands
If the underlying fax-gateway vendor has a delivery hiccup, a solo builder inherits the complaint with no code fix available — unlike most app bugs.
A narrow, shrinking audience
Faxing is a declining habit overall — growth depends on ranking for specific must-fax use cases (legal, medical, government forms), not broad organic pull.
AI angle
Something already asked for in market_gap — knowing a fax actually failed and fixing it without a support ticket — is markedly cheaper to build with AI than manual support triage.
Without AI
A human support queue investigating each "my fax never arrived" complaint one at a time, the exact bottleneck reviewers describe hitting.
With AI
A lightweight check flags a blank or unreadable scanned page before sending, and an automated retry-then-refund flow reacts the moment the gateway reports a failed delivery — no support ticket required, folding into the estimate above.
Conclusion
Build it. A real, if modest, occasional-use audience already exists — the incumbent is losing them to billing after cancellation, not to the idea of faxing from a phone.
5 weeks
Time to v1
$1.99/fax
No forced subscription
$2,500
Revenue at month 12
56/82
Recent reviews cite billing, not the faxing itself