— 2 min read
15 Tech Mistakes that wasted my time and money for FREE.
Starting a tech project as a non-technical founder can be difficult, and there is an apparent lack of resources online to help educate and save founders from making mistakes.
Here’s a list of mistakes other non-technical founders have made as a starting point in avoiding the same mistakes! If some of the terminology doesn’t make sense, don’t worry —this is only meant to give you a sense of the different issues that come up to look out for.
- Started my tech project as a SPA when SEO was a critical and important consideration, so we had to re-implement several pages using a different framework that supports SSR.
- Used AWS to host our servers and cloud infrastructure, costing around $600/mo when $150/mo was sufficient to get the same deployment using different services
- Had a developer spin up a server, and they didn’t leave any documentation on what was installed or done to deploy the application to production
- Didn’t check to see if my brand name was available as a .com domain before designing
- Hired a PM that essentially did nothing
- Launched a static landing page website on Kubernetes
- Didn’t have my code on Github, so when my developer left I couldn’t have a new developer look at the code
- Hired an outsourced agency, paid them 10k, and got a buggy product that didn’t work
- Hired an outsourced agency that developed the product in an unknown and outdated tech stack that no other developer understood
- Paid 100k for an ecommerce store build-out that amounted to two pages, didn’t write any penalty clauses for missed deadlines, product features, bugs, etc.
- Had a developer manually implement the admin panel, taking around 15-20% of their time along-side the actual website
- Decided to manually handle email, payment processing, or other staple pieces of functionality instead of using a paid $/monthly service to manage it for us
- Had a developer manually implement API/Graphql endpoints
- Didn’t use a CMS system so I have to ask my developer to make copy-based changes on the site constantly
- Hiring more than 2 developers thinking it would make my project finish faster