Describe the business naturally
Record or upload a short explanation of packages, prices, capacity, availability, deposits, and handoff rules.
A Mexico-first prototype that turns an event-business owner's voice note into a reviewable operating blueprint and assistant demo.
Describe the business. Review the system. Test it before activation.
AI can transcribe and extract the owner's explanation. Typed validation and deterministic engines govern quoting, availability, clarification, handoff, and every boundary between preview and live operation.
User value
Turn the way an owner already explains the business into rules that can be inspected and tested.
Record or upload a short explanation of packages, prices, capacity, availability, deposits, and handoff rules.
Correct the transcript, inspect the structured blueprint, and resolve important gaps before using it.
Try customer-style questions in a deterministic preview without activating WhatsApp, payments, or bookings.
Features
The current flow moves from a voice note to a constrained assistant preview.
Record up to one minute in the browser or upload supported audio after providing consent.
Request transcription, correct the result, and confirm it before blueprint generation.
Represent services, packages, prices, availability, deposits, required fields, tone, and handoffs.
Surface missing prices, contradictions, ambiguous dates, and unsupported rules instead of inventing values.
Calculate supported estimates, collect event details, check availability, and enter human handoff when needed.
Preview allowlisted changes as a diff and create a new blueprint version only after explicit application.
Save a demo, create a limited share link, or record activation interest without creating a live service.
How it works
Each stage remains distinct so a convincing demo cannot be mistaken for activation.
Provide contact and consent details, then record or upload the business explanation.
Use an explicitly selected provider and show the resulting text for correction.
Approve the transcript before it becomes input to blueprint generation.
Generate typed Events MX data and validate it against the product schema.
Expose important missing or contradictory information before the preview is considered usable.
Try customer messages against the deterministic blueprint without connecting a real channel.
Product concept
A voice note is useful input, but it is not permission to launch an unconstrained chatbot.
Transcription and structured extraction can use configured providers, but their output is not trusted directly.
Typed validation, quote logic, availability, conversation state, and handoff policy govern the preview.
Blueprint approval, integration setup, provider verification, operating mode, and live eligibility remain separate states.
Architecture
Public demo data remains separate from operational projects and live channel foundations.
A failed real provider does not manufacture success with mock or seed content.
Generated, corrected, approved, archived, and operational blueprint states remain distinct.
The public flow does not silently create operational projects, conversations, payments, bookings, or WhatsApp activity.
Technology
Development
Voice intake, transcript review, blueprint generation, deterministic preview, saving, limited sharing, and activation-interest capture are implemented. Production launch approval is explicitly withheld.
Implemented
Before public use
Provision production data and object storage, protect administrative routes, verify configured providers, add monitoring and platform protection, define retention and deletion, review privacy and consent, and complete mobile and difficult-audio QA.
DonApo lab notes
Notes about the thinking, architecture, development, and decisions behind this work.
A Spanish-language self-serve funnel exposed the voice, blueprint, and preview idea while preserving a strict boundary around activation.
Webhook handling, runtime binding, reply policy, an outbox, and provider status moved channel work forward without turning configuration into a launch claim.
A typed Events MX blueprint became the bridge between provider-assisted extraction and deterministic business behavior.
The first implementation separated receiving audio, transcription, confirmation, and blueprint generation into explicit states.