AUANI

Building Alternative Economies for Working-Class, Hispanic Immigrant Communities

Role: Founder, Product Designer, Brand Strategist, Engineer Status: Live in Production (DMV Market) Timeline: October 2025 → Present

Overview

Vision

Create alternative economies where working-class communities don't rely on extractive brands. Fair income for drivers (100% of delivery fees), transparent service fees for platform access, viable logistics for restaurants-without VC extraction.

What AUANI Is

Functional dispatch platform, Spanish-first interface, community-driven logistics. Named after the Purépecha word for "rabbit" (agility, intelligence, ancestral wisdom). Brand colors reflect Michoacán avocado hues-cultural and economic pride.

What AUANI Is Not

Savior brand, moralizing platform, cheap gimmick, VC-driven growth machine, commission-based extractor.

The Challenge & Pivot

Original Plan

Simultaneous US (DMV) and Mexico rollout with Spanish-first interface. Courier service in Uruapan, Michoacán + dispatch in Ecatepec/Mexico City.

External Constraints

Regulatory barriers, partnerships, operational issues forced Mexico postponement. Technical challenges in payments, distance calculations, APIs required single-market focus.

Strategic Adaptation

DMV-only launch (MD/DC/VA) to validate model. Mexico ready but paused. Soft launched Nov 15, 2025. First paid trip completed.

Technical Impact

Currency: USD/MXN • Metrics: Miles/km • i18n: Spanish UI/English admin • Security: Fixed double-submit • Maps: Business names + addresses • Firewall: Resolved AJAX blocks

Product Strategy

Phased Rollout Strategy

Phase 1

Drivers First

  • Drivers left with WhatsApp chaos if they avoid big apps
  • No unified dispatch, unstable demand, paying $130-150 weekly for access
  • AUANI gives structure without extraction-transparent pricing, job autonomy
  • Status: Manual onboarding, active fleet in DMV, Shipday dispatch live
Phase 2

Restaurants

  • Onboard once driver fleet reliable
  • WCFM multivendor portal ready for self-service menu management
  • 30-40% commission on big apps = unsustainable
  • Status: Live with v3.2.0! Includes food delivery and pickup checkout wizards, Stripe integration for payments, and automated order submission to the Shipday API.
Phase 3

Clients

  • Working-class, practical decision-making-99% mobile users
  • Minimal loyalty-driven by price and speed
  • 5-step wizard form optimized for mobile-first experience
  • Status: Live in production, first paid trip completed November 2025

User Research Insights

Mobile-First UX Priority

Finding: 99% of users are on mobile devices. Long single-page forms created friction.

Method: User testing, form analytics, mobile behavior patterns.

Impact: Rebuilt as 5-step wizard form with progress indicator, back navigation, step validation. Smooth transitions optimized for touchscreen.

Hybrid Onboarding Model

Finding: Manual onboarding + WhatsApp groups build trust faster than digital-only in working-class markets.

Method: Ethnographic field work, driver interviews, community engagement.

Impact: Temporary manual driver onboarding during launch. WhatsApp Business API integration deferred until driver network stable.

Business Name Recognition

Finding: Users don't always know street addresses-they say "pick up at Starbucks" or "drop off at Walmart."

Method: Form submission analysis, user testing, Google Places API types configuration.

Impact: Fixed autocomplete to accept both addresses AND business names/POIs. Country restrictions prevent international suggestions.

Price Transparency Matters

Finding: Working-class clients prioritize clarity over complexity. Hidden fees create distrust.

Method: Pricing display testing, user feedback, competitive analysis.

Impact: Price breakdown shows delivery fee (driver) separate from platform fee (AUANI). Desktop color contrast fixed for visibility.

Decision-Making Under Constraints

Trade-offs & Prioritization

Decision Point Options Considered Choice Made Rationale
Market Geography Multi-city Mexico vs. Single US market DMV-only Reduce operational complexity, validate model in controllable environment
Service Priority Launch both rideshare + delivery vs. Sequential Rideshare first Build driver supply before adding restaurant complexity
Tech Stack Custom build vs. API integrations Hybrid (Shipday API + custom) Speed to market without sacrificing control
Language Strategy English vs. Spanish vs. Bilingual Spanish UI, English backend Match end-user needs while maintaining operational efficiency
Growth Model VC funding vs. Bootstrapped Bootstrapped Maintain non-extractive model, avoid growth-at-all-costs pressure

Product Deep Dive: Conductores

Conduce tu propio camino con AUANI

¿Por qué pagar 25-40% de comisión cuando puedes quedarte con el 100%? Auani te conecta directamente con clientes que necesitan viajes y entregas.

Cómo Funciona

Registro Simple

Solo necesitas tu información personal y de tu vehículo. Todo se gestiona desde tu celular.

Tú Decides

Recibe pedidos o viajes directamente a la app. Tú decides cuáles envíos o viajes aceptas, sin penalizaciones automáticas.

Pago Directo

Tú decides cómo y cuándo cobrar: antes, durante o después del servicio. La tarifa de conductor siempre se paga completa, y puedes recibir propinas directamente.

Por Qué Auani es Diferente

Libre (Ideal para ingreso extra)

$0/mes

  • 0% Comisión
  • Sin limite de pedidos o viajes
  • 100% Pago directo + propinas
  • Horario flexible
  • Viajes de preferencia (aeropuerto)
  • Acceso a fondos de emergencia de vehículo con 0% interés
  • Mantenimiento esencial (aceite, rotación, inspecciones)
  • 50% descuento en la tarifa de servicio para familiares

La Tribu (Ideal para profesional de tiempo completo)

