Proof, and how to read it
Arrowhead delivering a system and a vendor publishing somebody else's result are different things. Every claim on this site says which one it is.
One delivered case, five industry references
That count is the honest one, and it is worth stating rather than hiding behind a grid of cards. Arrowhead has operated since 1989; most of that work sits behind customer confidentiality, and the published record is only what a source will support.
1
case Arrowhead delivered, named by the publishing vendor alongside its technology partners. The tracking software on that project was Xemelgo, not Mobi, and the page says so.
5
industry references published by Zebra Technologies from deployments other partners delivered. They show what the technology does. They are not Arrowhead's results.
Curtiss-Wright
Manufacturing · Delivered with Arrowhead, Xemelgo, and Zebra Technologies
Texas Children's Hospital
Healthcare · Industry reference from Zebra Technologies
Cepheid
Manufacturing · Industry reference from Zebra Technologies
Fanatics
Retail · Industry reference from Zebra Technologies
G3 Boats
Manufacturing · Industry reference from Zebra Technologies
DRMP, Inc.
Field Service · Industry reference from Zebra Technologies
Named accounts
Customer relationshipArrowhead has delivered rollouts and projects for these organizations, across 14 industries, and the accounts are current. Deliberately absent is a number against any of them: what a system did and what it achieved is a separate claim needing a source and the customer’s approval. Where that exists it appears above as a case study with its source attached.
AmgenPharmaceuticals · Arrowhead designed and deployed the system named.
AppleTechnology · Arrowhead designed and deployed the system named.
- Arizona State UniversityEducation · Arrowhead designed and deployed the system named.
- Banner HealthHealthcare · Arrowhead designed and deployed the system named.
- City of PhoenixGovernment · Arrowhead designed and deployed the system named.
Coca-ColaFood & Beverage · Arrowhead designed and deployed the system named.
DescartesSupply Chain Software · Arrowhead designed and deployed the system named.- Fry's Food StoresRetail · Arrowhead designed and deployed the system named.
GrifolsPharmaceuticals · Arrowhead designed and deployed the system named.
- Honeywell AerospaceAerospace · Arrowhead designed and deployed the system named.
- Intel CorporationManufacturing · Arrowhead designed and deployed the system named.
Mayo ClinicHealthcare · Arrowhead designed and deployed the system named.
Mission FoodsFood & Beverage · Arrowhead designed and deployed the system named.NestléFood & Beverage · Arrowhead designed and deployed the system named.
- Penske LogisticsLogistics · Arrowhead designed and deployed the system named.
- RaytheonDefense · Arrowhead designed and deployed the system named.
- Shamrock FoodsFood Distribution · Arrowhead designed and deployed the system named.
Walt DisneyEntertainment · Arrowhead designed and deployed the system named.
Names and marks are published with the account holder’s agreement. Arrowhead does not publish a customer mark it has not been given permission to use, and does not source marks from a third-party logo service.
What each label on this site means
Arrowhead delivering a system, a vendor publishing somebody else's result, a credential a third party issued us, software we run ourselves, a capability we offer, and a direction we have not shipped are six different things. They are labeled differently everywhere they appear.
- Arrowhead-delivered result
Arrowhead delivered the system and the result was measured in the customer's operation. Any partner that supplied part of the system is named.
- Vendor-supported result
A vendor published this result from a deployment another partner delivered. Arrowhead did not deliver it.
- Accredited capability
A credential or facility fact verified by a third party, such as an authorized service centre or a certified technician. Not a customer outcome.
- General capability
Something Arrowhead offers every customer. Not a customer outcome and not a promise about your operation.
- Customer relationship
A named account relationship. It says who we work with, never what was delivered or what it achieved.
- Technology partner
A vendor or partner relationship. Partner hardware in a building is not evidence that Arrowhead delivered that building's system.
- Unpublished reference
A real engagement we are not free to publish. Ask for the reference during discovery.
- Arrowhead-operated system
Software Arrowhead built and runs in production today, demonstrable on request. A fact about our own system, never a customer outcome.
- Future direction
Not available today. A direction, not a capability you can buy.
Only two of these may carry a number. A measured customer figure appears under Arrowhead-delivered result or Vendor-supported result and nowhere else. A percentage beside a capability is how a capability quietly becomes a result, so the build fails if one appears.
What we publish, and what we do not
Arrowhead has operated since 1989 and works with organizations that will not let a vendor put their name on a marketing page. Rather than publish logos we cannot substantiate, this is the policy.
What we publish
- Customer results we can source, labeled with who delivered the system and who measured the result.
- Industry references published by a technology vendor, labeled as that vendor's published result and not as ours.
- Credentials a third party issued us, named with the body that issued them.
- Software Arrowhead built and runs in production, demonstrable on request.
What we do not publish
- A customer name or logo without written permission from that customer.
- A result Arrowhead did not deliver, presented as though we did.
- A metric next to a relationship, where the relationship is all the evidence supports.
- A certification, service level, or security control we have not confirmed.
Named references are made available during technical discovery, with the customer's permission and under the confidentiality terms your procurement process requires.
What Arrowhead is accountable for
Arrowhead does not handle every aspect of a deployment, and saying so is not a weakness — an integrator that claims otherwise has not read its own statement of work. The split is published per service and per solution, and summarised on How We Work.
Arrowhead owns
- Hardware supply, staging, configuration, and installation
- Capture-point design and measured read-rate validation
- Mobi software inside the approved deployment scope
- The integration contract agreed in discovery
- In-house depot repair at 415 E Alamo Drive, Chandler
The customer owns
- Network readiness, power, and mounting access
- Source-system data and the system of record itself
- Operator time and change windows during rollout
- Operational acceptance against the discovery criteria
- The security and procurement review on their side