Enterprise Onboarding: 30/60/90-Day Plan

Use this checklist as shared kickoff record for customer administrator, implementation lead, security contact, and Lyniti deal owner. Record owners and target dates before work starts.

Enterprise Setup#

Submit the request#

Open the pricing page and select Enterprise.
Sign in or create an account when prompted.
Enter requested workspace name, legal company name, company size, contact details, and security, migration, integration, and support needs.
Submit the inquiry. Lyniti sales receives the request and contacts the named customer representative.

Submitting an inquiry does not create a workspace or start billing.

Review and provision#

Lyniti staff completes these steps after commercial and security terms are approved:

Open Enterprise Operations from admin sidebar.
Assign deal owner, record internal notes, and move inquiry through New, Contacted, and Won or Lost.
Authorized Lyniti staff records signed contract terms: legal entity, billing contact, pricing model, billing interval, invoice terms, seat, storage, bandwidth, invocation, and CRM client-record caps, plus each meter's overage policy and negotiated rate.
Provision workspace once. Provisioning creates Stripe customer, negotiated prices and subscription, all five usage caps, temporary staff ownership, and audit records.
Verify Stripe subscription items, invoice settings, all five caps and overage policies, and MFA policy before inviting customer administrator.

Hand ownership to customer#

Invite customer administrator using recipient-bound workspace invitation.
Confirm administrator joined workspace and verified account email.
Load workspace in Managed usage and handover, select customer administrator, and complete ownership transfer.
Confirm customer is Owner and temporary Lyniti staff no longer has membership, role, direct access, active sessions, or open real-time connections.
Begin 30/60/90-day plan below with customer-owned administration.

Engagement Record#

Create customer-approved kickoff record. Give every item named owner, target date, and status: Not started, In progress, Blocked, or Complete.

[ ] Executive sponsor recorded
[ ] Customer administrator recorded
[ ] Security contact recorded
[ ] Migration lead recorded
[ ] Lyniti deal owner recorded
[ ] Production launch owner and date recorded
[ ] Renewal owner and date recorded

Before Kickoff#

[ ] Confirm signed order, MSA, DPA, billing interval, all five contracted caps, and approved hard-block or metered-overage policy for each cap.
[ ] Confirm Stripe invoice billing contact and payment due terms.
[ ] Provision Enterprise workspace with MFA enforcement enabled unless contract says otherwise.
[ ] Invite customer administrator through recipient-bound workspace invite.
[ ] Customer administrator joins and verifies account email.
[ ] Transfer workspace ownership to customer administrator and remove temporary Lyniti staff membership.
[ ] Verify customer owner can open billing, team settings, roles, and audit records.

Days 0-30: Access and Security Baseline#

Identity and access#

[ ] Configure supported OAuth providers and approved email domains where available.
[ ] Document identity limitation: Lyniti does not currently provide SAML SSO or SCIM provisioning.
[ ] Define process for joiners, movers, leavers, and emergency access while SAML/SCIM are unavailable.
[ ] Review roles and permissions: Owner, Admin, Member, and any custom roles.
[ ] Assign least-privilege roles and name two customer-side workspace administrators.
[ ] Enforce MFA and confirm grace-period deadline for every member.
[ ] Register passkeys or TOTP and store backup codes through approved customer process.

Security review pack#

[ ] Deliver current architecture and encryption summary.
[ ] Deliver subprocessor and data-residency information.
[ ] Deliver agreed DPA, SLA, incident-response contacts, and status page link.
[ ] Record customer security questionnaire owner and response due date.
[ ] Confirm data classification, retention, export, and deletion requirements.

Success checkpoint#

[ ] Customer owner controls workspace without Lyniti membership.
[ ] Required users can sign in and complete MFA.
[ ] Role assignments and security exceptions have written approval.
[ ] Open security questions have owners and dates.

Days 31-60: Migration and Workflow Configuration#

Migration plan#

[ ] Inventory source systems, record counts, attachment volume, owners, and export formats.
[ ] Classify data into clients, accounts, invoices, contacts, files, and historical records.
[ ] Agree migration method for each source. Do not assume CSV or API import exists for every module.
[ ] Define transformation rules, required fields, currency, tax, fiscal year, and invoice numbering.
[ ] Run a representative test migration in an agreed non-production scope.
[ ] Reconcile row counts, financial totals, attachments, permissions, and sampled records.
[ ] Record rejected data and remediation owner.
[ ] Approve production cutover, source-system freeze, rollback decision point, and sign-off owner.

Workspace configuration#

