A vague brief gets a vague quote. If you want a price you can plan around, give the developer enough to understand what you need, who it is for, and what "finished" looks like. You do not need a long document. A page is enough.
1. Say what the project is, in two sentences
Start with the problem, not the technology. "We need a way for customers to book delivery slots on our WordPress store" is better than "We need a plugin". The developer can then suggest the right tool, which may not be the one you first imagined.
2. Say who will use it
Name the people: shop visitors, your own staff, your clients, an admin. Different users need different screens, and every extra user type adds work. List them, even if there are only two.
3. List what it must do, and what can wait
Write the must-haves as a short list of plain sentences, one action each. Then write a second list of nice-to-haves. This split is the most useful thing you can give a developer, because it lets them quote a first version and a later one.
4. Share examples and links
Send links to sites, apps or screenshots you like, and say what you like about each. Send links to anything the project must connect to, such as your website, a payment service, a delivery service or an existing tool. If you already have a design, attach it.
5. Tell us about the systems it touches
Mention where it will live (WordPress, a browser, a phone, your own server), which version or plan you use, and whether other tools must exchange data with it. Integrations are a common reason a price changes, so naming them early avoids surprises.
6. Give a date and a budget range
A target date and a rough budget are not a trap. They help the developer tell you what fits and what does not. If you are not sure about the budget, say so. A good developer will offer options at different levels instead of one number.
7. Say how you will decide
Tell the developer who approves the work, how quickly you can answer questions, and whether you need to show the plan to someone else first. Slow feedback is the most common cause of late projects, and it is easy to plan for when it is known up front.
A simple template
Copy this and fill it in:
- What we need: two sentences.
- Who will use it: the user types.
- Must have: a short list.
- Nice to have: a short list.
- Examples: links.
- Connects to: systems and tools.
- Target date and budget range:
- Who approves:
What happens next
When you send your brief, we reply with questions, then a written proposal with scope, timeline and price. The price you see in our estimate tool is a starting point and can be negotiated for special circumstances. Talking to us first costs nothing.
