SPOTIO

Two model capabilities carry the current positioning and the platform beneath them is conventional software.

The co-pilot handles the parts of field work that happen between stops: preparing a brief before a visit, capturing notes by voice while driving, scanning business cards, drafting follow up messages and offering in application guidance. The recommendation engine scores every record, proposes a next action, learns from outcomes and refreshes both during the day and overnight.

The positioning leans on them heavily. The page title, the headline and the opening paragraph all lead with the model layer, and the co-pilot launched only in April of this year.

What holds this out of the top band is what the customer is actually buying. Territory boundaries, route optimisation, location verified activity capture, pipeline management and record system synchronisation are deterministic software, and they are the reason a field team adopts this rather than a conventional record system. Third party sources report the co-pilot is sold as a separate module rather than included, which would confirm the reading.

The genuinely novel framing is that this model layer is built for a representative in a vehicle rather than at a desk, and voice capture between stops is the right answer to that constraint.

Ask whether the co-pilot is included or sold separately, and at what rate.

Every action the co-pilot takes is confirmed by the representative before it saves, stated plainly and repeated.

That sentence appears on the home page and again in the vendor's own guidance, which describes voice notes and activity updates being captured between stops with a confirmation tap before anything is written to the platform. It is the clearest human in the loop commitment recorded anywhere in this index. Most vendors describe approval as a setting, an option or a tier feature. This one states it as how the product behaves.

The design reason is worth noting: a representative dictating notes while driving cannot proof read, so the confirmation happens deliberately at the next stop rather than being assumed.

Oversight runs the other way too. Location verification confirms that a logged visit actually took place, which is a control on the person rather than the software, and hierarchical territory permissions govern who may access which leads. Real time dashboards show completed visits, time in field and territory coverage.

One of the vendor's own customers addresses the tension directly, framing that visibility as helping representatives earn more rather than monitoring them, which indicates the objection is common enough to answer.

What is unstated: what the recommendation engine may do unsupervised, and whether any audit trail records changes.

Ask whether the confirmation step can be disabled by an administrator.

Two model products, one refresh cadence disclosed, and no technology named.

Two passes across the home page, the feature navigation, the frequently asked questions and the product announcement located no model provider, no model name, no version, no statement of what visit notes, voice recordings, photographs or customer data are transmitted for inference, no training or retention position and no accuracy figure.

The recommendation engine is where the omission carries weight. It scores every record, ranks what a representative should do next, and improves through machine learning from outcomes. That scoring determines how a person spends their working day and which prospects go unvisited, and no basis, weighting or error rate is published.

One disclosure is better than the norm and deserves noting: the refresh cadence is stated as intraday and nightly, which tells a buyer how quickly a recommendation reflects new activity. That is operational detail most vendors omit entirely.

Voice capture raises a second question nothing addresses. Dictated notes between stops are audio of an employee, processed somewhere unstated, and business card scanning transmits images of third party contact details.

Ask which provider processes voice capture and what the recommendation score is computed from.

Thirteen named logos, six named executives quoted, two downloadable case studies and direct links to individual verified reviews.

The attribution is unusually complete. A chief sales officer, an executive vice president, a director of operations, a company president, a senior vice president of sales and marketing and a vice president of business development are each quoted by name against their own company. Two of those link to full case study documents, and one is reproduced inline with a structured problem and solution breakdown naming six specific operational failures the customer had before adoption.

Several testimonials link directly to the individual review on an independent platform rather than to a review page generally, so a reader can verify the quotation is real and unedited.

A research report on the state of business to business field sales carries its own statistics, and a newsroom documents product releases.

The deduction concerns the headline figures. Increases of forty six percent in productivity, twenty three percent in revenue and sixteen percent in team turnover reduction are labelled as verified results, and no methodology, sample, period or definition accompanies any of them. The section is illustrated with images whose filenames indicate they were generated rather than photographed, which is a small thing and sits oddly under a heading about verification.

Ask how the forty six percent productivity figure was measured and across how many customers.

Do not knock handling is the channel appropriate suppression list and it is a genuine one.