[ ] Configure chart of accounts, tax rates, categories, payment terms, and invoice numbering.
[ ] Configure project naming, team structure, roles, and required channels.
[ ] Validate contracted seat, storage, bandwidth, invocation, and CRM client-record limits against expected launch volume.
[ ] Confirm each overage policy from order form: hard block or metered overage per seat, storage GB, bandwidth GB, 1,000 invocations, and CRM client record.

Training#

[ ] Administrator session: ownership, invitations, roles, MFA policy, billing, and audit review.
[ ] Champion session: clients, tasks, files, chat, whiteboards, bookkeeping, and invoices in purchased scope.
[ ] End-user session with customer-specific workflows and support escalation path.
[ ] Record attendance, training materials, unanswered questions, and follow-up dates.

Success checkpoint#

[ ] Test migration reconciled and approved.
[ ] Production configuration signed off by business and security owners.
[ ] Customer champions can complete critical workflows without Lyniti staff access.

Days 61-90: Launch and Operational Readiness#

[ ] Execute approved production migration and reconciliation.
[ ] Confirm launch communication, office hours, and support severity contacts.
[ ] Review first-week authentication failures, permission issues, and workflow blockers.
[ ] Review seat, storage, bandwidth, invocation, and CRM client-record use against negotiated caps.
[ ] Confirm invoice delivery, billing contact, collection method, and next invoice date.
[ ] Review audit activity and remove unused accounts, invites, roles, and integrations.
[ ] Validate customer export and deletion procedures for governed data.
[ ] Close or assign every migration, training, and security action.

Day-90 acceptance#

[ ] Customer executive sponsor accepts operational handover.
[ ] Customer owner confirms ongoing access and administration responsibility.
[ ] Support path, severity definitions, and escalation contacts are documented.
[ ] Residual risks and product gaps have owners, target dates, and approved workarounds.
[ ] Success metrics and next usage review date are recorded.

Renewal Readiness#

[ ] 120 days before renewal: confirm business owner, renewal date, and procurement timeline.
[ ] 90 days before renewal: review adoption, support history, security changes, and roadmap dependencies.
[ ] 60 days before renewal: reconcile all five contracted caps and measured usage; agree required cap or price changes.
[ ] 30 days before renewal: complete quote, legal review, purchase order, and billing confirmation.
[ ] After renewal: update Stripe subscription, negotiated limits, audit record, and next review date.

Closeout Record#

Keep final approvals, migration reconciliation, training attendance, security exceptions, support contacts, and renewal dates in customer-approved record system. Do not place passwords, MFA secrets, backup codes, private keys, or production data in onboarding notes.

Enterprise Onboarding: 30/60/90-Day Plan

Use this checklist as shared kickoff record for customer administrator, implementation lead, security contact, and Lyniti deal owner. Record owners and target dates before work starts.

Enterprise Setup#

Submit the request#

Open the pricing page and select Enterprise.
Sign in or create an account when prompted.
Enter requested workspace name, legal company name, company size, contact details, and security, migration, integration, and support needs.
Submit the inquiry. Lyniti sales receives the request and contacts the named customer representative.

Submitting an inquiry does not create a workspace or start billing.

Review and provision#

Lyniti staff completes these steps after commercial and security terms are approved:

Open Enterprise Operations from admin sidebar.
Assign deal owner, record internal notes, and move inquiry through New, Contacted, and Won or Lost.
Authorized Lyniti staff records signed contract terms: legal entity, billing contact, pricing model, billing interval, invoice terms, seat, storage, bandwidth, invocation, and CRM client-record caps, plus each meter's overage policy and negotiated rate.
Provision workspace once. Provisioning creates Stripe customer, negotiated prices and subscription, all five usage caps, temporary staff ownership, and audit records.
Verify Stripe subscription items, invoice settings, all five caps and overage policies, and MFA policy before inviting customer administrator.

Hand ownership to customer#

Invite customer administrator using recipient-bound workspace invitation.
Confirm administrator joined workspace and verified account email.
Load workspace in Managed usage and handover, select customer administrator, and complete ownership transfer.
Confirm customer is Owner and temporary Lyniti staff no longer has membership, role, direct access, active sessions, or open real-time connections.
Begin 30/60/90-day plan below with customer-owned administration.

Engagement Record#

Create customer-approved kickoff record. Give every item named owner, target date, and status: Not started, In progress, Blocked, or Complete.

[ ] Executive sponsor recorded
[ ] Customer administrator recorded
[ ] Security contact recorded
[ ] Migration lead recorded
[ ] Lyniti deal owner recorded
[ ] Production launch owner and date recorded
[ ] Renewal owner and date recorded

Before Kickoff#

