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.
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-reported evidence
Source: Intercom Help: Using custom fonts in the Help Center
Intercom recommends four core weights plus italics for each when uploading a custom font family.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Brand, Support, Website is relevant to brand system, typography, trust and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Brand and Support, using evidence from Intercom Help: Using custom fonts in the Help Center as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.