Request demo

Start with the school you are trying to run.

The demo request path helps sort design-partner conversations, parallel-run pilots, and pricing follow-up. Submit stays disabled until lead routing is connected, so no data leaves this page.

production writes

The page is local proof only: no CRM, email, database write, webhook, analytics event, or notification is connected.

conversation paths

The form separates design-partner conversations, parallel-run pilot interest, and pricing follow-up.

student data

The request path should never ask for SSNs, payment data, passwords, grades, accommodations, or other student records.

Fit

readiness signals

School type, launch state, size, current system, and first problem help decide the next conversation.

Local proof only

Demo intake preview

Submit is disabled until demo intake is connected. The questions are ready for review, but no information is sent from this page.

Do not enter student data, SSNs, government IDs, grades, disability documentation, bank/card numbers, payment data, or passwords.

Name

Work emailUse a school or work email. Do not enter passwords.

School name

School typeChoose the closest fit for how the school is approved today.

Launch stateCalifornia BPPE remains the first regulatory path.

Active-student rangeUse approximate active students, not total alumni records.

Current systemThis helps shape migration and parallel-run discussion.

What should Otto help with first?Do not enter student data, SSNs, government IDs, grades, disability documentation, bank/card numbers, payment data, or passwords.

Interest

Design-partner conversationParallel-run pilot interestPricing follow-up

Local proof only. Nothing is submitted, stored, scored, or routed.

Fit

Three useful conversations to start.

The request path is meant to route the conversation, not automate a sales process yet.

Design-partner conversation

For schools willing to review workflows, terminology, and buyer proof before public launch.

Best when leadership can share how the school runs today.

Parallel-run pilot

For schools that want to compare Otto against current records before changing operations.

Best when the school can name the first program or campus to test.

Pricing follow-up

For buyers comparing total cost across LMS, SIS, CRM, e-signature, texting, meetings, and compliance tools.

Best when active-student count and current stack are known.

Readiness

What Otto needs to understand first.

These signals keep the first conversation practical without asking for private records.

School type

Career school, degree-granting college, or hybrid school determines which proof story matters first.

Launch state

California BPPE schools come first, while multi-state launches need additional rule-pack review.

Active-student range

Current active-student count maps the conversation to the public pricing tiers.

Current system

Spreadsheets, standalone LMS/SIS, point tools, or custom systems change the migration and pilot plan.