Start on Drive Solomon. Finish setup in Drive.
Drive Solomon handles signup, password creation, billing, and account setup. Once Drive shows your account in good standing, you open the Solomon app with the right access already in place.
Billing and account setup start here. The ongoing product experience opens after Drive finishes setup.
Four steps. No procurement loop.
Most operators start the account here, finish billing and setup in Drive, and then open the app the same day.
- Step 01
Tell Solomon how the operation runs
Trades, regions, team shape, intake channels, and the handoffs that hurt today. A short, structured intake — not a sales call.
- Step 02
Connect the systems to govern
FSM, scheduling, calendar, communications. Solomon reads live state and writes the work back through the tools you already use.
- Step 03
Codify the handoffs
Intake → dispatch → field → follow-up → reporting. Solomon proposes the workflow; you approve what becomes governed.
- Step 04
Handle billing in Drive Solomon
Drive Solomon manages checkout, subscriptions, password setup, and account-start handoffs before the day-to-day product experience opens in the app.
The minimum to bring the operating layer online.
Solomon doesn't need a data export or a project plan. It needs admin access to the systems you want under governance — and a clear answer about what's in scope.
- Admin access to your FSM or scheduling tool
- Calendar access for the team Solomon will coordinate
- The intake channels you want governed (forms, calls, inboxes)
- A short answer to: what handoff hurts the most today?
Permissions, scope, and what Solomon never touches.
Solomon is the operating layer above your existing systems. It reads live operational state and writes the work back through the tools you already use — only inside the scope you grant.
Scoped permissions
You decide which systems Solomon governs. Anything outside that scope stays untouched.
No silent data movement
Solomon doesn't relocate your operational data. It coordinates the systems where the data already lives.
Reversible by default
Disconnect a system at any time. Solomon stops governing that surface immediately; the system itself is untouched.
Onboarding questions, answered honestly.
No. Solomon is self-serve. The platform onboards you directly — no demo, no sales call, no procurement loop.
Admin access to the systems you want Solomon to govern — your FSM or scheduling tool, calendar, and the inboxes where intake lands. That's it.
The shape of your operation: trades you serve, how jobs come in, how dispatch works today, where follow-up breaks down. Solomon uses these answers to codify the handoffs you want under governance.
Drive Solomon owns billing. Stripe checkout and subscription management happen here, and once your account is in good standing you open the product from there.
Read-and-write inside the operational systems you want governed (e.g. scheduling, intake, communications). You scope what's in and what's out. Solomon never touches systems outside that scope.
The fastest way to see the operation as one system.
Start with the handoff that costs you the most. Expand from there.