From First Login to First Business Customer
Plan identity work by startup stage. Move from prototype accounts to pilots, support, business customers, and separate AI authorization boundaries.
Retrospective series date: 2026-10-16. This label describes the series order, not a historical publication.
Build identity controls when the product stage requires them. A prototype and a business-customer rollout have different needs.
Use this roadmap to identify the next decision. It is a planning guide, not a compliance certification or a requirement to buy every feature.
Prototype: prove the account boundary
Use synthetic users and data. Complete one sign-in journey and protect one private resource.
Decide whether users act alone or within organizations. Keep development credentials separate from customer environments.
Write down who owns the domain, repository, hosting, and identity service. Student teams can use the ownership handover template.
Pilot: control temporary access
Name the approved participants, roles, data, and end date. Decide who may invite more users.
Test denied access and account recovery. Confirm that a departing participant loses the intended access.
Use the pilot worksheet. A successful demonstration is not enough evidence for an uncontrolled public launch.
Early customers: operate accounts
Prepare support procedures for recovery, profile changes, suspicious sessions, and closure.
Give operators limited access and individual accounts. Record sensitive changes.
Review repeated support failures. They may reveal an unclear sign-in journey or weak recovery design.
The first-customer operations guide provides a weekly worksheet.
Business customers: model the organization
Separate the person, organization membership, role, and enterprise connection. A person may belong to several customers.
Verify the active organization in each relevant request. Make administrator powers explicit.
A customer's SSO request adds federation work. It does not remove application authorization or account-lifecycle responsibilities.
Review the multi-tenant guide before mapping enterprise groups to roles.
AI features: give the client its own authority
An AI client may act for a person. It should receive only the access needed for the approved task.
Separate the person's sign-in session from the client's authorization. Define audience, scope, expiry, and revocation according to the protocol and implementation.
Do not give an agent a broad human session merely because the user signed in.
The agent identity guide explains this boundary. Verify provider availability before depending on preview or planned features.
Use the stage review
| Stage | Decision | Evidence before moving forward |
|---|---|---|
| Prototype | Account model | One allowed and one denied request |
| Pilot | Temporary membership | Approved scope and removal test |
| Early customers | Account support | Recovery and revocation procedures |
| Business customer | Organization control | Cross-tenant tests and administrator review |
| AI feature | Delegated authority | Scoped grant and independent revocation test |
Do not advance because a checklist has ticks. Keep the observed result and unresolved risk beside each item.
Review existing choices before replacing them
A later stage may need configuration or operating changes rather than a provider migration.
Compare current capabilities against the next requirement. Use the provider scorecard when the gap is significant.
Migration has costs. Review identities, linked accounts, credentials, sessions, and rollback before scheduling it.
Find support that fits the decision
Use the national technology guide for broader product planning. Rajasthan founders can also use the ecosystem resource map.
Ask an incubator or mentor to review a specific decision and its evidence. Do not request a general approval for an undefined system.
Contact the NamoID team
NamoID can help you plan customer authentication and review integration choices at the current stage.
Message our team in Slack with your stack, account model, and next milestone. We can help you identify the next useful step.