Skyltfönster
Custom Requests
Den här sidan är inte översatt ännu, så du läser den engelska versionen.
Let brands ask for work outside your packages, then turn their brief into an offer you price.
A custom request is not a booking
It contains a brief and may include a requested delivery date, but it has no price and creates no contract. You set the deliverables, usage rights and price in the offer you send back.
Custom Requests give a brand a way to ask for work that is not covered by one of your fixed packages. The brand describes the job, you decide whether it is a fit, and you answer with an offer on your own terms.
Turn Custom Requests on
Go to Profile → Public profile settings. Under How a brand reaches you, turn on Custom Requests, then save your changes.
A signed-in brand will now see Send a Custom Request on your public profile. When they open it from a package, that package follows the request as context. When you have no visible packages, the profile shows a separate way to ask about a custom job.
Turning the switch off removes this option and stops new requests. Requests and offers that already exist are kept.
What a brand sends
The form asks for:
- A brief. What the brand needs, with enough detail for you to judge the work. The brief must be at least 20 characters and can be up to 4,000.
- Needed by. An optional date for when the brand would like the work.
- Package context. Added automatically when the brand started beside one of your packages.
The current form does not ask the brand to set your price or enter a budget. They can mention a budget in their brief if it matters to them, but it remains context. You still price the work.
A brand can have one unanswered custom request with you at a time. They can send another after you have answered or declined the first one.
Where requests appear
New requests land in Collab Requests → Custom Requests. Each request shows the brand, the time it was sent, their brief, the requested date if they supplied one, and the related package when there is one.
Older requests may also show a budget. That is the brand's old, self-reported budget, not your price, and it is never copied into your offer.
Answer with an offer
Choose Answer with an offer to open a draft proposal. Creator Space carries the useful context into the draft:
- The brand's brief becomes the scope notes.
- Their requested date becomes the delivery date.
- If they started from a package, its deliverable, published price and usage period can seed the first proposal line.
Everything in the draft remains yours to review and edit. Add the right deliverables, quantities, revisions, usage rights and price before sending it. Nothing is shown to the brand while the proposal is still a draft.
The proposal is delivered to the brand inside CollabNordic because they already have an account. Answering a custom request does not automatically add the brand to My Brands.
For every proposal field and the send flow, see Creating a proposal.
Decline a request
Choose Decline when the job is not a fit. Creator Space asks you to write a short reason, and the brand receives that reason in their notification.
Declining closes this request. It does not stop the brand from sending a new request later while Custom Requests remain switched on.
Custom Request or package booking?
| Package booking | Custom request | |
|---|---|---|
| What starts it | The brand chooses a published package | The brand sends a Custom Request outside the fixed offer |
| Price | Your published package price | You set the price in a proposal |
| Your response | Accept or decline | Answer with an offer or decline |
| What happens next | Acceptance sends the contract for payment | You finish and send a proposal for the brand to accept |
| When work starts | After the brand funds escrow | After the brand accepts the offer and funds escrow |
Both arrive under Collab Requests, but they stay on separate tabs because one is a booking at known terms and the other is a question that still needs an offer.