Research file · 2026-08-31

Upvoit

An India-based field-service CRM and dispatch platform with transparent per-user pricing, a wide connector list, and very small review samples.

This file records what was documented in reviewed public sources on 2026-08-31. It is not a security certification, a legal opinion, or a recommendation. Where something is marked not verified, it means we looked and did not find it publicly — not that it is absent or deficient.

The public record

Location
Ahmedabad, India
Legal entity
Excelhunters Technologies Pvt Ltd
History
2023
Category
Field-service CRM, dispatch, and operations
Phone
+1 7603 380 062
Support
Email, phone, and live sessions; support-hour statements differ across pages

Publicly identified principals

  • Paresh Kapuriya Founder & CEO

    Public profile identifies technology-leadership and ExcelHunters founding experience.

    Source
  • Kevinkumar Bhut Ratilal Director

    Public corporate data identifies him as a director of the named legal entity.

    Source

Public operating signals

Matched LinkedIn, Facebook, and Instagram accounts were actively posting product and operations content during the sample. The combined public audience was small; visible engagement was largely reaction-level. Follower count is not scored as product quality.

Source

Pricing, contract, security & exit

Pricing
$20/user/month monthly; $18 quarterly; $16 annual; 14-day trial
Contract
Verify cancellation and renewal terms in the accepted agreement
Security
Encrypted storage and daily backups are claimed. No independently verified SOC 2 or ISO evidence was located.
Data exit
PDF and Excel report export is documented. Full account export, post-termination availability, DPA, and continuity plan were not verified.

Third-party assurance

Vendor security controls documented

No matching public CSA STAR, TrustPartners, or major trust-center listing was located. Pricing and privacy materials describe encrypted storage and backups without a public independent artifact.

Source

Documented capabilities

  • Scheduling, dispatch, GPS, invoicing, payroll, CRM, and mobile apps
  • AI tools

Documented integrations

  • QuickBooks, Xero, Stripe, Zapier, Make, Twilio, and Square
  • API and Zapier webhooks are referenced

Looked for, not found in public sources

  • Offline mobile mode
  • Subcontractor-specific workflows

These are gaps in the public record. Ask the vendor directly; several may well exist without being publicly documented.

Score breakdown

Operational fit Field work, sales, estimating, and automation
18/22
Integration & data sync Accounting, ecosystem connections, and API evidence
11/14
Adoption & mobile Field-team usability, onboarding, and offline evidence
7/14
Support & reliability Reachability, published support, and operating evidence
9/14
Commercial clarity Public pricing, billing model, trial, cancellation, and renewal terms
9/10
Security, privacy & exit Third-party assurance evidence, privacy governance, and practical data exit
5/18
Company transparency Named principals, sustained operating communication, and review context
5/8
Public-Evidence Fit & Exit Score
64/100

How each dimension is scored ↗

Independent review signals

Public ratings are positive but tiny. Every rating here is shown with its count for that reason.

Small sample: 9 total reviews across all platforms. Ratings drawn from samples this size are not a reliable measure of broad market experience, in either direction.

Ratings belong to the platforms shown and were read on 2026-08-31. We do not host reviews, and we never convert review sentiment into a security or exit-readiness claim.

What to ask before you sign

  • Confirm which legal entity contracts with you and where data is held.
  • Resolve the conflicting published support hours in writing.
  • Confirm QuickBooks sync direction, offline behavior, and full export terms.

Source trail

Class A: legal, regulatory, product, or registry material. Class B: vendor-published support or product material. Class C: independent review platform or community source.

Something here out of date or wrong? Request a correction ↗