What you describe makes sense as a service on its own, but a tech consultancy doing work with a non tech cofounder longer term can be problematic: - startups,

What you describe makes sense as a service on its own, but a tech consultancy doing work with a non tech cofounder longer term can be problematic: - startups, in general, and especially before any funding, have cashflow issues. So you might deal with lots of late or non payments - non tech founders can have technically infeasible ideas, and don’t understand how hard/costly tech gets. If things go south, consultants make great scapegoats - non tech founders starting a tech company may struggle to get funding without a solid, fully committed true tech cofounder - founders in general don’t have experience with hiring software contractors. They don’t have people on staff that understand contract terms. They could sign something without understanding it, only later to get mad that they paid for dev hours on a feature the founder changed their mind on weeks later. - if the product isnt successful, consultants make great scapegoats. It’s often going to be your fault, because that’s easier than admitting the product was bad. I think for it to work you have to be someone truly committed to the founders problem space. You have to really be good at assessing whether someone’s an asshole, and likely to scare you over. You have to be amazing at building trust and showing commitment to this individual. This relationship will make or break you. It may end up not being far off from actually being a cofounder!