BlankSoftware

Portfolio: Operations

10 projects. See all 19

    • 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
    Stack
    • Python
    • Postgres
    • Stripe
    • MercadoPago
    • Dokku
    Visit the site

    • 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
    Stack
    • FastAPI
    • Next.js
    • Postgres
    • Stripe
    • Dokku
    Visit the site

    • 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
    Stack
    • Python
    • Postgres
    • MercadoPago
    • Dokku
    Visit the site

    • 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
    Stack
    • Python
    • Postgres
    • Dokku
    Visit the site

    • 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
    Stack
    • Python
    • Postgres
    • Dokku
    Visit the site

    • A cardiologist who publishes research and wanted to run his own site without depending on anyone.
    • His CV updates by pasting a document: an OpenAI API integration reads it and structures it on its own.
    Handles
    • Publications
    • CV, with AI-assisted import
    • Clinical content
    • Messages
    Stack
    • Python
    • Postgres
    • Dokku
    Visit the site

    • An accounting firm that wanted to change its own site. Down to the last word of the interface, they edit it themselves.
    Handles
    • Services
    • Posts
    • Team
    • Contact messages
    • Every string of interface copy, editable
    Stack
    • FastAPI
    • Jinja2
    • SQLAlchemy 2
    • Postgres
    • Dokku
    Visit the site

    • 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
    Stack
    • Next.js
    • FastAPI
    • Postgres
    • Cloudflare R2
    • Dokku
    Visit the site

    • A one-page personal site.
    Stack
    • Python
    • Flask
    Visit the site
What we do, and what it costs to start