You don’t need to know every platform to evaluate a marketing partner. However, you need explanations that link the activity to business objectives.
You can ask for those explanations without knowing the technical vocabulary. The conversation should help you decide what to continue, what to change and what else you need to learn.
“We optimized.” “We tested.” “We increased visibility.” These may describe real work. To be useful, they need a little more: what changed, which problem were we addressing, what did we observe and what will we do next?
These questions are natural. Their clarity helps both the client and the people working on the project.
A recommendation should be explainable
For a campaign, you should understand why that audience, message and channel are proposed. For a website, which problem the structure solves. For content, which reader’s question it answers.
A good explanation includes available information, assumptions and limitations. If the team cannot yet know which variant will work best, it must be able to propose a way to find out.
Confidence is not evidence. Sometimes the professional answer is: this is our hypothesis, this is why it is worth testing, and this is how we will interpret the result.
What you should see before production begins
The communication strategy explains the promise, arguments and evidence for the chosen audience. The promotion plan shows where we use them, with what objective, resources and evaluation criteria. Production turns these decisions into concrete materials.
Ask for a list connecting each asset with its purpose. A clean image for automated ad assembly, a demonstration video and a banner with integrated copy serve different roles. The agency should explain why each is proposed and how it is checked. That makes both the work and the effect of removing a deliverable visible.
Same data, two reports
The comparison is fictional. Imagine a campaign with 60 inquiries, 12 of them qualified and 30 still without a recorded status in the sales records.
A report must support a decision.
Fictional example: 60 inquiries, 12 qualified, and 30 with no recorded status.
Report A
- 60 inquiries
- Activities completed
- “We continue to optimize.”
Report B
- Known: 12 qualified inquiries
- Missing: status of 30 inquiries
- Decision: complete the missing data and review the campaign messages.
| What the client learns | Report A | Report B |
|---|---|---|
| Activity | 60 inquiries | 60 inquiries, with definition and period |
| Relevance | No explanation | 12 qualified according to agreed criteria |
| What is missing | Not specified | 30 without documented commercial results |
| Decision | Continue optimizing | Complete the status records and review messages attracting unsuitable inquiries |
Report B also makes the unknowns visible. We cannot treat all 30 unresolved inquiries as lost, or assume they will become sales. The next action has a reason and an owner.
What should a progress discussion contain?
We start with the objective and the relevant results. Then we discuss what has changed, what went differently from what we expected and what evidence we have. We end with decisions, priorities and dependencies.
An unsuccessful test can provide useful information if the question was clear and the conclusion is sound. Not every test has to be presented as a success. We need to know what we learned and whether it deserves further work.
The team should also flag its own mistakes: a wrong link, an incomplete implementation, an interpretation that needs revisiting. Correcting them and preventing a repeat are part of the collaboration.
Clarity starts before reporting
The proposal and working agreement should specify deliverables, stages, approvals, revisions and responsibilities. Clarify account access, delivered files, usage rights and what happens when the project ends.
The client has a part to play too: accurate offer information, timely feedback and relevant business data. If something the project depends on is delayed, explain the practical consequences and the available options.
Clearly shared responsibilities let both sides investigate a problem without a vague argument about blame.
What we apply to our work
At NOT MORE., we want every recommendation to be traceable from the problem to the decision. We explain what we propose, what we assume, what we will verify and what lies beyond the available information.
The criteria in this article can be used to evaluate us too. Professionalism shows in how we justify the work, welcome questions and correct what needs correcting.
Three questions for the next meeting
- What decision can we make from the results presented?
- What changed when a hypothesis was not supported?
- What do you need from us, and who owns the next step?
What do you need to understand from the collaboration?
Tell us what you are looking for and what remains unclear in the recommendations received. We can discuss how priorities, responsibilities and progress in a project like yours should be explained.
From understanding the need to taking responsibility for the work
An agency can contribute through research, strategy, creative work, technology and implementation. Its responsibility follows the work it takes on. At NOT MORE., we begin by understanding the objective, resources and what already exists. We then define the direction and do the work: produce, develop, configure, integrate and check the project’s components.
We can also work on business strategy, processes or internal checks when the solution depends on them. For example, we can design and implement CRM inquiry assignment, including checks that it works. The client’s team approves the process and names the people who continue the conversations. Our scope is visible before work begins.
| Stage | What we take responsibility for | What we clarify with your team |
|---|---|---|
| Understanding and direction | Proportionate analysis, options and a reasoned recommendation | Objective, information, resources and decision authority |
| Building and launching | The agreed creative work and implementation, with checks | Approvals, access, information and dependencies on other teams |
| After launch | Monitoring, optimization and reporting, where included | Measures, frequency, operating responsibilities and limits on changes |
A specific service can be enough to get started
A Growth Diagnostic clarifies where to focus the effort. A Focused Sprint organizes the work around one priority. A Growth Partnership supports delivery and evaluation over time. Individual services can be commissioned directly, and a diagnostic is optional when the need and conditions are clear enough. You do not need to go through all three formats.
A dependable partnership shows in an explained proposal, completed work and the way difficulties are handled. If a component is no longer justified, we discuss changing it. If we make an error, we flag it and correct it within our responsibility. Continuity has value when it helps the business move forward.
How much involvement the collaboration asks of you
It is reasonable to ask whether a project will add another coordination role to your day. We agree on who needs to be involved, what information is required and when approvals happen. Where possible, we group questions and feedback, and record decisions somewhere the teams can access. If a stage needs more participation, we explain it beforehand. You can then assess your team’s effort alongside the proposed fee and deliverables.
Choose the partner’s role around the contribution you need
You can bring in NOT MORE. for advice, strategy development, execution or coordination of the whole project. These can be commissioned separately. If your team or current agency already covers part of the work, we establish where we can contribute and how our deliverables connect with theirs.
For example, we could produce materials for a campaign managed by another agency or implement a technical component based on an existing strategy. Understanding requirements and checking dependencies are part of the assignment. They do not automatically mean rebuilding the strategy or taking over overall coordination. For each component, we agree on who proposes, executes, approves and monitors results.