An ecommerce brief template gives you a fixed set of questions to answer before you talk to any developer, agency or freelancer, so the people you contact all react to the same facts. Without one, the first call turns into an hour of you explaining your shop from scratch, three times, to three providers who each hear a slightly different story and then quote three different jobs.

This page holds the template itself (ten parts, each with prompts), a copy-ready plain-text version, a filled-in sample for an invented bakery, a list of things that do not belong in a first brief, and a length rule. The brief is step one of the hiring sequence on MarketPulse. Step two is the discovery call scorecard, and step three is comparing the quotes that come back.

What is an ecommerce brief, and who reads it?

A brief is a one to two page document you write and send to providers before anyone books a call. It describes your business, the job you want done, the numbers behind it and the limits you work within. Providers read it to decide whether the job fits them, which questions to ask you, and roughly how they would price it.

Three documents get mixed up here, so it helps to separate them:

  • The brief (you write it): what you need and why. It stays short and leaves the method open.
  • The proposal or quote (the provider writes it): how they would do the job, for how much, by when.
  • The statement of work (written by the provider, agreed by both): the signed list of what will be built, tested and handed over.

If the thing you are buying is a software tool rather than a person’s time, use the ecommerce software buying brief instead. The template below is for hiring help: a developer, designer, consultant, marketer or agency.

What are the ten parts of the template?

Each part has a job. If a provider can read only one part, they should still learn something they need. Answer the prompts in plain sentences; bullet points are fine.

PartPrompts to answerRough length
1. The businessWhat do you sell, from where, to whom? How do people buy from you today (shop counter, phone, Instagram messages, an old website)?3 to 5 lines
2. The jobIn one sentence: what must be true when the work is finished that is not true today?1 sentence
3. Why nowWhat triggered this? A date, a season, a contract ending, something broken, a new location?2 to 3 lines
4. Current setupPlatform and plan, theme, apps or plugins, till or POS system, payment provider, domain registrar, email tool, who holds admin access.A short list
5. ScopeNumbered lines in three groups: needed on day one, wanted later, out of scope.6 to 15 lines
6. NumbersProducts, variants, orders per week, shop locations, languages, currencies, peak weeks.A short list
7. ContentWho supplies photos, product text, prices and translations, and are they ready?3 to 5 lines
8. PeopleWho decides, who answers questions day to day, how many hours a week you can give the project.2 to 4 lines
9. Budget and datesA budget band, the hard deadline (if any), the dates you are unavailable.2 to 3 lines
10. What you want backThe reply format and the reply date.4 to 6 lines

Parts 2 and 5 carry the most weight. A provider who misreads the job in part 2 will quote the wrong project, and a provider who cannot see clear lines in part 5 will pad the price to cover what they had to guess.

Can you copy the template as plain text?

Yes. Paste this into an email or a document and fill the blanks. Delete any prompt that does not apply to you instead of writing “n/a”.

  1. The business. We are ____ in ____. We sell ____ to ____. Today customers buy by ____.
  2. The job. When this work is finished, ____.
  3. Why now. We need this because ____. The date that matters is ____.
  4. Current setup. Platform: ____. Theme: ____. Apps or plugins: ____. Till/POS: ____. Payments: ____. Domain registered with: ____ (in the name of ____). Admin access held by: ____.
  5. Scope. Day one: S1 ____, S2 ____, S3 ____. Later: L1 ____, L2 ____. Out of scope: X1 ____.
  6. Numbers. Products: ____. Variants: ____. Orders per week now: ____, at peak: ____. Locations: ____. Languages: ____.
  7. Content. Photos: ready / partly / not started. Product text: ____. Who writes missing text: ____.
  8. People. Decisions: ____. Daily contact: ____. Hours per week we can give: ____.
  9. Budget and dates. Budget band: ____ to ____. Must be live by: ____. We are away: ____.
  10. What we want back by ____. Your understanding of the job in two sentences, the questions you need answered, your approach in outline, a price range with what moves it up or down, who would do the work, and when you could start.

The S, L and X labels look fussy, and they pay for themselves later: providers can write “S3 is included, L1 would add about 6 hours”, and you can line those answers up in one table.

What does a filled-in brief look like?

Example only: Bramble Bakehouse is an invented bakery with one shop, used here to show the template filled in. The numbers are made up for the example.

1. The business. Bramble Bakehouse is a bakery with one shop and a small kitchen. We sell bread, pastries and celebration cakes to local customers. Today customers order cakes by Instagram message or by phone, and everything else is bought at the counter.

2. The job. When this work is finished, a customer can order and pay for a cake or a Saturday bread box online, choose a collection slot, and our staff see every order for the next day on one printed list.

3. Why now. We take around 30 cake orders a week by message and lose track of 1 or 2 of them. December is our busiest month and we want the system running by 15 November.

4. Current setup. No online shop. A card reader at the counter, a domain we registered ourselves, an email account on that domain. The owner holds every login.

5. Scope. Day one: S1 online shop with 45 products; S2 collection slots on Fridays and Saturdays with a limit per slot; S3 cake orders need 48 hours’ notice; S4 card payments; S5 a daily order list staff can print. Later: L1 local delivery within 5 km; L2 gift cards. Out of scope: X1 wholesale ordering for cafés.

6. Numbers. 45 products, 12 of them with size options. Around 30 cake orders and an estimated 60 bread boxes a week. One location. English only.

7. Content. Photos exist for 30 products. Prices are final. The owner writes the product text.

8. People. The owner decides. The shop manager answers daily questions. We can give 3 hours a week.

9. Budget and dates. Budget band €2,500 to €4,000 for setup, up to €100 a month for running costs. Live by 15 November. Away 20 to 27 October.

10. What we want back by 6 October. As in the template.

