1. Begin with decisions, not feature lists
An IT operations platform should help your organisation make and execute better decisions. A large catalogue of integrations is not enough if ownership remains unclear, records disagree or every action still requires manual investigation. Begin with three recurring situations that create work, risk or avoidable expenditure.
List the tools involved in each situation, the people responsible and the information needed. Include spreadsheets and informal handovers alongside identity, endpoint, HR, finance and procurement systems. Identify what should remain in an existing tool rather than assuming that a new platform must replace everything.
- Which decisions are slow today, and what makes them slow?
- Who will use the platform, approve actions and maintain records?
- What observable result would justify changing the current process?
2. Test coverage, integration depth and freshness
Ask vendors to demonstrate one representative record from its source through to a useful operational outcome. Separate discovery, import, enrichment, workflow initiation and write-back. Support for a provider does not establish support for every object, field or action.
Request an explanation of refresh behaviour, failed synchronisation and conflicting values. A timestamp should make clear whether it describes a source event, import or verification. Test missing and stale data rather than reviewing only complete demonstration records.
- Which systems, accounts and activities are covered, and which remain outside visibility?
- Can the platform distinguish source data, manual corrections and inferred relationships?
- Which permissions, credentials, mappings and plan restrictions apply to the required integration actions?
3. Examine permissions, evidence and security
Evaluate identity and authorisation separately. Signing in securely does not establish that someone should see every employee record or approve every operation. Ask how organisation membership, roles and tenant boundaries affect viewing, changing, approving and exporting data.
Reports should answer operational questions; evidence should also explain the source, timing and context behind an assertion. Check whether reviewers can trace an outcome to its supporting records. Integrity mechanisms are useful, but do not by themselves establish certification or legal sufficiency.
- Request a role-based demonstration, including a denied operation.
- Review MFA or passkey options, audit coverage and evidence export verification.
- Check current privacy, processing and subprocessor documents; raise unresolved security questions with the vendor.
4. Investigate delivery effort and commercial dependency
Ask what work your team must perform: source cleanup, account matching, permission review, process design, testing and ongoing ownership. Distinguish vendor assistance from work included in your agreement. Confirm support channels, escalation arrangements and contractual commitments rather than relying on a sales demonstration.
Review current pricing against your expected scope and growth. Ask which capabilities depend on plans, roles or usage. Examine exit options as carefully as onboarding: usable exports, relationship preservation, attachments and evidence may matter more than a basic record download.
- Can reports and underlying records be exported in usable formats?
- What happens to your workflows and history if you change provider?
- How would larger teams, more integrations and stronger separation of duties change cost and administration?
5. Use an evidence-based comparison scorecard
Apply the same scorecard to every candidate, including your current approach. Score each dimension from 0 to 3: 0 means absent or unverified, 1 means partial, 2 means demonstrated for the required scope, and 3 means demonstrated with acceptable exception handling. Record evidence and unresolved questions beside each score.
Assign weights before demonstrations, then calculate the weighted score as the sum of score multiplied by weight, divided by the sum of weights. Treat mandatory security or export requirements as pass-or-fail gates; a strong average must not conceal a critical failure.
- Operational fit: existing-tool compatibility, data coverage, integration depth and freshness.
- Control: identity, permissions, security, reporting and evidence.
- Sustainability: export, implementation effort, pricing, support, vendor dependency and scalability.
6. Validate a shortlist with a realistic scenario
For example, ask each vendor to review a departing employee’s assigned device, application access and unresolved ownership questions. Require a clear distinction between visible records, supported actions and items needing human investigation. Score the handling of uncertainty, not just the polished result.
Lojycal connects workplace records and operational workflows, with provider-specific integration paths and access controls. Available actions depend on configuration, permissions, mappings and plan or role gates; confirm these for your workspace. Review /pricing and relevant terms, then request a scoped demonstration. Use the same acceptance criteria even if another platform is the better fit.