TemplateDocs
Feature request
A feature request template that leads with the user's problem, not the solution, plus evidence, alternatives, and how success is measured.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your document
# Feature request: Let teams schedule reports instead of exporting manually
**Requested by:** Dana, Customer Success · **Date:** 2026-09-04
## The problem
Finance teams open the reports dashboard every Monday morning purely to export the same CSV and email it to stakeholders. It's a manual, forgettable chore that has already caused three missed board-meeting deadlines this quarter.
## Evidence it matters
12 of our top 20 accounts do this weekly, per usage logs. Support has logged 9 tickets asking for "an export I can schedule" in the last two months.
## Proposed solution
Add a "Schedule this report" option next to Export, with a day/time picker and an email delivery list, reusing the existing export pipeline.
## Alternatives considered
A Zapier integration - rejected, too much setup for non-technical users. A public API endpoint - rejected for now, since it doesn't solve the problem without the customer writing code.
## How we'll know it worked
At least 8 of the 12 accounts identified switch from manual export to a schedule within one month of launch, and related support tickets drop to zero.
How to use it well
- →If the problem section already names a UI, rewrite it - describing the solution before the problem is how teams end up building the wrong fix for the right pain.
- →Usage data beats a strong opinion. A count of accounts hitting the problem turns "I think users want this" into something a roadmap can actually be prioritized against.
- →Write the success measure before building anything - a request with no stated finish line quietly turns into a permanent feature nobody ever confirms was worth it.