Every payroll dollar rests on a single claim: this person was here, at this place, at this time. The system of record decides what that punch means. It cannot witness the punch. A phone says a button was pressed. A shared Chromebook says a PIN was typed. Paper says whatever was written. Each records time. None proves presence.
So we built the answer: a purpose-built endpoint at the door, an identity the organization controls, hardware that keeps capturing when the network drops, and a record of every attempt, not just the punches that went through. ClockConnect watches every endpoint we support; Assurance keeps the record. That is how we earned the line we still stand behind: the only timeclock you can take to an audit.
Time is where we first proved Presence. It is not the boundary of the category.
Who was involved. Where it happened, at what endpoint. When. How identity was established: a badge, a fingerprint, a face, a credential, a device. What physical event occurred. And what evidence exists to support it later.
Not every case needs every element. The category is the connection between a physical-world event and the digital system that has to act on it, made strong enough to hold.
We are entering a period when anything digital can be generated: a document, a signature, a voice, a record. Software will do more of the work every year, and do it faster than any person can check. Intelligence built on unreliable physical data produces bad conclusions. Autonomous action built on bad conclusions produces bad outcomes.
The one thing no model can manufacture is a person standing at a door, a bus in its bay, a key back in its cabinet. As everything downstream becomes automated, the physical event becomes the anchor. Proof of Presence is what earns the right to build anything on top of it.
Think of your systems of record as the museum. Everything a district knows lives there, and every decision it makes is made there: who gets paid, who fills the vacancy, who is allowed through which door. Touchpoint is not the museum. Touchpoint is the curator, and a curator of exactly one question: is this piece real? We answer it at the door, before anything goes in.
That is the whole relationship. A badge, a face, a fingerprint, a credential, an endpoint, a place, and a time go in. A verified event comes out, delivered to whatever system needs it, with the audit trail attached. The museum decides what the piece means and where it hangs. We make sure it is genuine, and we raise a hand when something doesn't add up.
We do not need to own the museum. We need to make sure nothing hangs in it that isn't real. Without that, the museum is full of pieces nobody can vouch for.
Digital systems need to know more than whether a worker arrived. Who entered this building, and when. Whether the contractor was on site for the work that was billed. Who received the vehicle, the key, the equipment, and who brought it back. What is in this room right now. What just changed, and what state a controlled space is in.
People, assets, places, events, and conditions. Every one is a version of the same foundational problem, and every one is a place Presence can go. That is the shape of the category, not a promise to build each piece. Some we will build, some we will acquire, some we will enable through others, some we will leave alone.
K-12 is where we proved it, one custodian opening a building before sunrise at a time. The gap between what software says should have happened and what actually happened exists wherever work is done by people who do not sit at a desk: municipal government, public works, transit, facilities, manufacturing, healthcare.
Presence tells us what happened. Intelligence tells us what it means. Action makes something happen.
A door that opens at 2 a.m. in a building that should be empty is a Presence event. Knowing that it matters is Intelligence. Alerting the one person who can do something about it is Action. Touchpoint does all three. This is where AI belongs, not as a label on a sensor or a clock, but as the layer that reads physical evidence that can be believed. And once an event is understood, the loop closes: a ticket, an alert, an update to another system, or a response back in the physical world.
We built them in that order, and we will keep building them in that order. Physical data first. Intelligence second. Action last. Each layer is only as sound as the one beneath it.
Touchpoint is not becoming an HCM company, a workflow company, a generic identity platform, or a collection of unrelated hardware. Touchpoint creates evidence of what actually happened. Other systems consume it. Every product, integration, and acquisition is measured against one question: does it make us better at proving what happened in the physical world, understanding what it means, and acting on it.
Yesterday, Touchpoint made reliable timeclocks. Today, Touchpoint proves what actually happened, understands what it means, and acts on it, beginning with whether the right employee was physically present for the events a district pays for. Next, Presence extends across people, assets, places, events, and conditions, and into every industry where work is done away from a desk. The vision is a mission-critical physical world made legible: physical data, intelligence, and autonomous digital and physical action, everywhere it matters.
The right person. The right place. The right moment. Trusted by the system that comes next.
Touchpoint connects the physical and digital worlds, beginning with Proof of Presence. This is the ground we build on.
If you're interested in learning more:
-> Book a 20-minute funding conversation with our team.