Duncan Knight 

If you are a non-technical founder with an idea for a product, hiring a developer can feel like the obvious first step. Sometimes it is the right move. But before committing to a permanent hire, get clear about what you need to learn, what needs building and who will make the technical decisions. A prototype, a short development project and a product serving paying customers create different demands. They may need different kinds of support. Start with the work and the respon

A business plan can describe an attractive opportunity and an ambitious growth target. Someone still needs to do the work. The team section should explain who is responsible today, which capabilities the business needs next and how you intend to build them. It is also a useful moment to examine your own role. As the company grows, the work you keep doing may prevent other people from taking responsibility or leave important decisions waiting for your attention. Here is how to

What will your product do? Who is it for? How will you know it is useful? Who will build it and what will it cost? These questions belong together. Your product development plan should connect what you intend to build with the customer need, the resources available and the evidence you want to gather. It should help you make decisions as well as explain your approach to someone else. For founders, that means being clear about what needs to happen next without pretending you c