Research file · 2026-08-31

FieldPulse

A mature field-service management platform with high independent-review volume, documented offline mode, and strong practical field-work coverage.

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
Dallas, Texas, United States
Legal entity
Flicent Inc.
History
2015
Category
Field-service management
Phone
Sales (817) 634-2218; support (469) 382-5668
Support
Phone, chat, demos; Mon–Fri 9am–6pm CST stated

Publicly identified principals

  • Gabriel Pinchev Founder & CEO

    Public profile identifies him as FieldPulse founder and an SMU Cox School of Business alumnus.

    Source
  • Alex Pinchev Co-Founder & Chairman

    Public company-profile material lists prior executive leadership at Acronis and Red Hat.

    Source

Public operating signals

Official Facebook and Instagram accounts were visibly active, with a substantially larger public audience and frequent educational, integration, and trade-community posts. LinkedIn appeared to publish less frequently in the accessible sample. Engagement included reactions and substantive comments.

Source

Pricing, contract, security & exit

Pricing
Custom, seat-based quote; exact rate card not public
Contract
One-year initial term with automatic renewal; 60 days written notice required before term end; cancellation does not yield a refund
Security
Privacy policy describes SSL and regular scanning. Independent SOC 2 or ISO evidence was not located.
Data exit
CSV export for customer information is documented. Complete account export, DPA, post-termination period, and wind-down plan were not verified.

Third-party assurance

Third-party assurance not located in reviewed public sources

No matching public CSA STAR, TrustPartners, or major trust-center listing was located under FieldPulse or Flicent Inc. Public policy materials describe SSL and regular scanning.

Source

Documented capabilities

  • Scheduling, dispatch, work orders, estimates, invoices, and e-signatures
  • Fleet/GPS functions and native mobile apps
  • Documented offline mode that saves data locally

Documented integrations

  • QuickBooks Online with two-way or one-way settings
  • API and webhooks through a support-issued key
  • CompanyCam and named partners

Looked for, not found in public sources

  • All subcontractor permissions
  • All job-costing plan dependencies

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
22/22
Integration & data sync Accounting, ecosystem connections, and API evidence
14/14
Adoption & mobile Field-team usability, onboarding, and offline evidence
13/14
Support & reliability Reachability, published support, and operating evidence
14/14
Commercial clarity Public pricing, billing model, trial, cancellation, and renewal terms
4/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
8/8
Public-Evidence Fit & Exit Score
80/100

How each dimension is scored ↗

Independent review signals

Large independent-review footprint. Users often cite usability, scheduling, support, and field use; some community feedback notes customization complexity and sync issues.

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

  • Get a written quote that defines seats, renewal, and implementation charges.
  • Request complete account-export, retention, DPA, and security terms.
  • Put a calendar control around the 60-day non-renewal notice window.

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 ↗