You've Got the Idea. You Don't Have the Team. Now What?

Most businesses I speak to have one. An idea for a product or a feature that comes up in every planning meeting, that everyone agrees is worth doing, and that is still sitting on the whiteboard a year later. Usually it is not the idea that is the problem. There is no one to build it, no time to shape it properly, and no spec clear enough to hand to anyone.

At this point companies tend to do one of two things. Some hire for it, taking on product and engineering headcount before the idea has been tested with a single customer. That gets expensive if the idea does not survive contact with the real world. Others hand it to an agency with a short brief and hope for the best. What usually comes back is the thing that was written down, which is not always the thing the business needed.

There is a more sensible route, and it starts much smaller than people expect. When I take an idea on, the first two weeks look roughly like this.

Sharpen the problem

The first few days are spent sharpening the problem. Who is this actually for, and what would they use it instead of? Most importantly, what is the single thing the first version has to do well? A lot of whiteboard ideas are really two or three products rolled into one, and the first decision is which part to build first.

Get something in front of people

Then I get something in front of people. A clickable prototype or a tight spec, depending on the idea. This used to take months. With the AI-assisted prototyping tools available now, a testable version of most ideas can exist inside a week, and I use them heavily for exactly this.

Test it

Next, test it. Five to ten real prospective users, watching where it falls over rather than asking whether they like it. People are polite. Behaviour is honest.

Plan the build

Only then do I plan the build. The technical approach, what gets built versus bought, how it connects to your existing systems, and who does the work. More often than not the answer is your existing developers, working from clear specs with proper product leadership alongside them, rather than a new team at all.

That is the work I do. I scope it, spec it, and build it hands-on with your developers, from first prototype through to something real customers use.

If you have an idea that has survived more than one planning cycle without being built, have a look at the Application Development and NPD page for how an engagement works. Rates are on the Pricing page, published openly. Or just get in touch and tell me what the idea is. I will happily tell you what its first two weeks should look like.