In production

Case studies

Two real systems running today: the problem each one solved, what we built and what changed.

Coddarix MCP

An MCP server that connects Claude to Instagram, Threads and Facebook Pages, plus a web dashboard to schedule posts and track results.

  • 3 networks

    Instagram, Threads and Facebook in one place

  • Weekly

    automatic email report

  • 40+

    tools Claude uses on your behalf

Context and problem

Publishing and measuring by hand took hours and meant jumping between tools all day.

What we built

A custom MCP server, backed by a Laravel REST API, that gives Claude the tools to run social accounts from a conversation, plus a web dashboard for the full picture.

  • Tools that let Claude publish, schedule, read analytics and review comments.
  • A Next.js dashboard with an editorial calendar, analytics and a weekly email report.
  • AI comment classification to flag the ones that need a reply.

Result

Posts scheduled straight from a conversation with Claude, and a weekly report that lands in your inbox on its own.

Tech stack

  • Laravel (REST API)
  • Next.js
  • Claude (MCP)
  • Meta Graph API
  • Laravel Cloud
  • Vercel

What's included

  • Post scheduling
  • Analytics
  • Weekly report
  • AI comment classification

How the project went

  1. Discovery

    1 week

  2. Build

    6 weeks

  3. Launch

    1 week

  4. Operation

    Ongoing improvements

Digital medical records

A custom system for a private medical practice: patient records, scheduling and clinical documents in one place.

  • 20,000+

    files migrated from Drive

  • ~70 GB

    organized by patient

  • 5 modules

    scheduling, records, prescriptions, roles and audit log

Context and problem

The patient archive lived in Google Drive folders: over 20,000 files and about 70 GB with no structure. Finding a lab result or putting together a prescription took time.

What we built

A web-based medical records system built around the practice, with the historical archive finally in order.

  • Scheduling, prescriptions and medical certificates on the practice's own letterhead.
  • Role-based permissions and a full change log.
  • The historical Drive archive was migrated and organized by patient.
  • WhatsApp appointment reminders.
  • Documents with a verification link.

Result

Each patient's history is found in seconds. Documents come out ready to print or send, with a verification link, and reminders go out over WhatsApp.

Tech stack

  • Laravel (API)
  • Next.js
  • Google Cloud Run
  • Cloud SQL
  • Google Drive API
  • WhatsApp Cloud API

What's included

  • Scheduling
  • Tabbed patient record
  • Prescriptions and certificates
  • Role-based permissions
  • Change log

How the project went

  1. Discovery

    2 weeks

  2. Build

    10 weeks

  3. Migration and launch

    3 weeks

  4. Operation

    Ongoing support

Screenshots use fictitious data

Does your process look like one of these?

Tell us what you do by hand today and we will reply with a diagnosis.

The form below is in Spanish; feel free to write your message in English.

Te respondemos por correo en menos de un día hábil.

Al escribirnos aceptas nuestro aviso de privacidad.