The marketplace sells two different shapes of work, and knowing which you want saves a conversation.
A service is bought
Fixed scope, published price, no discussion needed. "Add a GDPR consent banner", "fix Core Web Vitals on a slow site". Every service assumes you already have something to work on. There are 148 of them.
A project is scoped, then bought
"A website for my business" is somewhere between a few thousand and several tens of thousands, and nobody β buyer or seller β can say which until somebody asks how many pages it has, whether it sells anything, and who edits it afterwards.
So a project asks those questions first. Answer them and the price narrows as you go; each answer says what it costs and why.
How a quote happens
Projects end in quotes from several developers, not a checkout. You write a brief β the configurator pre-fills it from your answers, and there is an AI assist that expands your own words into the questions a developer would ask anyway. It will not invent requirements; anything it does not know goes into an open-questions list instead.
Then you pick who sees it, they reply, and you choose. No account is needed to ask; replies thread against your email address.
Prices are estimates until somebody reads the brief
Every number before that point is produced by a form. A developer who has read what you wrote will price it properly, and may well tell you it should be smaller.