01Acquire
RecordedPurchase and stock context
IT Asset Management
Know what a client owns, uses and needs to replace.
Connect hardware, software, licenses and warranties to the client record. Use the lifecycle view to plan renewals, reconcile stock and keep a traceable retirement record.
A record people can use
Keep the source, owner and next decision together.
Illustrative workflow · explore the steps · no action is executed
01
Discover or receive
Create an asset from inventory, procurement, stock receipt, import, or an authorized manual record.
Confirm this step for your release, permissions and environment.02
Assign and maintain
Link the asset to a customer, site, user, device, license, contract, warranty, and related configuration item.
Confirm this step for your release, permissions and environment.03
Audit or retire
Run a QR-assisted stocktake, resolve differences, or complete the governed decommission and disposition record.
Confirm this step for your release, permissions and environment.IT asset management
Ownership, lifecycle, commercial context, and historyAsset reconciliationDeclared and observed
02Discover
ObservedTechnical observation retained
03Reconcile
RequiredConflicts reviewed
04Lifecycle
TraceableAssignment through retirement
Reconcile what was bought, assigned, discovered, changed, and retired.
Keep source, observation time, owner, reconciliation, and lifecycle state visible for each asset.
Link assets to customers, users, sites, devices, contracts, services, incidents, documents, and dependencies.
Inside the workflow
The work this connects.
- Hardware lifecycle
- Track purchase, assignment, warranty, service, depreciation, replacement, and disposition dates.
- Software and licenses
- Connect entitlements, assignments, observed use, renewal, and over-allocation signals.
- Stock and procurement
- Manage requested, ordered, received, stocked, assigned, returned, and retired equipment states.
- Stocktakes and labels
- Use QR labels, mobile-friendly verification, discrepancy review, and signed inventory outcomes.
- CMDB relationships
- Link assets with customers, users, sites, devices, contracts, services, incidents, and documentation.
- Supporting records
- Keep custom fields, notes, photos, invoices, warranties, and attachments under scoped access.
Try one useful scenario
Resolve conflicting observations
Fictional example: two sources report different owners and an ambiguous software version for one serial number. Preserve both observations and let the authorized asset owner resolve the authoritative record. Follow asset A-17 from received to assigned, repaired and retired. The purchase record and discovered hostname disagree, so the asset owner approves the correction. Retirement requires a disposal record and credential/access removal. Software presence alone is neither usage evidence nor license entitlement; a depreciation estimate is not an accounting certification.
Illustrative evaluation scenario, not a recorded product result.What a useful result must show
Record source, timestamp, confidence, exception, reviewer and accepted identity. Recheck the installed version after remediation; a failed check remains unresolved.
Get the evaluation worksheet →Check the support boundaries
- Scan prerequisites and permission scope
- Observed versus declared asset identity
- Software publisher/version confidence
- IPAM, license usage and retirement evidence
Observed IP relationships are not DNS/DHCP administration or address planning. Software presence is not reliable usage/license compliance evidence; depreciation and QR workflows need their own support record.
Check public evidence and availability →Scope, availability and evaluation details
Discovered and declared data remain distinct until a governed reconciliation decides the authoritative value.
Warranty, procurement, licensing, and accounting depth depends on the supported provider or maintained record.
The proposed $99 monthly model includes the target product scope for evaluation, unlimited technicians, unlimited customers, and the first 50 managed devices. Final terms require confirmation. See transparent pricing →
Review full environment and integration scope
Multiple sources, one reconciled asset
Endpoint and network discovery, procurement receipts, stock intake, imports, and authorized manual records can feed the asset lifecycle while each source and observation remains visible.
Connected commercial and service context
Assets link to service tickets, contracts, procurement, licenses, warranties, customers, users, sites, documentation, and CMDB relationships without duplicating the source records.
IT asset management connects discovery, service operations, contracts, procurement, licenses, warranties, reporting, and CMDB relationships.
Questions, answered
Before you choose your next step.
Can discovered devices become managed assets?
Target design: Reconciliation links supported discovered inventory to an asset record while preserving source and observation history.
Does it track software licenses?
Target design: License entitlement, assignment, observed usage signals, renewal, and allocation exceptions can be tracked by client.
Can teams perform physical stocktakes?
Target design: QR-assisted verification supports counts, discrepancies, review, and recorded stocktake completion.
What happens when an asset is decommissioned?
The workflow records required recovery, data handling, disposition, approvals, and archival state while retaining connected history.