A familiar object.
A clearer next step.

At an activity station, the next step may be in a binder, on a wall, or known only to a staff member. We are exploring a consistent starting point: an emblem that opens the team's chosen guidance.

This is a problem hypothesis for discovery, not a measured customer outcome. Interview participants and support teams about existing routines, device access, content ownership, accessibility, and the situations where a physical touchpoint would actually help.

Our emblems and connected-bottle prototype make the physical work visible. The software foundation connects an object to an experience that can change without replacing the object.

The repository contains identity, organization-scoped routing, content, event, and operational foundations. Source code and demonstrations do not establish production readiness across every workflow. Golf, companion animals, energy, and live competition are additional application foundations, not proof of adoption. The current commercial record needs supporting contracts and financials in private diligence; no revenue or customer-growth figure is asserted here.

The initial discovery audience is care and supported-living organizations. The person using the experience, the staff maintaining it, and the buyer approving a pilot may be different people.

A pilot needs a budget-owning sponsor, consent and privacy review, a named content owner, a supported device plan, and a narrow use case. Begin with low-risk activity guidance. Do not assume reimbursement, clinical acceptance, a procurement award, or an existing provider partnership. Size the serviceable market bottom-up from qualified organizations and realistic pilot capacity, not an adjacent smart-packaging market total.

The proposed model combines paid pilot setup, physical emblems, and recurring software and support. Pricing will be tested against delivery cost and customer value.

Track design and setup hours, materials, encoding and quality checks, fulfillment, infrastructure, content maintenance, replacement, and support. Separate one-time service revenue from recurring revenue. No subscription run rate, margin, signed pilot price, or customer lifetime value is established by this briefing.

Founder Andrea Cozart-Lundin brings together software development, design, fabrication, and storytelling. The opportunity is to make the whole experience useful, not merely attach a link to an object.

Alternatives include printed guides, generic QR/NFC links, existing care software, and custom web experiences. Our proposed differentiation is durable physical design, updateable organization-controlled content, and a repeatable delivery workflow. Pilot evidence must establish whether that combination is worth paying for. Additional clinical, accessibility, security, sales, and operational expertise will be needed as scope grows.

Validate the need. Run a bounded pilot. Measure whether people can find and understand the next step. Expand only when the evidence supports it.

Discovery gate: participants and staff confirm a useful routine and accessibility requirements. Pilot gate: signed scope, baseline, agreed measures, owner, support plan, and privacy review. Evaluation gate: task completion, time to find guidance, help requests, errors, and qualitative feedback, without claiming causation or clinical efficacy. Commercial gate: payment, delivery cost, repeat use, and willingness to renew. These are proposed measures, not reported results.

Capital would support user discovery, accessibility work, a scoped pilot, software reliability, physical production, and company-record completion.

The raise amount, valuation, instrument, allocation of proceeds, hiring budget, and runway are not approved terms in this briefing. A financing budget should tie each cost to a milestone and include monthly cash needs, contingency, existing liabilities, and downside assumptions. Discuss fit first; review an approved instrument and disclosures separately before any commitment.

Demand, accessibility, delivery economics, reliable operation, ownership records, and financing terms still need evidence or formal approval.

Key risks include poor workflow fit, phone or connectivity barriers, stale instructions, content permissions, privacy, support burden, limited founder capacity, and unproven willingness to pay. Mitigations include a narrowly bounded pilot, accessible alternatives, named content owners, minimal data collection, tested failure paths, and separate executed corporate and IP records. Technical controls are not clinical validation or a compliance certification.

The first phase is discovery and a bounded pilot. Repeat delivery comes next. Broader applications and partner distribution follow only when demand, economics, and support capacity justify them.

Year-one priority: validate one use case. Years two and three: standardize delivery if customers renew and the unit economics work. Years four and five: consider partner distribution and additional applications if the shared platform reduces cost and operational risk. This is a conditional sequence, not a revenue forecast, promised launch schedule, or assurance of growth.