B2B WEBSITE RELAUNCH — EDITABLE BRIEF
H-Studio · Version 2026-11-05 · usable with any delivery partner
Instructions: save a copy, answer the prompts, mark unknowns OPEN.
Do not include passwords, personal CRM exports or confidential customer data.

Project / company: [Name]
Public website: [URL]
Brief version / date: [Version, date]
Internal decision owner: [Role]
Proposal baseline: [Version of page inventory and other attachments]

1. STARTING POINT
Which three specific problems should the relaunch solve?
[Problem / observation / evidence / affected task]
What works and should remain?
[Content, URLs, functions, editing workflows]
Why might improving the existing system be insufficient?
[Reason or open question]

2. VISITORS AND TASKS
Main audiences: [Roles and information needs]
Three priority journeys: [Entry → information → desired action]
How will we recognise an improvement after launch?
[Measure, existing baseline, tracking limitations, owner]
Which results are release acceptance and which are later business goals?
[Do not assume ranking or lead guarantees]

3. PAGE INVENTORY AND LANGUAGES
Attachment: [URL list with page type, language, retain/change/consolidate/remove]
New pages: [Page type → content items per language → required template]
Total templates: [Count] · total editorial URLs: [Count]
Languages / translation relationships: [Languages and full/partial coverage]
Also inventory: [Legal, error/confirmation pages, PDFs, media, exceptions]
Out of scope: [Shop, portal, configurator or other deliberate exclusions]

4. CONTENT AND APPROVAL
For each content group:
[Group / source material / writing / editing / translation / content entry / approval / date]
Who checks facts, usage rights and legally relevant claims? [Roles]
When will approved content be available? [Date and dependencies]
What happens if delivery is late? [Decision, effect on scope/timing]

5. EDITING AND CMS
A task without a developer: [Create content → preview → approve → publish]
Required roles and permissions: [Roles]
Language association, unpublishing and URL changes: [Expected behaviour]
Existing CMS / justified constraints / open technology decision: [Details]

6. FORMS AND INTEGRATIONS
Forms / necessary fields / recipients: [List]
Destination system and business owner: [CRM or other system, role]
When is an enquiry durably accepted? [Observable evidence]
How is receipt in the destination confirmed? [Evidence, correlation]
Failure behaviour: [Preservation, visible failure, owner, retry, duplicate prevention]
Test access and interface investigation: [Who / when / unverified assumptions]
Uploads, retention and privacy review: [Need and responsible specialist; no real customer data]

7. EXISTING URLS AND VISIBILITY
Available search/visit data and external links: [Source and period]
Important pages for search AND the sales process: [List / reason]
Owner of URL decisions and mapping: [Role]
Implementation and checks: [Redirects, status codes, metadata, internal links, languages, sitemap]
Post-launch monitoring: [Owner / period / response to problems]

8. DESIGN AND MEDIA
Existing guidance: [Design guide, logo, fonts, image rights]
New design work: [Templates, modules, states]
Reference websites: [URL and precise reason for including it]
Expected revision rounds and approval: [Count / decision owner]

9. USABILITY AND REQUIREMENTS
Devices / browsers / relevant usage conditions: [Matrix]
Accessibility: [Agreed standard, scope and assessment method]
Owner of applicable legal requirements: [Specialist / open review]
Measurable performance requirements on representative pages: [Conditions / checks]
Tracking and consent: [Purpose, necessary systems, specialist review]

10. BUDGET AND TIMING
Budget range: [Amount / currency / including or excluding VAT]
Additional costs to allow for: [Licences, hosting, translation, media, internal work, support]
Target date and reason: [Date / external dependency / flexible or fixed]
Decisions and deliveries needed: [Task / role / date]
What can be omitted or delivered later if constraints conflict? [Priority]

11. ACCEPTANCE
For each test: [Task / expected result / test data / environment / version / reviewer]
Include: main mobile journeys, editing and languages, durable enquiry acceptance
and destination receipt, integration failure, old URLs, keyboard/error behaviour,
account ownership and handover.
Which defects prevent launch? [Criteria]
Who decides on outstanding issues? [Role / documented approval process]

12. OPERATION AND HANDOVER
Owner / billing owner / administrator per account: [Domain, hosting, CMS, repository, CRM, analytics]
Recurring costs and scope: [Item / period / limit / owner]
Training, documentation, content export and recovery: [Deliverable and verification]
Launch assistance: [Duration / availability / included tasks]
Defect correction and later development: [Separate arrangements]
Support and escalation: [Owner, response arrangement; no unconfirmed 24/7 commitment]

QUESTIONS FOR EACH SUPPLIER — USE THE SAME FORMAT
Included: [Quantity, result, revision rounds]
Excluded: [Task, alternative owner, internal effort]
Unresolved: [Question, information owner, date]
Price consequence: [Fixed-price addition / bounded investigation / later decision]
Do not enter unknown costs as zero.

Guide with a fictional worked example and proposal comparison:
https://www.h-studio-berlin.de/en/blog/b2b-website-relaunch-brief