The 3 Questions I Ask Before Starting Any New Business Initiative

I have started a lot of things. Some of them turned into real businesses. Some of them burned time, money, and focus I could not get back.

After enough failed starts, I noticed a pattern. The initiatives that worked almost always passed a simple test I had been running in my head without naming it. The ones that failed almost always skipped it.

So I wrote it down. Three questions. I ask them before I commit to anything new, whether that is a new product, a new campaign, a new hire, or a new market. They are not magic. But they have saved me from a lot of expensive mistakes.

Why I Needed a Filter

I am a builder by nature. I see a problem and I want to solve it. That is mostly a strength. But it can become a liability when you are running multiple businesses at once and every new idea feels urgent.

At some point I was juggling lead generation for law firms, building out Cultivate Inbox as a cold email agency, managing a Wolf Pack of AI agents handling content and outreach, and trying to stay ahead on distribution across three separate sites. Every week something new would surface. A new channel. A new automation idea. A new market that looked promising.

Without a filter, I was saying yes to too many things. Each one started with momentum and then stalled because I did not have the bandwidth to see it through. The issue was not the ideas. The issue was that I was letting excitement make decisions that discipline should have been making.

Three questions fixed most of that.

Question 1: Does This Serve the Core?

The first question I ask is whether the new initiative actually serves what I am already building, or whether it is a distraction dressed up as an opportunity.

My core right now is two things: eNZeTi, the real-time intake coaching platform for law firms, and Cultivate Inbox, the cold email agency. Everything I do should either drive more revenue to one of those two, build the infrastructure that supports them, or sharpen my ability to run them better.

If a new initiative does not clearly plug into one of those, I make myself articulate exactly why I am considering it. Usually the honest answer is that it sounded interesting in the moment. That is not good enough.

The test I use: if I imagine I am already doing this new thing at scale, does it make my core businesses stronger or does it pull me away from them? If the answer is the latter, I stop there. I do not need to evaluate the rest.

Most ideas fail this question. That is the point. A filter that passes everything is not a filter.

Question 2: Can I Resource It Without Stealing From What Is Working?

If something passes the first question, I then ask whether I can actually resource it without cannibalizing what is already running.

Resources here means three things: time, attention, and money. All three are finite. All three are already allocated. If I take on something new, something currently running gets less of one or all of them.

I have a rule in my operation: revenue activities get resources first. Outreach, lead generation, deals, client retention. Everything else gets what is left. That rule exists because I have violated it before and watched things that were working slow down because I was off chasing something new.

The practical version of this question is: which existing bot, which existing campaign, which existing relationship takes the hit if I say yes to this? If I cannot name it, I probably have not thought it through. If I can name it and I am still willing to make that trade, then I can move to question three.

This question also forces me to think about whether the new initiative can be delegated. Part of the reason I built the Wolf Pack, my team of AI agents, was to give myself capacity I did not have before. Shakti handles content. Lobito runs lead scraping. Loki handles outreach drafts. If a new initiative fits inside what my existing team can absorb, the resource cost is much lower. If it requires me personally, the cost is much higher.

Question 3: What Does It Look Like If It Fails?

This is the one most people skip. They are focused on the upside and they assume the downside is just lost time. It is usually more than that.

When I ask what failure looks like, I am looking for three things. First, is the failure recoverable? If I spend two months building something and it does not work, can I absorb that? Or does it set back something critical?

Second, does failure have any residual value? The best kind of initiative is one where even a failed attempt teaches you something, builds an asset, or strengthens a relationship. A failed outreach campaign still gives me data. A failed product feature still tells me something about the market. If failure leaves nothing behind, I need a higher conviction level to proceed.

Third, what is the blast radius? Some failures are contained. They affect only the initiative that did not work. Others spread. They damage reputation, burn relationships, drain budget that was meant for something else. I want to understand the blast radius before I commit.

The goal is not to never fail. I have failed at plenty of things and most of those failures were instructive. The goal is to only take risks where I understand what I am risking and where even the downside is survivable.

A Real Example: Deciding to Build eNZeTi

When I first considered building what became eNZeTi, I ran it through all three questions.

Does it serve the core? At the time my core was cold email and outreach for law firms. I was already deep in that world. I was watching law firms spend serious money on marketing and then lose the cases they had already paid to attract because their intake process was broken. Building a tool to fix intake served the same market I was already in. It deepened my expertise instead of scattering it. Yes, it served the core.

Can I resource it? This one required honest accounting. Building a real product requires real time. I was not going to be able to keep running everything at the same level while starting something new. What I decided was that I could use the lead generation operation to fund the early development, and I could delegate more of the content and outreach work to the automation systems I was already building. The resource cost was real but manageable.

What does failure look like? If eNZeTi did not work, I would still have learned the intake market deeply. I would have relationships with law firm operators. I would have a clearer picture of where the real pain was. The failure would have residual value, and it would not destroy the outreach business that was already running. The blast radius was contained.

All three answers were acceptable. So I moved forward.

How I Use These in Practice

I do not run these questions like a formal checklist. I have asked them enough times that they live in the back of my head whenever something new comes up.

What I notice is that most ideas fail quickly on question one and I never have to get to the other two. That is fine. Speed of elimination is a feature, not a problem. The fastest way to protect your best work is to say no quickly to things that do not belong.

For bigger decisions, I actually write down my answers. Not a long document. Just a few sentences per question. The act of writing forces clarity that staying in my head does not. If I cannot write a clear answer to all three, I am not ready to decide.

I also revisit decisions after the fact. When something I started is not working, I go back to my original answers and check where my thinking was wrong. Usually the failure was visible in the answers if I had been honest enough at the time. Sometimes I was not. That is useful data too.

The Deeper Thing

Behind these three questions is a belief I have built slowly over years of building businesses: opportunity cost is real and it is usually invisible until it is too late.

Every yes is also a no. Every new initiative is pulling from a finite pool of resources, attention, and execution capacity. The founders I watch fail are not usually failing because they lack good ideas. They are failing because they are executing ten mediocre ideas instead of three great ones.

Three questions will not make every decision obvious. Some decisions are genuinely hard and require judgment that no framework can replace. But they will eliminate the easy mistakes, the ones you look back on and wonder why you ever said yes in the first place.

That alone is worth a lot.