Skip to content
Samlution

Interactive demo

Watch a lead become a reviewed proposal draft.

The interface is generated as the answer streams in: a pipeline, the sources that were read, the agent steps, the draft with its gaps marked, and the approval gate that stops it. A scripted provider answers, so the demo needs no API key.
Discuss a real deploymentRead the offer

Lead → proposal → approval

Generative UI · OpenUI Lang · mock provider

No model call

Interface ready

Ask about the workflow and the interface is generated as the answer streams in — the same component library renders whatever the model writes.

A scripted provider stands in for the model. The OpenUI system prompt, the component library and the streaming renderer are real.

Start with one of these

What this demonstrates

  • The answer is a generated interface, not a paragraph of text
  • One component library renders every response, as it streams
  • Sources and agent steps stay attached to the draft
  • A human approval gate stands between the draft and the client

What it does not

  • Call a live language model — a scripted provider answers
  • Store anything you type, or send it to a third party
  • Send an email or book a meeting on your behalf
  • Represent a measured client result

Try this first

Ask for the draft, then press Approve draft. The approval is recorded and the next view shows the audit trail it would have written.

Behind the demo

The model writes the interface, not just the words.

Each answer is OpenUI Lang — a small program of components from one library. The renderer draws it while it streams, so a partial answer is still readable.

One component library

Thirteen components defined for this workflow: Screen, Panel, Stage, Steps, Source, Draft, ApprovalGate, AuditTrail, Callout and their children. The model cannot draw anything outside it.

A mock provider, not a fake

The route uses the Vercel AI SDK and a mock language model that streams a scripted program. Swapping in a real provider is a one-line change; the prompt and renderer stay the same.

The approval gate is real

Approve fires the same action a production system would: it returns to the server, gets recorded, and starts the next step. Nothing is ever sent from the browser.

Next step

Want this running on your own pipeline?

We start with the workflow you repeat most, wire the approval gate first, and connect the systems after that.

Book a Discovery CallSee the offer

No obligationFixed scope, fixed feeApproval stays human

See how engagements run