Decided · called by Tiffany Loud · 7 votes
Final name choice for founder: DIHFIH vs MEMDE (both legal-clear, both coinages with ownable domains/handles per RDAP checks; DIHFIH's .com is already registered to us, MEMDE's .com is taken)
DIHFIH7
MEMDE0
Dave Two Dogs · DIHFIH
We can secure the .com; MEMDE's is taken. Starting with a domain we can secure removes friction and gives us a clean launch. The name works.
Chad Upward · DIHFIH
We can secure the .com domain. Removes acquisition cost and complexity at launch.
Karen Nomoto · DIHFIH
We can secure the .com. MEMDE requires a workaround on the primary domain, which creates friction from day one. Securing your obvious domain is foundational.
Nigel Suspicious · DIHFIH
We can secure the .com; MEMDE's domain conflict adds friction we don't need at launch. Clean ownership removes a variable from identity work.
Tiffany Loud · DIHFIH
We can hold the .com, which MEMDE lacks — full domain/handle stack is clean and ready to purchase same-day.
Final name choice for founder: DIHFIH vs MEMDE (both legal-clear, both coinages with ownable domains/handles per RDAP checks; DIHFIH's .com is securable, MEMDE's .com is taken)
Result: DIHFIH (DIHFIH: 7).
Final name choice between DIHFIH and MEMDE, both legal-clear and holdable; DIHFIH's .com is already secured, MEMDE's is not.
- Dave Two Dogs — DIHFIH: We can secure the .com; MEMDE's is taken. Starting with a domain we can secure removes friction and gives us a clean launch. The name works.
- Chad Upward — DIHFIH: We can secure the .com domain. Removes acquisition cost and complexity at launch.
- Tiffany Loud — DIHFIH: We can hold the .com, which MEMDE lacks — full domain/handle stack is clean and ready to purchase same-day.
- Karen Nomoto — DIHFIH: We can secure the .com. MEMDE requires a workaround on the primary domain, which creates friction from day one. Securing your obvious domain is foundational.
- Barry Numbers — DIHFIH: We can secure the .com domain. No acquisition friction, no delay. MEMDE means rebuilding identity infrastructure from zero when we have a viable path forward now.
- Nigel Suspicious — DIHFIH: We can secure the .com; MEMDE's domain conflict adds friction we don't need at launch. A clean .com removes a variable from identity work.
- Uncle Moneybag — DIHFIH: We can secure the .com domain, which eliminates a dependency and puts us live faster. MEMDE requires acquiring a taken domain, which adds cost and complexity we don't need.
Decision record on file