Five applications SMEs assemble first

1

Modest first projects, and that is fine

When creating an application becomes a description rather than an IT project, you might expect ambitious ideas. In practice, the first requests are modest. They target the shared spreadsheet nobody updates, the email chain where requests get lost, the paper form someone retypes on Friday evening.

That is good news. A modest first project fits on one page, is validated by the team and is useful from the first week of use. We explained how to write that page in Describing your need to AI. This article looks instead at what SMEs assemble first. For each application: today’s pain, what it does, what it connects to, and what stays a human decision.

1

A request portal for your customers

Today, requests arrive by email, by phone, sometimes by message to a colleague who is out of the office. The customer does not know where the request stands. The team does not know who is handling it. Attachments disappear into an inbox.

• The customer submits a request, attaches documents and follows its status without calling.
• Every request lands in one file, with its origin, its time and its owner.
• Missing information triggers a targeted question to the customer, not another round of emails.

The portal connects to customer management, quotes and tickets. A request becomes a quote or a ticket without being retyped, and the customer’s history stays complete.

2

Intervention and planning follow-up for field teams

Field teams live with a whiteboard schedule, paper job sheets and photos sent by message. When a customer asks where the intervention stands, someone has to call the technician. When the invoice goes out, it goes out late, because proof of completion is missing.

• Intervention requests, sites and the equipment concerned are gathered in one file.
• Technician availability is visible, and each intervention is assigned to a person and a time slot.
• The technician closes the job on site, with photos, signature and remarks, and that proof triggers the preparation of the invoice.

The application connects to planning and invoicing. A closed intervention becomes an invoice ready to be checked. Connected planning is described on the Neoo Scheduling page.

The human rule: reassigning a technician on a critical site is a decision validated by a manager, never an automatic reshuffle.

3

A management dashboard that reads the real numbers

Many SMEs steer with a dashboard built by hand, once a month, from copied exports. The day it is ready, it is already late. And when two figures contradict each other, nobody knows which one to trust.

• Sales, margin, cash, overdue invoices and open tickets are read from the connected system, not retyped.
• Every figure points back to the lines behind it: the quote, the invoice, the ticket.
• A variance against the previous period or the target is flagged, with its context.

The dashboard connects to finance, sales and support. It does not add a new source of figures, it reads the one that exists, the one Neoo Finance keeps up to date. Why those figures are born in operations is explained in Margin is decided inside operations.

A surprising figure deserves a question to a person, not an automatic correction.

The human rule: a variance triggers a question to someone, never an automatic correction. The dashboard shows, the person interprets.

4

A quote approval and follow-up flow

A quote is prepared in a document, approved by message, sent by email, then waits. Who followed it up? What discount was granted? The salesperson knows, sometimes. The rest of the company finds out when the order arrives, or does not.

1. 01
   Prepare

   The quote is prepared from the customer’s data and current prices, without copying.

2. 02
   Approve

   Above a threshold, the quote goes through an approval before sending. Below it, it goes out directly.

3. 03
   Send and follow

   The customer receives the quote, and the team sees whether it was opened, accepted or left without an answer.

4. 04
   Remind and convert

   Reminders are prepared on the agreed date. An accepted quote becomes an order, then an invoice.

The flow connects to customer management, orders and invoicing. It applies the three safeguards described in Automate without removing human judgment: a threshold, an approval, a record.

The human rule: a discount above the threshold needs an approval. The application prepares and presents it, a person gives it.

5

An equipment and contract register

For an IT provider or a maintenance company, knowledge of the customer’s equipment often lives in a technician’s head and in a few files. A contract reaches its end date without anyone noticing. A device at the end of its life fails on a Monday morning, and the emergency replaces prevention.

• Each customer has an equipment file: devices, versions, warranties, contacts.
• Contracts and their renewal dates are visible and prepared in advance.
• Incidents are attached to the equipment concerned, with their history.
• Alerts are prepared before the problem becomes an emergency.

The register connects to tickets, contracts and invoicing. Linked to monitoring, it turns a technical signal into a prepared action, as described in See an incident before it becomes an emergency. How monitoring works is detailed on the Neoo Monitoring page.

The human rule: no silent action on a customer’s infrastructure. An intervention is announced, approved and recorded.

7

In Neoo

In Neoo, these applications are assembled by Neoo Forge, the workshop that assembles your applications with AI. You describe the need in your own words, Forge proposes the screens, the rules and the automations, and your team validates before going live. You can see it on the Neoo Forge page.

Each application lives on the same foundation as your customers, your invoices and your tickets. It is connected from day one: no export, no double entry, no new isolated tool to maintain.

Murphy, the agent that keeps watch, handles the living part: it prepares questions to customers, quote reminders and renewal alerts, asks for approval when the rule requires it and keeps a record of every action. The human rules in this article become settings, not reminders pinned to the wall.

And if one of these applications becomes real know-how, it can become a product. A request portal built for you can be offered to other companies in your sector. We describe that path in From the idea to the software you sell. For the starting method, read Create a business application without coding.