1
2 Comments

Tools that enable an early stage founder to build strong engineering practices early

As a founder of a tech start up, your ability to iterate on product is critical to the success of your business. It's all too easy, under the pressure of delivery, to make mistakes in how you build your engineering capability. This often leads to significant difficulty to iterate as your team grows from 0 to 6 or more (more is out of scope in this instance)

I've been working on a product that provides practical guidance to a founder who has never established an engineering culture. The outcome of this guidance is that founder having ability to iterate at an increased rate as her engineering team increases in size

What are your thoughts? Would this be a valuable service?

Any guidance appreciated!

on February 6, 2020
  1. 1

    I am skeptical. When non-technical founders ask me for advice, I often say: ignore the tech bits for as long as you can and figure out marketing and sales because those are really hard.

    I want to say that most businesses change a lot before they get to $1M ARR, so there is a high chance that they will need to rewrite their software at some point around when they have a full time team for 4-5 developers on the startup.

    Can you give more details on what/how your product would work? Perhaps there is an opportunity for a list of tech tips based on the type of startup and the where you are in the traction stage.

    1. 1

      Thanks Vineet.

      I agree that a company is likely to need to rebuild at around that stage. What I'm suggesting is that in that scenario, the founder would be in a far better position if his engineering team of 4 have established really sound engineering practices prior to embarking on such a rebuild

      What you've suggested is vaguely what I'm aiming for, but with the addition of data driven advice for the founder.