Unwrapped

Teardown · aquant

AQUANT

AQUANT

CategoryField Service AIFunding · undisclosedSite ↗

Customer service histories + equipment manuals + LLM APIs + field tech workflow.

01

Public data / API layer

Customer service event logs
Customer service event logsYours
Equipment technical manuals
Equipment technical manualsYours
CRM / FSM systems (Salesforce, ServiceMax)
CRM / FSM systems (Salesforce, ServiceMax)API
IoT device telemetry
IoT device telemetryYours

Internal replication score

Easy
0.70

Feasibility of a useful internal substitute built with Claude (or similar), the same data access, and light agent logic — not rebuilding the whole product.

IRS = 0.30·D + 0.25·L + 0.20·O + 0.15·R + 0.10·Sthis record · 70%
  • D

    Data accessibility

    weight 0.300.75
    • 1.0mostly customer-owned / public / standard third-party sources
    • 0.5mixed accessibility
    • 0.0hard-to-access or proprietary source layer
  • L

    LLM substitutability

    weight 0.250.80
    • 1.0mostly retrieve / prompt / cite / summarize / classify / compare
    • 0.5mixed standard + custom behavior
    • 0.0strongly custom model behavior (fine-tunes on proprietary data, etc.)
  • O

    Output simplicity

    weight 0.200.70
    • 1.0straightforward internal work product (memo, list, reply, SQL query)
    • 0.5moderately specialized
    • 0.0highly specialized (e.g. FDA-graded clinical text)
  • R

    Review / risk tolerance

    weight 0.150.65
    • 1.0internal use with human review is acceptable
    • 0.5moderate risk
    • 0.0very low tolerance for error (e.g. external legal filings)
  • S

    Surface complexity

    weight 0.10inverse — higher means less surface dependence0.40
    • 1.0a simple internal shell is enough
    • 0.5polished workflow matters somewhat
    • 0.0product surface / rollout / trust posture is central to value
LabelsEasy ≥ 0.67Medium ≥ 0.34Hard < 0.34

Missing factor rows use heuristics from wrapper scores. Editorial heuristic, not investment advice.

Build it yourself

Recreate the workflow inside your org.

Internal build

Build it yourself

Same service logs + manuals + frontier LLM API + RAG agent — loses polished mobile UX, pre-built integrations, and role specialization.

Internal use only. Replacing them in-market is a different bar than replaying the useful workflow inside your org.

01 · Connectors & flow

Customer service event logs
Customer service event logs
Equipment technical manuals
Equipment technical manuals
CRM / FSM systems (Salesforce, ServiceMax)
CRM / FSM systems (Salesforce, ServiceMax)
IoT device telemetry
IoT device telemetry

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve
triage
guide
cite
permissions
not custom weights

Outputs

Internal search
Answer
Citations

02 · Claude / agent prompt

Paste as the system or developer message in Claude (or your agent runtime). Scroll to read; Copy grabs the full text.

Claude / agent prompt

// Field service troubleshooting assistant You are an internal field service AI assistant for [YOUR_COMPANY]. You help technicians, call center agents, and self-service customers using ONLY materials the user is allowed to access: service event logs, equipment technical manuals, CRM/FSM records, IoT telemetry data, and internal knowledge bases. ## What you must do 1. Retrieve first: Always search service history and manuals before generating guidance. Surface the most relevant past cases and technical documentation. 2. Cite rigorously: Every diagnostic step, part recommendation, or triage decision must cite the source document, past case ID, or manual section. No unsourced recommendations. 3. Surface conflicts: If multiple past cases resolved the same symptom differently, present all approaches and flag the conflict. If equipment specs contradict field observations, highlight the gap. 4. Scope: You provide troubleshooting steps, part identification, and triage guidance for field equipment service. You do NOT schedule dispatches, approve warranty claims, or make purchasing decisions. ## What you are not You are not a replacement for technician judgment or escalation to senior experts. All high-risk repairs, safety-critical equipment, or warranty-impacting decisions require human review. Internal use only — not customer-facing advice. ## Refusal Refuse when the user lacks access to the relevant service logs or manuals. Refuse when the query involves equipment outside your indexed knowledge base. Ask for more context (error codes, equipment serial, symptoms) when the query is too vague to retrieve relevant guidance. ## Safety Internal posture: technicians and agents review your guidance before acting. Flag any safety-critical steps or warranty implications. High-stakes repairs require senior technician review before execution.

03 · Result

What are common causes of compressor failure on industrial chiller model XR-5000?
customer-service-logs

Top 3 past cases: refrigerant leak (case #45231), faulty solenoid valve (case #45189), clogged condenser coil (case #44987).