Brand, Product & Full-Stack Build | Founder-Led

Building My Own Studio, Twice, On Purpose

OVERVIEW

Client work I do outside my own portfolio — Guantanamera, gotReps, Signet, Puente ATX, Blueprint AI — never had a single home, a shared identity, or a case-study format of its own. Puente Digital (puentedigitalatx.com, opens in a new tab) is that home: a bilingual design studio built around a simple premise, that brand strategy, digital design, and marketing should hold up equally in English and Spanish, not treat Spanish as an afterthought bolted onto an English site.

I designed and built the studio myself — brand, site, case-study system, and the infrastructure underneath it — from a blank domain to a live business in about five weeks. I used the build itself as a real test of process: instead of picking an AI coding tool on reputation, I built the homepage twice, once with Claude Code and once with Codex, to compare actual performance and responsive behavior side by side before deciding what to trust for client work going forward.

The result is a live studio site with its own brand system, a reusable case-study template shared by five real projects, and a full production stack — hosting, database, transactional email, and CDN — wired end to end. That foundation then stretched past the original brief: a new service line, Puente Build, with its own wordmark and site; a social post system built from the same design system; and a family of 3D icons that gives all of it a shared visual language.

Puente Digital homepage, desktop + mobile

SITUATION

A Studio That Didn't Exist Yet

I had years of client work — brand identity for Guantanamera, product design for gotReps, marketing work for Signet, a full product build for Puente ATX, a product site for Blueprint AI — living in scattered folders and one-off deliverables, with no single place that represented it as a body of work or gave a prospective client somewhere to land. None of it shared a name, a visual identity, or even a consistent case-study format.

Almost all of that work had something in common that most design studios don't lead with: it lived at the intersection of two languages and two cultures. That became the actual positioning, not an afterthought — a studio built specifically around bilingual and bicultural work, named for the thing it does: puente, bridge.

TASK

Build the Studio the Way I'd Tell a Client To

The brief I gave myself was the same one I'd give a client: settle positioning before touching a screen, design a system that could scale beyond the website, to future case studies, new services, and social channels, and don't hand-wave the infrastructure. Concretely:

• A brand and voice built around bilingual positioning, not generic "we do design" language
• A homepage and case-study template that could hold work as different as a fintech rebrand and a nonprofit product build
• A real answer, not a guess, to which AI coding tool to trust for client-facing implementation work
• An actual production stack — domain, hosting, database, email, CDN — chosen and configured myself

ACTION

1. From Idea to Infrastructure

Before any design work started, the studio needed to exist as a real, running piece of infrastructure — the part of "full-stack" that design case studies usually skip past. That meant buying the domain, then deliberately choosing a stack instead of defaulting to whatever was familiar: Vercel for hosting and deploys, Supabase for the database layer, Resend for transactional email, and Cloudflare for DNS and CDN.

Owning that decision — not just the visual system on top of it — is the difference between designing a studio and running one.

2. Brand and Voice

The palette is a cream canvas with deep ink and forest-green text and a lime accent — warm and confident rather than corporate, built in Archivo. Four commitments anchor every page and every future client engagement: bilingual by design, strategy before execution, design and marketing under one roof, and built for real audiences rather than assumed ones.

Those commitments aren't a mission-statement page — they're the filter every later decision, from the case-study template to the contact form, had to pass through.

Brand system: palette, type, and the four studio commitments

3. Building It Twice: Claude Code vs. Codex

Rather than pick an AI coding tool on reputation, I built the same homepage twice — once with Claude Code, once with Codex — from the same brief and design direction. The comparison was deliberately narrow and practical: real-world performance and responsive behavior across breakpoints, not a subjective "which one felt nicer" impression.

That head-to-head is what's actually running today, not a guess I made once and moved on from. It's also the same discipline I bring to client work — verify a tool's output against a real target before trusting it in production, rather than trusting it because it's the one everyone's using.

Claude Code vs. Codex

4. One Case-Study Template, Reused Five Times

The template that holds every case study — Guantanamera, gotReps, Signet, Blueprint AI, and this one's sibling, Puente ATX — is the same underlying structure and design system every time, not a new layout improvised per client. Standardizing that early meant every deliverable, from a brand identity project to a full product build, gets shown with the same level of polish and the same Puente Digital visual language behind it.

That's a small technical decision with a real business reason behind it — a prospective client shouldn't feel like they're looking at five different agencies depending on which case study they click.

One case-study template, five real client projects

5. A New Service Line: Puente Build