The vendor's own guidance describes arming representatives with residential data and skipping do not knock houses so they focus on addresses likely to convert. That is the doorstep equivalent of an exclusion list, and it matters legally as well as commercially: many municipalities operate do not knock registries and ordinances, and knocking on a flagged door is an enforcement matter rather than a courtesy failure.

Building the exclusion into the targeting layer, so the address never appears on a route, is better than relying on a representative to check.

A dedicated security and compliance page sits in the feature navigation, and call recording is described as serving training and compliance purposes.

What two passes could not locate: how do not knock lists are sourced or kept current, any calling hour restriction, any consent basis for the residential property and demographic data, and any opt out mechanism for the messaging and calling capabilities offered through the communications module.

That last gap matters because the multi channel module adds calling and texting to a product otherwise operating in person, which brings a different regulatory regime with it.

Ask where do not knock data comes from and how often it refreshes.

A privacy policy, a compliance page, and an unusual category of personal data nobody discusses.

What is published: a privacy policy and terms of service, a security and compliance page in the feature navigation, and explicit consent checkboxes on the enquiry forms linking to the policy. Two passes located no processing agreement, no subprocessor list, no retention schedule, no deletion commitment, no residency statement and no rights request process.

The holdings are what make this axis unusual for the index. Three categories accumulate here that no other record carries.

First, employee location data. Activity capture with location verification means the platform holds a record of where a named representative physically was and when, continuously, throughout their working day. That is among the most sensitive categories an employer can collect about staff.

Second, residential data about private individuals: property type, homeownership status and demographics for households that have had no contact with anyone.

Third, voice recordings and photographs captured in the field.

The vendor's own testimonial acknowledges the first concern directly, arguing the visibility is not surveillance, which indicates buyers raise it.

Ask how long representative location history is retained and who can see it.

One source is named and the more sensitive one is not.

The named one is good practice. For business to business work, representatives tap a building on the map and contact details are pulled from a major mapping platform, which the vendor identifies. That platform operates a commercial interface with published terms, so a buyer can establish what is permitted and what it costs.

The unnamed one is the residential data, and it is the half that needs disclosure most. The lead tool filters households by fifteen data points including property type, homeownership status and demographic attributes. Two passes located no supplier, no collection method, no consent basis, no accuracy claim and no refresh cadence for any of it.

That is information about private individuals at their home addresses, assembled so a stranger can decide whether to knock. The people described have not engaged with anyone and have no way to know they have been scored and filtered.

Do not knock status is presumably sourced alongside it and is equally unattributed, which matters more, because an out of date exclusion list produces a visit that should not have happened.

Ask which supplier provides the residential property and demographic data.

The one external data source is named, and it is a platform with a commercial interface built for exactly this.

Business contact details are pulled from a major mapping platform, identified by name in the vendor's own guidance. That platform publishes a commercial interface with documented terms and pricing for precisely this kind of lookup, so the arrangement is very likely licensed and a buyer can verify the terms independently. Naming the source rather than presenting the capability as proprietary is the transparent choice.

Record system integrations run to four major enterprise platforms plus a calendar service, all through sanctioned partner paths.

Two passes located no scraping, no social network automation, no browser extension operating a property the vendor does not own, no account renting and no capability depending on a third party failing to notice.

That clean position follows from the product's nature. A platform whose primary channel is a person physically walking up to a building has little reason to reach into someone else's network.

The residual question sits on provenance rather than terms: the residential data supplier is unnamed, so whatever licence governs it is unestablished, and that is graded separately.

Ask whether the mapping platform lookups run under a commercial interface agreement.

The confirmation gate is the safety control, and it is the right one for this product.

Because every co-pilot action requires a representative's confirmation before it writes, no generated text, transcription or extracted field reaches a customer record unreviewed. For a system capturing dictated notes in a moving vehicle, where transcription errors are likely and the speaker cannot proof read, that gate is doing real work rather than performing diligence.

Access controls are substantive: hierarchical territory permissions govern which representatives can see which leads, and a security and compliance page sits in the main feature navigation rather than the footer.

