Module · Project requests
A brief that arrives as a brief, not as “can you do something like this”.
For studios, agencies and anyone whose work starts with a conversation. The request form asks for scope, budget, timing and reference files up front, and each request moves through a small set of states — new, reviewing, quoted, won, lost — with the files and the numbers kept on the request.
Switched on per account rather than bought. Plans start at $20 a month.
The brief
Ask for the four things you would have asked on the call anyway.
What it is, roughly what it costs, when it is needed, and what it should look like. The form asks for a budget range rather than a number — what they can spend is a different question from what they are buying, and it is the one people actually answer.
You choose the fields. A photographer asks for a date and a location; an agency asks for the deliverables. Their answers arrive free-form, in their own words, because a form that only accepts your categories loses the sentence that mattered.
The states
New, reviewing, quoted, won or lost. That is the whole pipeline.
Five states, deliberately few. A studio does not need a sales funnel; it needs to know which briefs it has answered and which are waiting on the client. Moving a request is a one-field change, and nothing else happens when you do it.
Worth saying plainly: moving a request does not email anybody and is not written to an activity log. The state is for you, and telling the client is still a message you send.
The record
The brief, the files and the number, on the request that carries them.
Everything they sent stays on the request: the scope in their words, the answers to your own questions, the reference files, and the estimate you recorded with its range and any line items. Open it next March and the brief and the number are both still there.
What is not there is a thread and a client record. A request carries a name, an email and a company as text, so it is not joined to anything else — their second brief next year arrives as a second request rather than landing beside the first.
How you get it
On your plan, switched on for you.
Project requests is switched on per account rather than bought. It is not an add-on with a price of its own — your developer turns it on when your project is set up.
Project requests uses Forms & email, which every workspace already has.
Before you start