BleedingCoffee
PARKED
First off; I'm new to this forum and just finished reading the book. I have over the years continually seen and recognized problems and have had those thoughts such as: if only someone would or I can't believe we still do things like this... I have been working in my industry for the past 15 years started at the very bottom of the organization and currently have 300+ employees under my responsibility as I manage $200+million dollar projects. My career drivers and pay are good; but not fastlane great. And I have always felt there is more than this to life. Over the last few months I have keyed in on a major problem I see that plagues my industry, its an old world problem and something that will always be required unless mankind stops evolving and growing. I feel I understood some of the base principles that MJ talks about in his book and had started analyzing the solution I see to a major problem, but after reading the book I feel I have a much better understanding on the process required to solve this industry problem.
Sorry for the ramble - just felt it would be a good small intro for who I am and where I am starting from. So off the the question...
Currently I am still working in the industry as I feel at this stage it will help allow me to be in the loop to investigate and ask my peers on how they use specific tools, etc to better my design. Further, I still need to feed, house and clothe my family. I currently am developing key outlines on the overall end user need to the solution, taking this information and developing process flow and high level design. I have not hired or engaged a design and programming team to build prototypes or final solution; although I have started investigating and researching a couple individuals that have come recommended.
Here is my question: The solutions I have are large in scale opportunities, but could be implemented at various levels of magnitude. Also could be continually developed from small magnitude to large magnitude. This is where the question comes in:
Do I:
a. spend the time to develop a full blown enterprise level solution (but not market as such), which would need large capital and time but solve multiple of related problems in the industry. est 2 years+ startup time prior to launch.
b. start small; build a limited functioning solution that answers key parts to a problem but not some of the bigger issues, release that, generate revenue with proof of validity, and then continue to grow the solution to further full potential similar to how c. (below) would grow. Key here is starting much smaller - est 2-3 months startup to launch.
c. Solve one solution fully through a cycle of process flow on that issue; then build the additional interrelated solutions and have them tie back into each other to grow one integrated solution. est 6mo-1yr startup to launch.
Any advice and discussion would be appreciated!
Sorry for the ramble - just felt it would be a good small intro for who I am and where I am starting from. So off the the question...
Currently I am still working in the industry as I feel at this stage it will help allow me to be in the loop to investigate and ask my peers on how they use specific tools, etc to better my design. Further, I still need to feed, house and clothe my family. I currently am developing key outlines on the overall end user need to the solution, taking this information and developing process flow and high level design. I have not hired or engaged a design and programming team to build prototypes or final solution; although I have started investigating and researching a couple individuals that have come recommended.
Here is my question: The solutions I have are large in scale opportunities, but could be implemented at various levels of magnitude. Also could be continually developed from small magnitude to large magnitude. This is where the question comes in:
Do I:
a. spend the time to develop a full blown enterprise level solution (but not market as such), which would need large capital and time but solve multiple of related problems in the industry. est 2 years+ startup time prior to launch.
b. start small; build a limited functioning solution that answers key parts to a problem but not some of the bigger issues, release that, generate revenue with proof of validity, and then continue to grow the solution to further full potential similar to how c. (below) would grow. Key here is starting much smaller - est 2-3 months startup to launch.
c. Solve one solution fully through a cycle of process flow on that issue; then build the additional interrelated solutions and have them tie back into each other to grow one integrated solution. est 6mo-1yr startup to launch.
Any advice and discussion would be appreciated!
Dislike ads? Become a Fastlane member:
Subscribe today and surround yourself with winners and millionaire mentors, not those broke friends who only want to drink beer and play video games. :-)
Access Restricted: Unlock 1,000,000+ Posts
Stop Peeking Through the Keyhole.
Open the Door.
You hit a wall because the best advice isn't free—it's earned. Since 2007, MJ DeMarco has been active here daily (99.9% active rate), building a war room for entrepreneurs who refuse to settle for mediocrity.
- Active Daily: Life-changing content posted dozens of times every day. No dead threads.
- MJ's Inner Circle: Direct access to the author of The Millionaire Fastlane.
- Vetted Network: Connect with founders scaling to 7 and 8 figures.
- Proven Roadmaps: Strategy over motivation. Execution over "hustle porn."
"SCALED TO 6-FIGURE MONTHS"
"Tips and advice here saved me from huge mistakes, others allowed me to scale my business to 6-figure months."— User MitchC
"INSANE QUALITY OF PEOPLE"
"The number of high quality people I've met from this forum has been insane. All of it predicated on building real value."— User Richard Peck
"You are the average of the five people you surround yourself with."
Are you surrounding yourself with success?
