Documentation menu
Prepare an evaluation brief
Bring technical, security and budget evidence into one practical procurement review.
Give each reviewer an explicit question to answer. A successful evaluation ends with documented evidence, an agreed cost envelope and a clear list of open requirements.
Define the pilot
Choose a small set of representative vantage points: a branch, a remote worker or VDI session, and a cloud workload where appropriate. Name the services you want to measure and what would make the pilot successful. Follow the deployment journey to verify one agent and one result before expanding.
Bring to review: the scope, pilot owner, target services and expected monitoring hours. Separate continuously reporting machines from temporary sessions.
Review the evidence
Use the measurement explainer to understand silent hops, interrupted uploads and changing paths. Save the incident window and relevant records using the investigation guide. Record confidence limitations alongside the result.
Bring to review: one representative investigation, what RouteSpear helped establish, and what remains uncertain.
Review security and deployment
Start with security and control, the trust model and, where applicable, self-hosting. Document your requirements for identity, access, data location, retention and network access. Ask about any requirement that the published material does not answer; a feature description is not a contractual commitment or certification.
Bring to review: required controls, links to supporting documentation and open questions for the supplier.
Agree a budget envelope
Use the pricing calculator with all relevant use cases selected. Model a normal month and a busier month. For VDI, estimate concurrent reporting sessions and reporting hours rather than the total number of machine identities created. Include telemetry volume and follow the budget assumptions.
Bring to review: saved assumptions, expected cost, peak scenario and the person responsible for reviewing usage. Confirm commercial terms before treating an estimate as an approved purchase.
Share the open questions
Use Contact for a written question or book a demo to review the workflow together. Include the pilot scope and anonymized requirements. Keep credentials and private measurement exports out of public forms.