Requests vs projects
When to use Requests vs Projects—and how both differ from buying a ready marketplace listing.
At a glance
| Requests | Projects | Marketplace | |
|---|---|---|---|
| Shape | One brief → seller proposals | Longer work with seats / disciplines | Ready listing with price & timeline |
| Best for | A clear one-off need | Multiple roles or stages | A predefined service |
| Payment | Wallet after you accept a proposal | Per seat / project agreement | Direct purchase of the listing |
Use Requests when
- You can describe the outcome in a short brief.
- You want to compare several proposals before choosing.
- The work is usually one person or a limited scope.
Start at Services needed / Requests, post the brief, review proposals, and pick a seller.
Use Projects when
- You need more than one discipline (e.g. design + development + content).
- You want seats with separate budgets and deadlines.
- The scope is larger than a simple service request.
Create a project from Projects, add seats, then collect proposals per seat.
When to buy from the marketplace?
If a ready service matches your need—clear price, timeline, and inclusions—buy from the Marketplace. Use Requests or Projects when you need to find a partner instead of a ready listing.
Quick tips
- Write the brief in Arabic when your audience is Arabic; state expected delivery and budget when you can.
- Do not pay off-platform—use the wallet and escrow.
- Sellers: reply with realistic proposals; see also Sell on ELKNZ.