About

Who I Am

Six months ago, I had ideas. Today I have domains you can type into a browser, products people log into, and agents that work while I sleep. That is the part most founders never reach. I did not stay in the planning phase. I shipped.

I am a polyglot builder. I move between code, design, AI, and brand the way most people move between rooms in their own house, and I work across languages. That fluency is the engine, not a footnote. When a client needs a landing page that converts in one language and a sales pitch that lands in another, I do not assemble a team and wait. I build the brand book, write the copy in each language, hand-code the site, harden the security headers, point the DNS, and watch it go live.

I take something from idea to shipped, end to end, across four layers at once. Design that earns trust. Code that holds up. AI that does real work, not demos. Brand that makes the whole thing feel inevitable. Most people who can design a brand cannot ship the app, and most people who can ship the app cannot position the brand. I do both, then I deploy it and harden it for security and privacy.

My origin is honest and it carries weight. I work at an Atlanta law firm, where I started building the internal tools and records systems the office runs on. That practice became Signal Studio, the studio I am building now. What changed over these six months is not that I learned to build. It is that I learned to build the way a studio does, with the same stack repeating with confidence and the discipline to ship every time.

The Timeline

From first brand assets to a CRM in production

A six-month arc. Each phase: what I shipped, the win that mattered, the challenge I had to solve.

  1. January 2026. The First Brand

    The founding assets for my own psychoanalysis practice brand: brand book, competitive benchmark, 200 content hooks, logos, and bilingual landing pages. I established my own voice and visual identity from zero, the discipline I would later sell to clients. The challenge was translating a dense, intellectual field into a warm, accessible brand that works on Instagram without cheapening it, solved with a 200-hook content system that keeps the depth but makes it postable.

  2. March 2026. First Code Ships

    Brazil Signal, an interactive app that decodes Brazilian cultural signals, with a React and Vite front-end and an Express and CORS back-end. Proof I could ship a real front-end plus back-end app, not just static pages. The challenge was structuring fuzzy cultural knowledge into a clean data model and standing up an API to serve it. This is where the idea of AI agent squads as a force multiplier was born.

  3. April 2026. Platforms and Foundations

    The Truth Seekers non-profit launch kit, the first formal security audit of The Compatibility Code, and my VideoStudio editing environment. The Compatibility Code passed its first formal audit, and I built reusable creative infrastructure I would lean on for every project after. The lesson that stuck: treat security as a gate, not an afterthought.

  4. May 2026. The Shipping Sprint

    The month everything went live. Five-plus products shipped or deployed, three on live public domains. When One Contractor’s form provider went down on launch day with an HTTP 521 outage, I migrated the form backend from FormSubmit to Web3Forms live, mid-launch, and the site stayed up. That is the difference between a portfolio of plans and a portfolio of proof.

  5. June 2026. The Ambitious Wave

    Custom domains went live for two client companies. I built and deployed the Signal Studio CRM, a full firm-management app with server-enforced role-based data isolation, and migrated it live to Firestore with zero data loss. I also shipped a free, open World Cup prediction game on my own domain, and reached Estelita’s first fully automated end-to-end video. The challenge: a client brand needed faithful AI imagery, and trained models never matched her real identity, so I pivoted to real-photo image-to-image. The right answer was not a better model, it was better inputs.

Clients and Own Projects

Two proofs of one capability

Two distinct, mutually reinforcing proofs of the same capability.

What client work proves

I can be trusted to deliver. Real businesses handed me their brand and their live presence, and I shipped it, hardened it, and replaced their old sites without downtime.

What own products prove

Founder and builder credibility. Ambitious, technically deep, multi-system products I conceived, architected, and built from zero, with no client brief to lean on.

Together they tell one story: a builder who can be trusted with real stakes and who pushes her own frontier.

See all work