Product & Design
PRD Writer
Produces a structured product requirements document covering problem, users, success metrics, scope, user stories, and out-of-scope items. Useful for product managers scoping features before engineering starts. Product managers scoping features, founders who do their own product work, engineering leads who want design alignment before they commit a sprint, designers looking for a problem statement they can design to. A good PRD closes the gap between "here's what we want" and "here's what engineering built"; a bad PRD becomes a 15-page document that nobody reads and everyone re-interprets. Teams skip PRDs under deadline pressure and then spend the saved time arguing about what the feature was supposed to do. A structured writer produces a PRD that is concise, testable, and shaped around the questions reviewers actually ask.
One-Time Purchase
$19.99
PRD — Smart Invoice Reminders
Product: FinTrack Platform Author: Maya Chen (PM) Status: Draft, ready for review Target release: v2.3.0 Est. engineering size: 1.5 sprints
Summary
Headline
FinTrack's small-business users lose roughly 14% of monthly revenue to late payments. The #1 stated reason in recent support tickets is "I forgot to follow up." Smart Invoice Reminders adds in-product, scheduled payment reminders with per-invoice and account-level configuration. Phased rollout behind a feature flag because email deliverability errors carry real customer-trust risk.
Problem
FinTrack's small-business users currently have no in-app mechanism to schedule payment reminders — they export to email manually or rely on memory. Support tickets in the past 90 days (n=312) cite "I forgot to follow up" as the #1 stated reason for uncollected invoices. Competitors offer automated reminders; recent exit-survey data (n=47) shows 19% of churned users cited "no reminders" as a contributing factor.
Target users: Freelancers and small business owners with 10–100 active invoices per month who manage billing without a dedicated AR team.
Success Metrics
Targets at 60 days post-launch
Requirements
| ID | Requirement | Priority | Notes |
|---|---|---|---|
| R-1 | Configure reminder schedule per invoice (before due, on due, after due) | P0 | Defaults to 3-day-before, on-due, 7-day-after |
| R-2 | Account-level default schedule, overridable per invoice | P0 | Set once during onboarding |
| R-3 | Email delivery using user's existing FinTrack sender identity | P0 | SPF/DKIM authenticated |
| R-4 | Pre-built reminder template with invoice number, amount, one-click payment link | P0 | Custom note up to 280 characters |
| R-5 | Reminders stop automatically when invoice is marked paid or voided | P0 | Idempotency-guarded |
| R-6 | Activity log: when each reminder was sent, delivered, bounced | P1 | Surfaced on the invoice detail page |
| R-7 | Bulk apply default schedule to all open invoices | P1 | One-click migration in settings |
| R-8 | Per-account daily send limit to avoid spam flagging | P1 | Default 200/day, adjustable by support |
| R-9 | Test-send to self before saving a custom template | P2 | Reduces support volume |
User Stories
As a freelancer with 30 open invoices, I want automatic payment reminders on a schedule I define, so that I get paid faster without tracking each invoice by hand.
As a small business owner, I want to set a default reminder schedule at the account level, so that every new invoice inherits the policy without extra setup.
As a client receiving a reminder, I want the email to include the invoice amount and a one-click payment link, so that I can pay immediately without logging into a portal.
As a business owner reviewing collections, I want to see a log of all reminders sent per invoice, so that I can confirm follow-up happened before escalating.
Out of Scope
Not in v2.3
- SMS or in-app push reminders (email only)
- Custom HTML email templates
- Reminder scheduling for recurring invoices (depends on recurring billing v2.4)
- Two-way communication (reply-to-pay, disputes via email)
- Client-side portal changes
- A/B testing of reminder copy
Each of these has been considered. Most are deferred for scope; recurring-invoice reminders are deferred because they have a hard dependency on v2.4.
Open Questions
Q1 — Email infrastructure decision
Do we use FinTrack's existing transactional email provider or introduce a second provider for reminder volume? Cost model and deliverability profile differ. Owner: eng-infra. Must resolve before engineering kickoff.
Q2 — Payment-plan interaction
Should reminders pause when a payment plan is active on an invoice? Payment plans ship in v2.2; need to confirm the interaction before this PRD goes to engineering. Owner: PM (Maya).
Q3 — GDPR consent for EU clients
Legal review required: does auto-sending reminders to EU clients require additional consent capture under GDPR? Must resolve before Beta gate. Owner: legal.
Q4 — Outbound rate limit
What's the per-account daily limit on outbound reminder emails to avoid spam flagging? Affects R-8. Owner: eng-infra.
Rollout Plan
Phased rollout behind feature flag smart_reminders_v1
Why phased
Email deliverability errors and reminder logic bugs could damage client relationships at scale. Phased release lets us validate send rates and payment impact before full exposure.
Risk Register
| ID | Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|---|
| R1 | Reminder emails land in spam | Medium | High | SPF/DKIM on send; deliverability monitoring during beta; user-visible send log |
| R2 | Reminder fires after invoice is already paid (race condition) | Medium | Medium | Scheduler re-checks invoice status within 5 min of send; idempotency guard |
| R3 | Low adoption — users don't discover the feature | High | Medium | Contextual prompt on invoice creation; onboarding checklist entry; release notes email |
| R4 | Custom note becomes a phishing vector | Low | High | Strip links from the custom note; payment link is always the canonical FinTrack one |
Reviewer Checklist
- Problem framing matches support ticket and churn data on file
- Success metrics have agreed baselines (confirm with analytics before sign-off)
- Legal open question (Q3) resolved before Beta gate
- Email infrastructure decision (Q1) made before engineering kickoff
- Out-of-scope items confirmed with PM — especially recurring invoices
- R2 race condition covered in QA test plan
- Feature flag wired up before merge
This sample illustrates the skill's output format. FinTrack Platform is a fictional company used recurringly across these sample outputs. Real product data, ticket volumes, and churn figures are never included in sample outputs.
View full sample →
All sales final. No refunds on digital products.
Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.
Also in Product Management
Bundle price: $44. Compare this skill with the full workflow bundle or Pro access.
Best for
Product managers scoping a feature before engineering starts, founders who own product work themselves and need a structure to think through a problem, and engineering leads who want design alignment with a documented success metric before they commit a sprint. Most useful when the feature is meaningful enough to deserve a real PRD but small enough that a 15-page document would kill the team’s interest in reading it.
Not ideal for
Trivial work where the spec is implicit (‘fix the bug from the support ticket’) and the PRD ceremony exceeds the work itself. Also a poor fit very early in discovery when the problem is still being defined; a PRD locks in a solution shape before the team is ready to commit to one.
Included in this purchase
- Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
- Setup guidance for the right adapter in your workspace.
- One-time license for the purchased skill version.
Setup
Plan for a short copy-and-configure setup in your preferred agent workspace. No custom integration is required for the skill file itself.
Related Skills
$19.99
One-time license
$19.99
One-time license
$19.99
One-time license
Future Updates
This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.