How to write a brief for a digital partner

A digital brief shapes the engagement before a partner asks a question or proposes an approach. If it describes a preferred solution while leaving the commercial problem vague, every response will be built on an untested prescription.

The strongest briefs create enough shared context for a partner to decide whether it can help, challenge assumptions and offer comparable options. They do not need invented success statistics or a large procurement document. They need a clear problem, evidence, outcomes, constraints and an open account of the decision.

Give useful business context

Explain the moment the organisation is in. Growth through acquisition, a changing service model, a platform approaching end of support or repeated client friction may all affect the work. Include only history that changes the decision.

Identify the sponsor, affected teams and people who will use or operate the result. State whether the organisation has attempted related work and what was learned. A partner needs to understand relevant organisational conditions as well as the visible digital asset.

Avoid marketing language that conceals trade-offs. A candid description of capacity, governance and readiness helps serious suppliers plan a credible response.

Describe the problem with evidence

“We need a new website” is a proposed answer. A problem statement explains what is happening, to whom, with what consequence and how the organisation knows.

Evidence might include enquiry data, user research, support themes, operational time, accessibility findings, incidents, supplier notices, technical assessment or client feedback. Give definitions and known limits. A conversion measure with incomplete tracking should be labelled as such.

Separate observation from hypothesis. For example: qualified enquiries have declined; analytics suggest abandonment on service pages; research is required to determine whether comprehension, relevance, traffic quality or the enquiry process is responsible.

This gives a partner room to diagnose without pretending the organisation knows nothing.

State outcomes and guardrails

Describe the changes the investment should create. Outcomes may concern commercial demand, client task completion, colleague capacity, service quality, risk, cost or organisational capability.

For each important outcome, include the current baseline if known, a desired direction or justified target, the owner and the evidence that would support a decision. Avoid copying a percentage from another organisation.

Add guardrails. Faster publishing should not weaken review or accessibility. More enquiries should not mean lower relevance. Automation should not increase unobserved risk or transfer unreasonable work to another team.

If success cannot yet be quantified, say what discovery must establish. Uncertainty is a legitimate part of the brief.

Make constraints and obligations visible

Partners need to know the conditions within which recommendations must work. Cover relevant:

• budget and internal capacity;
• desired timing and immovable events;
• current technology, data and integrations;
• security, privacy, accessibility and records duties;
• procurement and contractual requirements;
• brand, content and service dependencies;
• governance and approval routes;
• suppliers or assets that must be retained;
• ownership and operating expectations after launch.

Ask appropriate specialists to confirm legal, regulatory and technical obligations. Do not turn a preference into a mandatory constraint merely because it appeared in an old policy.

Distinguish a deadline from an aspiration. If a date is genuinely fixed, explain the consequence and invite options around scope or phasing.

Share a budget range and its basis

Withholding budget can produce incomparable proposals. Suppliers guess the appropriate level of ambition, sometimes in opposite directions. A range lets them explain what can be achieved, which assumptions matter and where a phased approach may be necessary.

State whether the range includes tax, licences, research, content, data work, migration, internal effort, contingency and ongoing operation. Explain the approval status and whether a stronger evidence-based case could change it.

Budget transparency does not remove commercial scrutiny. Ask for costs, rates, assumptions, exclusions and options. Compare whole-life cost and value rather than treating the lowest initial figure as inherently safer.

A material outlier deserves investigation. It may reflect innovation or a different scope, and may also signal misunderstanding. Ask the supplier to reconcile the difference rather than applying a universal rule that the cheapest or fastest response must be wrong.

Explain how responses will be assessed

Set evaluation criteria and relative importance before proposals arrive. Consider:

• understanding and challenge of the problem;
• relevant capability and the assigned team;
• strength and proportionality of the proposed approach;
• evidence, assumptions and risk treatment;
• accessibility, security and quality;
• collaboration, knowledge transfer and operation;
• commercial clarity and total cost;
• conflicts, dependencies and supplier viability.

Tell partners who will decide and how clarification, presentation and negotiation will work. If price has a mandated weighting, disclose it. Hidden criteria reward suppliers for guessing.

Use a fair process. Give bidders equivalent material information and a route to ask questions. Protect confidential information and avoid requesting substantial unpaid speculative work that the organisation has no right to use.

Evaluate behaviour as well as prose

A polished proposal is evidence of proposal skill. Look at the working relationship around it.

Useful questions include:

• What did the partner seek to understand before recommending?
• Which assumptions did it challenge, and on what evidence?
• Who will actually deliver and how available are they?
• How will quality and progress be demonstrated?
• What happens when evidence changes scope?
• How are bad news and disagreement handled?
• What will the client own and be able to operate?
• How does transition work if the relationship ends?

Meet delivery leaders, inspect representative working artefacts and speak to references about a difficult project. Create a genuine technical or strategic question in the evaluation and observe whether the partner reasons through it rather than agreeing automatically.

Communication during procurement is useful behavioural evidence, although it is only one sample. Record commitments made in pitch conversations so they survive into contract and delivery.

Avoid three common brief failures

A feature list without context asks suppliers to price somebody else’s diagnosis. Include desired capabilities where evidence supports them, while explaining the need and allowing alternatives.

An exhaustive request for proposal can be necessary in regulated or public procurement. Length itself is not the problem. Remove duplicated questions, irrelevant boilerplate and formatting demands that do not improve the decision.

A fixed solution specification may be appropriate when architecture and requirements have been properly established. If significant uncertainty remains, state which elements are mandatory and invite challenge to the rest. Do not pay for expertise while preventing it from affecting the plan.

Keep the brief useful after appointment

The selected proposal and brief should feed the engagement charter, discovery plan and business case. Update assumptions openly as evidence develops. Preserve the original problem and desired outcomes so delivery does not become a list of features detached from purpose.

A good brief reduces avoidable ambiguity; it cannot guarantee a good engagement. Due diligence, contracting, governance and evidence throughout delivery still matter.

The downloadable digital-brief template covers business context, problem, outcomes, constraints, evaluation, timing and budget in a concise format. Adapt its depth to the risk and procurement route. If you want to test a draft before going to market, book a pre-brief consultation. The conversation can examine what belongs, what remains uncertain and whether likely scope and budget are aligned.

The brief is the first working artefact in the relationship. Make it useful enough to guide a decision, and open enough for a capable partner to improve the question.