Lunar Rails onboarding vision

The Activation Room

The dream is not a prettier application form. The dream is a prepared room where the client sees the fastest path to first value, while Lunar quietly turns discovery, compliance, documents, people, and service readiness into one guided activation path.

Open client prototype Open CS backend
A questionnaire collects information. An activation room gets a client to first value. That is the product distinction. Sumsub can be the verification layer. Lunar must own the journey.
Core promise

From discovery to first use, without making the client carry the system.

Lunar already had the calls. Lunar already knows the service intent. Lunar already knows the likely documents, people, and compliance gates. The client link should arrive after the hard thinking is done.

Experience Principles

The experience should feel like concierge activation, not generic onboarding.

Prepared

Start with what Lunar already knows.

Open on a prepared setup: services, people, expected activity, and missing items. Blank forms are the enemy.

Service-led

Clients unlock services, not compliance tasks.

The client thinks in outcomes: trade, settle, convert, report, operate. Lunar maps those outcomes to evidence behind the scenes.

Reason-coded

Every ask explains what it unlocks.

No random document scavenger hunt. Each request says why now, who it applies to, and which service it activates.

Human

Make customer success visible.

The client should feel guided by Lunar, not abandoned inside a portal. CS owns momentum and translation.

Progressive

Ask only for the next useful milestone.

Do not ask 80 questions up front when two items unlock the first quote, first settlement route, or first API prep.

Honest

Backend service truth must be sharper than frontend copy.

CS needs live, partner-routed, internal-review, and deferred states so Lunar never overpromises while trying to look smooth.

The Client Journey

The first screen should feel like momentum already exists.

1

Enter prepared room

“We prepared your Lunar setup from our conversations.”

2

Choose first value

Trade, settle, convert, report, or onboard team access.

3

Confirm people

Signer, UBO/control, trader, finance owner, technical owner.

4

Close activation gates

Upload only the evidence tied to selected services.

5

Reach first use

First quote, settlement route, treasury conversion, or API prep.

The Operating Layer

The client sees simplicity because Lunar absorbs complexity.

Layer
Client sees
Lunar sees
Why it matters
Services
What they can activate first
Live / partner / review / deferred status
Clear expectations without overclaiming
People
Who belongs on the account
Signer, UBO, trader, operator, technical owner
Authority is solved before first use
Documents
Focused upload room
Evidence matrix and reviewer ownership
No generic compliance scavenger hunt
Compliance
Plain activation gates
KYB, UBO, SOF, expected activity, wallet context, screening
The hard checks are handled without scaring the client
Sumsub
Verification handoff
Clean packet with prefilled context and missing-item state
Sumsub becomes infrastructure, not the experience

What We Measure

The dream has to become operational, or it stays pretty theater.

Time How long from link sent to first usable service?
Asks How many items did the client actually have to provide?
Loops How many times did Lunar ask for clarification?
Trust Did onboarding make Lunar feel more competent, not more bureaucratic?
Product thesis

The Activation Room is the first proof that Lunar is the Banking House.

If onboarding feels careful, prepared, intelligent, and human, the client starts trusting Lunar before the first transaction. That is the whole point. We are not just removing friction; we are making the first interaction feel like the product already works.