What is absent on the model side: no provider named, so no training or retention position exists for voice recordings, photographs, business card images or customer records passing through inference. No accuracy figure supports the recommendation scoring that directs a representative's day. No evaluation is published.

On the general side, two passes located no encryption statement, no incident response process, no breach notification commitment, no named security contact and no vulnerability disclosure route, though the compliance page was not opened.

The voice and photograph capture is the material worth asking about, since it accumulates continuously in the field.

Ask what happens to voice recordings after a note is confirmed.

A real person walks up and knocks, which resolves most of what this axis measures.

There is no persona, no synthetic sender, no automated messaging pretending to be human, no manufactured social signal and no undetectability question anywhere in the primary channel. The person on the other side of the door or the reception desk is looking at an actual human being who travelled there. Across a session dominated by records where the central question is whether the recipient knows they are talking to software, that is a categorical difference.

Do not knock handling gives a household a route to not be approached at all, which is the strongest form of recipient control available on this channel.

Two gaps keep it below the top band. The co-pilot drafts follow up emails and text messages after a visit, and nothing indicates to the recipient that the message was machine drafted. And call recording is offered through the communications module with no described notification to the person on the line, in a product sold across states with differing consent requirements.

One further consideration belongs here: the household has been scored on property and demographic data before anyone arrives, and has no visibility of that.

Ask what a recipient hears when a recorded call begins.

Four major enterprise record systems named, which is more than the size of this vendor would suggest.

The named integrations cover two of the largest enterprise resource platforms in the world alongside two of the most widely deployed record systems, plus a calendar service. Reaching that far up the enterprise stack matters here because the product's stated position is that it complements a record system rather than replacing it, and that promise only holds if the connection to the incumbent actually works.

A dedicated integrations page, a knowledge base on its own subdomain and a support site sit alongside.

The comparison hub is worth noting as an unusual choice. The vendor publishes six individual pages comparing itself against named competitors, which invites the comparison rather than avoiding it.

Around it: mobile applications, a podcast, an ebook library, a newsroom and a blog.

What two passes could not locate: any interface documentation, any authentication scheme, webhooks, or a model context protocol server. For a platform whose value depends on field data reaching other systems, the absence of a documented interface is the gap, and synchronisation appears to run only through the named connectors.

Ask whether a documented interface exists and what it exposes.

Nothing about the infrastructure was located, and the holdings are unusually sensitive.

Two passes across the home page, the feature navigation, the frequently asked questions and the footer found no hosting provider, no region, no data centre, no residency commitment, no tenancy or isolation model, no encryption statement, no backup position, no continuity plan, no uptime commitment and no status page. A security and compliance page exists in the navigation and was not opened, and would be the natural home for some of this.

What sits in storage makes the question sharper than usual. Continuous location history for named employees throughout their working day. Voice recordings captured in vehicles. Photographs taken in the field. Residential property and demographic records for households. Call recordings. Territory and pipeline data synchronised from enterprise record systems.

Employee location data in particular attracts specific handling requirements in several jurisdictions, and a buyer operating across state or national boundaries would need to establish where those traces are processed before deploying.

The company is identifiable, operating from a published address in Texas with a telephone number, so there is an accountable entity even though its infrastructure is undescribed.

Ask where location history and field recordings are stored.

A security and compliance page sits in the product navigation rather than the legal footer, which is the right place for it.

That placement is a small signal worth reading. Treating security as a feature a buyer evaluates, alongside territory management and route optimisation, rather than as a legal document filed at the bottom of the page, suggests it comes up in sales conversations often enough to warrant the position. The page was not opened in this pass, so what it contains is unrecorded.

Around it: a privacy policy, terms of service, hierarchical permissions controlling data access by territory, and single sign on reported by third parties as available at the top tier.

What two passes could not locate: any certification, audit report, penetration test, trust portal, encryption statement, subprocessor list, vulnerability disclosure route or named security contact.

The buyer profile makes the question live. Named customers include a metal trading business, a financial services company and a telecommunications provider, and the vertical list includes medical devices and pharmaceuticals, all of which run supplier assurance programmes that require documentary evidence.

