Sounds like you had success at the trade shows, I'm about to embark on that route too.
Can I ask how you went getting the word out at the shows, and any tips converting to a sale?
Did they mind that it was still an MVP?
I'm interested in the "Version control for data" feature. How does that work? I have data that is still changing in both content and structure. As the test suite grows, it is becoming a burden to maintain every time there is a change to the data. It would be great to be able to write tests against snapshots of the database, and be able to rollback to a different point for each test seamlessly.
Working in an industry where Manuals and Policy/Procedure documents dictate, I would also love this.
Eg. in the heavily regulated airline industry, Framemaker still persists as standard. Changes are typically made against a PDF as comments (handwritten or PDF annotations), attached to a paper "Manual Change Request" form and signed by manual owner and passed to a Tech Writer to replicate the change in Framemaker. Turnarounds in order of months are incurred, and where the regulator is involved, I have seen years.
A Git-style version control workflow would work well:
- allowing collaboration
- change documentation and approval is built in (even better if regulator can use it)
- publishing smaller amendments while larger ones develop
- reuse modules across manuals (eg. org charts)
However, uptake will occur when the learning curve is reduced...such as a well designed web UI