$199/mes

  • 0% Comisión
  • Sin limite de pedidos o viajes
  • 100% Pago directo + propinas
  • Horario flexible
  • Viajes de preferencia (aeropuerto)
  • Acceso a fondos de emergencia de vehículo con 0% interés
  • Mantenimiento esencial (aceite, rotación, inspecciones)
  • 50% descuento en la tarifa de servicio para familiares

Autonomía Total: No necesitas pagar nada para usar la plataforma. Tú eliges cuándo y qué trabajos aceptar, sin metas obligatorias ni algoritmos que presionen. Tu tarifa de conductor nunca se reduce.

Soporte: Atención rápida si surge algún problema con clientes o pagos.

Preguntas Frecuentes

¿Cuánto cuesta registrarme?

Nada. Ser conductor es gratis. Solo pagas $199/mes si decides unirte a La Tribu para tener mantenimiento mensual y acceso a un fondo de emergencia sin intereses.

¿Cómo funciona eso de que AUANI paga mi mantenimiento?

Si eres parte de La Tribu por 3 meses seguidos, recibes un servicio mensual: cambio de aceite, filtros, parabrisas y rotación de llantas en talleres certificados. Lo que pagas regresa a tu vehículo, tu herramienta de trabajo.

¿Qué necesito para empezar?

Tu información personal, datos del vehículo y un teléfono con buen internet. Se hace todo desde tu celular.

¿Cómo se calculan los precios de mis viajes?

El sistema usa Google Maps: $5 por las primeras 3 millas y $1.25 por cada milla extra. Si hay demasiada demanda, puede haber tarifa dinámica.

¿Cómo cobro a mis clientes?

Directo a tu cuenta: Cash App, Venmo, Zelle o efectivo. Tú decides cuándo cobrar: antes, durante o después, dependiendo de tu estrategia y del cliente.

¿AUANI toma comisión de mis ganancias?

No. Lo que el cliente paga es para ti. Las funciones premium no afectan tu tarifa.

¿Puedo recibir propinas?

Sí. Y van completas para ti.

¿Debo aceptar todos los pedidos o viajes?

No. Tú eliges qué tomar. No hay penalizaciones automáticas, pero si cancelas demasiado, lo hablamos.

¿Hay horarios obligatorios?

No. Entras y sales cuando quieras. No hay presión ni algoritmos castigándote.

¿Qué tipo de pedidos voy a recibir?

Principalmente viajes al inicio. Después comida. Más adelante podrás elegir tu preferencia.

¿Cuántos pedidos puedo esperar al día?

Es una comunidad nueva. Crece conforme tú te muevas, tus contactos y familiares.

¿Puedo invitar a amigos?

Claro. Entre más conductores responsables, más se mueve la comunidad. En un futuro corto, se les va pagar comisión por recomendaciones de conductores que se unan a La Tribu. Tendrás más oportunidades de ganancias.

¿Qué pasa si hay un problema con un cliente o un viaje?

Hay soporte local, sistema de fotos y registro en la app. Si alguien abusa, se suspende. Si algo rebasa a AUANI, se escala a las autoridades.

¿Qué pasa si el cliente no quiere pagar?

Si tienes prueba del servicio, recibes el pago igual.

¿Puedo trabajar con otras apps?

Sí. Eres un contratista independiente.

Product Deep Dive: Restaurantes

Vende en línea sin comisión por precio del pedido

La mayoría de las plataformas te quitan 30% por cada venta. Aquí no. Con tu menú tú mandas. $3 por orden. Sin comisiones ocultas.

Cómo Funciona

Conexión Google Business

Conecta tu perfil de Google Business. Si ya existe en Google Maps, es más rápido aprobar tu aplicación.

Pagos Directos (Stripe)

AUANI usa Stripe Connect. Pagos directos a tu cuenta cada semana, menos los costos de la tarifa de servicio por pedido.

Pedidos por Email

Sube tu menú y recibe pedidos por correo electrónico; no necesitas tableta. AUANI provee la plataforma para conectarte con más clientes hambrientos.

Por Qué Auani es Diferente

Principiante (Ideal para chef personal y ventas caseras)

$0/mes

  • 0% Comisión por precio
  • Tu página con menú y edición de productos
  • Órdenes por correo electrónico
  • Pagos automáticos por Stripe Connect
  • Tarifas claras por pedido ($3–$5)
  • Capacidad para usar tus propios empleados para entregar
  • Integración automática con la flota de AUANI
  • Sin mensualidad forzada ni contrato raro

Chef (Ideal para restaurantes listos para crecer)

$299/mes

  • Todo en el plan Principiante, más:
  • Tu propio sitio web (turestaurante.com)
  • Pedidos en línea y Campaña automatizada de SMS
  • Integración con flota de AUANI conductores de 4 y 5 estrellas
  • Programas de lealtad y mejores reportes de ventas
  • Soporte plus

Transparencia: Tú eliges los precios de tu menú. La tarifa de servicio es $5 por pedido en línea pagado con tarjeta y $3 por pedido por menús completos con fotos. Cobras directo, controlas tu menú y mantienes lo que ganas. Solo pagas el impuesto del 10% de comida y las tarifas normales de Stripe (2.9% + 30¢).

Flexibilidad: Puedes seguir usando UberEats o Grubhub. Usa AUANI para que los clientes te pidan directo sin regalar tu ganancia.

Preguntas Frecuentes

¿Cuánto cuesta registrarme?

Nada. El registro es gratis. Solo pagas la tarifa por pedido cuando vendes.

¿Qué necesito para empezar?

Fotos, precios y un correo electrónico dedicado donde recibir pedidos.

