A deliverables list
Every piece of work named separately so you can strike any line out and watch the price move.
Proposal
A scoped plan, in writing.
Tell us the outcome you need. You get back a written proposal with a fixed price and a timeline — before anything starts and with no obligation.
- Fixed price before work starts
- No obligation to proceed
- Written scope you keep
0 daysTo a written scope
0Cost to ask
0%Fixed-price work
0Point of contact
What happens next
- You send this form. Two minutes.
- We reply within one business day — usually with two or three questions, because the first brief never has everything.
- You get a written proposal: scope line by line, fixed price, timeline, and what we need from you.
- You decide. No follow-up sequence, no pressure. If it's not right we'll say so ourselves.
If your budget is better spent elsewhere — or a freelancer genuinely fits the job better — that's what the reply will say.
What arrives
What is actually in a proposal.
Usually four to six pages. Free, yours to keep, and no obligation attached to it.
An exclusions list
What is explicitly not included. This is the page that prevents the argument in week five.
A dated timeline
Milestones with dates, including what we need from you and when we need it.
One fixed number
A total that does not move unless you ask for something new — and then that gets priced before it starts.
The assumptions we made
Written down, so if one of them is wrong you can correct us before rather than after.
Ownership terms
Plain confirmation that the code, designs, accounts and automations end up yours.
Proposals
Reasonable to ask.
Two business days for most projects. Something with several integrations may take three or four, and we will tell you which it is when you ask.
Yes, and the document is yours regardless of what you decide. Some people use it to brief someone else. That is fine.
What you are trying to achieve, roughly when you need it, and any hard constraint we should design around. A budget range helps but is not required.