What the tool does
You describe the application, it builds it and puts it online. Every change is asked for in plain language and is seen immediately. The project stays recoverable, which sets it apart from a simple demonstration.
What we do with it
We use it for the phase where you have to show rather than describe: a main journey, a few screens, enough to put the tool into the hands of three or four people and watch what they do. The conclusions of that test are worth more than three meetings.
Its limits, said straight
What is generated quickly is rarely structured to last. As soon as the product has to handle real data, access rights or growing load, the foundations have to be rebuilt. We say so beforehand, not at invoice time.
