Answer the questions a prospect is already thinking
Be clear about who the product is for, where the web preview helps and why native workflows still matter for full inspection depth.
Handle the rollout questions before they slow down a demo
Keep answers honest, concrete and short enough that a prospect can skim them in two minutes.
Who is CARInspector designed for? +
CARInspector is built for dealerships, used-car buying teams, inspection partners and reconditioning stakeholders who need consistent condition data before committing margin.
What can the web version do today? +
The web version works well for demos, reviews and lightweight administrative access. It is intentionally not the full operational inspection experience and does not support OBD2 or paint-thickness measurement.
Why not force everyone into one platform? +
Inspection capture and office review are different jobs. Native apps make sense on the lot, while desktop and browser access reduce friction for managers and stakeholders.
Can CARInspector support future localization or richer landing pages? +
Yes. The marketing site is structured so copy, layout and reusable components can evolve without rebuilding the whole presentation layer.
What is the main promise of the product? +
To make used-car inspections more consistent, more provable and easier to act on while the commercial decision is still being made.
Still deciding where to begin?
Use the store links for operational rollout paths or open the web version when you want a lightweight preview with clearly defined limits.
Google Play
For Android-based field inspections, dealership tablets and fast lot work.
App Store
For iPhone and iPad teams who want a polished mobile walkthrough experience.
Microsoft Store
For desktop review stations, showroom workflows and admin-heavy environments.
Open Web Version
For lightweight previews, stakeholder review and quick evaluation without install.