Insights

Three Marketing Problems You Can Fix in Two Weeks

Three focused reviews can make the current objection pattern, blocked work, and accountable number visible with information the company already holds.

7 min readNorthstar Stack

Large infrastructure proposals often ask for a long build before anything useful becomes visible. A focused manual sprint is a faster way to test whether information flow is the constraint.

So here is the version that fits in two weeks, uses nothing you do not already own, and produces something you can read at the end of it. Every piece of it is manual on purpose.

Ten working days, and what each fix takes12345678910Objection listthe last thirty callsBlocked-on listone page, one hourThe number, visiblewire it to a pageWatch what changesthe part that decides
This is a focused manual sprint using existing records. The last row tests whether the new visibility changes an active decision or piece of work.

Days One to Three: The Objection List

Take a focused set of recent recorded sales calls. Use up to thirty when the volume allows, and choose a period recent enough to affect current work.

Listen or read through, and write down every reason a deal slowed or stopped. Not the CRM category, the actual sentence. Then count which ones recur.

By day three, produce a ranked list of the objections that recurred in the review, in the words buyers used and with each source attached. The value is a shared document tied to recent calls rather than separate memories of what buyers said.

Give it to the person responsible for the website and choose which repeated patterns deserve a message or page test.

Day Four: The Blocked-On List

One page. Everything marketing is currently waiting on from another team, who it is with, and how many days it has been sitting.

Illustrative blocked-on listWAITING ONTEAMAGEPricing page copy changeEngineering11 daysCase study approvalLegal6 daysProduct screenshots for launchDesign4 daysSegment definitions for the campaignSales ops2 days
Example values only. The age column turns a vague dependency into a visible fact that can be resolved or reprioritized.

The age column does the work. A request that has been open eleven days is a very different conversation from a request somebody vaguely remembers making, and the difference is entirely that one is written down where other people can see it.

Keep the first version intentionally simple and review it on a regular cadence. It is the fastest way on this list to turn a vague dependency into a visible operating fact.

Days Five to Seven: Make the Number Visible

Put the metric marketing is accountable for on a page anyone in the company can open, next to where it currently stands and what it needs to be.

Not a dashboard project. A page, updated from whatever system already holds the number.

What this changes is the volume of interruption. Repeated requests for a marketing update often come from people who cannot see the current state. Give them a current link and the answer no longer has to be reconstructed each time.

Week Two: Watch What Happens

The second week is not more building. It is paying attention, and it is the part that determines whether any of this was worth doing.

Questions marketing should be able to answer without looking anything upBEFOREAFTERWhat were the top three objections last month?Which competitor came up most often?Why did the last five accounts leave?What is marketing waiting on right now, and from whom?What number is marketing accountable for this quarter?
The manual sprint assembles these answers once from information the company already holds. A system is what keeps them current afterward.

Ask the five questions above of whoever runs marketing, without warning and without letting them look anything up. Record the baseline answers on day one. If the answers are now immediate and specific, the gap was real and you have measured the change.

Also watch the blocked-on list. If request ages begin falling after the list becomes visible, record that as evidence and check which dependencies changed without another escalation meeting.

What This Does Not Fix

Being honest about the ceiling matters more than the list, because the ceiling is the actual argument.

What a manual pass gets you, and where it stopsREACHESA list of what buyers actually object toVisible dependencies, with agesOne number everyone can seeEvidence that the gap was realDOES NOT REACHAnything that stays current on its ownPatterns across a whole quarterChurn reasons in the customer's wordsA week that survives you going on holiday
The right column is the argument for building something. The left column is how you find out whether it is worth building.

Everything above decays. The objection list begins aging as soon as new calls arrive and eventually becomes a historical document. The blocked-on page depends on a person remembering to update it, and that person will get busy. The number stays current only as long as somebody keeps wiring it.

Nothing here reads churn interviews, catches a pattern forming across a quarter, or survives the person who set it up going on holiday.

That is not a reason to skip it. It is the reason to do it first.

Why Manual First Is the Right Order

Two weeks of doing this by hand answers a question no vendor and no proposal can answer for you: whether information flow is actually your constraint.

If the objection list changes what marketing writes and the blocked-on page changes what gets unblocked, you have proof, and building something permanent is an easy decision made with evidence.

If nothing changes, the review has shown that information flow may not be the current limiting constraint. Learning that in two weeks is useful on its own.

Frequently asked questions

What marketing problems can actually be fixed in two weeks?

Three, and all of them manually. A ranked list of what buyers actually object to, assembled from recent call recordings. A published list of what marketing is waiting on and how long it has been waiting. And the metric marketing is accountable for, put on a page anyone can open.

How do you build an objection list from sales calls?

Take the last thirty recorded calls and write down every reason a deal slowed or stopped, using the sentence the buyer said rather than the CRM category. Then count which ones recur. Three days of focused review produces a ranked list tied directly to recent calls.

What is a blocked-on list and why does it work?

One page showing everything marketing is waiting on from another team, who holds it, and how many days it has been open. The age column does the work, because a request visibly open for eleven days is a different conversation than one somebody vaguely remembers making.

How long does a manual fix like this stay useful?

The objection list ages as new calls arrive and remains useful only while someone refreshes it. The blocked-on page lasts as long as someone remembers to update it. That decay is expected and is the point of doing it manually first.

Why do the manual version before building anything?

Because it answers whether information flow is actually your constraint, which no proposal can answer for you. If the lists change what gets written and what gets unblocked, you have evidence. If nothing changes, you learned it in two weeks rather than two quarters.

What does two weeks of manual work not reach?

Anything that stays current on its own, patterns forming across a quarter rather than a month, churn reasons in the customer's own words, and a process that survives the person who set it up taking time off.

How do you know whether it worked?

Ask whoever runs marketing five questions without warning: the top three objections last month, the most common competitor, why the last five accounts left, what marketing is waiting on and from whom, and the number they are accountable for. Immediate answers mean the gap was real and is now closed.

Work with Northstar Stack

Start with the Marketing Information Flow Diagnostic. Leave a work email and we will follow up with the right next step.