Loading...
Answers
MenuIs it viable to validate and fund my project at the same time?
Answers
Hi there - great question(s).
You "can" validate and fund projects at the same time. In fact, at some point the critical part of true validation is showing that quantitatively someone will pay something for your product/services. Now, whether you should fund while validating is the more important question. A lot of entrepreneurs look at the payment component as as round 2 or 3 validation point, and instead start with a tacit validation exercise, focusing less on business model (how much will someone pay for this and how will they pay?) and more on showing a consumer need/ability to target that market with your proposed solution.
In the example you use, if you do commence with taking pre-orders but ultimately the project falls through, you would and should be most inclined to fully refund their money (and stating that on the landing page could do wonders for your adoption of people pre-registering.) the reality is, unless you are showing a sample product or touting something that people can easily comprehend, the chances of you getting a volume of people (outside of your own network) to pre-order something from a brand new company might be on the slim side.
But let's say you do get people to sign up - the challenge is that you are using their cash to fund ongoing operations. So if the project falters or goes belly-up, the chances of you having all or even some of everyone's money might be slim. So this would be a reason to advocate potentially against using pre-orders (and collecting payments for them) to fund ongoing operations. A savvy buyer will note this too and may seek to avoid that risk altogether.
I could think of several ways you could fund ongoing operation with your product/early beta, but it really depends on 1) the product you're launching, 2) what your target buyers are, 3) your operational costs and 4) your goal of the beta/validation stages. It requires a bit of guidance and dialogue, but there are several options you should be able to choose from for funding, and if one of those is using pre-orders or the validation phase to generate funds, there are things you should strongly consider to protect yourself and your consumers.
Happy to hop on a call and discuss your idea and options further. Just follow the link and request a call!
For any fund-raising process, traction is the key. Since you are validating and cannot really talk about traction (so far), the next important factor is projections.
The way you prepare projections can be critical to raise funds in your case. If you need any any email in your pitch deck, you can setup a call with me! :)
Cheers, and good luck!
I've seen two companies with mid-seven figures funding, one of which I co-founded, fail first-hand. Neither of these companies validated the idea prior to building it. Based on these two experiences I'm a huge proponent of validating first, building second.
I think there are two common pitfalls that people with an idea fall into, when they choose to build first, validate second -
1 - If I think it's a great idea, there must be a lot of other people who do too.
I think this pitfall is caused mainly by the optimism that is naturally inherent in entrepreneurs. I personally have no shortage of ideas, most of which I believe are good ones :)
I took a course by Noah Kagan of AppSumo, where he suggests finding three paying customers, prior to building a product. When I started validating my ideas this way, prior to launching, I was surprised at how quickly I learned the lesson that just because I thought an idea was a great one, that didn't mean anyone else did.
2 - Building is more fun/satisfying than validating
When we're building something, we experience tangible progress and feel like we're exerting some degree of control over our future. Both of these experiences work powerfully on our conscious and sub-conscious mind.
As a result, it's easy to get pulled into a project, get enticed and distracted by the momentum that seems to building as we're making "progress", only to release the product to the market and have it fall flat due to lack of demand.
So, if it isn't clear by this point, my strong suggestion is to validate first, build second :) I think the good news is that the availability of crowdfunding platforms, landing page builders, etc., makes this approach easier than ever before.
You may also be surprised at how much work goes into validating your project, so you may still experience the satisfaction of feeling like you're making progress, if your idea begins to gain traction and/or you begin to interact and communicate with potential customers.
Good luck and always happy to discuss further on a call!
Related Questions
-
What is the best way to find full stack mobile developers who are willing to work with me for equity, and what is fair compensation?
It's highly unlikely that you will be able to find competent full-stack mobile developers willing to work with you for equity, but if you do, "fair" compensation would be 50% or more of the equity in the Company. Approaching any developer with just an idea, diminishes your credibility as a potential co-founder. Here's why: If you're non-technical, you must show a "relentless resourcefulness" in moving your idea forward. This means finding the money necessary to get an MVP or even click-able prototype completed to show that while you might not be technical, you have the ability to raise money, and have enough product sense that you can articulate that into a prototype. If you can't raise or spend the relatively small amount of money required to successfully build a prototype, what evidence are you providing that developer that you are going to be able to create value for the business long-term? Full-stack mobile developers (although this is often quite a misnomer) are one of the most in-demand skill-sets of all Silicon Valley companies. That means that you're competing against established companies that can pay top dollar, and still provide meaningful equity incentives as well as recently funded startups who have further along the road in turning their idea into reality. I would suggest that you look at hiring contractors (I know of some great mobile dev shops that are reasonable) to build your first version. Expect to go solo at least until you have some form of early prototype. Then, you're in a much better position to attract a technical co-founder. Happy to talk you through any of this at any point.TW
-
How do you build a MVP for an innovative tech b2b product? We would need good amount of funding to build a decent MVP and show businesses.
The idea of an MVP is 'minimum, viable' ... If you feel you need a "good amount" of funding, I would challenge if you are minimum enough. Obviously, without knowing the details of your product, your ideal customer, or what need you will solve, it is hard to help expose what is necessary in an MVP and what is a Phase II or Phase III feature. I am happy to help you work through this, or answer specific questions, to get you rolling. Just book a call with some times that will work for you. Regardless, I would love to know more about it and how it goes after launch. To your success, -ShaunSN
-
What is the best method for presenting minimum viable products to potential customers?
Whoa, start by reading the Lean book again; you're questions suggest you are making a classical mistake made by too many entrepreneurs who live and breath Lean Startup. An MVP is not the least you can show someone to evaluate whether or not building it is a good idea; an MVP is, by it's very definition, the Minimum Viable Product - not less than that. What is the minimum viable version of a professional collaboration network in which users create a professional profile visible to others? A website on which users can register, have a profile, and in some way collaborate with others: via QA, chat, content, etc. No? A minimum viable product is used not to validate if something is a good idea but that you can make it work; that you can acquire users through the means you think viable, you can monetize the business, and that you can learn from the users' experience and optimize that experience by improving the MVP. Now, that doesn't mean you just go build your MVP. I get the point of your question, but we should distinguish where you're at in the business and if you're ready for an MVP or you need to have more conversations with potential users. Worth noting, MOST entrepreneurs are ready to go right to an MVP. It's a bit of a misleading convention to think that entrepreneurs don't have a clue about the industry in which they work and what customers want; that is to say, you shouldn't be an entrepreneur trying to create this professional collaboration network if you don't know the market, have done some homework, talked to peers and friends, have some experience, etc. and already know that people DO want such a thing. Presuming you've done that, what would you present to potential users BEFORE actually building the MVP? For what do you need nothing more than some slides? It's not a trick question, you should show potential users slides and validate that what you intend to build is the best it can be. I call it "coffee shop testing" - build a slide of the homepage and the main screen used by registered users; sit in a coffee shop, and buy coffee for anyone who will give you 15 minutes. Show them the two slides and listen; don't explain, ONLY ask.... - For what is this a website? - Would you sign up for it? Why? - Would you tell your friends? Why? - What would you pay for it? Don't explain ANYTHING. If you have to explain something, verbally, you aren't ready to build your MVP - potential customers don't get it. Keep working with that slide alone until you get enough people who say they will sign up and know, roughly, what people will pay. THEN build your MVP and introduce it first to friends, family, peers, etc. to get your earliest adopters. At some point you're going to explore investors. There is no "ready" as the reaction from investors will entirely depend on who you're talking to, why, how much you need, etc. If you want to talk to investors with only the slides as you need capital to build the MVP, your investors are going to be banks, grants, crowdfunding, incubators, and MAYBE angels (banks are investors?! of course they are, don't think that startups only get money from people with cash to give you for equity). Know that it's VERY hard to raise money at this stage; why would I invest in your idea when all you've done is validate that people probably want it - you haven't built anything. A bank will give you a loan to do that, not many investors will take the risk. Still, know not that your MVP is "ready" but that at THAT stage, you have certain sources of capital with which you could have a conversation. When you build the MVP, those choices change. Now that you have something, don't talk to a bank, but a grant might still be viable. Certainly: angels, crowdfunding, accelerators, and maybe even VCs become interested. The extent to which they are depends on the traction you have relative to THEIR expectations - VCs are likely to want some significant adoption or revenue whereas Angels should be excited for your early adoption and validation and interested in helping you scale.PO
-
I'm looking for a great full service app design firm to build my app and help with all design, branding, development, etc. Anyone know any good ones?
Yes. Who I would recommend would depend on what you'd like to see happen. Are you building only for iOS, or only for Android, or both? Will you have a bunch of content/stuff in your app or just a little? Are you thinking game or non-game app? Do you already have a big fanbase or would you be trying to build one while building the app? It's easy to save a bunch of money on mobile development if you know how, and even easier to overspend. Making an app can be a ton of fun or a major headache. I'd recommend the fun. So if you want an outside perspective, give me a ring.AC
-
I've been working on an app concept for 6 months and built an MVP. Is it better to pay a development firm to build or hire a developer as a cofounder?
I have built two software companies by hiring out the development work. I sold one for a decent sum during the dot com era (circa 1999). I remain a shareholder in the other one. I currently work with amazing development company on behalf of one of my clients. Here are some things to consider. 1. Do you really want to give up equity? If not outsource. 2. How fast do you want to get to market? If sooner than later, outsource. 3. How capitalized are you? If undercapitalized, either outsource offshore (which runs about 20% of US rates), or bring on an equity development partner. I offer a free call to first time clients. Let's chat and I'll give you some great advice from three decades of experience. Just use this link to schedule the free call: https://clarity.fm/kevinmccarthy/FreeConsult Best regards, Kevin McCarthy Www.kevinmccarthy.comKM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.