Back to Resources
6 min read

How Do You Brief a Sitecore Vendor? Say What You Want, Not How

Listen to this article

Verified October 19, 2026.

Originally published February 25, 2025.

Say what should happen, and leave the how to them

Be precise about what you want: who it is for, what the visitor or author should see, and how you will check it worked. Be generous about how it gets built. Brief one component at a time, write each feature in three lines, keep the order of the backlog in your hands, and for anything risky, ask for a cheap throwaway version before the full build.

A two-panel guide. WHAT paired with a green check, meaning say this because it is what you want. HOW paired with an orange warning icon, meaning leave this to your agency.

The tortilla test

Send someone to buy high-protein tortillas and say "around 10 grams each is great." That is the going rate, so they grab a pack off the shelf. Now demand exactly 11.8 grams. Either they decide you did not mean it and buy the standard pack anyway, or they take you literally and build a factory for yours. Your Sitecore brief works the same way.

Why the how backfires

"Authors can add a promotion banner to any product page" is the 10-gram request: any Sitecore team can deliver it. "Build it as a controller rendering with this exact class structure and cache it this way" is the 11.8-gram version. Hand over that kind of recipe and one of two things happens.

They follow every line

Every "do it this way" becomes a hard constraint, including the ones you only added because you read they were best practice. Your vendor cannot tell your must-haves from your maybes, so all of it hardens into requirements, and the work slows and tangles.

Or they quietly ignore it

They drop the parts that look optional and build what they think you meant. Sometimes that lands. Often you find out while staring at something wrong, with no clean way to point at where it went sideways.

The one time to say how: consistency

There is a real exception. If the new work has to live next to what you already run, say so. If your other sites use SXA, ask for SXA. If you are headless on Next.js, the new site should be too. If your team serializes items one way, the vendor should follow it. That kind of how keeps the platform coherent, and it keeps the next team you hire from inheriting a mix of approaches.

The same logic applies to choosing the vendor. If your estate is Sitecore on .NET and Azure, hire people who live in that stack, not a shop that will learn it on your budget.

Brief one component at a time

A Sitecore site is not one giant thing to describe. It is a set of components: a hero, a card grid, a form, a promotion banner. They repeat, so you brief the shape once, not every instance. Give each component a one-page brief your vendor can read in two minutes:

  • The gist: what it is and where it appears, in one or two sentences.
  • Who does what: your vendor builds it; your authors place it and fill it in.
  • The fields authors fill in: for a card, perhaps a title, a one-line summary, an image and a link.
  • Rules: no title, no card; no image, show the brand color instead.
  • How it should feel: the whole card is clickable, with a light hover effect.
  • Room to grow: "a video might replace the image one day," as a heads-up, not a requirement.
  • Per screen: one card per row on phones, two on tablets, three on desktop.
  • A picture: a napkin sketch or a screenshot of a site that got it right.

Fill in exactly one, completely

Then fill in one real example: the actual title, summary, image and link for one card. Your vendor can build from a finished example far faster than from a description. A crooked hand-drawn sketch beats three careful paragraphs about spacing.

Ask for each feature in three lines

For behavior, not layout, write three lines:

  • As a visitor looking at a product that is out of stock
  • When I select "Email me when it is back"
  • Then my email is saved and I get one message when it returns

That is the shape practitioners call a user story,1 with its outcome written as given-when-then,2 minus the jargon. The first line names who it is for. The second names the exact moment. The third names a result you can watch happen, which makes it your test later.

Every edge case is three more lines

Each "but what if" is another short block, written down rather than argued in a meeting:

  • When the same visitor asks twice, then their email is saved once
  • When the product is already in stock, then the option never appears

Notice what is missing: no database tables, no framework names. Your three lines say what should happen; how to build it is the vendor's call.

Your backlog is a shopping list

Everything goes on one list

Every feature, component and bug lives on one list, the backlog.3 Work happening off the list is a bad sign.

Hard dependencies belong to your vendor

Some items carry a technical order: templates before the components that use them, a sign-in before anything behind it. Your vendor sets those, and overruling them never ends well.

Every other order belongs to you

Beyond those, the order is yours: it is your budget being spent. The Scrum Guide gives this job to the Product Owner, who is accountable for ordering the backlog.4 On your project, that is you or someone you name.

The life of an item

Each item moves through a few stops: New, Approved (you agreed to spend on it), In progress (their side: build, code review, their own testing), Verify (deployed where you can check it against your three lines) and Closed. If it fails your check, it goes back with notes. Our guide to what done means on a Sitecore project covers each stage's finish line and how to report a bug.

Approval guards your wallet

Nothing that costs real hours should reach a developer without your yes. Routine maintenance does not need your sign-off; new features and rebuilds do. Review work in batches at the end of each sprint rather than one item at a time.

Ask for the throwaway version first

For anything uncertain, such as a new integration, a search or personalization idea, or a feature that depends on a third-party service, ask for a bare-bones proof of concept before the full build. It needs no design. Its only job is to run your real data through the risky part and show you the result. If the result is good, build it properly. If it is not, shelve the idea before it becomes a project, and try again when the third party improves.

The whole thing in one line

Be clear about the what, generous about the how, and keep the order of the list in your hands. If you are planning an upgrade or a migration and want a second opinion on the brief, see our Sitecore services or talk to a senior Sitecore consultant.

References

Footnotes

  1. Atlassian. "User stories with examples and a template" ↑︎

  2. Cucumber. "Gherkin Reference" ↑︎

  3. Atlassian. "Product backlog: Tips for creation & prioritization" ↑︎

  4. Scrum Guides. "The 2020 Scrum Guide" ↑︎

Related Articles