Deploy
From a hundred-user pilot to a hundred-thousand-user programme.
A progressive deployment designed to measure real usage before committing to integration or scale. The stages describe the approach offered to pilot partners.
Three stages, three decisions
Each stage has an observable objective and an exit. Moving to the next stage is never automatic.
-
≈ 100 users
Learn. One country, one product, a few weeks. No heavy information-system integration upfront.
The partner
- chooses the participants;
- hands them the activation codes;
- shares their feedback.
Nano
- opens the country: language, currency, calendar;
- produces the batch of codes;
- follows usage with you.
-
≈ 10,000 users
Confirm. The offer becomes part of your customer relationship after the pilot is reviewed.
The partner
- bundles Nano with its products (policy, loan, membership);
- presents it in branches or through its own channels.
Nano
- code batches and a single invoice;
- usage dashboard (planned).
-
100,000 and more
Industrialise. Several countries and products, if the evidence supports it.
The partner
- runs the programme country by country.
Nano
- scales along the target architecture, designed from today.
What the pilot must help decide
Success is not merely proving that the technology works. We observe activation, understanding, usage, reminders users find useful, drop-off, support requests and perceived value for both users and the partner.
After the pilot, the programme can be adapted, extended or stopped before any major industrial commitment.
Who does what
| Task | Who |
|---|---|
| Choose the beneficiaries, present the service to them | Partner |
| Pay for a batch, or resell it with its own products | Partner |
| Hand out the activation codes | Partner |
| Open a country: language, currency, calendar, price | Nano |
| Host, secure, back up | Nano |
| Help the user | Nano: first inside the assistant (help tool), then by e-mail |
| Invoice | Nano, one invoice to the partner |
Country by country
Opening a country is a setting, not a development: language, currency, calendar and price are data.
- Language
- The assistant already speaks the user’s language. Nano translates what the user reads without going through the assistant: sign-in screens, e-mails, reminders. Today: French (validated), English, Spanish, Arabic, Danish (under review); Greenlandic (Kalaallisut) awaits a native speaker for validation.
- Currency
- Amounts stored in minor units with their ISO 4217 code. The user’s price is set per zone.
- Calendar
- Derived from the language or the country: Bikram Sambat in Nepal, the Ethiopian calendar in Ethiopia and Eritrea. Dates are converted by Nano, never guessed by the assistant.
- Phone numbers
- Every country code in the world. An account’s country is that of its verified number, never that of its IP address.
- Closed countries
- A country can be closed: no sign-in code is sent there and no tool answers there, even for an account created earlier.
Status at 4 October 2026
What deployment relies on, and where it stands.
- Live exists and runs
- In progress being built
- Planned decided, not started
| Feature | Status | Detail |
|---|---|---|
| Activation codes in batches | Live | Can be restricted to certain countries, with an expiry date; stored as hashes. |
| Prices by zone | Live | The mechanism is in place; actual prices are set country by country. |
| Invoice to the partner | Live | Gap-free numbering, VAT, credit notes, payment by bank transfer. First real invoice once the chartered accountant has validated the VAT treatments. |
| EN 16931 e-invoice | Live | Produced and validated against the official schemas. Transmission through an accredited platform: planned. |
| Nano app, with its own assistant | Live | For those without ChatGPT or Claude: the same products, through a small open model, interchangeable, hosted in Europe. |
| Sign-in code by text message | In progress | Demonstration mode today; real sending is built and being put into service. |
| Product life cycle | In progress | Seven stages, from lab to withdrawal, each held by a check: testing restricted to named testers, signed validation, release, shop pages generated from the catalogue. Built, being put into service. |
| Planned | Decided on 2 October 2026: a strictly bounded business service, never a general-purpose AI; not started. | |
| Linking customers to the partner account | Planned | To be built with the first partners. |
| Usage dashboard | Planned | To be built with the first partners. |
| Online payment by the user | Planned | No payment provider connected yet. |