mosaddik.dev
Hire me
All posts

How to brief a Wix developer and get an accurate quote

Mosaddik Billah 4 min read

Wix

An open notebook, a pencil, a phone and glasses on a white desk
Photo by JESHOOTS.COM on Unsplash
On this page
  1. 1. What the business does, and what the site is for
  2. 2. What exists already
  3. 3. The pages
  4. 4. What the site needs to do
  5. 5. Examples you like
  6. 6. Budget and timeline
  7. 7. After launch
  8. A brief template to copy
  9. What a good quote looks like

The quality of a quote depends on the quality of the request. “I need a Wix website, how much?” can mean a three-page site or a booking system with member accounts, and a developer can only guess. A short, clear brief gets you an accurate price, a realistic timeline, and fewer “that wasn’t included” moments later.

You don’t need technical words. Here is what to include, and a template you can copy.

1. What the business does, and what the site is for#

Two or three sentences about the business and the one main thing the website should achieve:

  • “We’re a cleaning company in Dhaka. The site should bring in quote requests for office cleaning.”
  • “I sell handmade jewellery. I want to take orders online instead of through Instagram messages.”

The goal shapes everything else: which pages matter most, what goes at the top of the home page, and what has to work perfectly.

2. What exists already#

  • Do you have a site now? On Wix or another platform? Share the link.
  • Do you have a logo, colours and fonts, or do they need creating?
  • Who writes the text, and do you have photos?
  • Do you own the domain, and do you have a Wix account and plan?

Missing content is the most common reason projects run late. Saying what’s ready, and what isn’t, lets the developer plan for it.

3. The pages#

A simple list is enough:

Home, About, Services (one page per service: 4 services), Pricing, Blog, Contact

If some pages are many items of the same kind, like products, team members, properties or courses, say roughly how many. These are often built as dynamic pages from a CMS collection, so you can add more yourself later.

4. What the site needs to do#

This is where costs vary most, so be specific. For each feature, describe what a visitor or your team does:

  • “Visitors book a 30-minute consultation and pay a deposit.”
  • “Members log in and see only their own documents.”
  • “New form entries go into our HubSpot CRM.”
  • “A chat assistant answers questions about our services.”

Mark each one must have or nice to have. It lets the developer quote the essentials and price the extras separately, so you can choose.

Some features are built into Wix; others need custom code with Velo, an app, or a connection to another service through its API. You don’t need to know which. A good developer will tell you, and suggest the simplest option.

5. Examples you like#

Send two or three websites you like, and say what you like about each: “the clean layout”, “how the pricing table works”, “the photos on the home page”. One sentence each is far more useful than links alone. A site you dislike, and why, helps too.

6. Budget and timeline#

Sharing a budget range isn’t giving away your negotiating position. It tells the developer which version of the project to propose. The same goal can be met with a simpler or a more advanced build.

For the timeline, give the date you need it by and why (a launch, an event, a season), so it’s clear which dates are fixed.

7. After launch#

  • Who will update the site day to day?
  • Do you want training, or a short guide?
  • Do you need ongoing help with changes, fixes or new features?

A brief template to copy#

Business: what we do, where, for whom.
Main goal of the site:
Current site (link), domain, Wix account: yes / no
Logo, colours, text, photos: ready / partly / not yet

Pages:
Repeating items (products, team, etc.) and roughly how many:

Features (must have):
Features (nice to have):
Other tools to connect (CRM, payments, email, booking):

Sites we like, and why:
Budget range:
Needed by (and why):
Who updates the site after launch:

What a good quote looks like#

When you send a brief like this, expect the reply to tell you what will be built, what isn’t included, how long it takes, the price, and what the developer needs from you. If anything in the brief was unclear, a good developer asks before quoting rather than guessing.

You can send me your brief through the contact form or on WhatsApp, and I’ll reply with a plan and a quote. For the kinds of work I do, see Wix website design and Wix Velo development.

Comments