Getting started
Create your first workspace, add the vendors you want to track, and record observed monthly spend alongside workspace and market estimates. Most teams start with their highest-spend vendors and expand from there.
Monitoring cost
Learn how source-labeled cost estimates and the pricing evidence timeline surface what changed, and how to read the severity bands on each cost alert so the right people act at the right time.
Planning renewals
Track contract terms and renewal timing per vendor, and bring observed spend, pricing evidence, contract history, and renewal risks into every renewal conversation.
Workspaces & access
Organize vendors, usage profiles, and alerts into isolated, multi-tenant workspaces for your teams, business units, or clients.
Building a renewal-ready vendor record
Asozal works best when each vendor record becomes the shared source of truth for spend, contract terms, pricing evidence, usage context, and renewal actions. Instead of waiting until the renewal window opens, start by adding the vendors that matter most: high-spend platforms, vendors with upcoming renewals, tools with unclear ownership, or contracts where usage and cost no longer seem aligned.
For each vendor, capture the basics first: renewal date, contract owner, current estimated spend, observed monthly spend, contract model, and any known pricing or packaging changes. Then add supporting evidence over time, such as pricing notes, invoices, contract details, usage observations, and renewal risks. The goal is to move renewal conversations from memory and scattered documents into one record that finance, procurement, engineering, and leadership can review together.
Choosing the right contract model
Use the Contract Model field to describe how the vendor charges your team. This helps Asozal organize the right kind of evidence and gives your team a clearer view of what to monitor before renewal.
Common models include:
- Flat subscription: Fixed monthly or annual cost, usually optimized by reviewing tier fit and unused features.
- Seat-based: Cost is tied to users, roles, or licenses, making utilization, inactive users, and shelfware important.
- Usage-metered: Cost changes with activity such as API calls, storage, compute, messages, or other usage units.
- Term commitment: A multi-year or fixed-value contract where actual spend should be compared against the original plan.
- Credit drawdown: A prepaid or committed pool of credits that should be monitored for over-burn or under-use.
- Tiered bundle: A package with included limits, modules, or feature bundles where the key question is whether the current tier still fits.
- Freemium, one-time, or support/perpetual: Non-standard models that should be tracked separately from recurring SaaS run-rate.
A simple workflow for new vendors
When adding a vendor, start small and build detail over time. A practical first pass is:
- Add the vendor name, owner, department, and renewal date.
- Select the contract model that best matches how the vendor charges.
- Enter current estimated spend and observed monthly spend.
- Add contract notes, pricing evidence, or renewal concerns.
- Record one next action, such as “confirm usage owner,” “request latest quote,” or “review inactive seats.”
This creates a usable vendor record quickly, even before every contract or invoice is uploaded. As new spend observations, pricing changes, or usage details are added, Asozal can help surface gaps, alerts, and renewal preparation items earlier.
Using evidence before renewal
A renewal-ready vendor record should answer more than “when does this renew?” It should help explain what changed, whether spend increased, whether usage supports the current tier, whether the vendor changed packaging, and what action should happen next.
Before a renewal, review:
- Observed monthly spend versus estimate
- Pricing evidence and recent packaging changes
- Contract start, end, and renewal dates
- Seat utilization or usage trends, when available
- Open alerts and renewal risks
- Evidence links and action history
- Recommended negotiation or follow-up actions
The stronger the record, the easier it is to ask better renewal questions, such as why a quote increased when observed spend was flat, whether unused seats should be removed, or whether a different tier or contract model would better match actual usage.
Data privacy and access controls
Asozal helps teams manage vendor, renewal, and spend information that may be sensitive to your business. The product is designed so customer data stays within your account and is visible only to authorized users based on their role and workspace access.
What data Asozal stores
Asozal stores the information you and your authorized users enter into the product. This may include vendor names, renewal dates, contract values, planned spend, vendor notes, workspace membership, account users, and product activity needed to operate the service.
How Asozal uses your data
Asozal uses customer data to provide product functionality, including vendor tracking, renewal planning, cost monitoring, alerts, workspace collaboration, and account reporting.
Asozal does not sell customer vendor records, spend data, contract details, renewal information, or workspace content.
Managing access
Account owners control who is invited into the account. Workspace access determines which users can participate in shared vendor and renewal workflows.
Use team and workspace settings to keep access limited to the people who need it.
Support access
Asozal personnel may access customer data only when needed to provide support, troubleshoot product issues, maintain security, or comply with legal obligations. Internal access is limited by role and business need.
Data deletion and export
Customers can remove vendor records from the product and may request account-level data export or deletion, subject to legal, billing, and security-retention requirements.
Learn more
For more context, read:
These guides explain why contract models and renewal evidence matter, and how teams can start improving vendor cost management with a small set of high-priority vendors.