ova
A hand touching a control panel built into a modern kitchen wall.

Building technology

A sales workspace from first call to order

Customer memory, quotations and order intake in one place, connected to the ERP and the mailbox.

All use cases

The problem

A technology manufacturer sells through a network of installers. Customer knowledge is spread across spreadsheets, shared folders, the ERP and individual mailboxes, and much of it sits with the sales reps themselves.

Quotations are built in complex workbooks and orders are retyped, so prices and items can differ between quotation, order and invoice. Follow-up depends on memory: which call is due, and which mail is still unanswered?

The journey

  1. A contact, with full history

    Your team

    The rep opens an installer and sees every contact moment, quotation and order at once.

  2. Follow-up comes to you

    Nova

    A call list and unanswered mails are prepared each day, with the context of the last contact.

  3. The quotation is built

    Your team

    The rep builds the quotation in the workspace, with the configuration knowledge built in.

  4. Items and prices are checked

    Nova

    Every line is checked against the ERP, and differences are flagged before anything is sent.

  5. Quotation becomes order

    Your team

    After confirmation, the order is created without retyping and the rep gives the final approval.

  6. One view of the figures

    Your systems

    Quotation, order and invoice match line by line, and feed the statistics and forecast.

Nova's solution direction

  • One workspace on top of what exists

    The ERP and Microsoft 365 stay in place. Sales works in one layer on top of them.

  • A customer memory that stays

    Knowledge moves from individual reps to the company, available to whoever picks up the call.

  • Checks before errors happen

    Item and price control is built into the quotation, rather than discovered on the invoice.

  • Step by step

    Starting with the core of contacts and quotations, with a clear go or no-go after a short pilot.

Anonymised use case, based on a real brief in our studio. Names and identifying details have been left out. It describes a solution direction, not a measured result.

More use cases

What's the use case you would start with?