← Back to Moxiq
The Moxiq Perspective

How we think
about the work.

Not frameworks. Not thought leadership for its own sake. Observations from real engagements — what we found, why it mattered, and what most people missed the first time around.

01
On Research

The first answer is
almost never the right one.

Every engagement I've run has had a moment where the obvious diagnosis turned out to be the surface of a deeper problem. The client who thinks their ads aren't working. The agency that thinks they need better creative. The contractor who thinks they lost the bid on price. In almost every case — the real problem was something nobody had looked at yet.

This is the thing about stopping at one run: you get the answer that was easiest to find. You don't get the answer that's actually true. A restaurant I worked with had been told by two different agencies that the problem was their social media presence. More posts. Better photos. Stronger hashtags. So they paid for more posts, took better photos, used stronger hashtags. Nothing changed.

When I looked at it properly — not just the Instagram account, but the website, the review platforms, the search behavior, the competitive landscape — the real problem was that the brand name was being cannibalized by a sister location in another city. Anyone searching the restaurant's name was finding the other location first. It had nine years of SEO equity, 1,200+ reviews, and thousands of followers. The new location was invisible to anyone who didn't already know to search by city name. No amount of Instagram content was going to fix that.

"The prior agency had been optimizing the wrong thing for months. Not because they were incompetent — because they stopped at the first plausible answer."

The discipline I've built into every engagement is to keep asking after the first answer appears. What else is true? What haven't we looked at? What would break this diagnosis if it were wrong? The research doesn't stop when you find something — it stops when you've found everything worth finding. That's a different stopping point.

It's slower. It's more uncomfortable. It occasionally means telling a client that the thing they've been investing in isn't the problem. But the alternative is delivering a polished answer to the wrong question — which is the most expensive outcome of all.

02
On Deliverables

A report is not
a deliverable.

The consulting industry has a document problem. Enormous amounts of effort go into producing things that look impressive, get presented on a call, get filed in a shared drive, and never get touched again. I've seen it happen to work I respected. I've watched clients nod at findings and then do nothing — not because they didn't care, but because the gap between "insight" and "action" was never bridged.

The gap has a name: it's called asking someone to figure out what to do next themselves. A report hands you analysis. A playbook hands you the next move. Those are not the same thing.

What a report gives you
Here is what we found. Here are our recommendations. Here is a framework you could consider applying. Good luck with implementation.
What a playbook gives you
Here is what we found. Here is the exact action for each finding. Here is who does it, in what order, by when, and what success looks like.

When I built the conference playbook for a destination marketing agency CEO, the difference wasn't the depth of research — it was that every section answered a question the team would have had to answer themselves on the ground. What format do we record in? What questions do we ask guests? Who films and who talks? What do we do with the footage at the end of each day? What happens the week after?

None of those questions are strategic. All of them will kill execution if they're not answered in advance. The value of a playbook isn't the intelligence in it — it's the operational gap it closes. It's the difference between arriving at a conference with a strategy and arriving with a plan.

"I don't consider a deliverable finished until I've asked: could someone open this Monday morning and know exactly what to do? If the answer is no — it's not done."

This is not a faster or easier way to work. It takes longer to get from insight to action than it does from insight to recommendation. But the thing clients are actually paying for isn't the insight. It's the change. And change requires a path, not a PDF.

03
On Discovery

I don't give you
homework. I do the work.

Standard consulting methodology assigns discovery work to the client. Log your tasks for 48 hours. Fill out this intake form. Complete this survey before our next call. The logic is reasonable: who knows the business better than the people running it? The problem is that this logic assumes the client has time, which is precisely what they don't have — which is usually why they hired you.

The first time I ran an AI Workflow Audit on a busy CEO, I handed him a task logging spreadsheet and asked him to track his time for two days. He agreed. He didn't do it. Not because he didn't want to — because by the time he remembered, the moment was gone. The next call arrived, the spreadsheet was empty, and we'd lost a week.

So I changed the methodology. Instead of asking clients to document their work, I started running the discovery myself — through 30-minute brain dump calls where I ask three high-yield questions and do all the logging. Through calendar audits. Through voice memo sessions that fit around their schedule. The output is identical. The burden is entirely different.

