I used to be Director of Research at "one company that makes some of the leading legal information access products". You won't likely divorce lawyers from thei

I used to be Director of Research at "one company that makes some of the leading legal information access products". You won't likely divorce lawyers from their beloved Word anytime soon. But your approach of plain text API is not what I would call a "solution" but a mere building block that may be used in a future solution. Law firms and sole practitioners will prefer something already finished, an end product. So I would call what you called "MVP" an "advanced feature", whereas your basic solution is still not there until it has a GUI (which may have to look like Word?). I personally love plain text, but legal documents have structure that ought to be dealt with in a solution for the future. The question is how to do that, and layout/formatting - while good for rendering - is not good for representing that structure. It's good that you are working on innovating in this space; I would encourage you to talk to customers and to learn about the products in this space [5,6]. Some must-have features like templating have already been mentioned here. [1] https://mena.thomsonreuters.com/en/products-services/legal/contract-express.html https://mena.thomsonreuters.com/en/products-services/legal/c... [2] https://www.trustradius.com/contract-management https://www.trustradius.com/contract-management