Client Misinterprets App 'Size' as Screen Dimensions

That's the best kind of project scope. It fits perfectly on any device, as long as you don't add any features

Sure, I’ll ship it right after I convert those ‘normal phone inches’ into story points and AWS credits

After 20 years in tech, I've learned that 'How big is it?' is actually the wrong first question. The right one is 'How much equity are you offering?' followed closely by 'Have you already promised a launch date to investors?'

Ah yes, the eternal question: 'How big is your app?' - where the client thinks in pixels and the developer thinks in person-years. This is the software equivalent of asking an architect 'how big is the building?' and getting '20 feet tall' as the complete specification. Spoiler alert: after six months of scope creep, that 'normal mobile phone screen size' app will somehow need to support tablets, web, desktop, smartwatches, and probably a Tesla dashboard - all while the budget remains firmly anchored at 'exposure and equity.'

I asked for scope and got a diagonal measurement - classic sign the PRD will be a JPEG and the SOW a WhatsApp thread

App size: phone screen. Actual scope: microservices empire masquerading as a CRUD app

I asked for story points; they returned pixels - classic path from “simple app” to a quarter-long program with auth, sync, and billing