Neural · Connected products
The truck roll costs more than the fix.
Once equipment is in the field, the expensive part is rarely the repair. It's the drive, the diagnosis on site, and the second visit for the part nobody knew was needed. Where a fleet already reports diagnostic-quality telemetry, most of that is avoidable. Where it doesn't, that gap is the first thing to size.
Read this first. Neural is the agent architecture we run inside our own company. It has not yet been deployed inside another equipment operator, and you would be the first. Every capability below is labelled for exactly where it stands, and the labels separate what runs at CKS from what is in client beta from what is only designed.
Contents
- 01Where it goes wrongThree places, in the order they cost you
- 02One unit, one afternoonThe whole loop, start to finish
- 03The workforceFive workflows and exactly where each one stands
- 04What we've actually doneStated precisely, including what we haven't
- 05DeploymentThe questions your IT group will ask first
- 06How it startsOne workflow, sixty days, read-only
[01]Where it goes wrong
Three places it costs you.
You find out when the customer calls
The unit reported the symptom hours or days before anyone acted on it. The first human to notice was the person paying for it, which is the worst possible order for that conversation.
Half the visits didn't need a visit
A technician drives out, finds a fault that could have been cleared remotely or a part that should have been on the van, and the customer waits for a second appointment either way.
The fleet data is real and unread
If the fleet reports at all, nobody has the hours to read a thousand devices looking for the pattern that would have predicted the failure. The data becomes an archive rather than a signal.
[02]One unit, one afternoon
What it looks like before dispatch.
Written in the present tense for readability. This is a designed sequence, not an account of something that has happened at a customer.
- 14:02
A unit's telemetry starts drifting in a way that matched three prior failures across the fleet, none of which looked urgent on the day.
- 14:03
The agent layer pulls the service history, the firmware version and what the previous three had in common, and drafts what a technician would need to bring.
- 14:20
Service manager reads it, agrees, and schedules the visit for the routine window rather than an emergency one.
- Or
the drift is one the fleet has cleared remotely before, in which case the recommendation says so and no van moves.
- ·
The customer hears from you before they notice anything, which is a different conversation entirely.
It recommends. Dispatch is a person's call, every time.
[03]The workforce
Five workflows, and where each one actually stands.
Every one has the same shape: a trigger, agent work, a human checkpoint, an artifact. The status under each name is the honest part, and it names where a workflow has actually run rather than how finished it feels.
Failure-pattern watch
Trigger
Continuously, across the fleet.
Agent actions
Correlates telemetry drift against prior failures, firmware versions and install conditions, rather than alerting on a single threshold.
Human checkpoint
Service engineering confirms the pattern before it becomes a rule.
Output
Units flagged with the historical match that flagged them.
Dispatch triage
Trigger
Before a visit is scheduled.
Agent actions
Checks whether the fault has been cleared remotely before, and if not, drafts the parts and steps the visit will need.
Human checkpoint
The service manager decides whether anyone drives.
Output
A recommendation with the parts list attached, or a remote fix.
Customer status draft
Trigger
When a unit is flagged.
Agent actions
Drafts the note to the customer in your voice, with what was seen and what happens next.
Human checkpoint
Nothing reaches a customer without a person sending it.
Output
A ready draft, so contact happens before the complaint.
Executive brief
Trigger
Every morning, before anyone is at a desk.
Agent actions
Reads across the systems that hold your operation and writes what changed, what slipped, and what needs a decision today.
Human checkpoint
You reply in the thread; the work routes from there.
Output
One brief, in the order you'd have asked for it.
Warranty exposure
Trigger
Monthly, across the installed base.
Agent actions
Projects which cohorts are trending toward warranty claims based on the patterns already seen, and sizes the exposure.
Human checkpoint
Finance and service review together before it informs a reserve.
Output
An exposure view by cohort, with the evidence behind it.
[04]Standing
What we've actually done.
Stated precisely, because in this category precision is the differentiator.
We built fleet monitoring for 1,000+ devices
A cloud platform for remotely monitoring, diagnosing and troubleshooting atmospheric water generation units deployed in corporate offices and school districts nationwide.
That platform removed truck rolls, measurably
60% reduction in on-site visits and 50% faster resolution, client-reported from the original engagement. To be exact about attribution: that was the conventional fleet platform, built before Neural existed. The agent layer had nothing to do with those numbers.
We run our own company on the agent layer
Neural plans, builds, reviews and ships at CKS every day. Demonstrable on a call.
The service workflows are designed, not deployed
Specified against the fleet platform we built. They have not run against another operator's installed base.
What we haven't done: run these agent workflows against another operator's fleet.
[05]Deployment
The questions IT will ask.
Answered here rather than in the third meeting.
- Where it runs
- Your infrastructure or a private tenant. Not a shared multi-tenant product.
- What it reads
- The systems you already run. Read access first, always.
- Who approves
- Actions you designate as consequential stop at a named person before they happen. You set that boundary; the platform enforces it rather than relying on discipline.
- What's recorded
- Each agent action is logged with its inputs, the sources it cited, what it did, and who approved it. The things that hold up in a review.
- Who owns it
- Your data and configuration are yours, and we'll put the exit terms in the contract rather than asking you to trust a web page.
[06]How it starts
One workflow. Sixty days.
Not a platform rollout. We pick the single workflow where it is costing you most, stand it up against your real systems, and you judge it on whether it caught things your people did not have time to.
Week 1
The workflow and the success metric are agreed in the first session, not discovered over a month. Read-only access to the systems it needs; your security review runs in parallel.
Weeks 2–7
It runs alongside your people on live work. Every output reviewed by your team, nothing acted on automatically, false positives tuned weekly.
Week 8
Measured against the metric we set in week 1. Keep it, change it, or walk away. Because it stayed read-only, walking away means revoking credentials and removing an integration rather than migrating off a platform.
- What it costs
- Fixed fee, quoted after the working session, so it is priced against your actual systems rather than a guess. No per-seat licence during the pilot.
- How it's judged
- One number, agreed before we start. Usually exceptions caught that your team didn't have hours to catch, measured against a baseline period.
- What we need
- Read-only access to two or three systems, one person who reviews the output, and an executive who reads the weekly.
- What you keep
- The configuration and everything it produced, whether or not you continue. Data handling and retention are in the agreement before access is granted.
A working session is ninety minutes with your operators, not a pitch. We map where the cost actually lands and tell you which parts of it are worth pointing an agent at, including the parts that are not.
Other sectors