[streetcat1]

So lets look at de risking the company offering.

If the company is derisked from the product side (even tough there is ton of work left) than you are like any other employee . If, on the other hand, you have some sort of a proprietary knowledge that is still needed for de risking to occur, than you have leverage.

When I read between the lines, I see that the CTO already derisked the product in the two years prior, and its looks like the CEO is derisking from the market side (i.e. have traction).

[hangryhippo]

Thanks Streetcat1! What would you consider as derisking? I think the product is still at conceptual stage with most major functionaility not yet developed. Would that be considered derisked?

[streetcat1]

So I am not sure what is your domain and what are your core uses cases. Derisking from the technical side for a typical web app is :

1) Is the API defined (if any) and implemented. Do you understand the domain entities. Do you need any outside knowledge to understand it.

2) Is the basic architecture standing? For example, division to micro services, GRPC interface between micro services.

3) Are the core 1-2 use cases implemented end to end ("tracing bullet"). I.e. from some sort of UI up to record in a database.

4) If you have any propriety algorithm, is it implemented.

5) If you have any propriety data (e.g. real estate listing), do you have the data and understand how to get it.

So if the functionality left is trivial (e.g. CRUD) than they can do it without you, hence they have the leverage.