Operational workflow · Independent product work

Chasely

A focused accounts-receivable follow-up system that shows solo service businesses who to chase today—and makes the next action easier to complete.

Explore the live demo
Chasely / Overdue
Total overdue$16,500
Invoices7
Oldest45d
Who to chase todayPriority
ACAcme Consulting$2,50045 days
BSBright Studio$1,80030 days
CLCedar Legal$4,20021 days

The challenge

Unpaid invoices get buried in spreadsheets. Follow-up history becomes scattered, prioritization is manual, and writing the next reminder creates avoidable friction.

The outcome

A deployed workflow that prioritizes overdue invoices, preserves a per-invoice chase history, prepares reminder messages, and imports existing spreadsheet data without trying to replace the user’s invoicing system.

My role: Product definition, requirements, scope control, architecture direction, implementation orchestration, verification, and deployment.

Selected decisions

Designed around the constraint, not the feature list.

01

Solve one operational question

The MVP centers on “who should I chase today?” rather than expanding into invoicing, payments, or accounting.

02

Integrate without replacement

Fixed-schema CSV import lets users bring existing records into the workflow without abandoning their current tools.

03

Make evaluation frictionless

A public, read-only demo exposes the product workflow without requiring a recruiter or reviewer to create an account.

Verification evidence

What supports the claim.

  • 21/21 current unit tests
  • Documented Playwright coverage
  • Public no-sign-in demo
  • Discovery, architecture, UX, and proof-map artifacts

Explicit boundaries

What I do not claim.

  • No paid-customer or revenue claim
  • No direct email delivery
  • No accounting-platform integration
  • No validated willingness-to-pay claim

Continue exploring

Next case study: PromptVault