How to Write a Marketing Brief That Gets Better Creative Work
A marketing brief needs to explain the business problem, the customers a campaign must reach and the information those customers need before buying. For SaaS and fintech companies, product capabilities, implementation requirements and purchasing concerns all belong in the assignment.
A global study by the BetterBriefs Project found a striking disagreement between marketers and the agencies they employ. While 80% of marketers believed they wrote good creative briefs, only 10% of agency professionals agreed. The research, published in 2021 and involving more than 1’700 respondents across over 70 countries, also found that 60% of marketers used the creative process to clarify their strategy.
The disagreement helps explain why agencies sometimes spend the early stages of a project establishing what their clients want to achieve. Management has approved a campaign without settling the intended audience, the commercial objective or the message it wants customers to understand.
A written brief provides little direction when those decisions remain open. Technology businesses face an additional difficulty. Their marketing departments tend to concentrate on product capabilities, while prospective customers want to establish whether the software solves their problem, how difficult it is to adopt and what they will pay.
Decide what the campaign must achieve
Before commissioning an agency, management needs to identify the business problem behind the assignment. A fintech company entering the Swiss wealth-management market might want more demonstrations of its portfolio-reporting software. That objective needs further definition. Independent asset managers consolidating data from several custodian banks have different requirements from private banks operating established internal systems. A campaign aimed at the first group might concentrate on data collection, reconciliation and consolidated reporting. The second may require detailed information about integration with existing infrastructure, security arrangements and implementation.
The brief also needs to establish the intended customer action. Generating product-demonstration requests calls for a different approach from introducing an unfamiliar provider to financial institutions that are not yet evaluating new software.
Management should identify one primary objective and agree on how it will be measured. Secondary ambitions belong in the document, with their relative importance made clear.
The agency then has a defined assignment, including the commercial priorities against which its proposals will be assessed.
Understand how customers evaluate the product
Software purchasing research provides a useful indication of the information marketing departments need to consider. Arcade’s 2026 survey of 600 B2B software buyers found that 47% regarded irrelevant or excessive AI language as a reason to disengage from marketing content. Vague promises about efficiency and cost savings also attracted criticism.
A provider promoting an AI-powered reporting platform needs to explain what the software does. Which records does it process? Which tasks remain with employees? How does the company handle customer data?
The same scrutiny applies to familiar technology claims. Seamless integration tells a bank’s IT department little about the systems supported or the work required to connect them. Enterprise-grade security needs documentation about relevant controls and independent assessments. Scalable architecture requires evidence appropriate to the volumes the customer expects to process.
A claim about reducing costs deserves similar care. The company needs to identify the work being reduced, the resources involved and the basis for any estimate. Technical language has its place. Engineers evaluating transaction-processing infrastructure expect accurate information about APIs, throughput, latency and system requirements. A procurement manager or finance director examining the same supplier needs a different set of details. A strong brief identifies these audiences and the information each requires. The agency then decides how to communicate it.
Map the people involved in purchasing
Enterprise software purchases involve several departments, each examining the supplier from a different perspective. G2’s 2026 Buyer Behavior Report found that 40% of surveyed software buyers identified evaluation as the longest stage of purchasing. Security reviews, budget approval and implementation planning were prominent causes of delay after suppliers had been selected. The research also found that 49% of respondents had experienced a chief financial officer reversing a purchase that the buying team had already approved during the preceding year. Marketing material designed exclusively for the product’s daily users leaves other decision-makers with unanswered questions.
A portfolio-reporting platform may appeal to an operations team because it reduces manual work. IT examines data connections and security. Procurement wants clear contractual responsibilities, while finance evaluates the full cost of adoption.
The brief should establish who initiates the purchase, who influences it and who can prevent the contract from proceeding. Supporting material then becomes part of campaign planning. Technical documentation, implementation information, product demonstrations and explanations of commercial terms help prospective customers build their internal purchasing case. Some documentation will be suitable for public marketing. Sensitive information may belong in a controlled sales or procurement process. The agency needs to understand that distinction.
Explain the product as customers use it
Product features make more sense when the agency understands the work customers perform. A reporting-software provider should describe how investment records reach its customers, which processes require manual reconciliation and where delays arise. The company can then explain precisely what its platform changes.
Information about implementation deserves equal attention. Buyers need to know which systems the product supports, what data needs migrating, how long deployment normally takes and which tasks remain with their own employees.
Subscription fees represent only part of the expenditure. Integration, training, support, internal staffing and migration all contribute to the cost of adopting enterprise software. Usage-based AI products introduce further questions about variable charges and spending controls.
The brief should provide accurate commercial information before the agency develops claims about affordability or efficiency. Financial institutions also have regulatory and contractual responsibilities when selecting technology suppliers. Swiss banks assess relevant outsourcing and operational-risk requirements under FINMA’s framework, while EU financial institutions must meet applicable obligations under the Digital Operational Resilience Act.
The precise requirements depend on the service and the institution. Marketing departments need the relevant information from their legal, compliance and technical colleagues, with clear boundaries around what the campaign is authorised to claim.
Include the reasons customers reject the product
Sales teams possess information that rarely appears in product descriptions. A financial software provider might attribute lost contracts to price, even though prospective customers expressed greater concern about moving historical data or obtaining support during the reporting period. That distinction changes the campaign. A cheaper subscription will not resolve uncertainty about implementation.
Briefs should draw on customer interviews, procurement questions, sales objections and previous proposals. Where available, lost-deal research provides evidence about competing suppliers and the factors that influenced purchasing decisions.
Companies also need to acknowledge product limitations. If a connection to a major banking system remains under development, the agency must know before advertising the platform’s integration capabilities.
Management opinions and verified customer findings should be identified separately. The agency is responsible for developing the creative approach, but it cannot substantiate claims without evidence from the business.
Agree on the assignment before production
A briefing meeting gives the agency an opportunity to question the objectives, review the customer evidence and identify gaps in the proposed campaign. Product specialists and sales representatives should participate when their knowledge is needed. Their involvement at the outset reduces the risk of technical corrections and commercial disagreements arriving after creative concepts have been approved. The BetterBriefs study found that 69% of marketers and 73% of agency professionals believed rebriefing happened too frequently.
A request to revise an advertisement against the original objective belongs within the agreed review process. Changing the campaign from lead generation to corporate repositioning alters the assignment and requires a new discussion about scope, cost and timetable.
The brief should name the final decision-maker, identify who approves technical and regulatory claims, and establish how the agency receives consolidated feedback.
Before production, a small group of prospective customers or relevant specialists can review the proposed message. Ask them to explain what the company sells, which problem the product addresses and what else they would need to know before considering a purchase.
Their responses help identify unclear language and missing information. A handful of interviews provides qualitative feedback, without establishing how the wider market will respond.
Exporis Guide: Preparing a Marketing Brief for SaaS and Fintech
Business objective: Define the commercial problem, the primary purpose of the campaign and the result management wants to achieve.
Target customers: Identify the industries, organisation types and customer groups the campaign needs to reach.
Purchasing decision: Establish who uses the product, who recommends it, who approves the contract and which departments examine supplier risk.
Existing workflow: Explain how customers perform the relevant work today, including the problems the product is intended to address.
Product information: Supply current capabilities, supported integrations, implementation requirements and known limitations.
Commercial terms: Include the pricing structure and material costs associated with deployment, usage, support and training.
Customer evidence: Provide research, sales objections, procurement questions, customer references and reasons for lost contracts.
Marketing claims: Identify the evidence supporting statements about performance, security, savings and implementation.
Competitive position: Explain where the product differs from alternatives, using accurate information that the agency can verify.
Creative assignment: Specify the message, intended customer action, required formats, channels, languages and budget.
Approval process: Name the people responsible for creative decisions, technical verification, compliance and changes to the original assignment.
Final check: Give the brief to someone unfamiliar with the project. If they cannot identify the audience, commercial problem, proposition and supporting evidence, the assignment needs further work.


