Loading...
Answers
MenuHow do I run a successful closed beta for my web application that is almost done with development?
YouthCloud is a management application for youth ministers. It allows them to track basic student information, but also has useful goal setting and accountability functions. Initial development will be wrapping up next month.
Answers
Create an ideal customer profile. Create some questions that will allow to you survey a potential tester to determine if they fit your profile. Design simple landing page with very clear value proposition that speaks to your ideal customer.
Ask for a minimum of information up-front (email), but ask for more info after they commit by submitting the first piece of info. (KISSmetrics does a good job of this on their current website trial signup).
Use the their answers to these profiling questions to put the applicants into buckets. Let in the most ideal bucket first, or split them into groups if they're big enough.
Try and measure engagement the best you can. Measure qualitative and quantitative data. Schedule calls with your beta testers to find out more, especially with the ones who's user behavior seemed to indicate that they didn't get value from your product. Find out why. Make sure they are indeed your ideal customer. Pick up the phone and get to know your customers inside and out. Meet them in person if possible. Incorporate their feedback quickly and get more feedback. Rinse repeat.
The first thing you're going to want to do is better "gate" your sign-ups. The fact that you're not trying to learn anything about who is signing-up by either providing different CTA's on your landing page or by offering them a quick survey for faster access, means you won't know which users' feedback is closest to your "ideal" user.
In early experiments I've run like this, we've seen a 5 question survey get between 20-30% response rate as a means by which to get faster access to the product, so absolutely worth doing.
I like to run different types of users through a closed beta. "Patient Influencers" are people who can lend credibility to your business when in launch (either by testimonials, press, access to potential customers or investors) and the other are your most "real" users. What you're most looking to do is collect that product feedback and look for where these two groups' feedback overlap.
I have a lot of experience in early-stage product ideation and guiding it to product/market fit. I'd be happy to give you some more and contextually-relevant guidance in a call.
Do you have specific concerns about running a closed beta, or are you just generally trying to be prepared for it?
Ideally, you would know or seek out an initial group of youth ministers who might be interested in using your application, interact with them directly, perhaps conducting some usability testing in person, but also monitoring their use of the app and continuing to work with them directly throughout the beta.
If you are successful at convincing these ministers of the value of your web application, they will help you convince others, which is usually the best way to grow. You might even select some of these initial customers to join a customer advisory board over the long term if that ends up feeling useful.
If you have concerns about scale, you can always move from a closed beta to an invite-only beta that helps you manage scale, but I'm not certain that's going to be one of your immediate problems.
I believe this link will give you all the help you need: https://medium.com/swlh/how-to-conduct-a-closed-beta-testing-with-zero-budget-acd19c2de43
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
What learning path do I have to take to become a "full-stack" web developer?
If I was just starting out, I'd consider learning Meteor (https://www.meteor.com/). It's just entered version 1.0 and after working with it for a little less than a year I do have some issues with it but it still makes for a very solid framework that gets you up and running very fast. You would only need to learn Javascript, and you can slowly work your way towards nodejs from there (which Meteor is based on) if you want to, or you could get the basics down and focus on learning design if you prefer.KD
-
How do you manage a developer who's slow, especially when you have a small budget and you don't feel like you'll get things done in time?
Usually Programmers are only slow when they don't know how to solve a particular problem. So they will spend a lot of time researching and a lot of trial & errors to solve a problem. It is important that before you engage a programmer on a project, you break down the entire project into simple, easy to understand modules. Let him give you an estimate of how many hours he will require to complete each of the modules. Example: a typical site will have a login module, registration, My account, profile etc. So let him estimate how much he will require to do the login. You can go even detail here. (e.g. how much extra time if you were to implement Facebook/Twitter Login?). Once he start developing, track his progress closely and make sure he is following his given timeline. If he goes over his budgeted time on a module, talk with him and see what went wrong. It is often seen that they may be wasting their time on something very insignificant that you may have asked him to implement, but you can totally go by without it too. So by understanding what is taking longer time, you will be able to prioritise things better. You definitely need some tools to get this done. Google Spreadsheet or Excel works just fine. But if you don't mind spending a few bucks there are many agile project management tools that you might look into. Here is a list, google them all and sign up for trials: * AgileZen * Agile Bench * Assembla * AssiTrack * Blossom * Basecamp * Breeze * DoneDone * Eidos * Fogbugz * GreenHopper * Jugggla * Kanbanpad * Pivotal Tracker Or the reason why he is slow can be purely non-technical. Sometime your developer may don't share the same level of enthusiasm as you about the idea that you are working on. They often don't often see the "bigger picture" (since you don't share everything with them explicitly). If you can somehow get them excited about what he is a part of, it will work like a drug :) He will work day and night without questioning you. But you need to work equally as hard as him. The moment he sees that you are the boss and he is just the guy doing work for you -- his mentality will shift from being part of something to being the low paid developer. Ultimately its all about motivation and making him a part of your venture. After all he deserves it, if he is really playing a crucial role in the entire development.SK
-
How do you take an app idea and turn it into an app? Who will help make the app? How do you connect it through social media? How much does it cost?
Having gone through this multiple times either in new startups or for side projects, here is how I would approach turning your idea into an app. 1. Defining the Minimum Viable Product Your first goal with any new idea should be about proving the idea and finding a market that wants the app you want to build. Achieving that quickly is probably one of the most important thing. To achieve that, you will need to write the specifications that will constitute your MVP. The MVP is basically the simplest expression of your idea to prove it. This step should not cost you much as you can do this on your own. 2. Design the app Before starting any development work, I would suggest you work with a good UX/UI designer to create wireframes and mockups of the app based on the specifications you came up with in step 1. You can find good designers in meetups & hackathons or on website like Dribbble or 99designs. If you want to reduce your costs, you can give shares in the project to the designer. Otherwise, it really depend on the size of the MVP but I would say it will probably cost between $5K-$10K. 3. Develop the app Once you have the specifications and the design of the app, you now need to find a good developer that will build it. Again, you can find good developers in meetups & hackathons or on sites like Github. If you want to reduce your costs, you can give shares in the project to the developer. Otherwise, it really depend on the size of the MVP but I would say it will probably cost between $10K-$25K. For this part however, I would recommend the developer becomes part of the project as his engagement will most likely be higher. 4. Test the app This step is not only about making sure the app is bug free, it's also making sure the app does what was intended in the specifications. To test the app, you can use platforms like BrowserStack or SauceLabs which gives you access to multiple devices/browsers. You can do this step on your own so the cost will be for the subscription to the test platform which would be around $100/month. Hope this helps and good luck with your project.VL
-
Which is the best hosted free bug tracking tool for a team size of up to 10 members?
Being a freelance developer for the last 10 years or so, I have seen and used almost every project management software you can think of, open-source and closed, and I have found that the "best bug tracking tool" completely depends on your process. I employ and direct teams in an Agile process that involves loose story-based requirements with point-based estimates, two-week cycles of iterative development, planning and retrospective sessions, and look-ahead and show-and-tell meetings with the stakeholders. It's important to me, then, that my tools have a method of capturing all those pieces with as much detail as I need but no more. On projects, I've successfully used Pivotal Tracker, Unfuddle, Redmine, Codebase HQ, Basecamp, Trello, and many others. I usually recommend people to Trello for light, agile management; it's essentially a digitized version of sticky notes and swim lanes. If your team actually needs a full-featured ticketing system, see Redmine (Rails), Trac (Python), or Mantis (PHP), depending on your language preference. Hosting a version of these yourself is fairly trivial, and numerous options exist for cheap or free hosted versions. For something in the middle, Github Issues is a good fit and the open-source clone GitLab.org replicates most of those features nicely. However, if you're looking for a hosted version, you're probably looking to offload that tricky "backup" thingy, and in that case, how important is your data? How proprietary? What's your business model? If you're working on an open-source project, Github will give your team a free account with private repos, issues, wikis, and the like. If you're okay with your project being "readable by all", public projects on Pivotal are still free. I'm mostly a consultant these days, leading small groups of junior or intermediate developers into a more productive, more mature, fully operational teams of senior software developers. One of the first things I teach folks is how to use a project management system... and why! It'll save your bacon if it's simple, effective, and reliable. With a few minutes of discussion about your project, I can probably help you select the right tool and service for your team. Let me know if I can help with that. Best of luck!DR
-
How should the dynamic between a ux designer and a developer who are working together look like?
It depends a lot of in the skill sets and experience of both people but in most cases the ux designer should be controlling the developer pretty heavily in order to make sure his ideas come through properly. The UX designer may just need to work on his approach so people don't feel bossed around and more like they are working together. In an ideal world, there would be a project manager who makes sure everything is communicated well and keeps the dynamic feeling great.JM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.