Growth idea action plan
Excluded internal domain list for clean customer views
Block your own company domain and other throwaway domains from auto-creating customer records so request views stay about buyers instead of your team.
Why this can grow a startup
Customer evidence gets noisy fast when internal testing and staff requests masquerade as real accounts. An exclusion list keeps the request graph honest. That matters for roadmap calls, reporting, and anything public-facing because the company can trust that counts and account views reflect actual customers rather than internal traffic.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where excluded internal domain list for clean customer views can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Product and Support channel.
- Use the evidence from linear.app to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
Linear excludes its own domain from Customer Requests so internal issue creation does not generate fake customer records, and also supports broader excluded-domain rules.
Source: Linear Docs (linear.app)
GrowthDex source hub: Linear Docs
Last checked: 2026-05-27
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Enterprise-tier request-threshold view for roadmap planning same source · 2 shared channels · 2 shared stages
- Dedicated feedback team for customer request intake same source · 2 shared channels · 1 shared stage
- Shared Slack channel linked to the customer record same source · 2 shared channels · 1 shared stage
- Customer email-domain auto-mapping for feedback identity same source · 2 shared channels · 1 shared stage
Related GrowthDex essays
- The request system should sort pain before the roadmap sees it support-led growth, product ops, brand trust
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory