See every tool your team pays for, who owns it, and when it renews, then check a calendar that groups every contract by urgency before the charge lands.
The problem
Not because the work is hard. Because nothing captured it.
Stack*form is a software and subscription inventory that tracks every tool your organization pays for, what it costs, and when it renews.
Add a tool once, and its cost, owner, category, and renewal date stay visible on a shared dashboard instead of scattered across credit card statements and one person's memory.
Register every tool with its cost, owner, country, category, usage type, and adoption level in one searchable, filterable table, with CSV export for finance.
See a running monthly and annual total across every active tool, computed live from what your team entered, not rebuilt by hand.
See spend broken down by category and by country, so the lines actually driving the bill are visible without adding up rows one at a time.
Every tool with a contract end date sorts into overdue, this week, this month, this quarter, or later; marking a tool renewed advances its date by one billing cycle automatically.
Set a cost threshold and an ordered approval chain, then route new tool requests through it, with a status and a record of every step.
Add them yourself, or share your organization's public intake link so the people who actually use each tool can report it, no login required.
Give each tool an owner, a monthly cost, a category, and a renewal date, once.
See what's overdue, due this week, this month, or later, sorted by urgency, before the charge lands.
Everything Stack*form does works on a Stack*form-only account, the same afternoon you sign up. Nothing here depends on another module being turned on, and nothing needs a data import to start being useful.
Sends
tool cost — Coming
The execution signal
Receives
the roster — Coming
The talent signal
Without the suite
An ops lead finds out a tool renewed for another year only when the invoice shows up, because nobody owned tracking it.
With it
's public intake and renewal calendar mean nothing renews as a surprise.
The monthly software total is a number you can state in a meeting instead of estimating from memory.
Owner assignment and the renewal calendar mean a departing employee's seats get found and cancelled instead of billing quietly for months.
The cost and category totals export straight into whatever review the number needs to survive, without rebuilding a spreadsheet every month.
Most teams track software spend in a spreadsheet someone updates when they remember to, cross-checked against a credit card statement once a number is in dispute, and that holds up until the spreadsheet is months out of date, which is most of the time. The honest comparison here is a spreadsheet and a statement, not an enterprise SaaS management platform: Stack*form is built for a marketing team's tool sprawl, not for corporate IT procurement at scale.
Before
Now
The monthly total lives across a dozen card charges
One inventory shows the total on screen, always current
A subscription renews and nobody notices until the charge lands
A renewal calendar sorts every contract by urgency before the date arrives
A departed employee's seat keeps billing until someone happens to notice
Every tool has a named owner, so an orphaned seat is a lookup, not a guess
New tool spend gets approved in a chat thread nobody can find again
A configurable approval chain with a status and a record on every request
What it does not decide
Your data
Stack*form does not call any AI model, and no tool, cost, or usage record in it is ever sent to an AI provider. Every number on the page, from a single tool's cost to the organization-wide monthly total, is computed directly from what your team entered.
Isolation
Every tool, workflow, request, and comment is scoped to your organization at the database level, checked on every read and write, with no path for one organization to query another's data.
Access
Anyone with an active Stack*form entitlement and a signed-in seat in your organization sees every record, cost included, with no separate finance-only view; the public intake link only lets an anonymous visitor insert a new tool record, with no read access to anything already in the inventory. Signal*form staff can access any organization's Stack*form data for support, the same support model every module in the suite uses.
Export
CSV export and the PDF reports both run on data your session already has permission to see, so every export carries the exact same access boundary as viewing the dashboard.
Deletion
Deleting a tool removes it, and its comments, immediately. There is no self-serve organization-level deletion today.
The dashboard reads directly from the tools your team submitted: a running monthly total, a spend breakdown by category and country, and a per-tool cost, computed from what was actually entered, not a demo number. What's on screen the day you add your first tool is the real dashboard, not a preview of one.
Single Tool
One signal, dialed in
billed monthly
Base
The full suite, small team
billed monthly
Pro
Growing agency pace
billed monthly
Agency
Full throttle, no limits
billed monthly
A credit is a prepaid token you spend each time the platform generates something with AI, like a brief or a report, so your plan includes a monthly batch and you can buy more when you run out.
See full pricingPrices in USD. Annual billing shown per month, billed yearly. Taxes may apply by region.
Related
Skill*form holds who is on your team today. Matching that roster automatically to tool ownership here is on the roadmap, not built yet, so assigning an owner in Stack*form is still a manual field.
Flow*form tracks what a project costs to deliver. Folding a tool's monthly cost into project overhead automatically is on the roadmap, so today the two totals are tracked separately.