Loading...
Answers
MenuWhat is the best way to prepare my pitch and/or approach a potential co-founder, increasing the chances that they'll say "YES"?
I have a fantastic, well-developed idea for a new subscription/coaching service. I have the needed expertise in branding, design, user experience, curating the content, social media strategy, marketing, etc. The website is already drafted, and social media is up and running. Now I'm looking for someone who can help with business and financial planning, coordinating legal and accounting, and making sure we start smart. Essentially the left brain to my right. Where do you recommend looking for co-founders (outside word of mouth), and what is the best way to pitch (or to prepare myself and my business idea/setup) in order to get the "YES"?
Answers
I have built multiple teams including bringing on cofounders, and being brought on as a cofounder. I also once brought on a cofounder who was responsible for doing the legal/financial/accounting. I wouldn’t do that again (we’re still great friends - just not enough value). I hope my experience can help you out.
Having a cofounder is like having a business spouse. Accordingly, much of the same aspects of relationship building apply, including the pitch and the subsequent “dating.” As you move forward in your relationship, your goal should be removing as much ambiguity as possible, as quickly as possible. A business litigator friend of mine used to say that 99% of breakdowns in partnerships occur because the relationship developed a high tolerance for ambiguity.
1. What you focus on in your first meeting depends on whether or not that person has been a cofounder and/or part of a startup in the past. If they have, they will likely want to start poking holes as quickly as possible, allowing you to be more granular in your discussion. If they haven't, you'll probably stay higher level at first. Both are fine, just be prepared for both scenarios.
2. You have to capture people's imagination with energy and a great story right off the bat. I have made the mistake of ‘just presenting the facts’ in our first meeting, and that generally doesn't go as well. You have to be honest, but you need people to get excited when pitching before they're able and willing to process the details and logic. This is so very important. Don’t overdo it, be humble and point out your gaps, but be excited!
3. The more you can show progress the better. After you capture the imagination, if you can show off the goods that's ideal. This helps them catch the vision, and it also helps them know you’re not full of it and could pull this off =)
4. Take your time. Don't ask them to cofound things on day one. Just like dating, just keep getting to know each other if things continue to progress positively.
5. Help them see where they fit, and define a clear path to on-boarding. By doing this, you’re removing ambiguity and risk, which helps them process the important things. At minimum, this includes 1) discussing ownership, and 2) defining a trial run. 1) Even if you just say, “I’ll take 60% you take 40% and we’ll dilute equally” and put that in writing, that’s a good start. Don’t wait on that. 2) Then, define a specific period of time that you'll test working together. Put a date on the calendar to address whether or not you work well together, and then be honest about it.
Ok…I have lots more to say (clearly) on partnership; but to your other questions:
You can grab templates for much of the more lightweight financial stuff. And/or, partner with a company who does these services vs. bringing on a cofounder who does “the business.” A great cofounder needs to be able to dabble across the business. If they’re a lawyer who can also do UX, marketing, customer service, etc. that’s great! Bring them on. But, that person is rare in my experience. A more CFO/accountant/legal type of person may be more of a post-funding/growth hire than a cofounder. So, I generally prefer to pay a one-time fee to get incorporated, get my books set up, and get my financial modeling done rather than take the risk of losing equity on someone who might not add enough value early on. I work with some partners who do this if you’d like more info.
Lastly, I have only ever found/been found via word of mouth. I have seen some sites who are geared towards helping find a cofounder, but I haven’t used them or had success when trying to find people online. I’m sure some others will have a different opinion, so hopefully you can get some more advice from other Clarity members.
Let me know if you’d like to chat more. I hope that helps!
There are Pitch Fests that allow you to do just that. Also join local MeetUp groups and ask the smartest and most business savvy people in your network if you can practice on them and get their feedback. Also record your pitch so you can see/hear yourself. Good luck!
Related Questions
-
How to deal with co-founders that aren't pulling their weight?
I feel your pain — I've been there several times in a couple of my companies. Each situation ended up being unique, and had to be handled differently. I think there are a few things to consider before you make your decision: -- 1. What is in your cofounder's way? Is you cofounder being held up by a lack of clarity? Lack of motivation? Lack of autonomy? One of my past cofounders was very good at getting the job done, but didn't naturally have the skill to lay out tasks in a manageable way. To get around this, I worked with the whole team (4 people) to write up process documentation that removed the need to "figure out what to do next" that was tripping up this cofounder. -- 2. What job was your cofounder brought on to complete? And is it being completed? One of my companies brought on a cofounder simply to give us a marketing platform — he had a huge online audience — but he did nothing else. At first, this caused tension; once we had specifically laid out who was on the team and for what purpose, it was easier to identify where responsibilities lay. -- 3. Is your cofounder capable of doing the job? One of the more painful ordeals I've gone through in business is bringing on a good friend, then realizing that — despite his talent and intelligence — he just wasn't able to perform the job I'd hired him for. His skills were better suited for a different job: he needs hands-on management; he works better with repetitive tasks that don't require big-picture thinking; he lacks assertiveness and confidence, which were critical for the management-level role he'd been hired to do. After I tried to clear everything in his way, it became clear the company couldn't survive if he remained on the team. I had to lay him off. -- 4. Do you just simply not like the way this cofounder works? In one of my startups, there was a cofounder who I didn't know all that well, but he had amazing industry contacts and domain knowledge. However, once we started working together it became clear that we had VERY different working styles. He drove me completely nuts with (what seemed to me to be) a very ADHD-style of planning, with projects starting and being dropped and then coming out of nowhere with a call at 21:00 to discuss something critical that would be forgotten tomorrow. I'm sure I drove him nuts, too. So eventually we ended up selling that company — it was that or shutter it — because we knew there wasn't a chance we'd be successful if we continued as we were. -- Working with other people is tricky in general. Our instinct is to assume that we're the best workers on the planet and everyone else is incompetent, an idiot, a slacker, or all of the above. Usually it's a combination of an organizational-level lack of clarity, poor communication, no processes, and (sometimes) plain ol' we-don't-see-eye-to-eye-on-things-ness. Hopefully that helps. Feel free to get in touch if you'd like to hear specifics on my situations, or if you'd like any help devising a strategy for resolving your cofounder trouble. Good luck!JL
-
Need some advice on how to build a team, and determining what kind of talent I need?
A great team looks like this - 2 full stack engineers. They can manage servers, security, build features and code front end JS/interactions. - 1 visual designer focused on product, information architecture, UX and flows. - 1 front end developer who can take designs and built out killer interactions and can wireup any back end code to the UI The CEO can manage product + customer development and everyone on the team does support. That's 5 people and can accomplish a lot!DM
-
What are some early symptoms of conflict between people working on a team together?
The number one would be shipping product (or anything really) out in front of a customer. If you can't work together to get something done fast, that is usually a huge indicator that somethings wrong. That usually means your values or mission aren't aligned.DM
-
What is your advice for building a team of like-minded individuals to help start your business?
I'm a feelance CFO and I work actively with early stage companies. I've been at this for almost 30 years. Some of my current and recent clients wrestle actively with this very questions. My advice is to have the tough conversations right up front, early in the team building process. This usually consists of answering questions like, "who's in charge and what does that really mean," "who gets how much of the company and when and in exchange for what," "what are you, you and you really bringing to the table in terms of skills and cash," and "who is really in a life situation that will allow them to sustain their commitment to the business?" Any team that can get through these questions can get through the trials of surviving startup. I'm happy to talk with you directly about these issues and, in particular, to help look at them through a strategic financial planning lens.HD
-
What does your a team look like for a software company of ten or less people? Or, how do you think it should be?
Instead of looking at who does what .. why not look at the things that need to get done for a small techology team. Product: 6 people - 3 full stack engineers - 2 front end developers - 1 designer / product person Marketing & Community, 1 person - Full time hire, or CEO Support & Operations, 1 person - Part time hire, or CEO + Whole team I believe it's important for everyone on the team to help with support. Also, if you have a great product, then support shouldn't be that taxing. Q&A is usually needed when you have a bad development process (no unit testing or continuous integration deployments). Outsource everything else. - Bookeeping - HR stuff - Legal - Government program paperwork Hope that helps. P.S. I would put as many people on product as that's where you'll get the most bang for your buck.DM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.