Loading...
Answers
MenuShould I continue developing my site further or keep a simple landing page with email capture to test my idea?
I have a landing page setup, do I develop the site further (be able to offer the product) and then upon order completion capture details? or leave it as a simple landing page with EOI capture (email)? (the former would entail additional spending as I am not a dev)
Answers
Depends on your objective.
If you really just want to know whether the idea is viable, you'll get the most bang for your buck by keeping things email-capture-only or putting up a "smoke test" where you have a Buy Now button that redirects to a "it's not available yet; but leave your email if you want to be notified when it's ready"... and see if you can get anyone to click "buy now" by clearly articulating on your landing page what the product will do for them. This also lets you test pricing sensitivity.
If you can't get anyone to leave an email or click "buy now" based on a really good description with images (or even better a video "demo") then building the actual product is unlikely to be worth it.
I have worked with startups for more than 15 years, mostly as a seed stage (pre revenue) VC.
More and more, funders and other stakeholders look towards third party proof points (e.g. users). If you can build a mock up or MVP great, but even a simple landing page with EOI proves that what you are working on may have legs.
Better to test, early and often is what the Lean Startup teaches us. Once you have proven something, only then move on, invest more, and build out. First search for problem/solution fit, then product / market fit, then scale.
If you'd like to discuss, drop me a follow up note and I can share more thoughts and resources.
capture the "intention" first and once you gauge the real interest continue building.
Use google forms to set up leads or interest, probably the best way to do it
http://www.google.com/forms/about/
Instead of building the product first, try and see if you could use some existing service to test our your market. For e.g. you could start a Facebook Group, or a mailing list to run things manually for a while. Get the user engagement, get a lot of feedback. And once you have enough material to work on, build the product.
In other words, get to market without building a product if you can. It's always easier to get some traction on existing (social networking and other) sites than a new standalone site.
1.Build the LP - converts?- If yes, move to step 2. If not, keep changing the traffic sources, message, style, features, product till something makes it convert. When it works, move to step 2.
2. Build the website like you have built the product but you haven't - If it converts build the product. If it doesn't, try step 3
3. Build a demo, simple video, all the stuff to show how your product works though you are yet to build the product - still doesn't convert? - Chuck it or pivot. If it works, build the product.
Related Questions
-
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
-
When is it better to find a technical co-founder before developing an MVP vs. hiring a freelancer to build it for you, and vice-versa?
A co-founder is a long-term relationships that should be built on trust, and passion, and time... time to fight, time to recover, time to build rapport. Ultimately, your co-founder shouldn't be based on *any* specific idea, because the two (or three?) of you could work on anything you are all passionate about, and either experience wild success or learn some great lessons along the way. An MVP doesn't require a co-founder get built. In fact, the less technical code required the better. You should be able to validate most ideas with some very basic tools: WordPress site, Email list, a set of google forms, and a little love. I think the most important question to ask yourself is, "Am I willing to have my idea change for the right person? Or am I just trying to find the best person to execute on my idea?" For what it's worth, I've seen much more success with the former than the latter.TK
-
Whats are some ways to beta test an iOS app?
Apple will allow a developer to register 100 UDID devices per 12 month cycle to test via TestFlight or HockeyApp. Having started with TestFlight, I would really encourage you NOT to use it, and go directly to HockeyApp. HockeyApp is a much better product. There is also enterprise distribution which allows you far more UDID's but whether you qualify for enterprise distribution is difficult to say. As part of your testing, I'd encourage to explicitly ask your testers to only register one device. One of the things we experienced was some testers registering 3 devices but only used one, essentially wasting those UDID's where we could have given to other testers. Who you invite to be a tester should be selective as well. I think you should have no more than 10 non-user users. These people should be people who have either built successful mobile apps or who are just such huge consumers of similar mobile apps to what you're building, that they can give you great product feedback even though they aren't your user. Specifically, they can help point out non obvious UI problems and better ways to implement particular features. The rest of your users should be highly qualified as actually wanting what you're building. If they can't articulate why they should be the first to use what you're building, they are likely the wrong tester. The more you can do to make them "beg" to be a tester, the higher the sign that the feedback you're getting from them can be considered "high-signal." In a limited beta test, you're really looking to understand the biggest UX pain-points. For example, are people not registering and providing you the additional permissions you are requiring? Are they not completing an action that could trigger virality? How far are they getting in their first user session? How much time are they spending per user session? Obviously, you'll be doing your fair share of bug squashing, but the core of it is around improving the core flows to minimize friction as much as possible. Lastly, keep in mind that even with highly motivated users, their attention spans and patience for early builds is limited, so make sure that each of your builds really make significant improvements. Happy to talk through any of this and more about mobile app testing.TW
-
Are you at risk of your competitors copying your features by building MVPs?
Yep. Although I don't think that's limited to MVPs. It's just always the case. You can copy code, features, etc. but you can't copy soul. There will always be people who copy you. It's better to keep moving forward and accept the copy cats than it would be to try and shield yourself. Keep an eye on the copy cats. But in the long run, if you're authentic and worthy, you will beat them.JR
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.