Growth idea action plan
Full font family upload before help-center rebrand
Upload the whole font family before rebranding the help center, not just one nice-looking file, so the support surface does not fracture across headings, buttons, and body copy.
Why this can grow a startup
Brand systems usually break in support pages first because the team treats typography as a cosmetic pass. It is not cosmetic once the reader is scanning headings, emphasis, buttons, and long-form instructions under pressure. Intercom's custom-font guidance makes the practical rule explicit: a branded help center needs the real weight map, not a single regular file and hope. When the whole family is present, the support surface feels maintained. When it is not, the page starts looking improvised even if the copy is good.
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 full font family upload before help-center rebrand can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Brand and Support channel.
- Use the evidence from intercom.com 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
Intercom says custom fonts should include Regular, Medium, Semi Bold, and Bold weights, plus italic versions for each, unless the team is using a variable font.
Source: Intercom Help: Using custom fonts in the Help Center (intercom.com)
GrowthDex source hub: Intercom Help: Using custom fonts in the Help Center
Last checked: 2026-05-30T21:15:00Z
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Public metrics dashboard as a buyer-trust surface 2 shared channels · 1 shared stage
- Custom-domain gate for private help-center articles 3 shared channels
- Translated collection gate before multilingual help-center launch 2 shared channels · 1 shared stage
- Collection-description scan copy for support routing 2 shared channels · 1 shared stage
Related GrowthDex essays
- The help center should look like the company, not the tooling brand trust, SEO, support-led growth
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