¿Hay mensualidades?

Nada a la fuerza ni compromisos raros.

¿Por qué mi tarifa es $5 o $3?

Si tu menú no tiene fotos completas, la tarifa es $5 por pedido. Si subes fotos para todos tus platillos, baja a $3. Es simple: las fotos venden.

¿Cómo recibo pagos?

Stripe procesa los cobros. Tus depósitos llegan semanalmente sin que hagas nada.

¿Auani toma comisión de mis ventas?

No. Solo pagas el impuesto de las tarifas de Stripe cuando alguien paga con tarjeta.

¿Necesito tableta?

No. Solo un email. Eso es todo.

¿Puedo seguir usando UberEats o Grubhub?

Sí. Usa AUANI para que los clientes te pidan directo sin regalar tu ganancia.

¿Qué pasa si tengo un problema con una orden?

Hay soporte local. Te ayudo a resolver situaciones razonables.

¿Mi personal puede hacer entregas?

Sí. Tú decides. Y ellos cobran directo, sin costo para ti, ya ganancia de ellos.

¿Esto funciona para cualquier tipo de restaurante?

Mientras tengas cuenta bancaria en línea, puedas manejar pedidos y mantener calidad, estoy para brindarte mi conocimiento de mercadeo digital para avanzar tu negocio.

UX & Design

Driver

Motivations

Predictable income, autonomy, alternatives to extractive apps

Barriers

WhatsApp chaos, inconsistent gigs, lack of unified dispatch

Opportunity

AUANI provides structure without extraction-reliable demand, transparent pricing

[Driver Photo Placeholder]

Restaurant Manager

Motivations

Reliable delivery, clarity in pricing, sustainable margins

Barriers

30–40% commissions on big apps, opaque fee structures

Opportunity

AUANI offers transparent, lower commissions with direct restaurant relationships

[Restaurant Manager Photo Placeholder]

Client (Rider/Diner)

Motivations

Affordability, speed, convenience

Reality

Minimal loyalty-will use whatever platform works and is cheapest

Opportunity

AUANI competes on price and reliability, not brand affinity

[Client Photo Placeholder]

Key User Journeys

Driver Onboarding → First Order → Payout

1. Discovery

WhatsApp group, word-of-mouth, community referral

2. Manual Onboarding

Phone call or in-person meeting, explain fee structure

3. Shipday Setup

Driver app download, account configuration, test order

4. Accept First Order

Shipday push notification, driver accepts, navigates to pickup

5. Complete Delivery

Mark complete in Shipday, customer receives tracking link

6. Receive Payment

Customer pays via CashApp/Venmo/Zelle/cash, driver gets 100%

[Driver App Screenshots Placeholder]

Client Order → Dispatch → Delivery (5-Step Wizard)

Step 1: Contact Info

Name, email, WhatsApp number

Step 2: Pickup Address

Google autocomplete (business names + addresses)

Step 3: Dropoff Address

Google autocomplete with country restriction

Step 4: Instructions

Optional delivery notes

Step 5: Review & Pay

Price breakdown: delivery fee + service fee, Stripe authorization

Order Dispatch

Submitted to Shipday, driver assigned, tracking link sent

[Client Wizard Form Screenshots Placeholder]

Restaurant Onboarding → Menu → Order (Future)

1. Partnership Outreach

Direct restaurant contact, pitch transparent fee model

2. WCFM Portal Setup

Self-service merchant dashboard, menu upload capability

3. Menu Configuration

Items, pricing, images, availability hours

4. Test Orders

Internal testing before public launch

5. Go Live

Customer orders via site, auto-dispatch to Shipday

[WCFM Restaurant Backend Screenshots Placeholder]

Visual Design System

Color Palette

Primary
#2C3E50

Accent
#3498DB

Success
#27AE60

Alert
#E74C3C

Warning
#F39C12

Typography

Heading 1 - Roboto Bold

Heading 2 - Roboto Semibold

Body text - Roboto Regular. Used for most content across the app. Optimized for readability on mobile devices.

Icon Library

[Icon Library Grid Placeholder - Material Design Icons]

Component Library

[Component Screenshots Placeholder - Buttons, Cards, Forms, Navigation]

Design Principles

  • Material Design Foundation: Familiar patterns for Android-first users
  • IA Aesthetic: DIY, modular, honest-no corporate polish
  • Cultural Context: Subtle Latin American visual cues without stereotyping
  • Working-Class Photography: Real people, real contexts-no stock photo gloss

Brand Strategy

Positioning

Functional alternative. Non-extractive. Pragmatic. Spanish-first.

AUANI is not a lifestyle brand or a savior narrative. It's a working system that respects working-class people's economic realities. The brand communicates context over blame, action over rhetoric, and Inteligencia Artesanal-the resourcefulness that built these communities in the first place.

Name & Symbolism

Purépecha Origins

"Auani" comes from the Purépecha word for "rabbit"-representing agility, intelligence, and ancestral wisdom. The Purépecha people of Michoacán built sophisticated economies long before Spanish colonization.

Michoacán Avocado Colors

Brand colors reflect the hues of the Michoacán avocado-a symbol of cultural and economic pride. Green represents growth, resilience, and the region's agricultural heritage.

Brand Pillars

Context Over Blame

We don't moralize about extractive platforms. We acknowledge the system and offer an alternative.

Action Over Rhetoric

No manifesto. No virtue signaling. Just a working platform that pays drivers fairly.

Inteligencia Artesanal

The DIY resourcefulness of working-class communities-modular, adaptive, honest.

Alternative Economics

