It's hard if you think of it as an afterthought. It's easy if you keep it in mind from the start and choose your stack and approach correctly from the start.
That's usually the problem with startup software - most if startup engineers will rather burn 10 hours coding that 1 hour thinking and choosing the right things.
What are some examples of the right things to choose? Are you thinking in the direction of technical decisions (e.g. the right programming language), or more about product design decisions?
That's usually the problem with startup software - most if startup engineers will rather burn 10 hours coding that 1 hour thinking and choosing the right things.