TechcelerateJoin now
Menu
Knowledge base · Validating the idea · Guide 1 of 8

How to develop an idea before you try to validate it.

Most ideas fade within days. Before testing one with customers, give it time, talk about it, write it down and be honest about your own runway and team.

We all get ideas every day. Almost all of them are forgotten within minutes, overtaken by the next one. A few linger, and a rare few keep coming back. When you decide to do something about one, you have reached the very first step of building a tech startup. That step is not validation yet. An idea has to be developed, by you as the originator, before it is clear enough to test.

Why it matters

If you start interviewing customers with a vague idea, you get vague answers. If you start building with a vague idea, you build the wrong thing. A few weeks spent sharpening the idea makes every later step faster: you know who to talk to, what to ask and what would change your mind.

Step by step

  1. Give it time. Keep a simple idea journal. Every time you notice the problem in the wild, write down where, who and what it cost them. As a rule of thumb, if the idea still excites you after a month and the journal keeps growing, it is worth taking further.
  2. Talk about it. Speak to friends, family and colleagues, but treat these as rehearsals, not evidence. You are not looking for praise. You are listening for questions you cannot answer yet. Keep a running list of those questions; it becomes your research plan.
  3. Write a one-page idea brief. Writing exposes gaps that talking hides. A good brief has six short sections: the problem in one sentence; who has it, as specifically as you can; what they do about it today; your proposed approach; why you are the right person to solve it; and what must be true for this to become a business. If you prefer a structured format, the Lean Canvas covers similar ground.
  4. List your riskiest assumptions. From the brief, pull out every statement you have not yet proven, such as “practice managers spend hours a week on this” or “they would pay monthly”. Rank them by how badly the idea fails if each one is wrong. The top three become the focus of your validation.
  5. Check your own runway. How many months can you give this before you need income? Add up your personal monthly costs and the savings or income you can rely on. The runway and burn calculator helps. Be honest with yourself and with anyone who depends on you.
  6. Look for co-founders and helpers. Most good companies are built by small teams with complementary skills. Write down the skills the idea needs that you do not have, and start conversations with people who might fill them. Agree nothing on equity yet, but notice who is genuinely curious.

Worked example

Priya, a former operations lead at a home care provider in Leeds, kept noticing carers swapping shifts by text message, with managers spending evenings reconciling rotas. After a month of journalling she had 23 examples. Talking to former colleagues raised questions she could not answer: who pays for rota software today, and do agencies or providers feel the pain more? Her one-page brief, which she called Rotawise, named the customer as small domiciliary care providers with 20 to 80 carers. Her riskiest assumptions were that managers lose at least three hours a week to rota changes and that providers already pay for a scheduling tool they dislike. With savings covering eight months and a technical friend interested, she had a clear plan for her first round of interviews.

Common mistakes

  • Keeping the idea secret. Ideas are rarely stolen; execution is what matters. Secrecy mostly stops you learning.
  • Quitting your job on day one, before you know whether anyone will pay. Validation can usually be done alongside other commitments.
  • Starting to build software before you understand the problem. Code feels like progress but often hides the real questions.
  • Falling in love with the solution. Describe the problem first in your brief. If you cannot write it without mentioning your product, you are not ready.
  • Treating enthusiasm from people close to you as evidence. They want to be supportive, which makes their opinion unreliable.

What to measure

  • Entries in your idea journal, and whether new ones keep appearing.
  • The number of open questions on your list, which should shrink as you learn.
  • Your top three riskiest assumptions, written down and ranked.
  • Months of personal runway, recalculated whenever your circumstances change.
  • Number of potential co-founders or helpers you have spoken to.
With SkilledUp Life

Volunteers can turn your journal notes into a structured one-page brief and run early desk research on the questions you cannot yet answer.

How a volunteer team helps with validating the idea · The idea validation team ↗ · How SkilledUp Life works ↗

SkilledUp Life is exclusively for tech companies. Volunteers cannot be paid in any form, including stipends, gift vouchers or expenses. All volunteering is remote, and no promises of paid roles can be made.
Execution Sprint

Idea validation, systematically.

Reading is the start. Members tackle validating the idea in a time-boxed Execution Sprint, alongside tech founders who have built, failed and exited, and leave with measurable results.

Building a tech startup?

Join tech founders who put execution before investment.

Become a member