Stage three
A site,a dashboard and the machinery that runs the thing.
The written description becomes three real surfaces: a website on castomUI, an operating dashboard in dash-b, and the workflows in castomFLOW that do the actual work. Not a mockup between them — three products you can open, edit and switch off.
These three are built from the same document, in parallel, by three systems that were designed to sit on the same shelf. That matters more than it sounds: the labels on the dashboard match the words on the site because both were generated from the same paragraph, not because somebody remembered to keep them in step.
Everything below opens in its own editor afterwards. castoMIND assembles the first version; it does not own it, lock it or require you to come back through castoMIND to change a heading.
Three surfaces
What gets built,
and by which part of the family.
The website — castomUI
Pages, copy, brand, published at an address. The copy is written from the description, so the site argues the case the document argued rather than the one a template assumed.
The dashboard — dash-b
The board the product is run from, laid out on day one. dash-b is a live dashboard designer that speaks 86 languages and fills itself from the platform underneath.
The workflows — castomFLOW
The steps that actually run it: the order that becomes an invoice, the reminder on day three, the nightly reconciliation. Deterministic where determinism is right, AI where judgement is genuinely needed.
This is where the folder stops being empty.
The dashboard exists before the first customer does.
This is the unusual one, and it is deliberate. Most new products get their measurement about four months in, when somebody finally asks what the repeat rate is and nobody can say. By then the first four months are unrecoverable — the data was never collected, because nowhere was collecting it.
Standing the board up on day one costs minutes and means the first month has numbers in it. Which is exactly the month whose numbers decide whether there is a second one.
A small heresy: the dashboard is more useful than the website in week one. The website is for the customers you do not have yet. The dashboard is how you find out why you do not have them.
- 1Site structurePages chosen from what the description implies. A price page exists because a price exists.
- 2Copy writtenFrom the written case, in the brand's voice, in the languages you asked for.
- 3PicturesRoyalty-free, from the platform's media library, licence and attribution attached to the file.
- 4Board laid outThe four or five numbers this kind of product lives or dies by. Not forty.
- 5Workflows builtEvery step the description implied somebody would otherwise do by hand.
- ·Then you open themThree editors, three normal products. Nothing is generated-and-frozen.
One description behind all threeEverything editable afterwards
What the workflows actually cover.
The description says what the product does, and most of what a product does is repetitive work somebody would otherwise perform by hand at nine in the morning. Those become workflows: an order becomes an invoice; a signup gets a welcome and a follow-up on day three; a supplier order gets split, sent and chased; a monthly report assembles itself on the first.
castomFLOW makes a point of not putting a model on every step, and castoMIND inherits that discipline. A reconciliation does not need judgement, it needs the same thing to happen the same way every time. Steps that genuinely need judgement — classify this message, draft that reply, choose between three options — get one, and only those are charged for.
The result is machinery you can read. When something goes wrong in month two, there is a run log with the branch it took and the values that decided it, rather than a shrug and a plausible theory.
What is underneath all three.
All three sit on castomAPI, which is why none of them needs anything bought in. The site's images come from a royalty-free library that searches eleven providers and keeps the licence attached. Address and country fields validate against 34.8 million rows of real reference data. The workflows can send an e-mail, an SMS or a push, take a payment, offer a booking slot or mint a short link, using the same account that signed in at the start.
None of that is an integration anybody sets up, and none of it has a key to rotate. It is the floor the whole family stands on.