Writing your brief
A good brief says what the product must do, who will use it, and roughly what you can spend. That's enough for us to reply with questions or a time for the free call. Only your name and email are required.
The brief is the form at zaions.com/start-a-project (opens in a new tab). It has three short steps.
What should the brief include?
Three things matter most. Everything else helps.
- What it must do. The jobs a person gets done with it, in your words. "Customers book a table and get a reminder" beats "a booking platform".
- Who will use it. Your customers, your staff, or both. On a phone, a computer, or each.
- Your budget range. A rough range is enough. It helps us shape the estimate.
If your idea is still a napkin sketch, that's a fine place to start. Send it as it is.
The form, step by step
Skip any field you're unsure of. It can wait for the free call or the written plan.
| Step | Field | What to put there |
|---|---|---|
| 1 · Your project | Services | Pick any that fit: web apps, mobile apps, browser extensions, desktop apps, graphic design, video editing, QA testing and automation, AI features and automation. Not sure? Skip it. |
| 1 · Your project | What you need | What it must do and who will use it. You can bold a line or make a bulleted list of features. Links to examples go here too. |
| 2 · Budget and timing | Package | The package closest to your budget; Packages explained covers each one. Arriving from a package's button picks it for you; change it any time. |
| 2 · Budget and timing | Budget range | One of five bands, from under $1,000 to $5,000 or more, or "Not sure yet". No band is too small to send. The bands follow the package floors on Pricing (opens in a new tab). |
| 2 · Budget and timing | Your target date | A launch, event or deadline you're working toward. It's your date, and it helps the plan. |
| 3 · About you | Your name, Email, Company | We reply to the email you type, so check it once. Company is optional. |
There's no upload field. Put links to sketches, documents, a shared folder or a competitor you like inside "What you need", and they reach us along with the brief.
An example of a good brief
Example, not a client. An illustration of the shape, written for these docs.
Services: Web apps, Mobile apps
What you need: I run a small bakery. Customers should be able to order a cake online, pick a pickup day and pay a deposit, and my two staff need one screen showing tomorrow's orders before they open. Most customers order from their phones, and most of them use Android.
Package: Build · Budget range: $3,000 to $5,000 · Target date: a date before the holiday season
Why it works: it names the people (customers and two staff), the jobs (order, pick a day, pay a deposit, see tomorrow's orders) and the device. It doesn't name a framework, a database or a feature list copied from someone else's app. That part's our job. The written plan shows you what we chose and why.
What if I'm not sure what I need?
Say so in the brief, or pick the free consultation.
A short brief is fine. "I need customers to book appointments, and I don't know if that's an app or a website" is a brief we can answer. On the free call we'll tell you which one costs you less, and the written estimate says so too if a cheaper package covers the job.
What happens after I send it?
You'll see "Brief sent" with the email address you typed, so a typo shows at once. Then:
- We read it and reply, either with questions or with a time for the free call.
- You get a written plan and estimate.
- You decide. Nothing is built until you say go.
If the send fails or you're offline, your answers stay on the page. Try again, or call +92 304 6619706.
Can I talk to someone instead?
Yes. Book the free consultation, and the brief opens with it already picked. The email addresses are on zaions.com/contact (opens in a new tab). Or call +92 304 6619706.
Next: How a project runs: what happens between the brief and the handover.