Professional Systems
Prototype

DonApo

A Mexico-first prototype that turns an event-business owner's voice note into a reviewable operating blueprint and assistant demo.

Category
Professional Systems
Platform
Web
Status
Prototype

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

Speak first. Configure second.

Turn the way an owner already explains the business into rules that can be inspected and tested.

01

Describe the business naturally

Record or upload a short explanation of packages, prices, capacity, availability, deposits, and handoff rules.

02

Review the interpretation

Correct the transcript, inspect the structured blueprint, and resolve important gaps before using it.

03

Test before connecting

Try customer-style questions in a deterministic preview without activating WhatsApp, payments, or bookings.

Features

A complete prototype funnel.

The current flow moves from a voice note to a constrained assistant preview.

  1. 01

    Voice intake

    Record up to one minute in the browser or upload supported audio after providing consent.

  2. 02

    Transcript review

    Request transcription, correct the result, and confirm it before blueprint generation.

  3. 03

    Typed business blueprint

    Represent services, packages, prices, availability, deposits, required fields, tone, and handoffs.

  4. 04

    Clarification detection

    Surface missing prices, contradictions, ambiguous dates, and unsupported rules instead of inventing values.

  5. 05

    Deterministic assistant preview

    Calculate supported estimates, collect event details, check availability, and enter human handoff when needed.

  6. 06

    Versioned corrections

    Preview allowlisted changes as a diff and create a new blueprint version only after explicit application.

  7. 07

    Safe demo continuation

    Save a demo, create a limited share link, or record activation interest without creating a live service.

How it works

From explanation to testable rules.

Each stage remains distinct so a convincing demo cannot be mistaken for activation.

  1. 01

    Describe

    Provide contact and consent details, then record or upload the business explanation.

  2. 02

    Transcribe

    Use an explicitly selected provider and show the resulting text for correction.

  3. 03

    Confirm

    Approve the transcript before it becomes input to blueprint generation.

  4. 04

    Structure

    Generate typed Events MX data and validate it against the product schema.

  5. 05

    Clarify

    Expose important missing or contradictory information before the preview is considered usable.

  6. 06

    Simulate

    Try customer messages against the deterministic blueprint without connecting a real channel.

Product concept

The blueprint is the product contract.

A voice note is useful input, but it is not permission to launch an unconstrained chatbot.

01

AI proposes structure

Transcription and structured extraction can use configured providers, but their output is not trusted directly.

02

Deterministic rules operate

Typed validation, quote logic, availability, conversation state, and handoff policy govern the preview.

03

Preview is not activation

Blueprint approval, integration setup, provider verification, operating mode, and live eligibility remain separate states.

Architecture

Provider-assisted setup. Rule-bound runtime.

Public demo data remains separate from operational projects and live channel foundations.

  1. 01Contact, consent, and voice intake
  2. 02Explicit transcription request
  3. 03Corrected and confirmed transcript
  4. 04Structured blueprint generation
  5. 05Schema and clarification checks
  6. 06Deterministic assistant preview
  7. 07Optional demo save, share, or interest

No silent fallback

A failed real provider does not manufacture success with mock or seed content.

Versioned review

Generated, corrected, approved, archived, and operational blueprint states remain distinct.

Demo data stays a demo

The public flow does not silently create operational projects, conversations, payments, bookings, or WhatsApp activity.

Technology

Typed rules behind a conversational setup.

Application

  • TypeScript
  • Next.js 15
  • React 19
  • CSS

Domain

  • Zod 3
  • Typed Events MX blueprint
  • Deterministic state machine
  • Quote and availability engines

Persistence

  • Prisma 6
  • PostgreSQL
  • Versioned blueprints
  • Separate demo and operational records

Providers

  • Optional OpenAI transcription
  • Optional structured extraction
  • WhatsApp Cloud API boundary
  • Vitest 4

Development

The public demo exists in development.

Voice intake, transcript review, blueprint generation, deterministic preview, saving, limited sharing, and activation-interest capture are implemented. Production launch approval is explicitly withheld.

Stage
Prototype
Vertical
Mexican event businesses
Automated suite
593 tests passing
Live WhatsApp
Not connected

Implemented

  • Spanish-language landing, static example, voice intake, transcript review, blueprint review, and assistant demo
  • Optional OpenAI transcription and structured generation behind explicit provider selection
  • Typed Events MX schema, conservative validation, missing-field analysis, and contradiction checks
  • Deterministic customer-input, quote, availability, conversation-state, and handoff engines
  • Versioned blueprints, correction previews, approval states, persisted Web previews, and operational records
  • Controlled WhatsApp webhook, runtime, reply-policy, outbox, sender, auto-send, and provider-status foundations behind safety gates

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.