The Question That Decides Whether Your Agentic Strategy Fails

If you're getting ready to build with agents or if you're struggling to see the results you keep hearing about, let me ask you the one question that will determine whether your agentic engineering strategy works:

Are you starting with the process, or with the model?

I've watched both paths play out. I spent more than a decade consulting on exactly this, inside startups, mid-market companies, and global enterprises, brought in to fix processes that were producing bad outcomes. The pattern held across every engagement: the fix lived in one of a handful of core phases, and it had nothing to do with the platform they'd paid for or the framework they'd just rolled out. Today my teams ship applications and features through an AI-PDLC every day, and I can tell you the choice you make in your first week will shape everything that follows.

The Process Pieces Have Never Changed

Here's what's true about application development: Frameworks have cycled for decades. Waterfall gave way to Agile, Agile spawned a dozen flavors, while the durable phases underneath stayed put:

1. ENVISION the need.
2. GATHER the requirements that solve the correct problem.
3. DESIGN the concept and design the architecture.
4. BUILD the product.
5. TEST and verify the product.
6. RELEASE the product.
7. SUPPORT the users.

Frameworks decide how you slice those phases and how fast you loop them. The phases themselves are the work, and they form a chain. Your outcome is governed by the weakest link in it.

Some teams did improve when they moved to Agile, because long feedback loops were the wrong fit for products with uncertain requirements. The framework change fixed a fit problem, and that's real. What it left untouched was practice. Teams that ran thin requirements and rushed design under Waterfall carried those habits into their sprints, and the work broke down for the same reasons it broke down before.

Many of those teams are looking at agentic development now and wondering why they're still struggling, and the truth is agents amplify whatever process you hand them — good and bad. Give them a strong specification and they produce work you can ship. Give them a vague ticket and they produce volume you have to untangle.

And agents change the economics of the chain. Under human teams, build carried most of the cost, which is why requirements and testing were the first things cut under a deadline. When build collapses toward zero, the cost moves to specification and verification, precisely the links weak teams were already skipping.

Start With the Process

So the work starts before an agent is ever engaged. Take the chain and audit it honestly, phase by phase. Strengthen the chain, and you strengthen your agentic output.

Tokens accelerate a process, but they also inherit its gaps. A team that struggles to elicit real user needs will generate elegant solutions to imagined problems. A team that skips technical design will accumulate architecture nobody can defend and potentially a nightmare to support. A team without a verification strategy will ship faster and learn about the consequences from its users.

The tools and frameworks will keep changing, but the key phases of any application development process haven't changed in decades. Your results will keep tracking the weakest links in your chain. So find them.

Start with the process.

Lunari builds agentic enterprise platforms and advises leadership teams deploying them. If this maps to a problem you are working on, we should talk.