SON Identity
NFC-based identity and networking, with the backend of a real SaaS platform.
Professional networking still runs on paper cards and dead-end contact exchanges — the artifact (the card) survives, but the connection doesn't get captured anywhere useful. SON Identity replaces the physical card with an NFC tap that's backed by a real identity and analytics platform, not just a digital business card gimmick.
This is a hardware + software product: the NFC card is only as good as the platform behind it — account management, subscriptions, and analytics have to work the moment someone taps, with zero setup friction for the person receiving the contact.
NFC hardware provisioning has to stay decoupled from account logic (a card can be reissued, lost, or reassigned without breaking a user's identity or history). Needs to support both individual professionals and teams/companies issuing cards at scale, which changes the admin and billing model from day one.
The physical card carries no data itself — it's a pointer, so identity, profile, and history live entirely server-side and can be updated, revoked, or migrated without reprinting anything.
NFC card (static identifier) → auth/resolution service → identity and profile store → analytics pipeline → admin dashboard.
Web platform for the account/admin/analytics layers, NFC read/write integration for the hardware layer, subscription/billing logic designed for both individual and multi-seat (team) accounts.
Started from the hardware constraint outward — decided what the card can't be allowed to know before designing what the platform should know, then built the admin/subscription layer once the identity model was stable.
Enables reissuing/lost-card recovery without identity loss.
Not bolted on later, since B2B card-issuing (companies ordering cards for their staff) is a materially different admin/billing shape than individual signup.
Initially under-scoped the analytics layer as an afterthought; realized engagement data (who scanned, when, from where) is actually core product value for professionals and teams, not a nice-to-have, and had to revisit the data model to capture it properly from day one instead of retrofitting.
In a hardware-linked product, the temptation is to treat the physical object as the product. It isn't — the platform is the product, and the card is the interface to it.
First cards issued, first team/company account onboarded, and first analytics dashboard shipped to a real user will be added here as soon as they exist. There's nothing to show yet — and I'd rather say that than invent a number.
Team/company self-serve issuing, deeper analytics (engagement scoring, CRM export), broader hardware form factors beyond the card.