Product teams/Custom AI applications
Lumen
The organization goes from a sentence to a running prototype, refines it in English, reviews it, and exports a brief. Invite-only. No public signup.
Confidential commission. We describe the system. We do not name the organization or show their data.
Claude · Next.js · Postgres · Review + export
Result
A product lead types one sentence, answers a few questions, and gets a page that actually runs. They refine it in English, send it for review, and leave with a PDF brief plus a standalone file a developer can open.
That used to be a day of designer ping-pong. We do not publish user counts or a live address.
The situation
The organization needed people inside the company to explore product ideas without hiring a designer for every sketch, and without handing a developer a paragraph.
Static mockups do not behave. Decks do not survive a click. The gap was: I have an idea, then I have something briefable.
They asked DevZo to design and build the product. It is our engineering, made for their workspace. We do not use the product’s internal name, and we do not name the company.
Constraints
The prototype had to run in a browser, not look like a picture of a product.
Two starting points: a blank sentence, or a URL whose brand had to carry into every generated screen.
Refines could not overwrite history. Versions, comments, and approvals attach to a specific cut.
Closed system: invite-only organizations, roles, sharing rules, an operator console. Model spend bounded.
Approach
Generation is a sequence of sharp model calls: questions, then the prototype, then change summaries, then the handoff. The interface is a product, not a themed chat window.
The decision that made it a company tool: organizations, not a public sandbox. Review is a gate: approve or send back, on a version.
What we shipped
Type an idea, or start from a URL. Answer a few clarifying questions. Receive a working single-page prototype.
Describe a change in plain English; keep every version. Reviewers comment and approve. Export a polished brief and the working file.
Around the loop: a project dashboard, org roles, per-project sharing, platform admin, usage tracking, and safety rails.
How it was built
A Next.js application, Postgres, session auth, Claude for every generation step, and a headless browser for PDF and screenshots. Fetching a client URL is locked down so it cannot be pointed at private networks.
We do not publish diagrams that map one-to-one onto their deploy.
What we’d do next
Onboarding for first-time invited users, a visual pass, and email invites when they want people who will not paste a link.
On this site: a short, approved clip of idea to first screen if they allow it. Never an admin console.