Guiadalajara
Guiadalajara is the platform we build and run ourselves. It started as the city's directory and marketplace and grew into what a local business needs to operate: appointment booking tailored to each business type, a point of sale with CFDI 4.0 e-invoicing, orders, loyalty and customer messaging. It runs on the web, with Flutter apps in beta for consumers, businesses and couriers, and with Blue/Green deployments and separate databases per environment. It's our lab: what we learn running it is the proven foundation we bring to client projects.
- Category
- Own platform
- Status
- Our own platform
The problem
A local business in Guadalajara runs on five tools that don't talk to each other: the directory where people find it, a calendar kept in a notebook or on WhatsApp, the point of sale, the tax portal for invoicing, and a delivery app that keeps the customer and a hefty commission. The problem isn't any single tool — it's the gaps between them.
The solution
- Business marketplace and directory with public profiles, catalogs and reviews.
- Appointment booking with rules per business type (health, beauty, services), availability and confirmations.
- Point of sale with built-in CFDI 4.0 e-invoicing, collections and reporting.
- Flutter apps for consumers, businesses and couriers on a single data platform.
- Blue/Green deployments, separate test and production environments, and a backup before every release.
How we built it
We designed, built and run the whole platform, from the brand and its design system to the infrastructure. The directory and marketplace has profiles, catalogs and reviews; booking follows rules per business type; the point of sale includes built-in CFDI 4.0 e-invoicing, collections and reports; and there are orders, loyalty and messaging between businesses and their customers.
The apps are built in Flutter (consumer, business, courier and support) on one database. Today they are in beta on TestFlight and in Google Play internal testing; none is approved in a public store yet, and we say so. Video calls, WhatsApp notifications and a software-answered voice line are built and in testing.
Operations are what we reuse most with clients: blue/green deployments without downtime, separate test and production environments, row-level security in the database and a backup before every release. CFDI 4.0 stamping is built and tested with real stamps in the test environment.
The result
- Platform live at guiadalajara.com, built and operated by our team.
- 400+ data models across 20 domains (POS, collections, loyalty, messaging, booking and more).
- Web in operation and Flutter apps in beta on the same platform.
Questions
- Why show our own product as a case?
- Because it is where we first prove what we bring to clients: e-invoicing, real-time features, apps and zero-downtime releases.
- Can parts of it be reused in our system?
- Yes: the CFDI module, the messaging and notification layer, the booking pattern and the deployment setup are reused in custom projects.
- Are the apps in the stores?
- They are in beta (TestFlight and Google Play internal testing); none is approved in a public store yet.
- What happens when you update the platform?
- It ships without downtime and the database is backed up before every change, the same practice we apply to client systems.
For something like this
Tech stack
- Next.js
- TypeScript
- PostgreSQL
- Flutter (iOS y Android)
- CFDI 4.0