Lawyer marketplace platforms: routing requests, first-to-accept and office performance

What a lawyer marketplace platform is

A lawyer marketplace platform is a two-sided product: clients bring legal requests, and law offices decide which requests to take. The platform sits between them and runs three jobs: matching a request to suitable offices, handing the request to the office that accepts it, and giving both sides a shared record of what happened.

That makes it different from a directory and from a law firm. A directory lists offices and leaves the client to call each one. A law firm provides the advice itself. A marketplace does neither: it carries the request to offices and opens a channel once one of them accepts, while the advice, the fees agreed between client and office, and the professional responsibility stay with the office.

AlMizan, the legal consultation marketplace FLUIDS designed and built for Oman, follows this model. Clients send a request to licensed law offices and chat with the office that accepts. The product says plainly that it is a marketplace, not a law firm, and that it does not provide legal advice. The client-side flow is covered in our guide on how to build a legal consultation app; this article looks at the marketplace rules behind it.

Broadcast vs direct requests: how routing works

Routing decides who sees a request. There are two basic models, and AlMizan supports both: a client can send one request to several offices at once, or lock it to one office or a specific lawyer.

Most platforms need both. A client who saw an office's profile and liked it should be able to send directly, which is why AlMizan lets a request start from an office, lawyer or service page. A client who simply needs help with a labor or real estate matter is better served by a broadcast to relevant offices.

The specialization chosen at the start of the request is what makes broadcast routing sensible. Without it, every office would see every request. With it, a family matter can be routed to offices that list family services, and a commercial dispute to those that handle commercial work.

How first-to-accept works, and the rules around it

First-to-accept means that when a request goes to several offices, the consultation belongs to whichever office accepts first, and the chat opens with that office. It sounds simple, but it needs careful engineering and clear product rules.

• Acceptance must be atomic. Two offices can tap accept within the same second. The server, not the app, must decide the winner in a single transaction, so exactly one office gets the consultation.
• The others need a clear outcome. Offices that did not win should see that the request has been taken, and it should leave their queue, instead of showing an error when they try to open it.
• Review before accept. Offices need enough of the request, its specialization, description and attachments, to decide whether they can help. Accepting blind leads to consultations that are quickly abandoned.
• No acceptance in time. Decide what happens if nobody accepts: notify the client, suggest more offices, or let them convert the request into a direct one.
• Withdrawal. Decide whether a client can withdraw a request that is still awaiting a reply, and what offices see if they do.

Onboarding offices and lawyers, including licence checks

Office onboarding is an operating process that the platform owner designs and staffs; software supports it but cannot replace it. A marketplace that promises licensed offices has to be able to show how each office was checked.

1. Application. The office submits its details, the lawyers who will work through the platform, and the specializations and services it offers.
2. Evidence. The office provides the licence or registration documents the operator requires in that market.
3. Review. A named person on the operator's team checks the evidence against the relevant official source, records the result and the date, and approves or rejects the office.
4. Profile setup. The approved office completes its lawyers, services, branches and working hours.
5. Visibility. The office chooses when it appears to clients. AlMizan's office details include whether the office is visible, so an office can pause new requests without leaving the platform.
6. Periodic re-check. Licences can lapse or change. The operator schedules reviews and can hide a profile pending renewal.

Keep the operator's controls separate from the office's own. An office can hide itself; only the operator should be able to suspend an office or mark it as verified. Mixing those two switches is a common source of confusion and disputes.

Measuring office performance fairly

Office performance in a lawyer marketplace is usually measured with three numbers: rating, response rate and average response time. AlMizan puts all three on the office dashboard, next to new requests and active consultations, so an office sees how it is doing while it works.

• Rating. Collected from the client after a consultation is closed. Decide the scale, whether a written comment is allowed, and how many ratings an office needs before an average is shown.
• Response rate. The share of requests an office responded to out of those it received. Define what counts as a response, and whether requests another office accepted first are excluded.
• Average response time. The time from a request reaching an office to that office's first response. Decide whether working hours are taken into account, since an office that is closed overnight should not look slow.

Written definitions matter more than the formula. Offices will accept a metric they understand and can improve; they will distrust one that changes without notice. Show offices how each number is calculated, and decide early whether metrics affect ranking in search or only inform the office and the operator.

Use the numbers to improve service, not to imply legal quality. A fast, well-rated office is responsive and pleasant to deal with; that is not the same as saying its advice is better. The platform's wording should keep that distinction.

Business model options, and the platform boundary

A lawyer marketplace can earn revenue in several ways, and the choice shapes the product as much as the finances. The common options are:

• Office subscriptions. Offices pay to be listed and receive requests. Simple to run and keeps the platform out of the client–office fee.
• Per accepted request. Offices pay when they take a request. Aligns cost with value, but needs clear rules on what counts as accepted.
• Client-paid consultations. The client pays through the app and the platform passes the fee to the office. This brings payment processing, refunds and regulated payment providers into scope.
• Featured placement. Offices pay for prominence. It needs clear labelling so clients can tell paid placement from ordinary results.

Whatever the model, the platform boundary stays the same: the marketplace connects clients and offices, and the office provides and answers for the advice. FLUIDS designed and built AlMizan's mobile experience, including the client journey and the office tools that support it. If you are planning a similar marketplace, see the AlMizan case study, our approach to marketplace platform development, and how marketplaces in other sectors handle quotes in our RFQ marketplace guide. Scope, price and timeline are agreed in a written proposal before development.