This is an economic experiment. Can we build viable logistics without VC extraction?

Tone & Voice

  • Direct: No euphemisms. Say what we mean.
  • Realistic: Acknowledge constraints and trade-offs.
  • Grounded: Talk to users like adults with economic agency.
  • Spanish-first: Primary language for working-class Latino markets in US + Mexico.
  • Not: Inspirational, corporate, apologetic, or moralizing.

Visual Identity

IA Aesthetic

DIY, modular approach-nothing overly polished. Reflects the resourcefulness of working-class communities. Material Design principles for familiar Android-first UX.

[Visual Example Placeholder]

Cultural Context

Purépecha symbolism without caricature. Michoacán avocado green as primary accent. Typography and imagery that feels familiar to Latino markets.

[Visual Example Placeholder]

Photography

Honest working-class imagery. Real drivers, real restaurants, real neighborhoods-no stock photo gloss. Spanish-language interface screenshots.

[Photo Example Placeholder]

Marketing & Copywriting

Spanish-first landing pages targeting drivers and restaurants with direct, practical messaging.

Driver Landing Page

auani.com/conductores/

Value Proposition

Headline: "Conduce tu propio camino con AUANI"

Translation: "Drive your own path with AUANI"

Sub-Headline: "¿Por qué pagar 25-40% de comisión cuando puedes quedarte con el 100%? Auani te conecta directamente con clientes que necesitan viajes y entregas."

Translation: "Why pay 25-40% commission when you can keep 100%? Auani connects you directly with customers who need rides and deliveries."

Key Messages

  • 0% Comisión: Drivers keep 100% of the fare.
  • 100% Pago directo + propinas: All tips and fares go directly to the driver.
  • Horario flexible: Full schedule autonomy, no quotas.
  • Tú eliges: Drivers choose which jobs to accept.

Call-to-Action

"Calcula Costos" & "Registro para Conductor" - Buttons leading to a cost calculator and registration form.

Social Proof

Focus on economic empowerment and community-driven logistics.

Restaurant Landing Page

auani.com/restaurantes/

Value Proposition

Headline: "Vende en línea sin comisión por precio del pedido"

Translation: "Sell online without commission on order price"

Sub-Headline: "La mayoría de las plataformas te quitan 30% por cada venta. Aquí no. Con tu menú tú mandas. $3 por orden. Sin comisiones ocultas."

Translation: "Most platforms take 30% for each sale. Not here. With your menu, you're in charge. $3 per order. No hidden commissions."

Key Messages

  • 0% Comisión por precio: No percentage taken from the sale price.
  • $3-5 USD por orden: Flat service fee vs. 30-40% commission on big platforms.
  • Tu menú, tus precios: Restaurants control menu and pricing.
  • Pagos directos: Weekly deposits via Stripe Connect.

Call-to-Action

"Calcula Costos" & "Registro para Restaurante" - Buttons leading to a cost calculator and registration form.

Economics Breakdown

Side-by-side comparison: AUANI $3-5 flat fee vs. DoorDash/Uber Eats 30-40% commission on $50 order.

Copywriting Principles

Spanish-First

Primary audience is Spanish-speaking working-class drivers and restaurant owners. All landing pages, forms, and communications in Spanish. English is secondary.

Economics-Forward

Lead with numbers. Show exact costs, comparisons, and savings. Working-class audiences make practical economic decisions-respect that.

Community Tone

No corporate jargon. No tech startup hype. Direct, honest, peer-to-peer voice. "We" not "our platform."

Transparency

Show all fees upfront. Explain how the platform works. No fine print tricks. If there's a catch, say it.

Engineering

System Architecture

[System Architecture Diagram Placeholder]

AUANI Web App

Role: Driver & Rider interfaces

Tech: React, Material-UI, Google Maps API

Language: Spanish UI, English backend

Shipday API

Role: Routing, dispatch, driver management

Integration: RESTful API, webhooks for real-time updates

Google Maps

Role: Geocoding, routing, distance calculation

Challenge: Imperial vs. metric conversion for pricing

Payment Processor

Role: Transaction handling, driver payouts

Challenge: US banking infrastructure, Latino banking habits

Restaurant Backend

