A short, easy-to-pronounce, universal name: Joost. For those wondering what the Venice Project was, well, it’s just an already buzzing Internet software start-up aiming at making of putting of each OS desktop a TV. Let’s now wish Joost will revolutionize the TV landscape. I’ve installed the desktop application: I like the interface a lot but can’t really test too much because too few channels are available so far. But still, great software – well-thought design.

Do you know Dragons’ Den? Well if you’re from the UK or the US, the answer’s probably yes. I had heard about the concept, but had actually never see the show. Dragon’s Den is a TV show on entrepreneurship and fundraising where you might come accross live investments.

I was especially impressed by the questions raised by the angels, be they from the UK (on the BBC) or the US. These guys really are professional investors. I wish this show was broadcasting in many more countries – especially where taking the high risk / high return bet to invest one’s personal money on innovative start ups isn’t quite sculpted in the culture of the area (mostly latin countries & Japan).

Here is a show that caught my interest in many respects (one amongst many), from the US version of Dragon’s Den:

JobLoft on dragons den part 1

[youtube=http://www.youtube.com/watch?v=Z9EkablfWVk]

JobLoft on dragons den part 2

[youtube=http://www.youtube.com/watch?v=lj8MNEgiDTU]

To answer an e-mail I received tonight.

Here’s a backbone you should use everytime you write a business plan. I’ve seen and written many. Many less than professionals of the entrepreneurial industry (angels, VCs, serial entrepreneurs, entrepreneurship or finance academics, etc.), but probably many more than the ‘rest of the world’ folks.

Two major pieces of advice first:

1) if you’re an entrepreneur, write business plans yourself. It’s a strategic responsibility. Don’t you ever outsource business planning! Writing a business plan directly helps you reflect on your business case. You’ll end up formalizing what was foggy in your mind. If you want your business to succeed, I beg you, stick to my words: having written your business plan yourself, you’ll be able to assess your capacity to abide – or not, by your forecasts. And since learning by doing – ie measuring the discrepancy between what you thought your business would be like and your actual performance – is by far the best MBA…

2) This is sort of less critical, but try your best to avoid business planning software – especially if you know already what business plans are like (dummies are excused: software provide a framework) and you plan to raise money somewhere. Investors see too many of these ready-to-throw-to-the-bin, software-wrapped business plans. Furthermore, this is especially true if you’re a creative person, the (often very relevant) frameworks these software provide will constrain your originality. So try to avoid business planning software (just repeating to make sure you got it). Use MS Word and Powerpoint, or OpenOffice, or even LaTeX or MS Dos 5 + Lotus 1.2.3., but do your best to avoid business planning software.

Allright. There you go with a ready-to-MODIFY (there’s no structure that fits all projects, you’ll have to make the following backbone evolve with the needs of your project) 20-page-long-max business plan structure:

1. Cover page with contact details, name of the project or company, recap of what it’s all about (raising funds or recruiting someone) – state ’strictly confidential’ on the footer of every single page (it doesn’t cost so much to add it)
2. Opportunity: where did it all came from? Make sure you have a story
3. Our concept / solution: how it fills in the gap
4. Our business model (textually)
5. Our business model (graphically, to avoid questions on your business model at the end of the presentation. These questions, when coming first, actually mean the people haven’t listened to you because you didn’t show them how your business would be such a cash cow. In other words, you won’t get a penny from them. The solution for you is to INSIST on the way(s) you’ll make money for you and them)
6. Competition [don't make the same mistake as everybody: think 'competitive universe', not just direct competitors. Most dangerours situations happen in the dark]
7. Value added of your solution vs. competitors (USP, stands for Unique Selling Point; if you’re still at school, use ‘Our competitive advantage’ – will make people smile)
8. The Team (all the team, not just the founders; I mean it)
9. Key figures from the market survey (attach the actual market survey to the miscellaneous back-up pages)
10. Pricing (how you did come up with your figures: benchmarking? taking a slice of the ROI generated for your clients? etc.)
11. Financials (a 5-year P&L statement will do, make it fit on one page; if you’re knowledgeable in finance, add the B/S in the misc. section)
12. Valuation (discount the forecasted free cash flows generated during these five years; take a rate of 10% (lousy markets &/or mature businesses) to 70% (very risky seed projects in trendy industries). State clearly that you’re well aware that discounting cash flows on the business plan of a company that yet doesn’t exist means nothing. It’s like planning your dating schedule with Diana Krall, Norah Jones & Cindy Crawford even though you never met and obviously don’t have any phone number to even think of making this happen. However, the valuation reveals how ambitious you are – something that may appeal to potential investors, and, if you’re really desperate for financing, will at least attract the fools.
13. Financing plan: what are the next steps?
14. Risk analysis [put 3 to 5 relevant risks you can think of. For instance: business plan risk, environmental risk, financial risk, reputational risk, market risk, political risk, etc. Whatever the business, both IDEA (or market) & EXECUTION (or operational) risks should be mentioned]
15. SWOT analysis (compulsory for techies, just to pretend you understand business; MBA-like bullshitters like me will add the SWOT to the miscellaneous back-up pages)
16. Where we’re standing (what you have achieved, and haven’t done so far)
17. Operational Plan (usually takes a few pages to explain HOW you’ll respect the above-mentioned financial figures; very few people write good operational plans because it’s very TOUGH no to get one of the guys in front of you waking up and say: “wait, I know this industry, you’re just talking non-sense’. Elaborating on the actual business operations, not just your dream or strategic vision, will force you show how your experience will constantly benefit the business, and if not, how common sense will help you achieve your goals. A 2/3-year horizon makes sense as far as the Operational Plan in concerned. Go far into the details of the 1st year in business. To restate things clearly, an operational plan is a road map aimed at showing that you know what it takes to execute perfectly)
18. So what? What’s in it for you (again, if you’re talking to potential investors, state things clearly: what you want from them, what you’re giving them, how you’ll get married, under which conditions, how you’ll separate (this time will come), in which circumstances; if you’re pitching a high flyer you want on your Executive Committee, do exactly the same)
19. Recap & contact details again

VS.

As a software development dummie, I’m not sure I have the legitimacy to strike an opinion about programming environments. But you know what? I don’t really care.

I’ve recently been developing on both integrated development interfaces, and to me, NetBeans 5.5 by far outperforms its long term rival Eclipse. I acknowledge both are really good. Eclipse, thanks to the size of its community and the stability of the initial code supplied by IBM Corp., has more plug-ins to offer to motivated software developers than NetBeans (it’s like Firefox vs. Opera). On the other hand, and to support my case: we live in a world in which nobody cares anymore about the code lines lying behind the actual software. People use software like a service, and what really matters most is the human – machine interface. Take Apple Inc.: they master the whole friendly-HMI development process. People actually buy Apple products because people’s eyes love Apple products’ material design and software interfaces.

In this respect, NetBeans has implemented a tool that I find amazing. NetBeans actually allows software developers to devise HMIs visually, through dragging and dropping – exactly like in Visual Studio for instance (although I find Visual Studio much simpler of use: you can almost write a software without knowing anything about software development).

On top of that, bear in mind the fact that, in Java for instance (using the swing or awt library, same business), hacking a proper interface is bloddy tedios – and you’ll end up having NetBeans beating Eclipse for this only reason (like, in my humble opinion and thanks to the convenience of its HMI, Opera beats FireFox despite FireFox’s tremendous plug-in library). Enough for me to make a purchasing decision worth 0$, 0€, 0£: go for NetBeans rather than Eclipse.