We create new videos weekly to help startups overcome their tech challenges
Have a challenge that you would like to share?
Just click below and I’ll answer it in my next video
Joel and his cofounder have already developed the first version of their product. They are now tackling Version 2, and are considering outsourcing some of the development to a Web agency.
Tatiana already has a first version of her solution. She is now conducting meetings with large companies in order to sell high-ticket access.
Joel and his cofounder already developed the first version of their product. They are now developing their Version 2, and are considering outsourcing the graphic design to improve the user experience of their app. The question they ask themselves is, how should they organize the development so that the designer and the developer could work effectively together?
Jerome and his cofounder already developed the first version of their product. They are now accelerating the business side of things and are wondering if they should consider getting their external CTO—the director of the Web agency that developed their solution.
In the previous video, we talked about the advantage of cloud solutions versus server hosting. But life is not that easy, especially when it comes to software development. To take full advantage of a cloud solution, an application needs to be tweaked for a bit. And that is where I would like to introduce the concept of a stateful and a stateless application.
Sacha and his cofounder already developed the first version of their product. They are now undertaking the Version 2 of their development and are considering moving to Amazon Web Services (AWS) as their cloud hosting solution.
Philippe already has an artificial intelligence developer on his team and he needs someone with complementary skills to develop his startup’s Web SaaS solution. Now he’s wondering if offshoring as a non-technical founder would be a reliable way to develop his startup‘s product.
Colette already has a great offline business with its own practitioners network. Her business is growing and she is about to develop a new set of tools to systematize her ecosystem and bring her business to a scalable level. She has already written the specifications to create both the Web and the mobile app. It’s now time to evaluate the developer’s proposal. Let’s see what a good one should contain.
Stephane has a huge experience as a consultant, with lots of knowledge and know-how to systematize. That gave him the idea to build a Web platform that could facilitate his clients’ work and enable them to reach their goal almost automatically.
Colette already has a great offline business with its own practitioners network. But since her business is growing, she needs to industrialize the way her team works, provide the tools to better organize meetings, and give more advice to her clients. After interviewing several software providers, she was exposed to multiple solutions to build the mobile-accessible interface she had imagined.
Olivier was able to build his first team with freelancers, and he relied on this option for several months. But he found it difficult to manage people remotely, and ended up hiring local developers to be able to keep an eye on them in his office. It is possible to build an entire team exclusively out of remote workers. But it entails changing everything we’ve learned in the past few decades about managing a team.
Ahmed is working with a freelancer to develop his e-commerce solution. He wants to raise funds to help the business grow. But investors don’t consider his project because he doesn’t have a technical co-founder. To help Ahmed move forward, let’s analyze the situation.
Marie is working with a freelancer to build her Web platform. She wants to add a chat so that users can have one-on-one conversations and create private chats about different topics. Her freelancer is wondering if he should develop his own solution from scratch or reuse existing software.
You might think that as a startup, you shouldn’t be concerned with such a heavy process… right? Think again. What if your hosting provider disappears? What if you lose your app’s source code? Don’t you think you might need a properly documented technical procedure to recover it? You definitely will. There are dozens of reasons to use a disaster recovery plan. The interesting fact is that if you face a major disaster, your business has a 90% chance of dying if you do not have a disaster recovery plan (DRP)! To figure out a DRP, you need to establish a few things.
Ronan and his team recently developed a new solution. This solution went through the pilot phase and now needs to be deployed for large companies. But large companies’ expectations are usually higher than those of startups’. So to make it through, let’s see what high expectations entail and how to achieve them.