WHY – why precision is an investment, not a cost
The time you spend organising the information that already exists in your company is one of the fastest-paying investments in the whole project. Instead of creating new documents from scratch, it is worth taking a close look at the business as it is today: its processes, data, constraints and goals.
Why does it matter so much?
An accurate quote
An overly general enquiry forces the agency to guess. And when an agency has to guess, it usually also has to protect itself against the most complex scenarios. The result? Quotes can differ significantly from one another, and the client does not always know where those differences come from.
If the brief is based on hard data, up-to-date documents and a realistic description of needs, the quote is more reliable. That way you pay for what you actually need — not for assumptions nobody had time to clarify.
Greater budget security
The most expensive changes are the ones that only surface at the design or development stage. They often stem not from new needs, but from the fact that important processes, exceptions or constraints were never described earlier.
A well-prepared brief reduces the risk of so-called Change Requests — additional, paid changes that modify the original scope of the project. The better you describe the requirements at the start, the easier it is to keep the project within the planned budget.
A platform that supports the business, not just the technology
A new e-commerce system should not be merely a modern tool. It should support sales, streamline processes and solve specific operational problems.
That is why the brief should be driven by real business goals: sales reports, financial data, logistics challenges, customer needs and team constraints. Only then can you design a platform that not only looks good and works technically, but actually contributes to the company’s results.
HOW – how to gather information without unnecessary effort
Most of the answers are probably already in your organisation. So the point is not to write a specification from scratch, but to make good use of the knowledge, documents and data you already have.
Who should be involved on the company side?
The best brief is created when it is not written from the perspective of just one person or one department. It is worth consulting it with the people who work every day with the processes the future platform is meant to support.
Logistics knows best how parcels are packed today, how returns are handled and where the bottlenecks are. Marketing knows the personas, communication, brand materials and planned campaigns. IT can point to the systems in use, licences, integrations and technical constraints. Sales knows customers’ most frequent questions, recurring problems and the moments when the purchasing process stalls.
The sooner you gather these perspectives, the lower the risk that important requirements will only come up during the project.
Which existing documents can you use?
You do not have to describe everything by hand. Often it is enough to reach for ready-made materials and attach them to the brief.
Instead of estimating traffic “off the top of your head”, use GA4 reports and show historical sales peaks. Instead of redrawing the product tree, use the current category structure — for example an export from your ERP or PIM system. Instead of describing your visual identity in words, attach the current brand book.
Materials prepared this way give the agency a much better starting point than general statements and shorten the stage of clarifying requirements.
WHAT – what should an e-commerce brief include?
Below you will find a list of the key areas worth covering in the brief. For each of them we also point out which resources from your organisation you can draw on.
Business goals and KPIs
Start by defining what the platform is supposed to achieve for the business. Is the goal to increase the average basket value? To automate part of the wholesale orders? To shorten customer service time? To improve conversion? Or perhaps to bring order to the B2B sales process?
It is worth showing not only the goal, but also the starting point. Reach for annual plans, sales reports and financial data. This way the agency will see what level the project starts from and which results really matter to your company.
Technology and architecture
In this section, describe the current technology environment and your preferences for the future platform. Are you considering an off-the-shelf SaaS solution, a self-hosted system or a flexible headless architecture? What traffic do you expect in the store? Which systems do you currently use — ERP, PIM, WMS, CRM, payment tools, invoicing systems, marketing automation?
The IT department will be the best source here. Ask for a simple list of the software in use, including versions. If your system vendors have API documentation ready, attach it to the brief. This makes it possible to assess the complexity of the integrations more quickly.
UX and design
Describe the requirements for the purchase path. Does the registration process follow a non-standard flow? Does checkout require additional steps? Do B2B customers need to see individual prices, credit limits or special order terms? Are there elements of the current store that are worth keeping?
Benchmarks will also help. Paste links to 3–5 platforms that clearly show the direction you like — not only visually, but also functionally.
It is worth attaching the brand book, existing mock-ups, sketches from workshops, past UX audits or notes from earlier work on the customer journey. Even working materials can be very helpful.
Content and SEO
In this section, define who will be responsible for product descriptions, photos, category content, how-to articles and other materials on the site. It is also worth indicating which content must be migrated from the current website and which will be created from scratch.
When it comes to SEO, migration is especially important. Based on the current URL structure, point out the key pages and sections to be moved. Attach an export from Google Search Console, the current sitemap or a list of the most important URLs. This makes it possible to plan safe redirects and reduce the risk of losing organic traffic.
Analytics
Describe what data your teams will need once the platform is live. Which reports are currently the most important for the management board, sales, marketing or customer service? Which metrics are analysed regularly? What data is missing?
There is no need to invent new metrics just for the brief. It is enough to gather the current dashboards, report screenshots and examples of analyses the company uses day to day. On that basis it is easier to plan the configuration of GA4, GTM and future reports.
What if the brief has “blank spots”?
This guide was designed to help you build a brief on your own, based on the resources you already have. Sometimes, however, the very process of gathering information reveals gaps: missing knowledge in a specific area, discrepancies between departments or difficulty making a technical decision — for example about the data flow between the ERP and the store.
This is natural, especially in larger e-commerce projects and when scaling a business.
If such “blank spots” appear while you are working on the brief, you can treat them as a signal that before the actual implementation it is worth running an additional clarification stage — for example short discovery workshops with analysts, technologists or the project team.
It does not have to be the first step, though. It is most effective to start with what you already have: documents, data, processes, reports and the team’s knowledge. Only on that basis is it worth deciding which areas need further refinement.
Key takeaways
- A good e-commerce brief does not have to be created from scratch — in most cases it is enough to organise the data, documents and knowledge that already exist in the organisation.
- A precise brief helps reduce the risk of underestimation, costly changes during the project and gaps between expectations and the final scope of work.
- It is worth involving different departments in preparing the brief: IT, logistics, marketing, sales and the people responsible for analytics.
- “Blank spots” in a brief are natural — what matters is naming them before implementation, rather than discovering them only at the design or development stage.