The number is not about &quot;Should I rewrite or not&quot;, I should have made that clearer in the post.<p>Some thoughts<p>&quot;Is low good or bad?&quot;<p>As it is a risk in your book, first it&#x27;s good to know.
Is low good or bad? Depends on your strategy. Fast time to market with a rewrite after Series-A, low seems good. Low growth, tight margins low seems a high risk to me.<p>&quot;What is the value of being able to migrate to another system?&quot;<p>I don&#x27;t know why people migrate or are forced to migrate, it depends on your situation I guess. From following HN people seem to rewrite their systems all the time. From working at startups as CTO, one reason to rewrite seems you can&#x27;t get the current technology stack stable (e.g. Web Framework does not scale for your type of business) or you can&#x27;t migrate your tech stack to a new version.<p>&quot;In additon, this number has no intrinsic value component.&quot;<p>Often when talking to CEOs they are suprised that they need to pony up some millions to completly rewrite a system because it can&#x27;t be upgraded to a new version of X, which they haven&#x27;t got in their budget and planning of their long term margin growth.<p>You&#x27;re right about the &#x27;improve&#x27; wording, I&#x27;ll think about a more neutral term. Same I&#x27;ll rethink the KPI wording.