Build
Finance Watchtower
A financial awareness system that helps people understand their position, recurring obligations, and upcoming money pressure without complicated budgeting.
Finance Watchtower is a financial awareness system for people who want clarity over their money without running a heavy budgeting process.
Project links
Current focus
- Sharpen the category around financial awareness and low-effort clarity
- Validate a low-effort onboarding flow built around current position and recurring bills
- Measure whether simple awareness check-ins can drive repeat usage
Modules
Finance Watchtower
A personal finance watchtower for people who want clarity over their money without maintaining a full budgeting system.
TL;DR: Most personal finance tools ask users to become part-time bookkeepers before they receive any value. Watchtower focuses on financial awareness: understand your current position, track recurring obligations, and see upcoming money pressure with minimal effort. The current build is focused on validating activation, repeat check-ins, and trust in the future roadmap.
Status: Building
Primary ICP: Young professionals managing their own finances
Category: Personal finance, financial awareness
Pricing: Pre-revenue; freemium is the current hypothesis
Snapshot
- North Star Metric: Weekly awareness review completion rate
- Activation: First dashboard view plus one recurring expense added or imported; baseline not measured yet
- Retention: Week 4 return rate for activated users; instrumentation planned
- Revenue: Pre-revenue
- Notable signal: The MVP is intentionally focused on three jobs: understand current position, track recurring bills, and spot upcoming money pressure
1. Context & Problem
The user and their job-to-be-done
- User: Young professionals with stable income, multiple recurring expenses, and low tolerance for spreadsheet-heavy money admin
- Context: The problem shows up between pay cycles, before bills land, and ahead of decisions like travel, housing, tax, or insurance renewals
- Current alternatives: Bank apps, spreadsheets, calendar reminders, and mental math across scattered accounts
- Pain: Users can usually see transactions, but they cannot quickly tell whether they are financially okay without reconstructing the picture themselves
Problem statement
For self-managing young professionals, financial blind spots appear between pay cycles and recurring obligations, causing avoidable stress and slower decisions because clarity requires too much manual effort.
Why now?
- Rising fixed expenses and subscription creep make rough money tracking feel less reliable
- Many users have already tried budgeting tools and learned they do not want a high-maintenance system
- A simpler awareness category creates a clearer wedge than competing head-on with full budgeting apps
2. Insight
Key insight: Most users do not want a budgeting system. They want a lightweight financial radar that answers three questions quickly: where do I stand right now, what is coming next, and what needs attention first?
Evidence:
- Detailed budgeting tools create setup and maintenance fatigue before users experience value
- The clearest message is simple: current position, recurring bills, and upcoming money pressure
- Users do not need more financial configuration; they need faster answers to basic money questions
Assumptions that must be true:
- Users will exchange granular control for lower setup and lower ongoing effort
- Recurring expenses plus current-position visibility are enough to create an immediate aha moment
- Lightweight awareness check-ins can retain users before advanced planning tools exist
3. The Strategic Bet
ICP
- Primary: Young professionals managing their own money, paying rent or mortgages, juggling recurring bills, and avoiding traditional budgeting products
- Secondary: Freelancers, early-stage families, and first-time property buyers who need clearer visibility before larger financial decisions
Positioning
- Category: Financial awareness tool
- Differentiator: Watchtower reduces finance management to a clear status view and recurring-obligation radar with far less overhead than a full budgeting workflow
- Promise: Stay aware of your finances with minimal effort
- Reason to believe: The MVP is intentionally constrained to the fastest clarity loop: financial position, recurring expenses, and upcoming bills
Moat hypothesis
If Watchtower becomes the trusted place users return to for low-friction money clarity, habit formation and structured recurring-obligation data create the foundation for future decision-support modules without requiring a category reset.
4. What We Will NOT Do
Explicit exclusions:
- ❌ Full envelope-style budgeting — because it increases setup cost before users understand the product’s value
- ❌ Deep investment, tax, and insurance workflows in the MVP — because they expand scope before the core awareness loop is validated
- ❌ Heavy customization and category design — because defaults are more important than control in the first-use experience
Kill criteria:
- If activation stays below 40% and week 4 awareness retention stays below 25% by 2026-05-15, narrow the product to recurring-expense visibility or pause expansion.
5. Success Metrics
North Star Metric
- Metric: Weekly awareness review completion rate
- Definition: The percentage of activated users who complete at least one meaningful awareness session in a week
- Why it matters: It measures whether the product creates an ongoing clarity habit instead of a one-time setup event
Input metrics
- Activation: First dashboard view plus one recurring expense added or imported in the first session
- Engagement: Awareness sessions per active user per week
- Retention: Activated users who return in week 4
- Revenue: Waitlist conversion to paid interest and willingness-to-pay interview signals
Instrumentation plan
- Events to track:
landing_page_cta_clicked,onboarding_started,dashboard_viewed,recurring_expense_added,upcoming_bill_viewed,awareness_session_completed,future_module_interest_clicked - Tools: Product analytics instrumentation planned; weekly manual review until the dashboard is live
- Reporting cadence: Weekly
6. Solution & MVP Scope
Product narrative
A user starts because they want clarity, not another financial chore. Watchtower helps them set up the minimum useful picture of their finances, then returns a simple status view with recurring obligations and upcoming pressure points. The aha moment is immediate: "I can tell where I stand without maintaining a complicated budget." From there, the product earns the right to expand into bigger money decisions.
MVP Goals → Features → Rationale
| Goal | Feature | Why this exists (rationale) | How we’ll measure it |
|---|---|---|---|
| Deliver instant clarity | Financial position snapshot | Users need a fast answer to "am I okay right now?" | First-session dashboard completion |
| Reduce surprise obligations | Recurring expense tracker | Recurring bills are the most common blind spot in personal money management | Recurring coverage rate |
| Create a low-effort habit | Upcoming bills and awareness dashboard | Users need a reason to return without doing full bookkeeping | Weekly awareness review completion rate |
UX principles (workflow philosophy made tangible)
- Principle 1: Clarity before categorization
- Principle 2: Defaults over manual configuration
- Principle 3: Awareness before optimization
7. Prioritisation & Tradeoffs
Prioritisation framework
- Inputs: Activation impact, effort, confidence, reduction in cognitive load, and learning value
- Decision rule: Prioritize the smallest changes that improve first-session clarity and repeat awareness behavior before expanding planning depth
Top 3 decisions (with reasoning)
- Decision: Lead with financial awareness as the category
Tradeoff: The product sounds less comprehensive to power users
Reasoning: Lower perceived maintenance cost makes the first-use promise stronger and more credible - Decision: Make recurring expenses a core surface area before advanced planning tools
Tradeoff: Long-range planning remains shallow in the short term
Reasoning: Recurring obligations are a high-frequency problem and the clearest source of avoidable financial surprises - Decision: Keep future modules visible only as roadmap signals
Tradeoff: Some users looking for an all-in-one finance suite will bounce
Reasoning: Signalling direction builds trust, but shipping too much too early weakens the core loop
Why this focus is durable
- The core user job stays stable across segments: people want a fast answer to where they stand, what is due next, and whether anything needs attention.
8. Execution Plan
Timeline (phases)
- Phase 1: 2026-03-07 → 2026-03-15 — finalize positioning, landing page copy, and onboarding narrative
- Phase 2: 2026-03-16 → 2026-03-31 — instrument onboarding, dashboard usage, and recurring-expense setup
- Phase 3: 2026-04-01 → 2026-04-20 — validate repeat awareness behavior and test interest in future planning modules
Risks & mitigations
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Users still categorize Watchtower as another budgeting app | M | H | Use category language, onboarding copy, and product demo to reinforce the awareness frame |
| Manual setup feels too slow | M | H | Bias toward defaults, quick-add recurring expenses, and minimal initial inputs |
| The product feels useful once but not repeatedly | M | H | Make upcoming bills and changes in financial position the primary re-entry triggers |
Launch checklist (summary)
- Tracking verified
- Onboarding complete
- Billing tested for paid experiments
- Support channel ready
- Rollout plan finalized
9. Pricing & Unit Economics
Pricing hypothesis
- Model: Freemium with a paid tier for advanced planning, reminders, and future decision-support modules
- Anchoring: The price should feel closer to a lightweight utility than a full financial planning service
- Expected willingness to pay: AUD $8-15 per month once recurring visibility and planning confidence are proven
Unit economics
- Variable costs: Hosting, analytics, email or reminder delivery, and customer support time
- Gross margin expectation: Greater than 85% at early SaaS scale
- Break-even: Roughly 250-300 paying users at initial pricing assumptions; validate after reminder and analytics costs are measured
Pricing experiments
| Experiment | Hypothesis | Change | Result | Learning |
|---|---|---|---|---|
| Beta pricing interviews | Users will pay for reduced financial uncertainty before they pay for forecasting depth | Test willingness to pay against reminder and planning concepts | Not run yet | Determine whether the first paid tier should be reminders, planning modules, or both |
10. Distribution Plan & Experiments
Distribution thesis
The first cohort should come from users already skeptical of traditional budgeting apps but motivated to feel more in control of day-to-day finances. The most efficient path is creator-led education and build-in-public content centered on clarity and low-effort money visibility, supported by direct conversations with users facing recurring-bill stress and bigger life decisions.
Channels (ranked)
- Personal writing about financial clarity and low-effort money systems — because it attracts the exact audience rejecting high-maintenance budgeting
- Build-in-public product updates — because the problem framing and roadmap are part of the story, not just promotion
- Direct network outreach — because early qualitative feedback is more valuable than broad top-of-funnel traffic
Experiment log
| Date | Channel | Hypothesis | Action | Outcome | Next |
|---|---|---|---|---|---|
| 2026-03-07 | Landing page copy | Awareness-first messaging will improve message clarity | Publish awareness-first landing page and build entry | In progress | Compare copy resonance in onboarding tests |
| 2026-03-14 | Personal writing | A positioning essay will attract higher-intent users than a feature announcement | Planned | Not run yet | Measure CTA clicks and onboarding starts |
| 2026-03-21 | Direct network | Guided walkthroughs will surface objections faster than passive signup data | Planned | Not run yet | Collect pattern-level objections by onboarding step |
11. Results, Learnings, Decisions
What happened (facts)
- The MVP is centered on current position, recurring expenses, and upcoming bills
- The page emphasizes clarity, low effort, and recurring-obligation visibility
- Instrumentation for activation and retention still needs to be finalized before quantitative claims are credible
What I learned (insights)
- Insight 1: A narrower category promise makes the product easier to understand and easier to trust
- Insight 2: Future modules are more useful as credibility signals than as launch scope
Decisions made
- Decision: Keep the core promise focused on awareness and clarity → because it creates the fastest path to user value
- Decision: Center recurring obligations and current position in the MVP → because they create the fastest path to user value
12. Reflection
What I would do differently next
- Test the awareness positioning with target users before spending more time on deeper module concepts
Weakest assumption in hindsight
- The weakest assumption is that awareness alone creates durable weekly behavior. The next test is whether upcoming bills and visible financial status changes are strong enough re-entry triggers.
What breaks at 10x scale
- Manual setup support, recurring-expense configuration help, and hand-held onboarding would become bottlenecks without stronger defaults or automated data capture.
Update log
2026-03-07: Launched MVP.