Case study · Scout
Scout: preparing and ordering works with an AI-assisted service file
Bringing in a plumber, an electrician or a cleaning company to work in a building is not ordered like a box of light bulbs. You have to choose the contractor, describe the work and allocate the expense to the right units. You also have to follow the job through to its invoice. For Scout, a procurement platform for property organisations, we built a complete service file. In it, AI helps draft the scope of works and break it down into tasks. The person placing the order reviews and edits these suggestions, and decisions remain with authorised people.
Scout is a B2B procurement platform for property organisations that manage properties made up of apartments and other units. It connects these organisations with product suppliers and service providers. We built it with Medusa and Mercur, two commerce and marketplace foundations. Some of a building’s needs go through the catalogue: supplies, equipment, consumables. Others involve work to be carried out on site: repairing, replacing, maintaining, refurbishing a unit. This second type of purchase has neither a product page nor a catalogue price. It relies on a contractor, a description of the works and a breakdown of the expense, followed by a series of exchanges through to the invoice. We therefore designed a flow in Scout that is separate from the basket, centred on a service file that supports the order from preparation to closure.
A dedicated flow for jobs, outside the basket
A basket works well for putting together items with known prices. A job follows a different logic. Before ordering, you need to know who can work on this site, what needs to be done and on which units. You also need to know which budget line carries the expense. Forcing this information into a product purchasing flow would have reduced it to comments that are hard to find again.
Team members at the property organisation therefore create a service purchase order in a dedicated file. This file brings together the choice of service provider, the scope of works, the tasks, their allocation, and then the history of what happens after sending. The steps are not scattered across an email, a spreadsheet and a phone call: each piece of information is attached to the job it relates to.
Choosing a contractor the organisation can call on for this site
Not every works company can operate everywhere. The search for service providers is carried out within the scope that the organisation can call on for the property concerned. The person placing the order chooses from among the contractors relevant to that site, without browsing a general directory.
This directory of service providers is taken from a directory external to Scout. The organisation does not have to maintain a second list of its contractors in the platform. Sometimes, however, a need concerns a company that is not yet listed. In that case, the team member can request the onboarding of a new service provider from within Scout. The request is thus made where the need arises.
From field notes to a scope of works, with AI support
Describing the work is often the trickiest part of a service order. Findings arrive as quick notes taken during a visit or after an issue is reported. A service provider needs a clearer statement to understand what is expected of them.
From these notes, AI drafts a proposed scope of works, or improves a text that has already been started. As an illustration, notes such as “leak under kitchen sink, seal to redo, check the trap” can become a structured paragraph describing the expected job. This text remains a suggestion: the person placing the order reviews, corrects and completes it before going any further. AI saves them from starting with a blank page. It decides neither the final content nor the sending.
Editable tasks, allocated to the right units and the right budget lines
An overall scope of works is not enough to price or track an expense. Once the scope of works has been drawn up, AI can break it down into separate task lines. These lines serve as the basis for pricing and allocating the work, but AI does not set any approved price: costs and allocations remain for the team member to check. The lines remain editable: they can add a forgotten task, correct one or remove one that does not match the request.
Each line is then split between the relevant accounting lines and units. For an organisation that manages properties made up of many units, this breakdown is essential. A single job may affect several apartments or fall under several expense lines. Scout checks these breakdowns and keeps the allocation at the level of each line. The cost of the service is thus linked, from the moment of ordering, to the place where the work takes place.
A draft until issue, then tracked sending
Preparing a works order sometimes happens in several stages. You wait for clarification from the site or check a breakdown before committing. The file can therefore be saved as a draft. The team member then picks it up again at the step where they left it, without anything being sent to the service provider.
When the file is ready, the person placing the order issues it. Scout checks that the required conditions are met before turning the preparation into a commitment to the service provider. The purchase order is then sent to the service provider from the file. If the order was delivered to them by other means, this transmission can be recorded manually and thus appears in the history. If sending a notification fails, it can be retried on its own, without redoing the file.
Tracking the job and changing service provider in the event of a refusal
After sending, the file becomes the tracking point for the job. It brings together its history, the invoices received and the progress of the service. The details of a purchase order can still be modified when its status allows, by the people who have the right to do so.
A service provider may refuse a job. In that case, the refused order can be reassigned to another service provider approved for the site. The history of the refusal is kept, and the job continues without the file having to be redone. An order can also be cancelled by giving a reason. Scout first checks the obligations already committed, to avoid mistakenly cancelling an order that has already been invoiced or processed.
On the invoice side, a manager or an accountant can accept a service invoice, mark it as reviewed, reassign its lines to the budget line or unit actually concerned, or reject it. A rejected invoice is not lost. If transmission to accounting fails, it can be retried without recreating the service. Once the invoices have been confirmed and the job is complete, a file that meets the conditions can be closed. Completed jobs are thus distinguished from those still to be followed up.
Property organisations that use Scout thus have, for their works, a flow separate from the basket. It runs from choosing a contractor approved for the site through to closing the file. AI helps turn field notes into a scope of works and tasks. The people responsible for the order remain in control of its content and of every decision.