Solutions

Concrete situations, before market categories.

Nano is designed for digital services that are simple, occasional and important enough not to be forgotten. These scenarios are value hypotheses to test — not claimed deployments.

Six journeys to test in the field

Each one connects a user need, the institution’s role and what a pilot should measure.

  • The policyholder and their vehicle

    The problem
    A poorly maintained vehicle, an overdue roadworthiness test, a forgotten policy renewal.
    What Nano does
    The policyholder records the vehicle by talking to their assistant; Nano reminds them by e-mail before the service, the test, the renewal.
    Measure together
    Activation, regularity of records, acted-on reminders and the quality of contact between renewals. Any effect on claims remains to be demonstrated.
  • The driver and the financed asset

    The problem
    A loan backed by a work tool — a taxi, a motorbike, tomorrow a boat — depends on the condition of that tool.
    What Nano does
    The borrower tracks the vehicle, its odometer, its expenses and its deadlines from the assistant they already have.
    Measure together
    Use of the record, documented maintenance and perceived value. Any effect on portfolio quality is a hypothesis, not a promise.
  • Cooperatives

    The problem
    Many scattered members who forget the same things on the same dates.
    What Nano does
    The same service for every member, each with their own account, data and reminders.
    For you
    A concrete service to offer members, with no tool to build or maintain.
  • Garage networks

    The problem
    A customer seen once, then lost from sight.
    What Nano does
    The customer is told when a service is due, by mileage or by date.
    For you
    An ongoing relationship rather than a one-off visit.
  • NGOs and donors

    The problem
    A support programme that must leave a lasting tool behind, at no cost to the beneficiary.
    What Nano does
    Full sponsorship: the programme pays for a batch of codes, the beneficiary uses the service without paying anything.
    For you
    A cost known in advance, a single invoice, measurable use.
  • Telecom operators

    The problem
    Mobile plans that all look alike.
    What Nano does
    A useful service, tied to the subscriber’s phone number, to include in an offer.
    For you
    A concrete difference, with no app to get installed.

As of 4 October 2026: two products online, a third in testing

Each product plugs into the same infrastructure: account, languages, calendars, reminders, rights and billing are already there. A product goes through stages held by automated checks: testing restricted to named testers, a signed validation, then release.

  • Mini Fleet

    One to five vehicles: deadlines by date or mileage, odometer readings, expenses. E-mail reminders.

  • Deadline Notebook

    Anything dated that must not be forgotten: an insurance policy, a payment, a renewal. E-mail reminders.

  • Troubleshooting In testing

    A heating professional’s diagnostic tree, played step by step from the assistant: a test, a reading, the next step, down to the fault. The first product from an outside supplier: they keep ownership of their know-how, Nano distributes it. Restricted to its testers.

  • Next

    More software, from Nano or from outside suppliers, served by the same infrastructure and subject to the same stages before opening.

Your case is not on the list?

Tell us what your customers must not forget. That is often where a new product starts.