How would you quickly prototype/test a service that usually takes place over several months?

Look on Google Communities for technology focused BETA testing groups... Look on Linkedin Groups for business focused potential testers... Look on Facebook Pages for people who like apps/companies like what you are trying to bring to market... That should get you started.

You can try here, there will most likely be some 'experts' in the mix of people that check it out. https://www.reddit.com/r/AlphaAndBetaUsers https://www.reddit.com/r/NewProducts Also, I would do a search through Clarity for 'wordpress' or 'video' and book a call with someone that's an expert in the field. Send a link via a Clarity message and they might have time to check it out briefly before your call, and then they can also go through it with you on the call. Other than that, you could google blogs about wordpress plugins and contact them. best of luck, Lee

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.

You can get real people to interact on a site like usertesting.com — it's a paid service to get you real feedback from real humans. If you want access to your demographic, you'll need to find out where they hang out and come up with an offer to encourage them to try your service (a closed beta, free access in exchange for submitting evaluations and feedback, etc.). Ads and/or sponsored posts could be useful here. Or you can set up your own user testing arrangement and offer to pay people a small amount in exchange for using the app. This should probably be your last-ditch effort, though. Good luck!

While you are considering bringing all the Content Marketing & Measurement features and capabilities together with Project Managment ( I am assuming some type of cohesive management Dashboard with combined analytics ?), you might want to consider the following: - the integrated product should not make it a challenging user experience overall - is this something the customer/client needs, do you have relevant feedback to validate such a move ? - what might be the benefits to the platform & users by such a change It is hard to comment regarding APIs without more context on your goals. I have leveraged publicly available connectors & API modules to connect CRM, marketing automation and payment functions successfully. Happy to discuss further over a call and address your questions