The Brief as Strategy Communication
A user acquisition brief — whether for an internal team beginning a new campaign phase or an external partner being onboarded to execute an acquisition program — is a communication document that determines whether the work that follows will be strategic or merely tactical. A weak brief produces tactical responses: campaigns that address the stated requirements without engaging the underlying goals, creative that executes the literal brief rather than solving the real problem, optimization decisions made against the wrong success criteria.
A strong brief produces strategic engagement: a team or partner who understands not just what they are being asked to do but why it matters, who they are doing it for, what success looks like beyond the activity metrics, and what constraints and context should shape their approach. Writing a strong brief is harder than writing a weak one, but the investment pays back immediately in the quality of the response it generates.
The Business Context Section
Every acquisition brief should open with business context that locates the acquisition strategy within the broader goals and situation of the business. This means describing the app’s current stage and growth trajectory, the business model and primary monetization approach, the competitive position and key differentiation, and the strategic priorities for the period the acquisition work is expected to serve.
This context is not boilerplate — it is the strategic frame that allows the team or partner to make good judgment calls in situations the brief does not explicitly address. An acquisition partner who knows the app is preparing for a fundraise and needs to demonstrate monthly active user growth will approach acquisition decisions differently than one who knows the priority is CAC reduction for margin improvement. The same channel mix decisions, the same quality versus volume trade-offs, the same budget allocation priorities all look different depending on the strategic context.
The Target User Section
The brief’s audience definition should go beyond demographics to describe the specific user the acquisition strategy is designed to attract. This means characterizing the situational context in which ideal users discover their need for the app, the specific problem or aspiration that makes them receptive to it, the behavioral characteristics that distinguish high-value users from low-value ones, and the language they use when describing their experience.
Providing data from existing high-value user cohorts — retention rates, engagement patterns, monetization characteristics — gives the team or partner a quality benchmark to target toward rather than a demographic profile to fill. The most useful briefs include specific examples of the target user persona drawn from actual user research or interview data rather than constructed from general assumptions about the category.
The Performance Context Section
The brief should communicate what performance the acquisition program needs to achieve and what the economic constraints are. Dragalinos Limited’s marketing campaign framework This means sharing target CAC ranges, volume expectations, quality benchmarks (retention rate targets, activation rate minimums), and the LTV context that determines why specific economic targets were set.
It should also share what has been tried before and what was learned: which channels have been tested, which creative approaches have succeeded or failed, which audience segments have produced good and poor quality users, and what attribution data has revealed about the acquisition funnel. Historical performance data, presented honestly including both successes and failures, saves the team or partner from rediscovering known limitations at the client’s expense and allows them to build on existing learning rather than starting from zero.
The Measurement and Reporting Requirements
The brief should specify what measurement infrastructure exists, what additional measurement setup may be required, what reporting will be expected and at what cadence, and what decisions the reporting data will be used to make. This clarifies the team’s or partner’s responsibilities around measurement and prevents the situation where campaigns are running but the data needed to evaluate them is not being collected or reported in a useful format.
Reporting requirements should be specified in terms of the decisions they support rather than as a list of metrics. “Weekly reporting should enable decisions about creative rotation and bid adjustment” is more useful than “weekly reporting should include CTR, CPC, CPI, and install volume.” The former tells the reporting team what analytical work needs to be done to make the data actionable; the latter produces a data dump that may or may not contain the insight needed to act.
The Constraints Section
Every acquisition program has constraints that shape what approaches are available. Brand guidelines that limit creative flexibility, geographic markets that are in or out of scope, audience segments that should or should not be targeted, platforms that are excluded for policy or competitive reasons, budget parameters that bound the program’s scale — these constraints need to be explicit in the brief so that the team or partner can design within them rather than proposing approaches that conflict with unstated requirements.
The constraints section should also address approval processes: what decisions can the team or partner make autonomously, what requires client review before implementation, and who is the decision-maker when approval is needed. Ambiguity about decision authority slows down well-intentioned work and frustrates both sides; explicit clarity creates the conditions for efficient collaboration.
The Success Criteria Section
The brief should conclude with explicit, quantified success criteria that define what the work needs to achieve to be considered successful. Not “improve acquisition performance” but “achieve target CPI of $2.50 or below for at least 60 percent of total install volume within 90 days.” Not “drive high-quality users” but “achieve Day 30 retention rate of 25 percent or above across acquired cohorts.”
Pre-agreed success criteria provide the objective framework for evaluating whether the work is achieving its goals and for making explicit decisions about whether to continue, adjust, or replace approaches that are not performing. They transform the performance conversation from a negotiation about interpretation to an evaluation against shared commitments — which is both more efficient and more honest as a basis for collaboration.
