reph

Templates · Product

One-pager template

A single-page pitch for an idea: problem, solution, why now

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

You want a decision-maker to react to an idea before anyone spends weeks on a full spec

Who it's for

Product managerFounderExecutive

Filled example

The template filled in for a made-up company, so you can see what good looks like.

Offline mode for field technicians

Author: Diego Alvarez · Date: 2026-09-18

We want approval to staff two engineers for one quarter to make Fieldstone Field work offline. Technicians lose signal on a third of job sites, and it has become the top reason we lose renewals to Toolbelt.

Problem

Fieldstone Field technicians inspect equipment in basements, plant rooms and rural sites. When the app loses signal, it cannot load a job or save a checklist, so technicians fill in paper and retype it later. In our September survey of 140 technicians, 61% said they lost work at least weekly. Four of the last nine churned accounts named connectivity as a reason, worth $210k in annual revenue.

Proposed solution

Download each technician's jobs for the day when they start their shift, let them complete checklists, photos and signatures offline, and sync automatically when signal returns. Conflicts (a dispatcher changed the job meanwhile) are flagged for the technician to review, never silently overwritten.

Why now

Toolbelt shipped offline support in July and their sales team leads with it in every competitive deal. Our mobile app also moved to the new local database in August, which makes this a quarter of work rather than the rewrite it would have been last year.

Who it's for

Field technicians at mid-size facilities companies (50 to 500 technicians). Dispatchers also benefit because jobs close the same day.

How we'll measure success

  • Jobs closed on the same day they are worked rises from 72% to 90% within two months of launch
  • Connectivity disappears from churn reasons over the next two quarters
  • Paper fallback forms reported in surveys drop by half

Risks

  • Sync conflicts confuse technicians. Mitigation: a simple review screen, tested with five customers before launch.
  • Storage on older Android devices. Photos can fill the phone; we cap offline photo storage at 500 MB.
  • Scope creep into full offline dispatch. Dispatch stays online only; this is technician work only.

Ask

Two mobile engineers (Ana and Kofi) for Q1, plus a decision from the product leadership meeting by 2026-10-01 so we can plan the quarter.

The template

Show the blank template

One-pager

Author: [your name] · Date: [date]

If a reader only gets the first paragraph, they should still know what you want and why it matters now.

Problem

Who has this problem, how you know, and what it costs them today, in time, money or churn.

Proposed solution

What you'd build, in a few sentences a non-specialist on the team can picture. Save the mechanics for a follow-up doc.

Why now

What changed (a new capability, a competitor move, a growing cost of inaction) that makes this the right time, not six months ago or from now.

Who it's for

The primary user or customer segment. Naming a second segment as "also benefits" is fine; naming five means you haven't picked one.

How we'll measure success

  • A number that moves, and by how much, within a stated window

Risks

The two or three ways this fails (technical, market, or organizational) and how big a deal that would be.

Ask

What you need from the reader: budget, headcount, a decision, or just a reaction by a date.

Questions

How long is a one-pager?
One screen or one printed page. Cut until it fits
Should it have a budget?
Only a rough order of magnitude in the Ask, the detail belongs in a later plan
What happens after it is approved?
The same author turns it into a feature brief or PRD within a week or two, and the Ask (people, money, time) is confirmed there before work starts

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "One-pager" with search_docs, then read it with read_doc. Draft problem, why now and success measures from the customer interview notes, churn or sales loss reasons and market notes linked in the doc. Keep it to one page with the ask in the opening paragraph. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (the assumptions that most need checking) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Related templates

Analytics request

Brief for a data or analytics request: the decision it informs, the exact question, metric definitions, segments, timeframe, sources, due date and output format

Product managerResearcherMarketerExecutiveOperationsAnyone

Experiment (A/B) plan

Hypothesis, variants, metrics, sample size and decision rule

Product managerResearcherEngineer

Feature brief

Short brief aligning team on a feature before design

Product managerDesignerEngineer

Launch checklist

Everything to ship a feature: eng, docs, support, marketing

Product managerManager

PRD / requirements doc

Problem, users, requirements, success metrics and scope for a feature

Product managerEngineerDesigner

Roadmap

Now / next / later themes with a timeline

Product managerExecutiveManager

Start with this template →Sign in