← All blueprints

SaaS Spend Tracker

Nobody knows how many software tools we're actually paying for.

Every tool with its annual cost, owner and renewal date, and a reminder 30 days before anything renews.

No.
009
Department
Finance
Build time
1 hr
Difficulty
Beginner
Team size
10–200 people
Replaces
Zylo
Software spend62 TOOLSJFMAMJJASOANNUAL SPEND$184,200+12% VS LAST YEARFigmaDESIGN · OWNER ANA$9,600NotionCOMPANY · OWNER BEN$12,000RENEWS IN 30DZoomCOMPANY · OWNER CY$7,200123

Parts

  • 1

    Annual spend

    Total software spend per month and per year, and how it's trending.

  • 2

    Tools & owners

    Every tool with its cost, seat count, owner and the team that uses it.

  • 3

    Renewal alerts

    The owner hears about it 30 days before a renewal, while there's still time.

  • 4

    Seat check

    Paid seats against active users, to catch the obvious waste.

Data model

  • Tool { name, owner, team, annual_cost, seats, renews_on, notice_days }
  • Review { tool_id, decision, note, reviewed_at }

Build prompt

prompt.txt
Build an internal tool for my team: "SaaS Spend Tracker".

The problem: Nobody knows how many software tools we're actually paying for.
Who uses it: a team of 10–200 people.

What it should do:
- Annual spend: Total software spend per month and per year, and how it's trending.
- Tools & owners: Every tool with its cost, seat count, owner and the team that uses it.
- Renewal alerts: The owner hears about it 30 days before a renewal, while there's still time.
- Seat check: Paid seats against active users, to catch the obvious waste.

Data:
- Tool { name, owner, team, annual_cost, seats, renews_on, notice_days }
- Review { tool_id, decision, note, reviewed_at }

Constraints:
- Built for one team inside one company. Simple sign-in (or none), no billing, no multi-tenant setup.
- Fast, calm and obvious enough that teammates need zero training.
- Data must persist and be shared across the team.
- Ship the simplest version that works, then tell me what you'd add next.

Works with Claude, ChatGPT, Cursor, Lovable, Replit or Type.

Variations

  • Import from a card statement CSV
  • Per-team budgets with a running total
  • 'Do we already pay for something like this?' search

A new blueprint every week

Sent on Sundays. One tool per email.

More blueprints