Most services marketplaces in 2026 still treat the request-to-quote loop as plumbing. The buyer fills a form, the form fans out to suppliers, suppliers reply through email or message. The loop is the actual product, the place where the marketplace earns or loses every transaction, and it is the part that gets the least design attention. This is a sketch of what it looks like when designed properly, using our work on Dreilokale as a reference for the event-location category.

The loop is the product.

A buyer arrives with a need. The buyer describes the need. The marketplace decides which suppliers should see it. Suppliers reply with offers. The buyer compares. One conversation continues. Most marketplaces optimise the arrival and the conversation. The decisive part is what happens in the middle, and it is designable.

Designing the request.

A bad request is a long open-text box and a submit button. The supplier reads a wall of prose, mostly guesses, and replies with a generic quote. A good request is a structured object that surfaces the right questions on the screen and produces a brief the supplier can answer in minutes:

  • Anchor field. A single question that frames the request (date, location, headcount, format). Without this, downstream questions are noise.
  • Constraints surfaced. Budget, must-haves, deal-breakers, deadlines. Presented as inputs, not buried in prose.
  • Context written once. A short description of what the buyer is doing and why, captured once, reused in every quote interaction.
  • Verifying signals. Identity, organisation, previous activity on the marketplace. Suppliers reply more thoughtfully when the buyer is real.

Routing supply.

The marketplace decides which suppliers see the request. The default is to fan it out wide and let the buyer drown in five generic quotes. The better pattern is curated routing: match on hard constraints (date availability, location, capacity), then a short tail of qualified suppliers (three to five) actually see the request. Each supplier knows they are in a small set, and the quote quality reflects it. The buyer receives a manageable shortlist instead of an inbox flood.

What a good quote looks like.

Free-form prose replies are noise. A designed quote is a short structured object the buyer can compare across suppliers:

  • Headline number. A price or a band. Hidden price kills comparison.
  • What is included. Three to five concrete lines, not a brochure.
  • Conditions. Capacity, deposit, cancellation window, anything that materially changes the offer.
  • A short note. One paragraph in the supplier's voice. The note is where the supplier distinguishes themselves; the structure is what makes distinction visible.

The response window.

The marketplace sets a clock. Suppliers know they have (say) 48 hours to respond before the request expires from their queue. The buyer knows the window. Late suppliers drop out automatically and the buyer sees a complete shortlist on schedule rather than a trickle of stale replies. The window is one of the highest-leverage design decisions in the loop; the right value is category- specific and worth A/B testing.

Common failure modes.

  1. Open-ended fan-out. The request goes to twenty suppliers, each spends five minutes, the buyer drowns, most suppliers waste their time, the marketplace loses supply within two cycles.
  2. Unstructured replies. Suppliers send their own email templates. The buyer cannot compare. The decision-load gets dumped back onto the buyer the platform promised to help.
  3. No clock. The buyer assembles a shortlist over two weeks instead of two days. Energy decays. Many requests die of timeout.
  4. No identity. Suppliers cannot tell a serious request from a tire-kicker. Reply quality bottoms out.

Common questions.

Should the marketplace assign a single supplier or let the buyer choose? Both shapes work. Curated single-match (the platform picks one supplier, the buyer accepts or declines) works in high-trust categories (hospitality bookings, professional services with strong verification). Shortlist (three to five) works in comparison-driven categories (events, venues, renovations).

What is Dreilokale's shape? Curated shortlist, structured request, structured quotes, 48-hour window, identity verification on both sides. The loop is the product. The interface is built around it, not around it.

Related reading. Marketplace design principles and Marketplace trust signals 2026 cover the surrounding architecture. The glossary entry on marketplace platform has the one-paragraph definition.