How to Conduct a Closed Beta Testing with Zero Budget

1.5 Months, 100+ Companies, 20 Industries — KeepSolid Sign Story.

The goal of this post: incrementally show how we conducted a closed beta test for KeepSolid Sign from scratch — within a limited amount of time and with limited resources. So if you are a startuper, marketing specialist or an entrepreneur, interested in giving your MVP or beta product into hands of first users, stay awhile and listen.

Photo by Japheth Mast on Unsplash

When developing your own product, it would certainly be cool to do everything like Hotjar did.

But what if you’re more limited in time, people, resources, and budget?

And if, despite that, you still want to let first users test your product to gather valuable feedback from them, while you’re still in the development phase?

This is exactly the situation we had, when we were deep in the development of our latest app, KeepSolid Sign.

It is a cool (obviously) service for e-signing contracts and other documents. At that point, we had a bit more than MVP for three platforms — macOS, iOS, and Android, so we decided it’s time to conduct a closed exclusive beta.

We’ve only had up to 2 months (actually took us only 1,5) to complete it, since we’re planning an open beta for 4 platforms (Windows included) and a web application by the end of September.