Role: Menu management, order processing

  • Status: Live with v3.2.0! Includes food delivery and pickup checkout wizards, Stripe integration for payments, and automated order submission to the Shipday API.
  • Food Ordering System (v3.2.0)

    Role: End-to-end food delivery and pickup checkout flow.

    Components: Delivery and Pickup checkout wizards, integrated with Stripe and Shipday.

    Admin/Oversight

    Role: Manual community engagement, dispute resolution

    Human Layer: Not fully automated-personal touch critical

    Technology Stack

    Frontend

    • WordPress: CMS foundation
    • Custom Theme: Material Design principles
    • Google Maps JS API: Map rendering, geocoding
    • Spanish i18n: Translations, locale management

    Backend & E-commerce

    • WordPress Core: PHP 8+, MySQL
    • WooCommerce: Payment processing, order management
    • WCFM: Multi-vendor marketplace for restaurants
    • Custom Plugins: Driver dispatch, trip tracking, **Food Ordering System (v3.2.0)**

    Integrations

    • Stripe: Payment processing, driver payouts
    • Shipday API: Routing, dispatch, driver management
    • Google Maps Platform: Geocoding, distance matrix
    • WhatsApp Business API: On horizon (approval pending)

    Infrastructure

    • Hosting: Managed WordPress hosting
    • SSL/Security: Let's Encrypt, Cloudflare
    • Database: MySQL with WP optimization
    • CDN: Static asset delivery

    Tech Stack Rationale

    Why WordPress + WooCommerce: Familiar ecosystem for managing complex multi-sided marketplace. WooCommerce handles payments/orders out of the box. WCFM allows restaurant self-service menu management without custom admin builds.

    Why Shipday: Avoid reinventing dispatch/routing logic. Focus energy on UX and economic model, not logistics algorithms. API integration gives control without operational overhead.

    Why Stripe: Robust payment infrastructure with support for split payments (driver payouts), recurring billing potential, and Latino banking integrations (prepaid cards, remittances).

    Why Custom Plugins: Core marketplace logic (driver onboarding, trip matching, payout schedules) requires custom WordPress plugin development. Not achievable with off-the-shelf solutions.

    Why Spanish UI + English Backend: End users need native language. Admin/dev work is faster in English. WordPress allows clean separation via translation files.

    On the Horizon (Update)

    The integration of the **WhatsApp Business API** has been put on hold indefinitely. The team is currently focusing on optimizing the existing dispatch and payment infrastructure (v3.2.0) and will revisit this feature once business registration and core operations are fully stabilized.

    Current driver communication continues via direct phone support and non-API WhatsApp groups.

    Code Samples

    Driver Fare Calculation (PHP)

    Calculates the driver fare based on distance, implementing the $5 base fare for the first 3 miles and $1.25 per extra mile logic.

    /**
     * Calculates the driver fare based on distance (miles).
     * $5 for the first 3 miles, $1.25 for every extra mile.
     *
     * @param float $distance_miles Distance in miles.
     * @return float Calculated fare.
     */
    public function calculate_driver_fare( $distance_miles ) {
        $base_fare = 5.00;
        $base_distance = 3.0;
        $rate_per_mile = 1.25;
    
        if ( $distance_miles <= $base_distance ) {
            return $base_fare;
        }
    
        $extra_distance = $distance_miles - $base_distance;
        $extra_fare = $extra_distance * $rate_per_mile;
    
        return round( $base_fare + $extra_fare, 2 );
    }

    Shipday API Order Submission (PHP)

    Submits a new order to the Shipday dispatch API using WordPress's HTTP API (wp_remote_request) for driver assignment.

    /**
     * Submits a new order to the Shipday dispatch API.
     *
     * @param array $order_data Order details (pickup, dropoff, items).
     * @return array API response.
     */
    public function submit_order_to_shipday( $order_data ) {
        $api_key = get_option( 'auani_shipday_api_key' );
        $endpoint = 'https://api.shipday.com/orders';
        
        $args = array(
            'headers' => array(
                'Authorization' => 'Basic ' . base64_encode( $api_key . ':' ),
                'Content-Type'  => 'application/json',
            ),
            'body'    => json_encode( $order_data ),
            'method'  => 'POST',
            'timeout' => 15,
        );
    
        $response = wp_remote_request( $endpoint, $args );
    
        if ( is_wp_error( $response ) ) {
            // Log error and return
            auani_log('error', 'Shipday API Error: ' . $response->get_error_message());
            return array( 'error' => $response->get_error_message() );
        }
    
        $body = wp_remote_retrieve_body( $response );
        return json_decode( $body, true );
    }

    Plugin Architecture: Main Class Initialization

    WordPress plugin structure with modular component loading and Stripe feature flag:

    /**
     * Main AUANI Plugin Class
     * Initializes all plugin components and manages lifecycle.
     */
    class AUANI_Plugin {
        private static $instance = null;
        
        /**
         * Check if Stripe is enabled
         */
        public static function is_stripe_enabled() {
            return get_option('auani_enable_stripe', 'no') === 'yes';
        }
        
        /**
         * Get single instance (Singleton pattern)
         */
        public static function get_instance() {
            if (null === self::$instance) {
                self::$instance = new self();
            }
            return self::$instance;
        }
        
        /**
         * Constructor - Initialize the plugin
         */
        private function __construct() {
            $this->load_dependencies();
            $this->init_hooks();
            
            auani_log('info', 'AUANI Plugin initialized - Version ' . AUANI_VERSION . 
                (self::is_stripe_enabled() ? ' (Stripe ENABLED)' : ' (Stripe DISABLED)'));
        }
        
        /**
         * Load plugin dependencies
         */
        private function load_dependencies() {
            // Core utilities (must load first)
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-logger.php';
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-utilities.php';
            
            // Core functionality
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-pricing-calculator.php';
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-shipday-api.php';
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-wcfm-integration.php';
            
            // Stripe payment integration (only if enabled)
            if (self::is_stripe_enabled()) {
                $stripe_files = array(
                    'class-auani-stripe-handler.php',
                    'class-auani-order-payment-tracker.php',
                    'class-auani-payment-interceptor.php',
                );
                
                foreach ($stripe_files as $file) {
                    $file_path = AUANI_PLUGIN_DIR . 'includes/' . $file;
                    if (file_exists($file_path)) {
                        require_once $file_path;
                    }
                }
            }
        }
        
        /**
         * Initialize hooks
         */
        private function init_hooks() {
            // ... (hooks for admin, frontend, etc.)
        }
    }
    AUANI_Plugin::get_instance();

    WordPress plugin structure with modular component loading and Stripe feature flag:

    /**
     * Main AUANI Plugin Class
     * Initializes all plugin components and manages lifecycle.
     */
    class AUANI_Plugin {
        private static $instance = null;
        
        /**
         * Check if Stripe is enabled
         */
        public static function is_stripe_enabled() {
            return get_option('auani_enable_stripe', 'no') === 'yes';
        }
        
        /**
         * Get single instance (Singleton pattern)
         */
        public static function get_instance() {
            if (null === self::$instance) {
                self::$instance = new self();
            }
            return self::$instance;
        }
        
        /**
         * Constructor - Initialize the plugin
         */
        private function __construct() {
            $this->load_dependencies();
            $this->init_hooks();
            
            auani_log('info', 'AUANI Plugin initialized - Version ' . AUANI_VERSION . 
                (self::is_stripe_enabled() ? ' (Stripe ENABLED)' : ' (Stripe DISABLED)'));
        }
        
        /**
         * Load plugin dependencies
         */
        private function load_dependencies() {
            // Core utilities (must load first)
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-logger.php';
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-utilities.php';
            
            // Core functionality
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-pricing-calculator.php';
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-shipday-api.php';
            require_once AUANI_PLUGIN_DIR . 'includes/class-auani-wcfm-integration.php';
            
            // Stripe payment integration (only if enabled)
            if (self::is_stripe_enabled()) {
                $stripe_files = array(
                    'class-auani-stripe-handler.php',
                    'class-auani-order-payment-tracker.php',
                    'class-auani-payment-interceptor.php',
                );
                
                foreach ($stripe_files as $file) {
                    $file_path = AUANI_PLUGIN_DIR . 'includes/' . $file;
                    if (file_exists($file_path)) {
                        require_once $file_path;
                    }
                }
            }
        }
    }
    
    // Initialize the plugin
    auani_init();

    Multi-Market Pricing Configuration

    Plugin activation sets defaults for both US (miles, USD) and Mexico (km, MXN) markets:

    /**
     * Plugin activation - Set market-specific pricing defaults
     */
    public function activate() {
        $defaults = array(
            // US Market defaults (DMV)
            'auani_us_base_rate' => 5.00,      // USD
            'auani_us_per_mile' => 1.25,       // USD per mile
            'auani_us_platform_fee' => 2.00,   // USD
            'auani_us_surge_multiplier' => 1.0,
            'auani_us_free_orders' => 'no',
            
            // Mexico Market defaults (Uruapan/Ecatepec - future)
            'auani_mx_base_rate' => 40.00,     // MXN
            'auani_mx_per_km' => 2.50,         // MXN per kilometer
            'auani_mx_platform_fee' => 35.00,  // MXN
            'auani_mx_surge_multiplier' => 1.0,
            'auani_mx_free_orders' => 'no',
            
            // Enable logging by default
            'auani_enable_logging' => 'yes',
        );
        
        foreach ($defaults as $key => $value) {
            if (false === get_option($key)) {
                add_option($key, $value);
            }
        }
        
        // Create Stripe payment tracking table if enabled
        if (self::is_stripe_enabled()) {
            $tracker = new AUANI_Order_Payment_Tracker();
            $tracker->create_table();
        }
        
        flush_rewrite_rules();
    }

    Component Initialization & Conditional Loading

    WordPress hooks system for initializing shortcodes, WCFM integration, and Stripe features:

    /**
     * Initialize plugin components
     */
    public function init_components() {
        // Initialize shortcodes for pricing display and customer forms
        AUANI_Pricing_Display::init();
        AUANI_Customer_Form::init();
        
        // Initialize admin settings
        if (is_admin()) {
            AUANI_Admin_Settings::init();
            AUANI_Dashboard::init(); // Improved dashboard
            AUANI_Admin_Debug_Logs::init(); // Debug log viewer
        }
        
        // Initialize WCFM integration if WCFM is active
        if (AUANI_Utilities::is_wcfm_active()) {
            AUANI_WCFM_Integration::init();
            auani_log('info', 'WCFM detected and integration initialized');
        }
        
        // Initialize user registration prompt
        AUANI_User_Registration::init();
        
        // Initialize Food Delivery/Pickup Checkouts
        AUANI_Food_Delivery_Checkout::init();
        AUANI_Food_Pickup_Checkout::init();
        
        // Initialize Stripe components (only if enabled via admin settings)
        if (self::is_stripe_enabled()) {
            if (class_exists('AUANI_Payment_Cron')) {
                AUANI_Payment_Cron::init();
                auani_log('info', 'Stripe Payment Cron initialized');
            }
            
            if (class_exists('AUANI_Shipday_Webhook')) {
                AUANI_Shipday_Webhook::init();
                auani_log('info', 'Shipday Webhook initialized');
            }
            
            if (class_exists('AUANI_Payment_Interceptor')) {
                AUANI_Payment_Interceptor::init();
                auani_log('info', 'Payment Interceptor initialized');
            }
        }
    }

    v3.2.0 Rideshare & Plugin Upgrades

    The core rideshare functionality received significant upgrades to improve stability, logging, and payment handling, paving the way for the new food delivery module.

    • Improved Debugging: Dedicated AUANI_Debug_Logger class and admin interface for surgical troubleshooting, replacing generic auani_log function.
    • Payment Interceptor: New AUANI_Payment_Interceptor class ensures all Stripe payments are correctly tracked and linked to WooCommerce orders before final processing.
    • Dashboard Improvement: Enhanced admin dashboard (class-auani-dashboard-improved.php) for better operational oversight.
    • Defensive Coding: Added checks for WCFM function existence in new shortcodes to prevent fatal errors when WCFM is not active.

    WordPress Plugin Folder Structure

    auani-dispatch-manager/          # WordPress plugin root (v3.2.0)
    ├── auani.php                     # Main plugin file (v3.2.0)
    ├── includes/                     # Core PHP classes
    │   ├── class-auani-logger.php
    │   ├── class-auani-utilities.php
    │   ├── class-auani-pricing-calculator.php
    │   ├── class-auani-pricing-display.php
    │   ├── class-auani-customer-form.php
    │   ├── class-auani-shipday-api.php
    │   ├── class-auani-wcfm-integration.php
    │   ├── class-auani-user-registration.php
    │   │
    │   ├── class-auani-food-delivery-checkout.php # NEW: Food Delivery Wizard
    │   ├── class-auani-food-pickup-checkout.php   # NEW: Food Pickup Wizard
    │   ├── class-auani-debug-logger.php           # NEW: Dedicated Debug Logger
    │   │
    │   └── stripe/ (conditional loading if enabled)
    │       ├── class-auani-stripe-handler.php
    │       ├── class-auani-order-payment-tracker.php
    │       ├── class-auani-payment-interceptor.php
    │       ├── class-auani-payment-cron.php
    │       └── class-auani-shipday-webhook.php
    │
    ├── assets/
    │   ├── css/
    │   │   ├── auani-frontend.css
    │   │   ├── auani-stripe-frontend.css
    │   │   ├── auani-wizard.css
    │   │   └── auani-admin.css
    │   │
    │   └── js/
    │       ├── auani-frontend.js        # Google Maps autocomplete
    │       ├── auani-wizard.js          # 5-step form navigation
    │       └── auani-stripe-frontend.js # Payment processing
    │
    ├── admin/
    │   └── class-auani-admin-settings.php
    │
    └── languages/                    # i18n translation files
    

    Economics

    Unit Economics Breakdown

    The Core Principle: Drivers Keep 100%

    AUANI does not take commission from driver earnings. Drivers receive 100% of the trip fare they charge. The platform is funded by a separate service fee charged to customers for access to the dispatch system.

    This is fundamentally different from Uber/Lyft, which take 30-40% commission from the driver's earnings. AUANI's model treats drivers as independent service providers who set their rates and keep what they earn.

    Rideshare Trip

    Trip Fare (to driver) $12.00
    Platform Service Fee (to AUANI) $3.00
    Customer Pays Total $15.00

    Driver receives: $12.00 (100% of trip fare)

    AUANI receives: $3.00 (service fee, sometimes waived)

    Note: Service fee covers platform operations, insurance, support. Driver payout is never reduced-even when service fee is waived, driver still gets $12.

    Delivery Order

    Order Subtotal (to restaurant) $25.00
    Delivery Fee (to driver) $5.00
    Online Order Service Fee (to AUANI) $3.00
    Customer Pays Total $33.00

    Restaurant receives: $25.00 (100% of order value)

    Driver receives: $5.00 (100% of delivery fee)

    AUANI receives: $3.00 (service fee for online card payment processing)

    Note: $3-$5 service fee charged to restaurant for accepting online card payments. Driver keeps full delivery fee. No commission taken from restaurant sales.

    Competitive Comparison

    Platform Driver/Restaurant Payout Platform Revenue Model
    AUANI 100% of trip/order value $3-$5 service fee (separate) Service fee model, no commission
    Uber / Lyft 60-70% (commission taken from driver) 30-40% commission from driver earnings Commission-based extraction
    DoorDash / Uber Eats 60-70% (restaurant) 30-40% commission from restaurant sales Commission-based extraction

    Key Difference: AUANI does not reduce driver/restaurant earnings through commission. The service fee is a separate, transparent charge for platform access-not a percentage cut of what workers earn.

    Transparent Pricing Structure

    Dispatch Pricing Model

    US Market (DMV):

    Base Rate: $5.00 USD (first 3 miles)

    Additional Distance: +$1.25 USD per mile

    Platform Service Fee: $3.00 USD (fixed)

    Mexico Market (future):

    Base Rate: $40.00 MXN (first 1 km)

    Additional Distance: +$2.50 MXN per km

    Platform Service Fee: $35.00 MXN (fixed)

    How It Works for Drivers:

    Drivers view available orders in Shipday app with distance and delivery fee pre-calculated. They choose to accept or ignore orders. Drivers do not set their own rates-rates are calculated automatically based on distance.

    Example Order (US):
    • 7 miles total distance
    • Base: $5.00 (first 3 miles) + Extra: $5.00 (4 miles × $1.25) = $10.00 delivery fee
    • Service Fee: $3.00
    • Customer Pays: $13.00
    • Driver Sees in App: "$10.00 for 7 miles" → Accept or Ignore
    • Driver Receives: $10.00 (100% if accepted)
    • AUANI Receives: $3.00 (service fee)

    Testing Mode: 300 free orders/month allocated for testing. Service fee can be waived without affecting driver payout.

    Surge Pricing: Feature available but not currently in use. Will be introduced transparently as demand requires.

    Delivery & Pickup Pricing (v3.2.0)

    The new food delivery module introduces a custom, 3-step checkout wizard to handle the split payment model and ensure a smooth mobile-first experience.

    Restaurant Payout: 100% of food subtotal.

    Driver Payout: 100% of the calculated Delivery Fee (paid by customer directly to driver).

    AUANI Revenue: Service Fee ($3.00 - $5.00) + Sales Tax (collected and remitted).

    Payment Flow Example:
    • Customer Pays via Stripe (Now): Food Subtotal + Sales Tax + AUANI Service Fee.
    • Customer Pays Driver (Upon Delivery): Delivery Fee (cash, Zelle, Venmo, CashApp).
    Example Order Breakdown:
    Food Subtotal$30.00
    Sales Tax (6%)$1.80
    AUANI Service Fee$3.00
    Total Paid via Card (Stripe)$34.80
    Delivery Fee (to Driver)$5.00
    Total Customer Cost$39.80

    Key Feature: The custom checkout wizard ensures the customer only pays the food subtotal, tax, and service fee via card, while the driver's fee is clearly separated for direct payment upon delivery.

    Pricing Philosophy

    No Commission: AUANI does not take a percentage of what drivers or restaurants earn. They keep 100% of their earnings.

    Transparent Service Fee: Customers see exactly what they're paying for platform access. No hidden fees.

    Flexible Waivers: Service fee can be waived without affecting driver/restaurant payouts. This allows for promotions and community support.

    Driver Autonomy: Drivers set their own rates based on distance, time, and market conditions. Platform doesn't dictate pricing.

    No Surge Pricing (Yet): Keeping it simple for MVP. Dynamic pricing may be introduced later with full transparency.

    ROI & Viability Calculator

    [Interactive ROI Calculator Placeholder]

    Input: # of trips/day, avg service fee collected, operational costs

    Output: Monthly revenue, platform sustainability, break-even analysis

    Scenario Modeling

    Scenario Trips/Day Avg Service Fee Monthly Revenue Driver Payouts Platform Margin
    Conservative 50 $3.00 $4,500 $18,000 $4,500
    Moderate 100 $3.00 $9,000 $36,000 $9,000
    Optimistic 200 $3.00 $18,000 $72,000 $18,000

    Note: Driver payouts shown separately to emphasize that drivers receive 100% of trip fares. Platform revenue comes entirely from service fees.

    Viability Notes

    Break-even: Platform needs ~$5-7k/month to cover ops, insurance, support, infrastructure.

    Conservative scenario: Achievable with 10 active drivers, 5 trips/day each. Service fee revenue: $4,500/month.

    Driver economics: At 5 trips/day × $12 avg fare = $60/day per driver = ~$1,800/month (part-time). Drivers keep every dollar they earn.

    Scaling challenge: Service fee model requires higher volume than commission model to be viable. But it preserves driver/restaurant economics.

    Not VC-viable: This model doesn't scale to billion-dollar exits. Growth is constrained by community trust and operational capacity. That's intentional.

    Operations

    Driver Onboarding Process

    1. Discovery & Outreach

    • WhatsApp groups (existing driver networks)
    • Word-of-mouth referrals
    • In-person community events
    • Flyers at gas stations, car washes

    2. Initial Contact

    • Phone call or in-person meeting
    • Explain AUANI model, commission structure
    • Answer questions, build trust
    • Human touch = critical at this stage

    3. Documentation & Compliance

    • Insurance verification
    • Background check
    • Vehicle inspection
    • Banking info for payouts

    4. App Training

    • Walkthrough of driver app (Spanish interface)
    • How to accept/decline trips
    • Navigation integration
    • Payment/payout process

    5. First Trip Support

    • Test ride with admin support on call
    • Live feedback, troubleshooting
    • Build confidence before solo trips

    6. Ongoing Support

    • WhatsApp group for driver community
    • Direct phone line to admin
    • Weekly payouts, transparent breakdowns

    Community-First Approach

    Human Engagement as Infrastructure

    Unlike app-only competitors, AUANI treats human relationships as core infrastructure. Drivers don't just download an app-they join a community with direct support.

    Engagement Tactics

    • WhatsApp Groups: Drivers share tips, ask questions, build solidarity
    • In-Person Meetups: Quarterly gatherings to discuss challenges, improvements
    • Direct Phone Support: Admin available for real-time problem-solving
    • Transparent Communication: Platform changes, pricing updates communicated clearly
    • Feedback Loops: Drivers influence product decisions (e.g., payout timing, navigation preferences)

    Trust-Building Mechanisms

    Pay Transparency: Drivers see exactly how much each trip pays before accepting.

    Weekly Payouts: Consistent schedule, detailed breakdowns.

    No Arbitrary Deactivations: Disputes handled through direct conversation, not algorithmic bans.

    Respect for Autonomy: Drivers set own schedules, decline trips without penalty.

    Logistics & Dispatch

    Rideshare Dispatch

    Current System: Shipday API handles routing, driver matching, real-time tracking.

    How It Works:

    1. Rider requests trip via app
    2. Shipday finds nearest available driver
    3. Driver receives notification, accepts/declines
    4. Real-time tracking via Google Maps
    5. Trip completes, payment processed automatically

    Delivery Dispatch (Staging)

    Current Status: Backend ready, restaurant testing in progress.

    How It Will Work:

    1. Customer places order via app
    2. Restaurant confirms order, prep time
    3. Shipday assigns driver based on proximity, availability
    4. Driver picks up from restaurant
    5. Real-time tracking to customer
    6. Delivery confirmation, payment settled

    Operational Challenges

    • Driver Availability: Balancing supply/demand without surge pricing
    • Restaurant Coordination: Ensuring accurate prep times, timely pickups
    • Customer Expectations: Competing with Uber/DoorDash on speed while maintaining economics
    • Quality Control: Manual oversight required-can't fully automate dispute resolution

    Artifacts & Documentation

    Tangible outputs from the project-design systems, code libraries, research docs, calculators.

    Design System

    [Color Swatches, Typography, Icon Library Placeholder]
    View Full Design System →

    Component Library

    [React Component Screenshots Placeholder]
    View Component Docs →

    Code Repository

    [GitHub Folder Structure Screenshot Placeholder]
    View on GitHub →

    User Research Findings

    [Research Summary Document Placeholder]
    View Research Report →

    ROI Calculator

    [Excel/Google Sheets Screenshot Placeholder]
    Open Calculator →

    Marketing Materials

    [Flyers, Social Media Assets Placeholder]
    View Assets →