That sample runs to about 330 words. Notice what it does: it names the job as an outcome staff can check (the printed list), it gives a deadline with a reason, and it says the owner holds every login, which tells providers early that accounts stay with the shop.

How do you write the scope lines so the quotes match?

Scope is where briefs go wrong. Owners write features (“we need a booking system”) when providers need outcomes they can test. Rewrite each line until a stranger could tick it off:

Vague lineTestable line
Nice product pagesEach product page shows price, sizes, allergens and the collection days.
Booking for cakesCake orders need 48 hours’ notice, and the calendar blocks days that are full.
Good on mobileA customer can finish an order on a phone without zooming.
Connect to the tillStock sold at the counter reduces online stock within 15 minutes.

Three rules keep the list honest:

  • One outcome per line. “Payments and delivery” is two lines, because a provider can price one and not the other.
  • Put “later” items in writing. Providers who know local delivery is coming in spring will set up the shop so it can be added without rebuilding.
  • Name the out-of-scope items. If you leave wholesale ordering unsaid, one provider will include it and quote double.

What should you leave out of a first brief?

A first brief goes to people you have not hired, so some things stay out on purpose:

  • Passwords and logins. Never, in any form. Access is set up later, through staff or collaborator accounts, once someone is hired.
  • Your full product spreadsheet. Give the count and one sample row. The full file goes to the provider you hire.
  • A prescribed solution. “We need a headless build with a custom app” closes off cheaper answers. Describe the job and let providers propose the method; their proposals tell you who understood it.
  • Exact turnover and margins. Order counts and a budget band are enough to size the work. Detailed finances add nothing at this stage.
  • Thirty pages of design inspiration. Link two or three shops you like and say one thing you like about each.
  • Contract terms. Payment schedules, penalties and ownership clauses come in the contract. The brief only states the facts that shape them, such as who holds the accounts.
  • Complaints about your last provider. State what is broken. The history belongs in the call, if at all.

How long should an ecommerce brief be?

Aim for 400 to 900 words, or one to two pages. The bakery sample above sits at the short end because the job is small. A migration with stock syncing and two shop locations will need the longer end.

Use these limits as a check:

  • If any single part runs past 150 words, move the detail into a list of attachments (“product sample, current site map, photo of the order book”) that you send after the call.
  • If the whole brief runs past two pages, you are writing the statement of work for the provider. Stop and cut back to outcomes.
  • If it is under 250 words, part 5 or part 6 is probably missing.

Writing time for a small shop is about one to two hours, most of it spent on the scope lines and on counting products and orders. Give yourself a test before sending: hand the brief to someone who knows nothing about the project and ask them to tell you the job in two sentences. If they cannot, part 2 needs another pass.

How do you send the brief to providers?

Send the same brief, on the same day, with the same reply date to each provider. Three is a good number: enough to compare, few enough to read properly. Give them seven to ten working days; good providers are busy, and a reply written in two hours is a reply that skipped your brief.

Sample covering message:

“We are looking for help to set up online ordering for our bakery. The attached brief explains the job, our numbers and our budget band. If it fits your work, please reply by 6 October in the format described in part 10. We will book short calls with the providers whose replies fit best.”

Keep a simple log: who received it, when, when they replied, and whether they used your format. Then book calls only with the replies that answered part 10, and score those calls with the discovery call scorecard.

What do the replies tell you before any call?

The reply is the first piece of real work a provider does for you, and it costs them nothing to do well. Read each one against your brief:

  • Did they restate the job correctly? A two-sentence summary that matches part 2 means they read it.
  • Did they ask about specific scope lines? “For S2, do slot limits differ between Friday and Saturday?” is a good sign. Generic questions are a weak one.
  • Did they flag a risk you missed? Mentioning that 48-hour notice and slot limits need testing together shows they have built something like it.
  • Did they name who would do the work?
  • Did they ignore the brief and send a standard package? That is one of the agency red flags, and it predicts how they will treat your change requests later.

FAQ

Should I put my budget in the brief?

Yes, as a band such as €2,500 to €4,000. Without it, one provider plans a €1,500 setup and another a €12,000 build, and neither reply helps you. A band also lets a provider say early that the job does not fit, which saves everyone a call.

Do I need to choose a platform before writing the brief?

No. If you already sell on a platform, name it in part 4. If you have not chosen one, say so and ask providers to recommend one in their reply with a reason. The Shopify vs WooCommerce guide helps you judge their answers.

Can I send the same brief to an agency and a freelancer?

Yes, and it makes the comparison fairer, because both answer the same job. Part 8 matters more here: a freelancer needs to know how quickly you answer questions, since nobody else on their side can wait for you.

Should I ask providers to sign an NDA first?

For a small shop the brief rarely holds anything secret, so an NDA mostly slows replies down. If something is confidential, such as a new product line, leave it out of the brief and share it on the call with the provider you are leaning towards.

What if a provider sends a fixed package instead of answering my brief?

Reply once and ask them to map the package against your scope lines S1 to S5. If they still cannot say which lines the package covers, drop them. A provider who will not work from your brief before you pay will not work from it after.

Should I update the brief after the calls?

Yes, if the calls taught you something. Add a dated version 2 with the changes listed at the top and send it to the providers still in the running, so their quotes are based on the same facts.

Is the brief part of the contract?

No. The contract and the statement of work are separate documents. You can ask for the brief to be attached to the statement of work as background, so the original job description stays on record.

What should you do next?

Copy the plain-text template, fill in parts 2 and 5 first, then the rest. Count your products and weekly orders before you write part 6, because guesses there change quotes more than anything else.

If you want a second pair of eyes on the brief before it goes out, send it through the MarketPulse contact form and say what kind of help you are planning to hire.