One extension of the studio was a new service line. Puente Build is a specialized practice inside Puente Digital for contractors and design professionals who need CAD drafting, 3D visualization, and Revit & BIM production support without adding another full-time role. I treated it as an extension of the studio, not a separate company: its own wordmark and site, built on Puente Digital's design system and linked back to it.

The design problem was less visual than definitional. A service like this only works if a prospective client can see exactly what goes in, what comes out, and who is responsible for what, so the page is organized around those answers.

Puente Build homepage: Blueprint → Built slider, approach, and capabilities

Three capabilities, each with a clear deliverable

CAD Drafting turns sketches, PDFs, and legacy plans into organized CAD files and existing-condition drawings. 3D Visualization helps clients understand remodels, interiors, and finish selections through clear models and presentation-ready renderings. Revit & BIM Support adds capacity for models, redlines, families, and documentation. Each one is sized so a client can start with a single deliverable or bring the team into an established workflow.

Two audiences, two kinds of value

A contractor presenting to a homeowner needs something different from a design firm working through a production backlog, so the page speaks to each separately. For contractors in the field: present project ideas more clearly, visualize remodeling and finish options, document existing conditions, and communicate in English or Spanish. For design professionals in the studio: add production capacity in peak periods, develop drawings from markups and redlines, and keep files, revisions, and handoffs organized.

A four-step process, and limits stated up front

Every engagement follows the same four steps, Share, Define, Produce, Review, with scope and responsibility confirmed before production begins. The page also states its limits in plain language: Puente Build provides drafting, visualization, and BIM production support; the client confirms field dimensions and source information; and anything that requires licensed architectural or engineering responsibility is reviewed and approved by the appropriate professional. Putting the limits on the page is a trust decision, the same instinct behind the "what the system must never do" sections in Puente ATX.

Who we help, how we work, and the scope and responsibility statement

The hero carries one interactive idea: a drag-to-compare "Blueprint → Built" slider that shows the same house as a technical drawing and as a finished building. It explains the whole service in one gesture. The site is bilingual, English and Spanish, like the rest of the studio, and I built it with Claude Code. Production is handled with a specialized production team, so the offer is backed by real capacity, and my own background in CAD drafting and 3D modeling shaped how the work is scoped. Puente Build is newly launched and still validating demand.

6. A Social Post System, Built From the Design System

Once the site existed, the same design system had to work somewhere very different: a feed. I built the studio's post system from the site's own ingredients, forest-green and cream grounds, the lime accent, heavy sans headlines with a serif italic second voice, a halftone dot pattern, and the logo in a fixed position, so a post reads as Puente Digital before anyone reads a word of it.

Bilingual by design shows up here too. Some posts are in English, some in Spanish, and some set the two side by side: "Un puente conecta" pairs Marcas ↔ Comunidades and English ↔ Español in a single layout. The 3D icons from the next section sit inside the compositions as the visual anchor.

Selected posts from the system: alternating dark and light grounds, bilingual headlines, and 3D icons as the visual anchor

It's early, and I'd rather say so plainly. In the four weeks from September 10 to October 7, 2026, the studio's Facebook page reached 192 views from 40 viewers, and 65% of those views came from people who don't follow the page yet. Those are small numbers; the signal worth reading is that the content is travelling beyond existing followers.

7. A Family of 3D Icons

A brand with only a logo and a palette gets forgettable in a feed. The missing piece was an object language, so I built a family of 3D icons that carry the identity into places a logo can't go. They share a soft, clay-like finish, rounded forms, and the same palette of forest green, lime, and cream, and each one stands for an idea the studio works with: growth strategy, human collaboration, shared ideas, brand reach, a connected community, and accompaniment.

The process was iterative, and the work was in direction rather than generation. I created them with ChatGPT, guided by the design system, and kept refining until the set read as one family instead of a pile of separate images:

1. Start from the design system: palette, finish, and form language
2. Generate and iterate across many rounds
3. Curate: keep only the icons that hold together as one set

Choosing what stays out of the set mattered as much as making it.

The icon family: growth strategy, human collaboration, shared ideas, brand reach, connected community, and accompaniment

RESULT

A Studio, Not Just a Site

What's live today:

• A bilingual studio brand and site, built from a blank domain in about five weeks
• A production stack — Vercel, Supabase, Resend, and Cloudflare — chosen and wired solo
• A reusable case-study template already holding five real client projects
• Puente Build, a new CAD drafting, 3D visualization, and Revit & BIM support service line, live with its own bilingual site
• A social post system and a family of 3D icons drawn from the same design system
• A real, evidence-based comparison of two AI coding tools built on the same brief