Portfolio: Systems and dashboards
9 projects. See all 19
- Healthcare by membership rather than by visit — individual, family or company — so that cost stops being the reason someone does not see a doctor.
- Sign-up by CURP and payment through MercadoPago: built for how people register and pay in Mexico.
HandlesVisit the site- Individual, family and company memberships
- CURP sign-up
- MercadoPago billing
- Member records
- A wellness centre had booking, payments and publishing in three separate systems. Now it is one.
- The public site holds none of its own text: the team writes it from here, in two languages, without touching code.
- It charges through Stripe and MercadoPago at once, because its customers pay both ways.
Handles- Bookings
- Payments through Stripe and MercadoPago
- Nine pages of content in two languages
- Staff and access
StackVisit the site
Python
Postgres
Stripe
MercadoPago- Dokku
- A tasting is an event with a capacity, not a catalogue product. The platform sells seats, not units.
- Bookings, holds and per-event codes, so filling a table does not depend on WhatsApp.
Handles- Events by venue
- Schedules and capacity
- Bookings and seats
- Holds
- Per-event discount codes
- Subscriptions
- Hosts
- Site content
StackVisit the site
FastAPI
Next.js- Postgres
- Stripe
- Dokku
- Teaching online is not selling a course once: the academy lives on subscriptions that renew on their own.
- Courses, mentoring and incubator programmes in one place, with payment solved for Mexico.
Handles- Courses and classes
- Enrolments
- Recurring subscriptions
- Payments through two MercadoPago applications
- Catalogue, versioned by migration
StackVisit the site- Python
- Postgres
- MercadoPago
- Dokku
- Five client sites that used to be edited one by one are now written from a single place, each with its own language and brand.
- The studio publishes without asking a developer for anything.
Handles- Five client sites
- Pages and entries per tenant
- Media on Firebase
- Newsletters
- Analytics
StackVisit the site- Python
- Postgres
- Dokku
- A scrap yard buys and sells in cash all day. The system turns that into numbers that balance at closing time.
- Every transaction carries a photo, a weight and a price, so a note can be reconstructed months later.
Handles- Purchase and sale notes
- Inventory by material
- Conversions and losses
- Cash, counted physically by denomination
- Commissions
- Branches
- Partners and deals
- Calls and follow-up
StackVisit the site- Python
- Postgres
- Dokku
- A platform in development.
- A client should not have to ask how their project is going. The portal shows it: phases, deliverables, tickets and invoices.
- The same template we use for client work. If it did not hold up, this is where it would show first.
Handles- Projects and phases
- Steps waiting on the client
- Tickets with evidence
- Invoices, display-only
- Invites and sessions
StackVisit the site- Next.js
- FastAPI
- Postgres
Cloudflare R2- Dokku
- A psychologist finishes a video session. PIA transcribes it and writes an anonymised clinical summary, structured for their school of therapy.
- Eight schools, from CBT to psychoanalysis, each with its own structure. The model records only what was said: no names, no diagnoses, no guesses.
- Finding a therapist is the hardest part of starting. Here you search, connect and book; the Zoom link and the calendar invite create themselves.
- Every psychologist is reviewed by a person before any patient can find them.
Handles- Psychologist search and matching
- Sessions with Zoom and Google Calendar
- AI session transcripts and summaries
- Memberships with recurring billing
- Vetting of every psychologist
- Messages, notes and notifications
StackVisit the site- FastAPI
- Next.js
- Postgres
- OpenAI
- MercadoPago