Bezel Team intent

People with real product ideas need production software, not clickthrough demos or generic AI coding sessions. They often cannot translate domain expertise into screens, architecture, build plans, deployment decisions, and operating workflows. Existing AI dev tools start too late at prompt-to-code; agencies are expensive and opaque; no current workflow combines meticulous product design, human-reviewable screens, multi-model critique, AI-first workflow transformation, agent-built implementation, and production hosting in one guided process.

Dreamborn Build guides a product owner from raw idea to production software. It uses Bezel to run an AI-first product studio process: discovery, intent, AI-first opportunity mapping, screen-by-screen design, wireframes, architecture, build planning, managed AI dev execution, proof review, deployment, hosting, and iteration.

• Should the first customer flow require Dreamborn operator review at every gate, or only at architecture/build/release gates?
• Should wireframes initially be structured HTML inside Dreamborn Build, or exported image artifacts as well?
• What is the first paid package: fixed-price product design sprint, build sprint, or bundled design+build pilot?
• Should Dreamborn hosting be the default for V1 unless customer explicitly asks for connected infrastructure?

• item: metric: string, target: string
• item: metric: string, target: string
• item: metric: string, target: string
• item: metric: string, target: string
• item: metric: string, target: string