I have launched some micro-saas products for B2B to give you some background for me. Here is what I typicality have in place for a private beta: 1) Intercom for

I have launched some micro-saas products for B2B to give you some background for me. Here is what I typicality have in place for a private beta: 1) Intercom for easy communication in-app 2) Google Analytics for general page tracking 3) Amplitude for tracking granular user actions 4) Rollbar for tracking errors when users don't report issues (you would be surprised how often users don't communicate small or even larger issues to you) 5) I make sure I have some basic self-help tools in the app for betas such as password resets, etc. That is it for basic tools I've used for SaaS betas. As for the private beta itself, I always try to schedule some in-person meets, or virtual screenshares once a week or every few weeks to get a list of issues, wants, etc. that each user has about the product, I then compile all of that feedback into Waffle or Trello so I can get a count of which issues are the most pressing or most requested. As for the funnel, I am not entirely sure what you mean, but as users give me feedback and as I work through their issues / updates I try to position the conversation as if we fix X, Y, and Z or add X, Y, and Z will you pay us (whatever amount) for the subscription. It's good to get them to commit to the next step even if its 6 months out. Also, yes it is completely okay if you take invoices vs. having an automated system. They should understand where you are at since you are not officially launched and be empathetic to that, if not, they are probably not the best fit for the beta. The biggest expectation is they are their to provide you with valuable feedback so you can make this the perfect tool for them an any future customer that looks like them. Hope that answers all of your questions.