How to choose the next marketing project for your business
Choose the next marketing project by identifying where the customer journey is breaking down. A business with few relevant visitors needs a different response from one receiving enquiries that nobody follows up. Check the offer, available evidence and operational capacity before choosing a channel. Then define a bounded project, assign ownership and agree what will be measured. The right priority is the most useful next constraint to address, not necessarily the newest tool or loudest request.
Locate the gap before naming a channel
Start by separating discovery, understanding, action and follow-up. Discovery concerns whether relevant people encounter the business. Understanding concerns whether they can see the offer and why it matters. Action concerns whether they can enquire, book or buy easily. Follow-up concerns what happens after that action. These stages are connected, but a weakness in one does not automatically require the same solution as a weakness in another.
Use recent customer journeys to make the discussion concrete. Ask how the person first found the business, what information they needed, where they hesitated and how the enquiry was handled. Include lost opportunities where the reason is known. Avoid treating every unanswered question as a traffic problem. Sometimes customers arrived but could not find a price explanation or a suitable contact route.
Write the current problem in one sentence without naming a platform. A hypothetical supplier might say that quote requests arrive without the product specifications needed to respond. That points towards better product information and enquiry handling. It does not yet justify a new advertising campaign. Keeping the problem separate from a preferred channel gives the team room to choose a more appropriate first project.
Check the offer and the next step
Review the offer as a new customer would see it. Can they understand who it is for, what is included and what happens next? If the business uses broad terms such as end-to-end solutions, ask whether the page explains the actual deliverables. Clear service information can reduce confusion before any additional marketing activity is added.
Check the next action on a phone. Call the number, open the enquiry link and read the destination message. Review form fields and the confirmation shown after submission. If customers are expected to book, verify that the booking process matches the stated availability and responsibilities. A campaign can increase the number of people encountering a broken process, so basic usability deserves attention first.
Also check whether the business can fulfil the promise. An offer with unclear delivery timing or an unmonitored inbox can create disappointment even when the marketing is persuasive. Identify the operational owner and agree what response the customer should receive. If the offer itself is changing, document that decision before briefing creative work. Otherwise, the team may spend time producing material for a promise that is still unsettled.
Use the evidence you have and identify what is missing
Bring together website behaviour, enquiry records, sales outcomes and customer questions. Each source provides a different view. Website analytics can show recorded actions on the site. A sales record can show whether an enquiry became a suitable opportunity. Customer conversations can explain why someone hesitated. None of these alone describes the full journey.
Check definitions before comparing numbers. A WhatsApp click is not the same as a conversation, and a conversation is not the same as a qualified enquiry. Google Analytics describes key events as important business actions, but the event you select still needs a clear operational meaning. Record which action is measured and what it does not prove.
List the important unknowns. You may not know which campaign led to a phone enquiry or why a customer chose another supplier. Do not fill those gaps with confident assumptions. A small tracking or enquiry-classification project can sometimes be a useful first step because it improves the next decision. The aim is enough evidence to choose responsibly, not a perfect dashboard that delays every practical improvement.
Compare projects using a simple decision table
Create a shortlist of concrete projects rather than broad aspirations. Better SEO is too vague to compare with a new product launch page. A clearer project might be improving five service pages, adding a quote brief, setting up a reliable welcome message or organising lead follow-up. Each should have a defined outcome and a rough scope.
For each option, record the customer problem addressed, supporting evidence, dependencies, effort, cost category and internal owner. Consider likely usefulness without pretending to know a precise return. A low-cost task can still be a poor priority if it addresses a minor issue. A larger task may be justified when it removes a clear obstacle affecting many relevant customers.
Use a rating system only as a discussion aid. A table of numbers does not make weak assumptions reliable. If one project receives a high score because someone guessed a large revenue increase, expose that assumption. Compare what can actually be observed. The best shortlist usually includes a mixture of immediate corrections and projects that require preparation, with a clear explanation of why one should happen first.
Respect dependencies and internal capacity
Some work must happen before other work can succeed. A product catalogue may need accurate data before an online store is built. A campaign may need a useful landing page before traffic is purchased. A CRM may need agreed lead stages before automation is configured. Identify these dependencies so the business does not commission several projects that block one another.
Check the team's capacity to supply inputs and review work. A project requiring product photographs, service details and multiple approvals can stall even when the supplier is ready. Assign internal owners and agree review windows. The quoted delivery period often depends on those inputs, so capacity planning is part of marketing planning rather than a separate administrative concern.
Choose a scope that can be completed and used. A small improvement that reaches customers is more useful than a large unfinished system. This does not mean always choosing the easiest task. It means matching the project's ambition with the available resources and dependencies. Our strategy and automation support can be scoped around that sequence, connecting the business objective with the practical work required to deliver it.
Turn the priority into a clear brief
Write the brief around the problem, audience and intended action. Include the current situation, relevant evidence and what the first project should change. State the deliverables separately from the outcome. A landing page is a deliverable; helping relevant visitors understand a service and request a quote is the purpose. Both are needed to review the work properly.
Define what is included and what is separate. If a project covers website copy and layout, clarify whether photography, development, tracking or ongoing campaigns are part of the scope. If it covers CRM setup, specify which enquiry sources and stages are included. Clear boundaries make proposals more comparable and reduce disagreements after work starts.
Record approvals, inputs, responsibilities and a sensible review point. Identify who can make decisions when feedback conflicts. Keep the brief readable enough that it remains useful during delivery. If the selected project is a website, the website brief checklist provides a more detailed planning structure. A good brief does not need to predict every detail, but it should explain the decisions already made and the questions still to resolve.
Agree measures that match the project
Choose measures that reflect the project's role in the journey. For a service page update, relevant enquiries and the quality of the information received may matter more than raw page views. For a follow-up project, response time, unresolved leads and recorded outcomes may be more useful. For a catalogue cleanup, accuracy and maintainability may be the immediate measures.
Set a starting point where reliable data is available. Keep definitions stable during the review period. If the team changes what counts as a qualified enquiry halfway through, document it rather than comparing the totals as if nothing changed. Include operational measures and customer feedback where the sample is too small for strong numerical conclusions.
Do not demand a single return figure from a project that the available data cannot isolate. Several changes may happen at once, and sales cycles may be longer than the initial review period. State what the evidence suggests and what remains uncertain. The review should support the next decision, not force a confident success story. This approach makes it easier to learn from both useful outcomes and projects that need adjustment.
Review the first project and choose the next dependency
At the review point, return to the original problem. Ask what changed, whether customers can complete the intended action and what operational work remains. Separate delivery completion from business impact. A project can be correctly delivered while revealing another constraint, such as slow follow-up or unclear pricing. That information should inform the next priority.
Keep a short decision record with the evidence, conclusion and next action. Avoid restarting the whole strategy because one metric moved unexpectedly. Check for changes in traffic quality, seasonality, stock, offer or staffing that could affect the result. When the data is limited, acknowledge that limit and choose a proportionate next test rather than making a broad claim.
Maintain a connected backlog. The next project should build on the foundation already created, whether that means improving content, testing a campaign or organising leads in a small business CRM. A sequence of clear projects is easier to manage than a collection of disconnected initiatives. The business gains a more useful system when each investment addresses an observed constraint and leaves the team better prepared for the next decision.
Common questions
Should I start with social media, SEO or ads?
Start with the customer problem and the offer. Different channels serve different discovery and consideration needs. Check whether the website and follow-up process can handle the next action before choosing where to create more attention.
What if I have very little data?
Use actual customer questions, recent enquiries and a simple journey review. Record the unknowns and consider a small measurement improvement where it will change decisions. Limited data is a reason for careful assumptions, not for inventing certainty.
How many marketing projects should I run at once?
Choose a number the team can supply, approve and maintain. Projects with shared dependencies should be sequenced. A smaller set of completed, connected improvements is often easier to assess than many simultaneous changes.
