Back
Pat

Hey Jo, I already responded to this but apparently it did not get posted.

I like it overall. I think, the one things that I would do is make it a bit shorter and I would try to come to the USP / your solution as soon as possible. But please note I am not an experienced marketing expert.

I would be more than happy to go into more detail and potentially help with the wording if you like. One suggestion: You could create a public google docs with the draft and enable track changes. That way others, more experienced people and maybe native english speakers could chime in.

Cheers, Pat

Hey Spencer, thank you. That really resonated with me. Just the other day I heard a podcast with Seth Godin where he spoke about the fact that humans are terrible at understanding the "sunk cost" concept. And this is so true for me. I have invested a lot of time and energy into Mission Control. It will be extremely hard to a) let go of it or b) remove features and narrow the use case. To be honest, I have already reduced the use case and removed features in the past weeks. I got carried away because I was not able to keep it simple while also creating something meaningful and different.

If you have a moment and are willing to elaborate on your first impression: Would you be able to point your finger at the part that you feel I could/should remove/reduce? What should I focus on from your perspective?

Thank you!

Thing is you don't have to completely let go of everything, you can launch and then add features later. Do you have a list of features that are done and not done? Try to remove the ones that are not done first. I personally would remove the data & analytics part to launch, and work on adding this later when you have a userbase to get feedback from on what data they would actually want/need.

Hey Jo, Thank you for you response and the warm welcome! Yes, another aspect of me building this app was to "just start" and get into the mode of doing things. I am telling myself almost every day that it does not matter whether Mission Control will be "succesful" (whatever that means) or not. If I just keep going, something will come out of it. Whether a completely different idea, the people that I get to know along the way or the knowledge that I am gaining now about new things. I was thinking about going (back) into IT Consulting. I worked 7 years for one of the bigger IT Consulting firms and I could see myself working as a Freelancer / Consultant in a particular field which I think is totally underserved and will become bigger in the next years (Funny enough, it is close to what you suggested in your first sentence)

Let me know if you want to have a chat someday. I have never used Telegram before but you can find me if you search for Pat_BMC.

Cheers,
Pat

Hey Ebrahim-Khalil! Thank you. Great advise which reminded me of a plan I had set before I started working on Mission Control. Unfortunately, I did not stick to that plan because I got lost in technical challenges (big mistake, I should have at least dedicated 30%-50& of my time on e.g. building in public from the very beginning) I made the experience that for me personally short work sessions (i.e. 30min, 60min) don't work. I just never stick to the time windows I scheduled.

What worked better (still not perfect but better) for me is to schedule "work weeks". For example, 1 week of building the product, 1 week of promoting the app, reaching out to potential users, 1 week of writing etc, etc.

I will start doing this again now and will spend some time today on how I want to structure each month in weekly chunks.

Question: Can you elaborate a little bit more on how you plan to automate your marketing? And, what things should one focus on from a marketing perspective in the beginning (i.e. what would bring the best "bang for buck" /"bang for energy/time") in your opinion?

Hi Pat. I like the idea of "work weeks" - provides focus on activities. I am new to automating marketing. I am starting with basic email series. For example, a user subscribes and receives a set of tutorials via email.