I'm currently coaching a program called Summer of Startups. It's an ambitious project started by student-run organizations in Helsinki to encourage students to create a startup during the summer rather than taking a summer job. The government-funded program offers €750 per month to each participant and runs from July through August.
My job as a coach is to encourage, challenge and provide feedback to the 10 teams that were selected. In early July, they were mostly wild ambitions and ideas-on-paper, but after one month of working on their prototypes, meeting mentors and taking part in a pitching competition, they have become early-stage startups. Being a startup founder myself, I find it very easy to relate with them. However, this is my first time on the other side of the table, and this new perspective taught me a few points I would like to share.
Because of this, they try many different things, and see how that affects their offering. One of our teams, Incspark put it very well: "It's a bit like we're building something random, take a few steps back and say, 'It seems that we have been building a car!'"
Instead of thinking what your users might want in the future, start gathering users now and ask them. Don't overdo plans, but be lean, focus on building a prototype and lower your development cycles so you can keep pushing updates and learn.
It's important to define your tasks and to have an idea of who makes the calls on certain topics from the start so you can delegate to the right person.
What makes a great team? Experience helps, but keep in mind that you need balance (where do you have gaps?), communication skills (divas are difficult to manage), ability to commit to plans, to deliver and to learn. But more than anything, make sure you surround yourself with people who will complete you and stick around when the hard times come.
Listen to people's complaints, however negative, badly formulated or nonconstructive they are. Sure, they are criticizing your baby and it hurts, but keep in mind that your users are not paid to give you hints on how to make a better product. So don't try to counter-argue with them and explain how they are wrong, or convince yourself that they are wrong and wouldn't have liked your service anyway.
A pitch is not about convincing, informing or educating and it doesn't have to be formal. It's not a keynote or a presentation - it's a sales argumentation wrapped up in a show. People most likely aren't experts in your field or understand your technology. You need to convince them to invest their time, contacts, content or money in your idea. Win them over with a value proposition and a story that sounds strong, memorable and believable. Give a great demo, deliver on bold claims and don't sound like a tool.

Summer of Startups teams meet Jaiku founders
The problem is that, without experience, or even a prototype, you're unlikely to get good terms, and risk getting diluted and burnt very quickly. If your burn rate is buying noodles and living at your parents, you don't need to raise money, so focus on creating value first!
Before you meet people, try to learn something about their agenda on LinkedIn or Facebook, maybe you can help, maybe they're on the board of a competitor. When you scout for VC, look them up on TheFunded.
Prepare yourself, so you can ask the right questions, offer the right things, and filter the bullshit.
Network, attend events, share your thoughts with others, bounce ideas, blog about your daily progress, share your story with others. Don't postpone it because you think that your product isn't ready or that people will judge you. Tell the world about your passion, and they might just be willing to listen.
I think that anyone with experience has a duty to help the newcomers. I've learned that the role of a coach is not so much to encourage people, but to continuously push, question and challenge them, so that they can find their way by themselves. In that sense, my role is to help recognize failure and success. If those of us with experience do this early and often enough, maybe we'll see less of the former and more of the latter.