Started 3 other companies in Canada.
Worked at BlackBerry. Managed teams.
Ride motorcycles, fly airplanes.
If you're looking to understand better how you can integrate blockchain in your product, or if you're looking to develop your idea of a Decentralized Application and do an ICO, ask away!
I've been running Blockchain meetups, contributed to Ethereum standards, and created multiple Decentralized Apps using Solidity and web3.js
If you're looking to add ML or specialized AI to your product or looking to get more actionable (and profitable!) insights from the data you already have, let's talk about what is possible!
I have more than five years of experience with Hadoop, Spark, NoSQL, Tensor Flow, and other ML/BigData systems, and I know how to build them right.
I will discuss your project with you, no matter the stage you're at: from developing an idea to facing 10m+ users scalability issues.
I will tap into my expertise starting, and scaling companies, managing products, projects, and teams, and will offer actionable insights and advice.
I migrated, built, and scaled cloud deployments supporting millions of users and tens of thousands of requests per second.
I will help you with anything cloud-related: from using new cloud services to integrations to scaling.
You need to support your family somehow, and securing finding is not a fast process.
I'd definitely suggest you look for a job or contract work at this point. It will at least support you while you're searching for funding of your startup.
Be prepared to pivot though, because it might be so that your idea - however good it is - is not viable to build a business upon.
For the teams I've been working with in the past, a "lightweight Scrum" was working the best. "Lightweight" means that we won't have a formal planning poker or face-to-face daily stand-ups, or sometimes even points estimation.
What we'd have is bi-weekly planning, tracking, and asynchronous reports (What was done yesterday? What you plan on doing today? Is there anything that's blocking you?)
We would also iterate fast, and make sure we adapt if something unplanned comes up.
Having been working with dozens of teams - both local and remote - I can give you some more specific tips on how to improve the velocity of your current team, but I'd need to know more details :)