Here's a little curve-ball from the usual dev oriented discussions on dev.to - how do you prepare for investor technical due-diligence?
Little background, I've been working as senior/full stack dev for a QA company from UK for last 6 years, been with the company pretty much since it first started. We use in-house developed issue management web-app to collect defects from remote testers, review in house, then report valid categorised issues back to client.
We're at the point where business runs comfortably, and founder is now looking for potential partner(s) to take the company to the next level. Part of that process is of course partners getting someone they trust in for technical due-diligence.
I wonder if anyone has any tips or first hand experience on best way to prepare?
One slightly concern I have due to our previous CTO, who was with us very briefly, stating that our PHP/CodeIgniter solution wouldn't scale and investors would want to re-write it as default anyway. For record, being old-school Java guy, he didn't like NodeJS either, so we were in technical-direction-limbo for about a year.
Other than causing the damn impostor syndrome to kick in, I'm now trying to defuse this proactively.
Being biased, of course, for me the app runs smooth even on lower end AWS instance (2-3% CPU) without us ever specifically doing any optimision on the code or architecture - so we def still have some dev-tricks in the bag and we can still throw a lot of hardware on it.
However just saying "meh, it'll be fine" is not what any auditor would want to hear, regardless if they are biased towards technology or not.
I'd personally refrain from complete rewrite, let alone rewrite in different language, based on app size and existing in-house skill, but if the change is needed, I'd rather do it now and be in right place in 1-2 years than going down the wrong path and running into existential issues later.
Would it be enough to reverse-engineer very top end estimated user count from revenue targets (knowing how many users we need to deliver a report, I can figure out how many projects we need to deliver to reach revenue targets, etc), prove that we can handle these numbers, and/or list specific ways we would improve the platform when hitting these numbers?
Aside of that, I assume the most important thing over anything else they want to see is our ability to grow from dev side (bluntly, putting that investor money in effective use).
Therefor our time from now on might be better spent on making sure we have greater separation of concerns, more documentation, more structure in place for existing tech stack to quickly and effortlessly on-board either fulltime devs/designers or freelancers. And/or have feature/changes roadmap in place, just waiting for that extra dev resource to quickly implement the changes.
Any comments on this topic welcome.
First time poster, so please be gentle :) Cheers.