[ ] Confirm signed order, MSA, DPA, billing interval, all five contracted caps, and approved hard-block or metered-overage policy for each cap.
[ ] Confirm Stripe invoice billing contact and payment due terms.
[ ] Provision Enterprise workspace with MFA enforcement enabled unless contract says otherwise.
[ ] Invite customer administrator through recipient-bound workspace invite.
[ ] Customer administrator joins and verifies account email.
[ ] Transfer workspace ownership to customer administrator and remove temporary Lyniti staff membership.
[ ] Verify customer owner can open billing, team settings, roles, and audit records.

Days 0-30: Access and Security Baseline#

Identity and access#

[ ] Configure supported OAuth providers and approved email domains where available.
[ ] Document identity limitation: Lyniti does not currently provide SAML SSO or SCIM provisioning.
[ ] Define process for joiners, movers, leavers, and emergency access while SAML/SCIM are unavailable.
[ ] Review roles and permissions: Owner, Admin, Member, and any custom roles.
[ ] Assign least-privilege roles and name two customer-side workspace administrators.
[ ] Enforce MFA and confirm grace-period deadline for every member.
[ ] Register passkeys or TOTP and store backup codes through approved customer process.

Security review pack#

[ ] Deliver current architecture and encryption summary.
[ ] Deliver subprocessor and data-residency information.
[ ] Deliver agreed DPA, SLA, incident-response contacts, and status page link.
[ ] Record customer security questionnaire owner and response due date.
[ ] Confirm data classification, retention, export, and deletion requirements.

Success checkpoint#

[ ] Customer owner controls workspace without Lyniti membership.
[ ] Required users can sign in and complete MFA.
[ ] Role assignments and security exceptions have written approval.
[ ] Open security questions have owners and dates.

Days 31-60: Migration and Workflow Configuration#

Migration plan#

[ ] Inventory source systems, record counts, attachment volume, owners, and export formats.
[ ] Classify data into clients, accounts, invoices, contacts, files, and historical records.
[ ] Agree migration method for each source. Do not assume CSV or API import exists for every module.
[ ] Define transformation rules, required fields, currency, tax, fiscal year, and invoice numbering.
[ ] Run a representative test migration in an agreed non-production scope.
[ ] Reconcile row counts, financial totals, attachments, permissions, and sampled records.
[ ] Record rejected data and remediation owner.
[ ] Approve production cutover, source-system freeze, rollback decision point, and sign-off owner.

Workspace configuration#

[ ] Configure chart of accounts, tax rates, categories, payment terms, and invoice numbering.
[ ] Configure project naming, team structure, roles, and required channels.
[ ] Validate contracted seat, storage, bandwidth, invocation, and CRM client-record limits against expected launch volume.
[ ] Confirm each overage policy from order form: hard block or metered overage per seat, storage GB, bandwidth GB, 1,000 invocations, and CRM client record.

Training#

[ ] Administrator session: ownership, invitations, roles, MFA policy, billing, and audit review.
[ ] Champion session: clients, tasks, files, chat, whiteboards, bookkeeping, and invoices in purchased scope.
[ ] End-user session with customer-specific workflows and support escalation path.
[ ] Record attendance, training materials, unanswered questions, and follow-up dates.

Success checkpoint#

[ ] Test migration reconciled and approved.
[ ] Production configuration signed off by business and security owners.
[ ] Customer champions can complete critical workflows without Lyniti staff access.

Days 61-90: Launch and Operational Readiness#

[ ] Execute approved production migration and reconciliation.
[ ] Confirm launch communication, office hours, and support severity contacts.
[ ] Review first-week authentication failures, permission issues, and workflow blockers.
[ ] Review seat, storage, bandwidth, invocation, and CRM client-record use against negotiated caps.
[ ] Confirm invoice delivery, billing contact, collection method, and next invoice date.
[ ] Review audit activity and remove unused accounts, invites, roles, and integrations.
[ ] Validate customer export and deletion procedures for governed data.
[ ] Close or assign every migration, training, and security action.

Day-90 acceptance#

[ ] Customer executive sponsor accepts operational handover.
[ ] Customer owner confirms ongoing access and administration responsibility.
[ ] Support path, severity definitions, and escalation contacts are documented.
[ ] Residual risks and product gaps have owners, target dates, and approved workarounds.
[ ] Success metrics and next usage review date are recorded.

Renewal Readiness#

[ ] 120 days before renewal: confirm business owner, renewal date, and procurement timeline.
[ ] 90 days before renewal: review adoption, support history, security changes, and roadmap dependencies.
[ ] 60 days before renewal: reconcile all five contracted caps and measured usage; agree required cap or price changes.
[ ] 30 days before renewal: complete quote, legal review, purchase order, and billing confirmation.
[ ] After renewal: update Stripe subscription, negotiated limits, audit record, and next review date.