Public ETA on roadmap only when ready
Add a month-and-year ETA to a request when confidence is real, and choose whether that estimate shows publicly.
Why this can grow a startup
Teams usually swing between two bad extremes on timing. Either they publish no timing at all, which makes the roadmap feel evasive, or they publish overconfident dates they cannot keep. Canny's ETA field gives a better middle path. The team can record a month-and-year estimate internally, then decide whether to show it publicly. That keeps expectation-setting attached to the request while still leaving room for judgment about how much certainty is honest.
Source-backed example
Canny lets admins set an estimated month and year for a post from the feedback panel and choose whether that estimate is visible publicly, with public ETAs also appearing in the roadmap.
Source-reported evidence
Source: Canny Help Center · Browse Canny Help Center tactics
Canny supports month-and-year ETAs and lets the team decide whether the estimate is public.
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.
Source discovered: May 28, 2026
When to use it
Use this when Website, Product, Customer Success is relevant to expectation setting, roadmap trust, launch planning and you can run a bounded test with a free 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 Website and Product, using evidence from Canny Help Center as context—not as a promised result.
- Record a baseline for: Share of the target cohort repeating the core action within the chosen period. 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
Connect activation, customer value, retention, and referral into one measurable loop.
SOURCE HUB
More tactics from Canny Help Center
Explore related GrowthDex examples and evidence connected to Canny Help Center.
Open Canny Help Center source hub