Product template

One-page product spec

Go from a problem statement and a few notes to a one-page spec with goals, scope, open questions and how you'll measure success.

Use this templateUsed by 5,400 teams
Product

What you fill inPreview

Problem
Customers can't tell which invoices are overdue
Notes
Support tickets, two customer calls, last quarter's churn survey
Team
Billing squad, four engineers, one designer

Example output

Generated by Pilot

Overdue invoices at a glance

Owner: Billing squad. Status: Draft for review. Target: end of Q1.

Problem

Customers can’t see which invoices are overdue without opening each one. In the last quarter, 64 support tickets asked some version of “what do I still owe”, and two of the five accounts that churned named billing confusion as a reason.

Goals

  • A customer can see every overdue invoice from the billing page in one view.
  • Finance contacts get a reminder before an invoice becomes overdue, not after.
  • Billing tickets about overdue status drop by half within two months of launch.

Scope

In scope

  • An “Overdue” filter and badge on the invoice list.
  • A summary at the top of the billing page: total due, total overdue, next due date.
  • An email reminder three days before the due date, on by default.

Out of scope

  • Partial payments and payment plans.
  • Changes to how invoices are generated.

Open questions

  1. Should the reminder go to the account owner, the finance contact, or both?
  2. Do we show overdue amounts to people without billing permissions?
  3. How do we handle invoices disputed in support?

How we’ll measure it

Metric Today Target
Billing tickets about overdue 64 30
Invoices paid after due date 22% 15%
Reminder emails opened n/a 50%
All templates

Your next draft is already started

Join 14,000 teams that research, write and ship with Pilot.