Strategy Matters More Than Code

AI has made it genuinely fast to build almost anything.

Features that used to take a developer a week can get prototyped in an afternoon. Scripts that required a specialist can be generated in minutes. The barrier to building has collapsed.

Which means the barrier is no longer implementation.

It's judgment.

Speed Without Direction Makes Things Worse Faster

I've watched this play out with merchants who use AI tools to move fast on their stores.

They build an automation. It works — until a product name changes and suddenly the automation is routing the wrong items. They add a custom script. It works — until they add a new sales channel and now it's breaking the checkout. They ship a feature quickly. It works — until they try to scale and realize the foundation doesn't support what they're trying to do.

None of these are AI problems. They're planning problems.

The speed AI offers is real. But speed amplifies the quality of the decisions underneath it. Good strategy plus fast execution is powerful. Unclear strategy plus fast execution just creates technical debt faster.

When a Merchant Has Clarity, Development Is Easy

This is something I've noticed across dozens of projects.

The work is rarely hard when the direction is clear.

Clear goals mean clear tradeoffs. Clear tradeoffs mean decisions happen fast. Decisions happening fast means the project moves.

The projects that stall — where scope keeps shifting, where "can we just add one more thing" becomes a running theme — almost never stall because of technical problems. They stall because the direction wasn't settled before the building started.

I've had clients come to me after difficult experiences with other developers. The complaint is usually about communication or quality. But when I dig in, the real issue was almost always alignment. Everyone was building fast toward different assumptions about what the store was supposed to become.

That's not a developer problem. It's a strategy problem that showed up in the code.

The Developer Who Just Does What You Ask

There's a version of this job that's purely executional.

You give me the spec. I build it. Pixel perfect, on time, no surprises.

That's valuable — if you already know exactly what you want. If you've already thought through how today's decision affects the next six months. If you've already mapped out how this feature fits into the way your store will operate a year from now.

Most merchants haven't done all of that. Not because they're not smart — because that thinking is hard, and it's not what they were hired to do.

What they need isn't someone to execute their guesses faster. It's someone who can help them think through the tradeoffs and land on decisions that hold up over time.

That's a different kind of work than pure execution. It costs more. It takes longer upfront. And it almost always saves significant time and money on the back end.

What Strategy Actually Looks Like in Practice

It's not a presentation or a document.

It's a set of questions asked before the work starts.

What problem are we actually solving right now? What does this feature unlock, and what does it foreclose? If this store doubles in volume next year, does this decision still make sense? Who is this change for — and is that who we're trying to serve?

Sometimes the answer to those questions is: yes, build it. Sometimes it's: not yet. Sometimes it's: this is the wrong solution to the right problem.

The answers aren't always complicated. But asking the questions before building saves the kind of rework that quietly doubles the cost of a project.

Code Can Be Rewritten. Architecture Decisions Stick.

A bad headline can be changed in a minute. A bad structural decision in how your store is set up can take weeks to unwind — if you can unwind it at all.

That asymmetry matters.

The stores I've seen scale cleanly weren't always the fastest to build. They were the ones where the early decisions were made with the future in mind.

Not a perfect plan. Not a locked-down spec. Just enough thinking upfront to avoid the kind of shortcuts that become load-bearing walls.

That's what strategy is.

Not a plan that predicts everything. A habit of asking the right questions before the building starts.

If you're starting a Shopify project and want to think through the strategy before touching the store, that's exactly what the first conversation is for.