How Tools in the Wild Tests and Reviews Software

Written by Olivia Evans · Updated July 2026

Tools in the Wild publishes hands-on software comparisons for the field service industry. Our goal is to help readers understand how products differ in real workflows, not just vendor marketing claims or feature lists that claim a product has one feature that’s barely built out.

Whenever possible, we access and use the products ourselves. We compare them using realistic business scenarios, document what happens, verify factual claims against official sources, and explain where our conclusions reflect editorial judgment.

Our Approach at a Glance

  • Hands-on access whenever possible
  • Official-source verification
  • No paid rankings
  • Visible limitations and corrections

Our Editorial Principles

Our reviews follow a few basic principles:

  • Products should be tested hands-on whenever possible.
  • Competing products should be evaluated through comparable workflows.
  • Direct observations should be distinguished from vendor-documented capabilities.
  • Material limitations, account restrictions, and commercial relationships should be disclosed.
  • Vendors cannot purchase rankings or control conclusion.
  • Recommendations should reflect the needs of the reader and the use case being evaluated.

Note: Top-ranking products are not necessarily the best product for every business. Our articles explain which product performed best for the specific workflows, priorities, and customer type covered by that comparison. Our top choice is usually the best one-side fits all product with the most extensive capabilities for certain needs.

How We Choose Products

We select products based primarily on:

  • Popularity within the market
  • Market position and relevance
  • Availability for meaningful testing

Complimentary access may make it possible for us to review a product that would otherwise be difficult to evaluate. Please note it does NOT guarantee inclusion, a favorable result, or a particular ranking.

Not every relevant product can be included in every comparison. Exclusion does not necessarily mean that a product is inferior. It may reflect the scope of the article, limited access, or the need to keep the comparison focused.

How Hands-On Testing Works

Whenever possible, every ranked product is accessed and tested directly by the Tools in the Wild editorial team.

For comparison articles, we create a realistic sample business and repeat the same general scenario across the products being evaluated. Depending on the topic, this may include creating customers, employees, products, jobs, appointments, invoices, reports, projects, automations, or other relevant records.

We then complete the workflows that matter most to the article’s target reader.

Examples may include:

  • Setting up the product
  • Configuring a core feature
  • Completing a transaction or operational workflow
  • Reviewing reporting and administrative tools
  • Testing mobile and desktop interfaces
  • Checking the experience available to employees or customers
  • Identifying required add-ons, workarounds, or separate configuration steps

Our general standard is to complete each evaluated workflow at least once. Articles may use additional repetitions when necessary to confirm inconsistent behavior or test different configurations.

The page-specific methodology on each comparison explains the exact products, interfaces, workflows, account types, testing period, and limitations involved.

When Direct Product Access Is Limited

Hands-on access is our preferred standard, but it is not always possible to access every feature or subscription level.

When direct access is unavailable or restricted, we may use:

  • Official vendor documentation
  • Vendor demonstrations
  • Product videos or training materials
  • Information provided by vendor support
  • Publicly available product interfaces and customer-facing materials

We do not present a product as fully hands-on tested when our conclusions are based primarily on documentation or demonstrations. Any material limitation in access will be disclosed in the relevant article.

If a feature is unavailable in a trial account, we check official documentation and may contact vendor support to determine whether it is available through another subscription tier, add-on, role, or configuration.

How We Compare Products

Tools in the Wild does not force every comparison into a universal numerical score.

Instead, we compare the products feature by feature and examine how their differences affect the workflow being tested. Rankings are based on editorial judgment after completing the relevant tasks.

Depending on the article, we may consider:

  • Whether the workflow can be completed
  • How directly the product supports it
  • How much setup or configuration is required
  • Whether separate modules or add-ons are needed
  • The amount and quality of information available
  • The experience for administrators, employees, and technicians
  • Reporting and management capabilities
  • Mobile and desktop usability
  • Important limitations or workarounds

Statements such as “easier,” “faster,” “more flexible,” or “best for” are editorial conclusions based on our testing. They are not presented as objective facts.

How We Collect and Verify Evidence

During testing, we may collect:

  • Screenshots
  • Written testing notes
  • Sample reports
  • Customer-facing messages
  • Support responses
  • Links to official documentation

Selected screenshots and supporting sources may be included in the article. We do not normally publish every internal note or test record.

After hands-on testing, we check factual product-capability claims against current official vendor documentation whenever suitable documentation is available.

We distinguish between:

What We Observed

This is behavior the editorial team directly encountered while using the product.

What the Vendor Documents

This is a capability described in an official help center, support article, product guide, or response from vendor support.

What We Concluded

This is our editorial interpretation of how well the product performed for the use case being evaluated.

The absence of a feature from a help article is not automatically treated as proof that the feature does not exist. When the evidence is incomplete, we qualify the claim, contact support when practical, or state that we could not verify the capability.

Trial, Paid, and Complimentary Accounts

Our testing may use trial accounts, accounts paid for by Tools in the Wild, or complimentary access provided by a vendor.

The type of access may influence which products we are able to test. It does not determine the outcome of the review.

Editorial Independence

Tools in the Wild is currently free of affiliate links and sponsored content.

Vendors do not pay for inclusion or rankings, do not review articles before publication, and do not control our findings or conclusions.

Vendors may contact us after publication to report factual errors, provide updated documentation, or explain product changes. We review those submissions, but vendors cannot require us to change an editorial opinion or ranking.

Tools in the Wild may introduce affiliate links or sponsored content in the future. Any such relationship will be clearly disclosed. Commercial relationships will not determine product rankings or override our editorial standards.

Use of Artificial Intelligence

Tools in the Wild may use artificial-intelligence tools to edit existing text for grammar, readability, organization, or clarity.

AI is not used to conduct product testing, make ranking decisions, or replace the underlying research and evidence. It is also not used to create the initial research or draft findings for our reviews.

Published conclusions remain the responsibility of the Tools in the Wild editorial team.

Updates and Corrections

Software products change frequently. Features, prices, subscription tiers, interfaces, and documentation may change after an article is published.

We update articles when we identify meaningful changes in:

  • Product behavior
  • Official documentation
  • Pricing or packaging
  • Subscription requirements
  • Availability of features
  • Material factual information

A visible review or update date may be shown when an article has been substantially checked or revised.

Readers and vendors are welcome to report potential errors. Corrections are evaluated using direct product evidence, official documentation, and other relevant primary sources.

To report a correction, email hi@toolsinthewild.com with:

  • The article URL
  • The statement that may be inaccurate
  • A description of the issue
  • Supporting official documentation, when available

Limitations

No software evaluation can test every feature, configuration, subscription level, integration, device, or edge case.

Unless an article states otherwise:

  • Each core workflow is generally tested once.
  • Results reflect the product at the time of testing.
  • Features may differ by subscription tier or add-on.
  • Account permissions may affect what is visible.
  • Regional availability may vary.
  • Mobile testing may be limited to one operating system.
  • Integrations are not assumed to work unless they were tested or clearly documented.
  • Vendor documentation may change after publication.

Every comparison includes page-specific limitations when they materially affect the findings.

Page-Specific Testing Disclosures

Each hands-on comparison includes a concise “How we tested” section explaining:

  • Which products were evaluated
  • When they were tested
  • Which desktop and mobile interfaces were tested
  • Which workflows were completed
  • What evidence was collected
  • Any important limitations

This allows readers to understand both our general editorial standards and the exact work behind a particular recommendation.

Our mission is simple: honest, hands-on software reviews you can trust.