The brief listed a dozen CCaaS integrations — Genesys, Five9, the usual roster. The implied task: build a data-upload flow.
I didn't. Not because it wasn't needed, but because "how data gets in" isn't one problem. It's three completely different products, and I didn't yet know which one we were building:
- It just appears from Claritel's own bots. Then there's no uploader at all — you need an ingestion status page, not a drag-and-drop.
- Someone bulk-uploads a folder of recordings. Then you need a real upload surface: file mapping, validation, dedupe, progress, failure handling.
- You connect a third-party CCaaS. Then it's an integrations screen — auth, sync config, connection health. A different mental model entirely.
Each is a different week of work and a different verb in the navigation. Build the bulk-uploader when every launch customer is Claritel-native, and you've shipped a flow nobody ever touches.
So I flagged it as a blocking clarification instead of guessing: where does data actually come from for v1's first customer? The empty state, the first-run experience, whether "upload" even exists in the nav — all of it hangs on that one answer.
The most expensive screens are the ones built for a user who doesn't exist.