Expandi ProductLead lists and import
Rebuilt Expandi's lead lists and CSV import, two places users decided the product was broken when it was only unclear.
CSV import generated about fifty support tickets a week after three years of complaints. In lead lists, people typed a name, got no results and concluded search didn't work. Neither was a bug, which made them harder to fix.
- import support tickets a week before
- ~50
- steps to import, with errors shown per row
- 3
- filters decluttered
- 14
- Search obeyed filters the user couldn't see.
- Import skipped rows silently, so people re-uploaded the same file and then opened a ticket.
- SDRs moving leads between tools every week, usually from spreadsheets of a few thousand rows.
- Team leads who inherit lists built by someone else and need to know what's in them.
- Make the system explain itself before adding features: visible filters, and an import that accounts for every row.
- I pushed to reuse one bulk-action bar and one tag picker across lists and the inbox, instead of designing new ones for each.
- A three-step import that detects columns and returns a file of what it skipped and why.
- Lists with visible filters, column management and a bulk-action bar that survives pagination.
- Import shipped February 2026; lead lists August to September.
- Import tickets went from about fifty a week to under fifteen.
(Keep browsing)
