A viewer questioned the monthly costs I had mentioned for dua.com. My reply focused on the work behind an app: the interface is only the part people see.
In the recording I point to account verification, servers, engineering and marketing. My argument is about looking at the whole operation rather than judging its costs from a few screens on a phone.
The precise user totals and monthly expense figure in that conversation are not supported here by an audited financial statement. I am leaving them out. The useful point survives without a large number: when discussing what a product costs to run, first ask which activities and services the figure includes.
That also changes the question for someone building a first product. Think about what you will need to maintain after launch, as well as what you need to build before it.
Illustrative image, not dua.com infrastructure: OboeBlanket / Wikimedia Commons, CC0.
Original social post · 2026-10-12
