Not knowing tech can be an advantage—naivety keeps you focused on outcomes instead of implementation constraints
James wasn't technical, but he looked at WordPress Multisite and thought 'I think that's got the same DNA as a SaaS product—central database, separate secure installs, user authentication.' His developer built a custom layer on top for £4,000. Technical founders would have said 'WordPress can't scale' or 'that's not the right foundation.' James just focused on the outcome: does it solve the problem? The product never creaked—not at 100 customers, not at 500, not at 1,000+. Naivety can be a superpower because you don't know what's 'impossible.' You just focus on getting to the outcome and figure out the path. Technical knowledge is valuable, but it can also create artificial constraints that prevent you from finding creative solutions.
When to use
Use this mindset when you're tempted to overengineer or when technical people tell you something 'can't be done.' Instead of accepting constraints, focus ruthlessly on the outcome you need and explore unconventional paths. Sometimes the 'wrong' technical foundation is right for getting to market fast.
Don't do this
Using lack of technical knowledge as an excuse ('I can't build this because I don't code') or, conversely, letting technical knowledge prevent you from pursuing simple solutions ('WordPress isn't scalable enough for a SaaS'). Naivety is only valuable when combined with resourcefulness.
1 Founder Who Did This
Had no accounting background but combined marketing expertise and magic performance background with Paul Barnes' accounting methodology - naivety kept focus on outcomes rather than industry conventions