Team

The people who built the moat, and the partner scaling it.

The defensible part is already done. This team conceived the sensing system, secured four issued US patents, and put it into real venues. For the commercial and capital-formation build, Klynkz works with an engineering and implementation partner that brings the platform, the raise infrastructure, and the go-to-market engine.

The proof in the people

The hard, defensible part is built

A team slide earns trust by what it has done, not by a list of titles. The moat that carries this company, the patents and the proprietary data set, was built by this team rather than bought. They conceived the sensing hardware, secured four issued patents covering the hardware, the full system, the enabling physics, and the expansion verticals, and deployed the system into a Gaming and Sports Entertainment Group and across two MLB seasons. That is invention proven in the field, which is the part of a hardware company that is hardest to replicate.

4 issued
US patents secured

Hardware, system, physics, expansion

Deployed
Into real venues

Gaming and MLB, not a lab

Real-time
Working product

Sub-3-second bottle read, live

The roles

The operating roles

The founding team holds the invention, the IP, and the venue relationships that produced the proof. Named bios are supplied by Klynkz and confirmed against the data room before they ship; the roles below describe the functions the company carries, framed around what each is accountable for rather than a credential list.

RoleWhat this role owns
Founder and inventorbio to confirmConceived the sensing system, named on the issued patents, set the product and technology direction.
Hardware and sensing engineeringbio to confirmThe force-sensing resistor array, the RFID antenna, and the concentrating layer that makes the read work near liquids.
Cloud and AI engineeringbio to confirmThe cloud tracking, shrinkage detection, reorder prediction, and POS reconciliation across eight POS systems.
Commercial and venue relationshipsbio to confirmThe Gaming and MLB deployments that produced the measured first-year results.

Named founder bios are [bio to confirm] and are supplied by Klynkz, then reconciled against the data room before any name ships. The roles above describe the functions carried, not specific individuals.

The execution layer

Light Brands, engineering and capital-formation partner

Klynkz works with Light Brands as its engineering and capital-formation implementation partner. The partner builds and runs the commercial and raise infrastructure: the investor platform and data room, the financial model and valuation work, the securities-pathway structuring, and the go-to-market engine that makes the venue target credible. The role is capabilities, not headcount on the cap table; the founding team owns the invention and the company.

CapabilityWhat it delivers
Platform engineeringThe investor site, the PIN-gated data room, and the model-driven financial surfaces.
Capital formationFinancial model reconciliation, valuation defense, and the sources-and-uses for the raise.
Securities structuringThe Reg D 506(c) pathway, the verification flow, and the risk-disclosure framework, for licensed counsel to review and approve.
Go-to-market enginePipeline build, channel partnerships, and the ROI-led motion that scales toward the venue target.
The boundary

Who owns what

The division of labor is clean. The founding team owns the invention, the issued IP, the proprietary data set, and the company. The implementation partner owns the commercial and raise execution. That boundary is what lets an investor read a team that has already done the defensible part and a partner that supplies the execution capacity to scale it.

Diagram
flowchart LR
  F["Founding team
invention, 4 patents,
data set, company"] --> P["Proven, protected asset"]
  L["Light Brands partner
platform, capital formation,
go-to-market"] --> E["Execution capacity"]
  P --> S["Scale from proof
to category"]
  E --> S
The combination

Why the pairing works

The question an investor asks of an early team is whether it can scale a company, not just build a product. The honest answer pairs proven invention with execution capacity: the founding team did the hard, defensible part, and the implementation partner brings the platform, the raise infrastructure, and the go-to-market engine. The combination is what turns a proven system into a scaled one.

The moat was built by this team, not bought. The execution capacity to scale it is the partner's contribution. An investor backs proven invention plus a credible path to distribution, not a promise.