Questions agencies ask before they send a brief.

Your Demos (ydemos) turns one client brief into a complete working demo in about four to five hours, with no effort from your agency during the build. You get nine deliverables: a strategy and product blueprint, brand system, logo, landing page, UX flows, wireframes, a full build plan, a polished working app with demo logins for every type of user and realistic data, and an exportable file bundle.

Chat builders make you the production operator: you prompt, review and steer, one step at a time. ydemos works from one structured brief and returns the assembled package. You don't prompt it, and there are no revision rounds or meetings. It also includes the strategy, brand, UX and build plan, white-label hosting and exact-element client feedback, not just generated code.

We aren't making a claim about any other tool's output quality. It's a different way of working.

No. It's a polished, clickable demo built on fictional data, with no real payments and no live third-party connections. It's designed to help a client react to an idea. ydemos is the step before Figma, Lovable, Cursor or a dev team, so everything after it starts from something real.

Mainly agencies, design and dev studios, consultants and freelancers who pitch new work every month. It also works for venture studios, accelerators and founders who want to test an idea before spending real money. Everyone uses the same workspace and roles.

One short structured form with:

• Client or project name (2–120 characters)
• What the app does (20–2,000 characters)
• Users and roles (1–8), each with what they need to do
• Must-have features (1–20), each kept as a distinct requirement
• Look and feel, or "No visual preference"
• Optional references (up to 5 labelled links). These guide the look only and are never treated as instructions.

There are no budget, schedule or meeting fields. You can edit everything up to the moment you press Submit brief and start build.

The standard build time is about four to five hours. The plan is 4h 30m across seven phases, with a 30-minute recovery reserve and a hard limit of 300 minutes. When you submit, you'll see "Estimated delivery in about 4 hours 30 minutes; allow up to 5 hours." The estimate updates as phases hand off. It's a target, not a guarantee for every brief.

No. Once a run starts, nobody interrupts you. Where the brief leaves gaps, the build makes conservative choices and labels them as inferences, never as client decisions. If an ambiguity stops it delivering reliably, the run is marked blocked or failed and you're notified.

A live timeline with each phase's status (queued, running, complete, blocked or failed), the brief requirements it covers, a concise progress update and the ETA. Previews only appear once a phase has passed validation. You won't see raw prompts or unchecked claims.

We email you when the run starts, if it's blocked or fails, and when delivery is ready. An optional Slack alert covers the same events.

A run is complete only when it passes the completion gate: all nine deliverables are present and consistent with each other, every must-have feature traces back to your brief, the working app runs, and every app role has a working demo login. Polished documents can't stand in for a broken app or a missing feature.

It's marked blocked or failed, with the reason and the evidence. Brief, transient tool failures get one automatic retry. A phase that fails its quality check gets at most two repair attempts. Anything already validated is kept. If it still can't pass, we tell you plainly. We never present a partial build as finished.

A ZIP with the app and landing-page source, brand assets and logo, every written deliverable, the fictional seed data, and a README with local run instructions and an index of every deliverable. It contains no credentials, secrets or real-person data. It's yours to keep and take further.

No. Every demo is hosted on your own link and fully white-labelled. There's no ydemos name, logo, watermark, link or fallback URL anywhere the client can see, including loading screens, the analytics prompt, feedback confirmations and error pages.

Yes. Client sharing needs a domain or subdomain your agency owns, for example demo.youragency.com. We verify it with a DNS challenge and wait until HTTPS is ready. Until then, sharing stays off. There's no ydemos-branded fallback. Custom-domain sharing is included and isn't an add-on.

No. A finished build creates a private preview. You review a five-point checklist (brief fidelity, white-label integrity, role logins and permissions, fictional seeded data, claims and source traceability), and the link turns on only once every check passes and you confirm. You decide whether and when to share.

No. They open the link and explore. They can enter the demo as each app role, for example Studio Admin, Instructor or Member. Those are logins inside the demo app, not ydemos accounts, and they never give access to your workspace.

Yes. Start a live walkthrough and both of you see the same screen. Your client can take control or leave whenever they like, and can keep exploring on their own afterwards.

Your client clicks any part of the app, circles or draws on it, adds a note and sends it, live or in their own time. Every note is tied to the exact screen and element. For example, "Show remaining spots on each class card" arrives pinned to the class card it's about.

Never automatically. CX-Pen notes are for your review. You decide what a note means, whether it matters and what happens next. If you want a changed demo, that's a new brief and a new run, and your original run and evidence are kept.

When your client opened the demo, how long they spent and which screens they viewed. We only collect these after the client agrees. If they decline, the demo still works and nothing is collected. Sessions are anonymous unless the client chooses to identify themselves to you directly.

No. We never email, message or call your clients. They get no notifications about the build. The client relationship is yours.

$299 USD per demo, everything included, with no subscription. There are no seat fees, no viewer fees and no add-ons at launch. The price is shown before you submit a paid brief.

Your first demo is free, once per agency. You'll need a verified business email, a declaration that the brief is for a real client project, and the client or project name. A ydemos admin reviews each request before production starts, so approval isn't automatic. If it isn't approved, you can still order a paid demo.

If a paid demo doesn't produce a package that passes the completion gate within the 300-minute hard limit, for reasons on our side, the agency owner can request a full refund within 14 calendar days. An admin reviews and processes it. Refunds aren't automatic. Changing your mind, changing the brief or wanting revisions doesn't qualify on its own.

No. "Everything included" covers the nine deliverables and the sharing tools, not unlimited revisions. Use the feedback to write a new brief, and the new demo is charged at the standard price.

Hosting is included, but we don't promise a fixed or unlimited term. If nobody at your agency touches a demo for 90 days, we notify the owner. If there's still no activity 30 days later, the client link is disabled and its hosting released. Client views alone don't count as agency activity.

Between us and your agency, you own the custom deliverables made for your demo. Ownership transfers after payment, or on delivery for the free first demo. You can use, modify and pass them to your client for the client's project. Our underlying platform, reusable components and know-how stay ours, and you get a licence for anything of ours that's embedded. Third-party and open-source parts keep their own licences.

No. Generated names and logos aren't trademark-cleared and may not be unique. Check them, and get any permissions you need, before using them in production.

No, not by default. Briefs, attachments, generated files, viewer analytics and CX-Pen notes are confidential service data. They're used only to deliver, secure and support your service. Any other use would need your separate, specific opt-in.

No. Every seeded person and record is fictional. If we detect real personal data in a brief, it's kept out of generation or the run is blocked for review. Only submit what you're authorised to share.

We refuse phishing clones, credential theft, impersonation of a real person or brand as if official, illegal uses, and copying of protected code, assets or distinctive interfaces. Operational demos of regulated products that make unsupported claims or collect sensitive data are also refused. Unclear cases are held for admin review before any run starts. A safe, fictional, non-operational alternative is often possible.

We target WCAG 2.2 AA for the platform and for generated demos, using automated checks plus human review of keyboard use, focus, labels, contrast, errors and responsive layouts. An unresolved applicable Level A or AA failure blocks a demo from being marked ready to share.

Yes. When they first open it, they see a clear, accessible line under your agency's name: "AI-generated demo; discuss it with [your agency]". It has no ydemos branding. Your own delivery screens also state that the package is AI-generated and needs your review before sharing.