A cross-platform softphone built by a Bulgarian team. It only does the client, which keeps it neutral towards every SIP provider.
# Communications clients are one of the hardest categories to charge for — users expect free, enterprises demand customisation. The survivors run three models together.
The softphone category has an awkward shape: the function looks trivial (it makes a call), the perceived price is near zero, and the engineering is hard (protocols, media, system compatibility). That mismatch makes any single revenue model fragile.
The free edition does not earn money; it occupies the recommendation slot. When somebody asks in a forum which softphone to use, being in the answer is continuous free traffic. Too crippled and reputation suffers; too complete and paid conversion collapses. That balance needs constant tuning.
Payment points sit where work hurts: multiple accounts, call recording, conferencing, forwarding rules, priority support. Individuals do not need them; people taking dozens of calls a day will pay.
The reason to pay for a softphone is never more features. It is that somebody answers when it breaks.
This layer usually carries the revenue. Carriers want a branded client, device vendors want calling inside their product — high unit value, long cycles, strong stickiness. Once integrated into somebody's product, replacement is expensive.
The cost is long sales cycles and heavy customisation, which requires a technical pre-sales team.
Free builds brand awareness, commercial validates feature value, white label pays the bills. In reverse, requirements from white-label customers settle into general capabilities that return to the commercial edition. It is a virtuous loop, provided the architecture supports both standardisation and customisation at once.
If you build a vertical tool, the structure transfers: free tier for distribution, subscription to validate value, customisation and licensing for large accounts. Three legs is more tiring than one and considerably more stable.