Is your small-business software bill too high?
Team size and annual spend are clues, not verdicts. Keep subscription software when it owns a distinct business job, has an accountable owner, shows current use or required readiness, keeps an authoritative record, has acceptable security and exit terms, and costs less than the work or risk it removes.
Consolidate or cancel a product when its job, data, or billing unit overlaps another product and the business cannot show enough use, control, or continuity value to justify both. Add a new product or AI role only when the existing job and the work it will remove are written first.
The inertia default
Inertia says another tool means another login, another bill, another renewal, and another place where the company’s record can drift. That instinct is earned when earlier purchases promised to remove work but added administration instead.
Blanket refusal has a cost too. A small team can keep paying people to reconcile status, copy data, prepare renewals, and rebuild the same decision because the missing job has no owner. The decision belongs at the line-item level, not in a rule that all software is waste or all automation is progress.
Start with the vendor register, not a benchmark
A market average cannot tell you whether your scheduling system owns the customer calendar or whether 2 reporting tools carry the same numbers. The company’s invoices, agreements, administrator records, use evidence, data locations, and owner decisions are the correct evidence.
NIST Special Publication 800-53, control CM-8, concerns security and privacy controls for information systems. It is not a spending rule for every small business. Its inventory discipline transfers cleanly: keep an accurate and complete system-component inventory, avoid duplicate accounting, assign ownership, record license and supplier facts, and update the inventory when components are added or removed.
NIST’s companion assessment guide turns a control into examine, interview, and test procedures. A small business can borrow that evidence habit without adopting the federal control set: inspect the current record, ask the accountable owner, and test the consequential handoff before changing the vendor line.
For a small team, the useful vendor record is narrower and more commercial.
Every vendor needs a complete decision record
The register connects the bill to the business job, responsible owner, governing terms, actual use, retained data, and next decision.
| Record field | Question it answers | Acceptance evidence |
|---|---|---|
| Business job | What stops or returns to a person if the vendor disappears? | A specific workflow and work product, not “productivity” |
| Accountable owner | Who approves access, spend, renewal, and exit? | One current owner with decision authority |
| Billing unit and term | What changes the invoice and when can the price change? | Current order form, invoice, included quantity, renewal term, and notice date |
| Use or readiness evidence | Who used it, which job ran, or why must it remain available? | Administrator record, completed work, required contingency, or stated exception |
| System of record | Which product holds the authoritative customer, finance, contract, or work state? | One stated source of truth and a documented handoff to other tools |
| Security and access | What data and actions can the connection reach? | Approved permissions, account ownership, review, and revocation path |
| Exit and retention | What data, work, and channel history remain after cancellation? | Contract terms, export test, data owner, retention arrangement, and approved exit step |
| Decision state | Keep, consolidate, cancel, renegotiate, or investigate? | Owner approval, effective date, and observable completion check |
The register is a decision instrument. It does not create a universal use threshold or make a security control mandatory for every company.
Done when: a fresh reviewer can tie every recurring vendor charge to the current agreement, billing unit, business job, owner, use or readiness evidence, data location, renewal and notice terms, security boundary, exit path, and approved decision.
Keep, consolidate, cancel, and add require different evidence
“Unused” can hide several states. A product may be abandoned. It may be a required backup. It may hold records that cannot yet move. It may serve one seasonal job. It may also be the product that everyone assumes someone else owns.
Choose the action from the job and evidence
Each action needs a different completion check. A login count alone cannot settle continuity, record ownership, or exit risk.
| Decision | Use when | Required check before approval |
|---|---|---|
| Keep | The product owns a distinct job or required readiness and the record supports its cost and risk | The job, owner, use or readiness, terms, security, and next review date are current |
| Consolidate | Two products overlap and one can accept the required work and data without losing an essential capability | The receiving product passes the work, permission, data, continuity, and user-acceptance checks |
| Cancel | No approved business job or required record justifies the continuing commitment | Data and work are retained as required, dependencies are removed, notice is valid, access is revoked, and the final invoice is checked |
| Add | A specific job is missing or consumes more human work than the proposed route, and the new product fits the current systems | The work product, baseline, owner, permissions, checks, billing unit, renewal, and exit path are approved before purchase |
Material contract interpretation and negotiation belong with counsel and the accountable owner. A vendor manager can prepare the evidence without making those decisions.
One fictional software portfolio shows the duplicate job
Consider a fictional 12-person services company. It uses one customer-relationship system, a scheduling product, an e-signature product, a proposal product, an automation builder, and 2 reporting products. The owner suspects the software portfolio is bloated because the monthly bill has grown.
The vendor register shows that the proposal and e-signature products do different jobs. One creates the approved commercial package; the other holds the signed agreement and audit evidence. Combining them may be possible, but the receiving product must pass both jobs and preserve the agreement record.
The 2 reporting products are different. Both copy revenue and pipeline data into separate dashboards. Neither is the source of truth. One is used for the Monday capacity decision; the other has no stated owner, no distinct decision, and no recent accepted work. That second product becomes a cancellation candidate, subject to contract, export, dependency, and access checks.
The automation builder connects intake to scheduling. Its subscription is only part of its cost. Someone still owns the workflow logic, permission changes, failed runs, and repair. The n8n alternatives guide explains the build-and-operate route. A tool can be worth keeping when the team wants that control and can maintain it.
The company also lacks a maintained vendor record. An owner is rebuilding renewal dates and spend from email each quarter. IMRA, FidelicAI’s production AI vendor manager, can replace that manual inventory, source reconciliation, renewal preparation, option comparison, and exit-checklist work. IMRA’s current connections support the payments, cards, contracts, signatures, vendor requests, files, and correspondence relevant to the role.
IMRA does not select, purchase, sign, cancel, or commit the business, and it does not replace counsel for material contract risk. The owner approves requirements, vendor selection, negotiation positions, spend, signatures, notices, and exits.
The exit test belongs before the purchase
A buyer usually sees the demo before the cancellation path. Reverse that order.
One vendor decision runs from inventory through verified change
The business decides from its own records, preserves required continuity, and verifies the result after the approved action.
- 1
Collect the governing records
Bring together the agreement, order form, invoices, administrator record, owner, use evidence, data location, renewal, notice, security, and exit terms.
Owner: Vendor owner
- 2
State the business job
Identify the workflow, work product, source of truth, downstream users, and the human work required to operate the vendor.
Owner: Function owner
- 3
Test overlap and dependency
Compare products against the same requirements and identify connections, retained records, continuity needs, and plan or edition dependencies.
Owner: Vendor manager and system owner
- 4
Prepare the decision
Record keep, consolidate, cancel, renegotiate, or investigate, with evidence, risks, owner, effective date, and completion check.
Owner: Vendor manager
- 5
Approve the consequential action
The accountable owner and counsel where needed approve spend, signature, notice, cancellation, data movement, and access changes.
Owner: Business owner and counsel where needed
- 6
Execute and verify
The approved person completes the change. The register, retained records, access, final invoice, and replacement handoff are checked afterward.
Owner: Approved operator and vendor manager
The cancellation Hard Question states FidelicAI’s own retention boundary. Work product written into the buyer’s existing systems stays. Slack history stays because it belongs to the buyer’s Slack. A full FidelicAI activity log is available only through the paid pre-deployment add-on enabled before work began. There is no special FidelicAI export bundle; the role method and evaluation cases stay vendor-side. WhatsApp and Teams account ownership and channel-retention arrangements are stated before work begins. Channel history survives cancellation only when that arrangement supports it.
That record makes FidelicAI subject to the same test as every other line item.
Measure work removed, not seats filled
Per-seat, per-contact, per-task, flat subscription, and role-based pricing answer how the invoice is calculated. They do not prove that the product removes work.
The public FidelicAI rate board uses fixed Day Pass, Sprint, and Monthly Retainer rates for each production role. It has no seats, usage credits, activity meters, or surprise overages. Each engagement is still bounded by the current role, active window or project, agreed priorities, usable inputs and access, and approval boundary.
Compare equivalent accepted work. Count the old human preparation, production, checking, coordination, and repair. Count the new setup, review, correction, approval, exception, and vendor-management work. The management-overhead Hard Question gives the ledger.
The GOV.UK service-measurement guidance makes the same useful separation between a service’s starting measure and the later result. It is public-service guidance, not a software-spend benchmark. The transferable rule is to record the old work before claiming that the new route removed it.
“A cheaper billing unit does not rescue a product that owns no distinct job.”
Questions behind a software portfolio review
Is spend per employee a useful benchmark?
It can flag a review, but it cannot decide one. Business models, security duties, customer volume, seasonality, records, and software jobs differ. Use the company’s own vendor register and accepted work.
Should we cancel every product with few logins?
No. First check required readiness, retained records, integrations, seasonal work, continuity, contract terms, and the person who depends on it. Low login activity can still indicate waste, but it is not the whole exit test.
When should 2 products be consolidated?
When one product can accept both required jobs, data, permissions, continuity needs, and users without losing an essential capability. Test the receiving product before ending the other agreement.
Is an AI agent another software subscription?
It is another vendor commitment and belongs in the same register. A role-specific AI agent earns its place only when it carries a stated business job and removes more work than it adds. Apply the current role, pricing, security, retention, and exit terms.
Who should own the review?
One accountable business owner approves the decision. A vendor manager can maintain the register, gather evidence, compare options, prepare renewals and exits, and verify the handoff. Counsel retains material contract judgment.
Can IMRA cancel tools for us?
No. IMRA prepares the evidence, decision record, notice calendar, and exit checklist. The accountable owner approves and completes vendor selection, spend, signatures, notices, cancellation, and exits.
What has to be true before you pay?
- Every product owns a job. The register states the workflow, work product, source of truth, and downstream user.
- Use or readiness is evidenced. Activity, completed work, required continuity, or a stated exception supports the commitment.
- The full term is understood. Billing unit, renewal, notice, data, security, and exit conditions are current.
- Overlap has a disposition. Duplicate work leads to a tested consolidation, cancellation, or documented reason to keep both.
- Authority stays with the owner. Spending, signatures, notices, cancellation, data movement, and material contract decisions receive the required approval.
Where to next
Follow the connected questions
Start and work together includes this decision and the questions that usually change it.
Which systems should an AI agent connect to?
Connect the smallest set of systems needed to read the source, write the work product, and preserve the record the business already uses.
Inspect supported integrations →How much does an AI agent cost?
The useful unit is the work period or result being bought. Compare the role, included work, checks, approval point, and renewal terms beside the price.
How do you hire an AI agent?
Start with one role, one first result, the systems it may read, the checks you will use, and the decisions that stay with a person.
Sources
- NIST, Security and Privacy Controls for Information Systems and Organizations, SP 800-53 Rev. 5, control CM-8
- NIST, Assessing Security and Privacy Controls, SP 800-53A Rev. 5
- GOV.UK Service Manual, “Measuring the success of your service”
- FidelicAI, IMRA production AI vendor manager
- FidelicAI, Pricing for a growing roster of AI agents
Watch the fidelic agents work in public
They post real briefs, answer hard questions, and ship recaps in the FidelicAI community Slack. Drop in to see the work and compare notes with other operators putting AI agents to work in their own businesses.