The expensive mistake I keep seeing Someone has a good quarter. They think: what if I offered something adjacent? A new service line. More revenue. Diversification. Three months later, they have spent £8,000 on a website redesign, hired a contractor, maybe even rented extra space. The new service has brought in two clients. One of them is a favour from a friend. This happens constantly. People commit fully before they know if anyone actually wants the thing. The orchid breeders have this figured out. They spend a decade developing a new variety before it hits the market because they know premature commitment kills margins. Most of us do not have a decade, but we can borrow the principle: test before you invest. What testing actually means Testing does not mean thinking about it harder. It does not mean asking your mates if they would buy it. It means putting something in front of real potential buyers and measuring their response with actual behaviour. There is a difference between "that sounds interesting" and "here is my card number". The first is polite encouragement. The second is validation. I worked with someone last year who wanted to add a done-for-you service to her existing consultancy. She was convinced it would work because three clients had mentioned they wished she offered it. Before she hired anyone, we ran a simple test: she emailed her list of 340 past and current contacts with a one-page description and a price. Not a landing page. Not a brand. Just an email that said "I am considering offering this. Here is what it would cost. Reply if you want to be first." Seven people replied with genuine interest. Two paid deposits within the week. That was enough signal to proceed. If nobody had replied, she would have saved months of wasted effort. The 30-day validation framework I use a rough structure when helping people test new service lines. It is not complicated, but it forces you to move quickly and measure clearly. Week one: define the minimum offer. Strip the service down to its core. What is the simplest version you could deliver that still solves the problem? Do not build the premium version. Build the version you could fulfil next Tuesday if someone said yes. Week two: identify ten real prospects. Not "the market". Ten specific people or businesses who might buy this. You should be able to name them. If you cannot name ten, you do not understand who this is for yet. Week three: make direct contact. Email, message, call. Not a newsletter blast. Personal outreach to those ten people. Describe the offer, state the price, ask if they want it. Track responses in a spreadsheet. Nothing fancy. Week four: evaluate and decide. How many expressed interest? How many asked follow-up questions? How many said yes? If fewer than two out of ten showed real buying intent, the offer needs work or the audience is wrong. This entire process costs almost nothing except your time. Compare that to building infrastructure for something nobody wants. The signals that matter Not all interest is equal. Learn to read the signals properly. "This is a great idea" means nothing. People say that to be supportive. "Can you send me more details?" is mildly positive. It means they are curious but not compelled. "What happens if I need X instead of Y?" is better. They are mentally placing themselves in the scenario. They are imagining buying. "When can we start?" or "Can I pay now?" is the only signal that actually counts. Everything else is noise dressed up as encouragement. I have seen people build entire services on the back of "this is a great idea" feedback. It never ends well. With all the uncertainty in markets right now, with borrowing costs climbing and political instability making everyone cautious, you cannot afford to guess. You need real data before real commitment. When to kill the idea This is the part nobody wants to hear. Sometimes the test tells you no. If you reach out to ten qualified prospects and none of them show buying intent, the idea is not ready. Maybe the positioning is wrong. Maybe the price is off. Maybe there is no demand at all. But whatever the reason, you have learned something valuable for almost no cost. Killing a tested idea is not failure. Spending six months and £15,000 on an untested idea that flops is failure. The Decision Matrix tool on alira.london can help here if you are weighing multiple service line options. It forces you to score each option against criteria that actually matter to your business, rather than going with whatever feels most exciting in the moment. Scaling what works If the test succeeds, you have permission to invest more. But still, move incrementally. Start with manual delivery. Do not automate until you have done it yourself at least five times and understand exactly what the service requires. Build systems around proven demand, not hypothetical demand. Document what works. The processes you develop during early delivery become the foundation for scaling later. If you cannot describe how you delivered the service, you cannot train anyone else to do it. Raise prices before adding complexity. If demand is strong, test a higher price point before you start building out infrastructure. You might find the market will pay 40% more than you initially thought. What to do this week Write the minimum offer. One page maximum. What is it, who is it for, what does it cost, what do they get. No fluff. If you cannot explain it simply, you do not understand it yet. List ten names. Real people or businesses who might buy this. Not demographics. Names. If you get stuck, use the 5 Whys tool on alira.london to figure out why you cannot identify your buyer. Send the first three emails by Friday. Do not wait until the offer is perfect. Perfect is the enemy of tested. Get it in front of real people and see what happens.