1. Manage applications as ongoing responsibilities
SaaS management is the ongoing practice of understanding which cloud applications an organisation uses, why they are needed, who is responsible and how access and spending are controlled. The problem is rarely just the number of applications. It is the gap between purchase, allocation, actual need and accountable ownership.
When those elements drift apart, teams renew services without a clear sponsor, buy overlapping functionality or discover during offboarding that nobody owns an account. A useful programme therefore combines IT, finance, procurement, application owners and the people who depend on each service.
- Give each application a business owner and an operational contact.
- Record its purpose, approval status and the source supporting its inclusion.
2. Discovery creates a baseline, not complete certainty
SaaS discovery brings together permitted signals about applications. General practices include reviewing identity assignments, procurement records, expenses, supplier invoices and employee declarations. Each source has blind spots: an invoice does not identify every user, while an identity assignment does not establish the full subscription cost.
Shadow IT means technology adopted outside the organisation's established approval or management processes. Include it in the baseline without treating every unfamiliar application as misconduct. Employees may be solving a genuine gap in the approved toolset. Discovery should establish what is known, what is uncertain and who can clarify it.
- Record the scope and date of each source reviewed.
- Do not infer complete coverage from a successful connection or a populated application list.
3. Separate licence allocation from actual use
Purchased seats, assigned licences, enabled accounts and active use are different measures. A licence may be allocated but unnecessary, or appear inactive because the available usage signal excludes occasional but essential work. Define the observation period and ask the owner before proposing a change.
Duplicate applications also need interpretation. Two design tools may overlap, but one could support a specialist requirement or an external partner. Compare business purpose, data dependencies, contractual commitments and migration effort before recommending consolidation. Removing apparent duplication without that context can create more operational disruption than value.
- Separate unused-seat candidates from confirmed reclaimable licences.
- Check shared accounts, seasonal roles and specialist exceptions.
- Require appropriate approval before changing allocations, and verify the resulting state.
4. Connect costs, commitments and renewal decisions
Subscription visibility requires more than a monthly amount. Record the billing basis, currency, contract period, owner and renewal or notice dates where available. Distinguish paid commitments from estimates and avoid assuming that reclaiming a seat immediately reduces an invoice. Contract minimums or billing terms may prevent an immediate reduction.
In a fictional example, two departments pay for overlapping survey tools. The review finds that one supports a required integration and that the other has an upcoming notice deadline. The sensible next step is an owner-led requirements and contract review, not automatic cancellation.
- Attach renewal decisions to a named owner and verified contract information.
- Track missing notice dates as unresolved risks rather than inventing deadlines.
5. Keep employee changes and records aligned
Onboarding should allocate approved applications according to role and confirmed need. Internal moves should trigger a review of both new and existing access. Offboarding should identify application accounts, ownership transfers and licence follow-up, while respecting retention requirements and approval boundaries.
Spreadsheets can support a small initial inventory, but manually maintained copies easily diverge. A row may retain an outdated owner or show a licence as removed when the application still grants access. The issue is not the file format alone: it is the absence of dependable updates, controlled actions and verification.
- Use a stable employee identifier rather than names alone.
- Distinguish task completion from confirmation in the application.
- Assign follow-up responsibility when a system cannot be updated through a supported connection.
6. Evaluate Lojycal against your SaaS operating model
Lojycal currently provides connected inventory, licence, procurement, finance and employee workflow capabilities. These can bring operational records and responsibilities together. The broader practices described here, including usage analysis, contract interpretation and consolidation assessment, should not be read as a claim that every application exposes those functions through Lojycal.
Confirm discovery sources, available fields and supported actions for your plan and workspace. Provider permissions, credentials, mappings and roles affect what is possible; no connection establishes visibility into all SaaS activity.
- Pilot a small set of applications with different ownership and billing arrangements.
- Reconcile sample allocations and costs against authoritative sources.
- Test an employee-change scenario, including an exception and result verification.
- Ask how unknown usage and manual records remain distinguishable.
- Review /pricing for current plans and use /contact to clarify application-specific requirements.