01
Brain dump callThree questions, 30 minutes, I transcribe and categorize everything. The client talks. I build the inventory.
02
Calendar auditI review two weeks of calendar entries and map recurring time costs without the client lifting a finger.
03
Voice memo sessionsClient records a 5-minute voice note at the end of the day for three days. I do everything else.

The insight this unlocked wasn't methodological — it was positional. If you want to work with executives, you cannot make them the analyst. They'll agree to things they won't do, not because they're unreliable, but because their calendar is already full and your homework competes with everything else on it.

The discovery approach became a service differentiator: I do the work with you, not at you. That line came directly from watching the empty spreadsheet and asking why. The answer was obvious once I asked the question. It always is — after you ask it.

04
On AI

AI visibility is the gap
your agency hasn't mentioned.

In every client audit I've run in the last year, there is one consistent finding: the business is invisible to AI-generated search results — and nobody working with them has flagged it. Not as a gap. Not as a risk. Not as a priority. It simply hasn't come up.

This isn't a criticism of agencies. AI search optimization is genuinely new, and most marketing professionals are still working from a mental model built around Google's traditional ranking algorithm. That model is becoming wrong fast. ChatGPT, Perplexity, and Google AI Overviews are now handling a meaningful share of discovery queries — especially for the kind of high-consideration decisions that produce valuable customers.

Here is what most businesses don't know: AI tools don't rank websites. They read them. If your site renders via JavaScript, if you have no schema markup, if your review volume is thin — the AI doesn't see you at all. It's not that you rank poorly. You simply don't exist in the answer.

"A restaurant I audited was getting strong Google reviews and had decent organic traffic. It was still nearly absent from every AI-generated dining recommendation for its category. The two things are not the same problem."

The fixes are not complicated. Crawlable website content. Restaurant or business schema markup in JSON-LD. Review velocity above a threshold that signals credibility to AI training data. NAP consistency across every platform. A press footprint in the right local publications. None of these require a significant budget. All of them require someone to actually check.

The opportunity isn't in being early to AI optimization — most businesses have already missed early. The opportunity is in being ahead of your immediate competitors, most of whom are in exactly the same position you are right now: invisible in the results their best customers see first, working with an agency that hasn't mentioned it.

05
On Competitive Intelligence

You should know more about
your competition than they know about you.

Most competitive analysis is superficial and late. It happens after a decision has already been made — after you've committed to pursuing an RFP, after you've decided to enter a market, after you've lost a bid and are trying to understand why. The research that changes outcomes happens before the decision, not after.

When I run a pursuit intelligence report on a competitive RFP, the first thing I look for is the incumbent. Not to attack them — to understand exactly where they're vulnerable. What do they do well that you'll need to match? What have they never done that the RFP is explicitly asking for? What has changed since they won the contract that might make the client ready for something different?

In one engagement, the incumbent had built and hosted the client's website. That's a switching cost — and a real one. But it's also a known, addressable objection. The proposal that wins is the one that names it directly rather than hoping the evaluation committee doesn't notice. Pretending an obstacle doesn't exist doesn't make it go away. Addressing it head-on is how you demonstrate that you've done the work.

01
Read the public recordBudget data, board minutes, prior contracts, annual reports — most government and institutional clients are legally required to publish information that most competing agencies never look at.
02
Map every incumbent vulnerabilityNot to attack — to anticipate. For every gap you find, there's a counter-strategy. For every advantage they have, there's a framing question.
03
Find the thing they structurally cannot doThe most durable differentiator is one your competitor can't build in 27 days. That's the one to lead with.

The RFP I analyzed had one explicit differentiator buried in the scope: the client had named AI-driven search optimization as a requirement. The incumbent showed no capability in this area anywhere in their public presence. That's not a feature to mention in a capabilities section — that's a standalone proposal section with a header. Because it's the thing they can't answer.

Competitive intelligence isn't about knowing more than your competitor in general. It's about knowing the specific thing that changes how you show up — and having the discipline to find it before you start writing.

Thinking like this is what we bring to every engagement.

If you want a research partner who keeps going until it's right — not until it's good enough — let's talk.

Start a Conversation