Before Spending a Euro: The Brutal Reality
Every year, millions of euros are wasted on web projects that should never have seen the light of day. Not because the ideas were bad, but because the right questions weren't asked at the right time.
Here are the 4 questions that can save you from this waste.
"Measure twice, cut once." - Carpenter's proverb
This principle applies perfectly to web projects. Better to spend time upfront than on post-launch fixes.
Question #1: Does Your Idea Solve a Real Problem?
This is the most important question and yet the most neglected. Too many projects are born from a moment's inspiration without real validation of the need.
The "pain point" test
Complete this sentence: "My users lose _____ (time/money/energy) because of _____ (current problem)."
Concrete example:
"Our salespeople lose 2 hours per day manually entering quotes because our current system doesn't integrate with our CRM."
If you can't complete this sentence with precise data, your project risks solving a non-existent problem.
Field validation
Get out of your office and talk to 10 people from your target. Ask them:
- "What's your biggest problem in [domain]?"
- "How much time/money does it cost you?"
- "What have you tried to solve it?"
- "Would you pay for a solution?"
If 7 out of 10 people don't confirm the problem, it's a red flag.
Case study: The app that never took off
An entrepreneur spent €50,000 developing a "ride-sharing app for pets". The idea seemed brilliant on paper. Problem: after 6 months, only 12 active users.
Why? He had never validated that pet owners actually had this need. Most preferred to transport their pets themselves.
Question #2: Is Your Solution Technically Feasible?
Having a good idea isn't enough. You still need to be able to implement it with current technology and your budget.
The 3 levels of feasibility
Level 1: Technically possible
The technology exists but may require significant resources.
Level 2: Technically accessible
Achievable with standard skills and budget.
Level 3: Technically simple
Can be developed quickly with existing tools.
Questions to ask your developer
Technical checklist:
- ☐ What technologies are needed?
- ☐ What integrations are required?
- ☐ What are the major technical challenges?
- ☐ Do custom components need to be developed?
- ☐ What's the complexity of the architecture?
The "miracle solution" trap
Beware of solutions that promise to revolutionize an entire sector. The more revolutionary, the more technically risky.
⚠️ Warning signs:
- Requires inventing new technology
- No competitor has succeeded in doing it
- Depends on immature emerging technology
- Requires integration of 10+ external systems
Question #3: Is Your Budget Realistic?
Budget underestimation is one of the main causes of web project failure. Here's how to avoid it.
The 3-budget rule
Technical budget: Development, testing, deployment
Marketing budget: User acquisition, communication
Operational budget: Maintenance, support, evolution
Many entrepreneurs only consider the technical budget. Fatal error.
Realistic estimation by project type
Orders of magnitude:
- Showcase site: €2,000 - €10,000
- Simple e-commerce: €5,000 - €25,000
- Web application: €10,000 - €100,000
- Complex platform: €50,000 - €500,000
The hidden cost of maintenance
Count on 20% of the initial budget per year for maintenance and evolution. A €50,000 project will cost €10,000/year in maintenance.
Budget questions to ask
- What's my total available budget?
- Over how much time can I spread it?
- Have I planned the marketing budget?
- What happens if I exceed by 30%?
- Do I have a plan B if it doesn't work?
Question #4: Is Your Timing Right?
Even the best idea in the world can fail if it comes at the wrong time. Timing is crucial.
The 3 dimensions of timing
Market timing: Is the market ready for your solution?
Personal timing: Do you have time to dedicate to it?
Competitive timing: Are you too early or too late?
Timing questions to ask yourself
Timing checklist:
- ☐ Is the market adopting this type of solution?
- ☐ Are my competitors already established?
- ☐ Do I have time to dedicate to the project?
- ☐ Is my team available?
- ☐ Are economic conditions favorable?
The "first mover" trap
Being first isn't always an advantage. Sometimes it's better to let pioneers deal with the teething problems and learn from their mistakes.
Case study: Too early vs Too late
Too early: Google Glass (2014) - Technology was ready, but not the market.
Too late: Google+ (2011) - Market was mature, but Facebook was already dominant.
Just in time: Instagram (2010) - Arrived when smartphones finally allowed beautiful photos.
The 7-Step Feasibility Test
Before launching your project, take this test:
Feasibility test:
- Problem: 10 people confirm the problem
- Solution: Your solution solves the problem
- Market: The market is large enough
- Technical: It's technically feasible
- Budget: You have the means
- Timing: The moment is opportune
- Commitment: You're ready to dedicate yourself to it
If you can't check at least 6 out of 7 boxes, reconsider your project.
Conclusion: Measure Twice, Develop Once
These 4 questions may seem tedious, but they can save you months of useless development and thousands of wasted euros.
Remember:
- It's better to abandon a bad idea early than late
- Validation costs less than development
- A "no" in the feasibility phase is better than failure in production
Take time to properly define the problem before building the solution. Your finances and mental health will thank you.