Employee location tracking adds a dimension most assurance reviews are not used to assessing.

Ask which certifications the security and compliance page lists.

The vendor used to publish four named tiers with figures and stopped.

Third party records show a structure of four plans at thirty nine, sixty nine and one hundred and twenty nine dollars per user monthly with an enterprise tier above. In 2024 that was replaced by two segment based plans plus a custom arrangement, and the numbers came off the site. A plans page exists and, according to multiple independent sources testing it this year, carries no figures and routes to a demonstration request.

Removing published pricing is a deliberate act rather than an omission, and it is the finding here.

What a buyer cannot see without a sales call: the price, but also four material constraints. There is a five user minimum, so a smaller team cannot buy at all. Billing is annual only with no monthly option. There is no free plan and no free trial. And four capability modules are sold separately from the base subscription, covering calling and texting, the model co-pilot, the residential lead tool and one further module, none with a published rate.

Those add ons matter because the communications module carries the calling and texting capability that several published case studies describe as central to the value.

Third party estimates place the entry point near twenty five dollars per user monthly and the floor around fifteen hundred dollars annually before additions, with figures varying widely by source and vintage.

Ask what each of the four add on modules costs per user.

The architecture works in the customer's favour and nothing about leaving is described.

The favourable part is structural. This platform positions itself explicitly as complementing a record system rather than replacing it, and synchronises field activity into whichever one the customer already runs. That means visits, notes, lead status and pipeline movement accumulate continuously in a system the customer owns, so the operational history is not trapped here in the first place. For a customer running one of the four named enterprise platforms, most of what matters has already left.

What two passes could not locate: any export mechanism, format or scope statement, any deletion commitment, any retention position after cancellation, any account closure process, or any interface through which data could be extracted programmatically.

The material that would not have synchronised is worth naming: territory definitions built up over years, route history, location verification traces, field photographs and voice notes, and performance analytics by representative.

Commercially the exit is constrained rather than clean. Annual billing with a five user minimum and no monthly option means a customer cannot leave mid term, and no cancellation terms were located.

Ask what an export contains and whether territory definitions travel.

The primary channel has no deliverability question, and the secondary one is undescribed.

A representative knocking on a door does not need authentication records or a warm up pool. The channel equivalent of discipline here is whether the right doors are approached, and on that the product does well: do not knock exclusion applied before routing, filtering by property attributes so effort concentrates where it is relevant, and route optimisation reducing the number of wasted approaches.

Call recording supports review of how conversations actually went.

The gap sits in the communications module, which adds calling, email and text messaging sent from the mobile application, and which case studies describe customers adopting. Two passes located no sender authentication guidance, no sending limits, no bounce handling, no text messaging opt out mechanism, no calling hour restriction and no measured data for any of it.

That module is sold separately from the base subscription, which may explain why it is documented lightly, but a customer buying it is sending on three regulated channels with no described discipline behind any of them.

Ask what limits and opt out handling apply to the messaging and calling module.

Two full solution paths, eight named verticals, four role paths, and a frequently asked question rejecting the narrow label.

The business to business path covers business services, commercial construction, distribution, and medical devices and pharmaceuticals. The consumer path covers home improvement, home services, roofing and storm restoration, and telecommunications. Each has its own overview page and its own vertical pages beneath, rather than one template with a swapped noun.

Medical devices and pharmaceuticals is the strongest signal that the business to business side is real. That is a regulated, relationship led, multi visit field motion with nothing in common with doorstep selling, and building for it is a deliberate choice.

Roles are segmented separately for representatives, sales leaders and revenue operations, plus a fourth path for growth investors, which is an unusual audience to address directly and suggests private equity backed roll ups among the customer base.

The enquiry form asks industry across fourteen options and team size across six bands from one to four representatives up to five hundred and one plus, which shows the genuine spread.

The vendor answers the positioning question head on, stating plainly that it is not merely a canvassing application and naming the full vertical range.

Ask which verticals the business to business side is strongest in by customer count.