First step... Advice appreciated!

Hi all,

I've been running around with an idea for waaay too long and need to take this first step... Please bear with me...

Short backstory: I'm a freelance Consultant in the European/Dutch high tech industry, guiding and teaching organizations on how to define and manage product requirements.

One obstacle that is hard to remove, is to get the quality of the Requirement consistently high. I believe that it's not through a lack of knowledge on the authors part, but due to the time pressure they face.

A few years back (yes, that long) I thought about doing something about this; helping requirements engineers to write better requirements efficiently. This can be done by using requirements boilerplates (look up 'Easy Approach to Requirements Syntax', or EARS, if you're interested); predefined textual formats that are clear and concise and leave the author to think about the content instead of the formulation.

A while ago I decided to put thoughts into action. So, what am I working on? It's called Boilah; an on-line boilerplate-based authoring tool where the user can select from a range of predefined, configurable boilerplates and fill in 'the blanks' with their expertise. Then, they can quickly copy-paste the full text into whatever tool they are using to manage the test (e.g. Word, JIRA, or a specialized Requirements Management tool). This application independence makes it unique, in my opinion, and very flexible.

The neat thing is, the concept works for Requirements, but also for User Stories, Product Vision statements and Test Cases/Acceptance criteria (each of which could be managed in different applications...). And that's just the 'Product Definition' area. I can imagine (but have no feedback, yet) that the concept is applicable in different fields, too; anywhere where people are writing 'standard' texts where they need to make choices and/or fill in the blanks.

Oh, and data security is not really an issue (a concern for some big companies I've worked with) as the actual authoring is all Front-end only and does not go to the server... (with minor caveats)

Okay, so where am I now?

• The website (https://boilah.com) is live, but I feel it can do with some work.
• I have an MVP locally, but I'm working on improving the UI. Once this is done, I can include screenshots on the website.
• I'm working on the Backend API in parallel (user/team/account management, personal preferences, save some specific data)
• There are many future enhancements and features in the pipeline already, so there's room to grow.

BUT...

I'm still really at the Validating stage... So I'd love to get your feedback on the whole thing.

• Does the whole thing make sense? Does it resonate?
• Does the website explain it properly, do you think?
• Do you know any other areas where this can be applicable (real-estate agencies, medical/doctor's offices, ...?)

What next steps would you suggest?

I really appreciate the feedback/encouragement/reality checks!