Before
Requests were hard to compare
When information arrives in free form, the team must first reconstruct category, venue, participants, services, access constraints, logistics and contacts.
EMPV / Project04
More structured requests, human decision retained
Request qualification and quoting system
Requests arrived, but the team had to reconstruct what the customer was actually asking for before evaluating them.
Event type, audience size, venue, access constraints, equipment, transport, setup and technical support could emerge at different moments in the conversation. Before quoting, the team first had to rebuild the context.
What we changedWe did not automate the quote. We automated the information collection needed to prepare it well.
System
A flow that prepares human evaluation
The flow collects a compact set of information and adapts some questions to event type. No public pricing and no automatic quotation: the final decision stays with the team.
01 / The problem
Before quoting, the event has to be understood.
Conferences, weddings, DJ sets and private parties do not need the same information. A generic form can create leads without creating requests that are actually easy to evaluate.
02 / The decision
Structure the request without turning it into an endless configurator.
The V1 keeps a small number of main paths and gathers event type, date, location, participants, services, power, access, logistics and contact details.
03 / The boundary
Technology prepares; the team decides.
The summary is indicative, prices are not public and every request is evaluated directly by the team. That is a product choice, not missing automation.
04 / The outcome
A digital presence that produces more usable requests.
The website and guided flow become one commercial entry point: the customer describes the event, the system structures the data and the team receives a more consistent context to work from.