TemplateDocs
One-page project proposal
A one-page project proposal template: the problem, proposed solution, cost and effort, expected outcome, and the decision you need by when.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your document
# Self-serve password reset
**Proposed by:** Meera, Support Engineering · **Date:** 2026-09-04
## Problem
Password resets are our #1 support ticket category - 1,200 tickets a month, 14-minute average handle time, and a 6-hour queue overnight when no agent is on shift.
## Proposed solution
Add a self-serve reset flow gated by email plus SMS verification, reusing the auth service's existing token issuance. No new infrastructure - it's a new route and two email templates.
## Cost and effort
One engineer, three weeks. No new vendor spend - reuses existing SMS credits, roughly $40 a month at current volume.
## Expected outcome
Ticket volume in this category drops by an estimated 70%, freeing about 140 support hours a month and closing the overnight gap entirely.
## Decision requested
Approve the three-week build and give Support Engineering priority on the shared auth service for that window. Please respond by Sep 12.
How to use it well
- →Cut everything that isn't the problem, the fix, the cost, and the payoff - a proposal that needs a second page is asking the reader to schedule a meeting instead of deciding.
- →Put a number on the problem and a number on the outcome. "This is annoying users" gets deferred forever; "1,200 tickets a month, projected to drop 70%" gets a yes or a no.
- →Name an actual date in the decision line. Without one, a one-pager that everyone agrees is "a good idea" quietly never gets approved.