D.S.

Take us to the moment you decided to build this — what were you doing and what triggered it?

The current product only exposed API to generate E-invoices via Tax Authority network. This requires a complex integration and know-how of every field in XML to be able to test a happy flow or put E-invoice issuance at work in user's compliance practice. The sales cycle extends due to POC integration and if onboarded then value realisation takes another month in integration. So, why not have a simple way to test company's excellent E-invoicing solution or even put to use if you have low volume usecase(which is for any size of company when the mandate gets rolled out)

What did you explicitly decide not to build, and why?

No hard business rule validations or orchestration or transformation on user's input. API product does it downstream. Reduce complexity in the build and user experience

What did you discover after you built it — from using it yourself or from showing it to others?

The assisted guidance via inline validation is a showstopper. Surprisingly even large enterprise loves it as it makes things clear on what data of transaction fits where in first try.

When did you last open it, and what for?

Last opened it a month ago to replicate the product in the company's central platform