The State of Stick platform
BUILD INTELLIGENT SYSTEMS
FOR THE PHYSICAL WORLD.
State of Stick is an AI-native physical-world systems platform. We combine software, manufacturing, persistent identity, governed experiences, and lifecycle intelligence so real products, places, and assets can become useful, trusted, measurable systems.
NFC, QR, secure chips, and other interfaces are delivery options—not the product. The system is the AI orchestration, identity, governance, software, manufacturing, lifecycle, and reporting behind them.
In plain terms: someone standing in front of a product can immediately reach the right information or action, and the organization that made or manages that product can keep the experience current after the product leaves the factory.
Shared platform architecture
THE INDUSTRY CHANGES.
THE PLATFORM DOES NOT.
A premium physical product is the deployment layer and valuable commercial entry point. Persistent identity connects it to a governed platform that can keep approved information, records, experiences, and actions useful over time.
STATE OF STICK PLATFORM
Identity
A shared, serialized, or higher-assurance record appropriate to the product and risk.
Management
Organization-controlled destinations, content, lifecycle states, and roles.
Analytics
Aggregate interaction and action signals tied to the physical touchpoint.
Authorization + verification
Approved access and trust signals without treating every interaction as authentication.
AI experiences
Optional assistance grounded in approved content—not the authority for safety, identity, or compliance.
Lifecycle records
Guidance, service, warranty, provenance, replacement, and next actions over time.
The responsible organization remains the authority for its records, instructions, access rules, claims, and systems of record. Connectivity can use the technology appropriate to the program; identification is not automatically authentication.
What this actually means
SHOW THE USEFUL MOMENT.
These are the kinds of programs the platform is designed to support. Each example begins with something a company already manufactures, sells, installs, services, teaches with, or needs people to trust.
Example 01
A MANUFACTURER PUTS A PRODUCT RECORD ON A MACHINE
- The physical thing
- Hydraulic pump, robot, industrial tool, or replacement component
- What happens
- A technician taps the durable identity while standing at the product.
- What they get
- They see the correct manual, serial or batch context, service history, approved replacement parts, and a support action.
- What State of Stick manages
- State of Stick keeps the physical identity connected to the manufacturer-controlled experience and records aggregate support activity.
- Why the organization cares
Example 02
A BRAND KEEPS WORKING AFTER THE PACKAGE LEAVES THE SHELF
- The physical thing
- Bottle, jar, box, limited release, or premium package
- What happens
- A customer taps or scans because the package offers a useful story, recipe, registration, verification, or reorder path.
- What they get
- The brand can update the destination after distribution without remaking the physical piece.
- What State of Stick manages
- State of Stick manages shared or serialized identities, destinations, campaign context, and aggregate action reporting.
- Why the organization cares
Example 03
APPROVED GUIDANCE STAYS WITH THE EQUIPMENT
- The physical thing
- Training station, medical-device demo, laboratory tool, or public asset
- What happens
- A learner, operator, or visitor opens the current organization-approved resource at the point of need.
- What they get
- They receive the right checklist, video, accessible format, support path, or escalation—not an uncontrolled AI answer.
- What State of Stick manages
- State of Stick routes the person to governed content while the responsible organization remains the authority.
- Why the organization cares
Example 04
A VALUABLE OBJECT RECEIVES THE RIGHT LEVEL OF TRUST
- The physical thing
- Serialized edition, authorized product, collectible, service part, or field asset
- What happens
- A buyer, owner, or technician checks the record attached to the physical item.
- What they get
- The result clearly states what is identified, what is verified, who issued the record, and what the person should do next.
- What State of Stick manages
- State of Stick supports shared, serialized, access-controlled, or higher-assurance paths appropriate to the risk.
- Why the organization cares
Platform capabilities
SIX CONNECTED CAPABILITIES.
IDENTITY
Connect one product family, a serialized production run, or a higher-assurance authorized object to the right record.
SOFTWARE
Control destinations, content, roles, lifecycle state, and approved next actions after the physical system is deployed.
AI ORCHESTRATION
Ground interpretation, recommendations, drafts, and operator intelligence in approved context while humans and deterministic code retain authority.
TRUST + AUTHORIZATION
Apply access and verification appropriate to the risk without pretending every tap or scan proves authenticity.
LIFECYCLE INTELLIGENCE
Measure intentional interaction and turn product, service, support, and operator context into useful next decisions.
MANUFACTURING + OPERATIONS
Design, produce, encode, assemble, provision, support, and improve the physical deployment with tenant-aware operational controls.
How a program operates
FROM AUTHORITY
TO LIFECYCLE.
A credible deployment begins with ownership and boundaries, not a tag. Technology, integrations, and assurance increase only when the use case justifies them.
- 01DEFINE AUTHORITY
Name the organization, system, and people responsible for every record, instruction, claim, and access rule.
- 02CHOOSE THE IDENTITY
Use a shared, serialized, or higher-assurance configuration based on value, risk, and the promised outcome.
- 03MAKE + ACTIVATE
Design the physical touchpoint and governed digital experience as one deployable product system.
- 04MANAGE THE LIFECYCLE
Update approved destinations, support product states, and keep the useful next action current.
- 05MEASURE + IMPROVE
Review aggregate engagement and action signals, then improve the next run or service experience.
Evidence with honest labels
PROOF, PILOTS,
AND CONCEPTS.
Deployed work, active collaborations, internal demonstrations, and proposals answer different questions. State of Stick labels each one so a possible application is never mistaken for adoption.
Deployed case study
CUSTOM CAULDRON CONNECTED BOTTLES
A live physical product and digital experience demonstrating persistent product identity, story, and post-sale engagement.
View deployed case study →Active collaboration
OLD WORLD OLIVE CO. CONNECTED RETAIL
A bounded founding-partner launch path for connected packaging, retail experience, and measurable customer action.
View collaboration brief →Internal platform demonstration
MANUFACTURING PRODUCT PASSPORT
A demonstration of product identity, manuals, lifecycle records, service history, and replacement-part paths.
Explore manufacturing demo →Internal platform demonstration
HEALTHCARE EQUIPMENT SUPPORT
A bounded training and support demonstration that excludes patient data and preserves authoritative institutional systems.
Explore healthcare demo →Partnership proposal · not adopted
CONNECTED COLLECTIBLE PILOT
A clearly labeled concept showing how edition identity, collector experience, and authorized records could work.
View proposal →Start bounded, then scale
ONE USEFUL ACTION.
Start with a credible pilot around one physical product or asset. Prove that the identity and experience improve support, service, learning, trust, or customer action before expanding.