Claro Case Study

Claro
An AI co-pilot for the job search

I built a product from scratch using AI as my implementation partner. No engineering background. Just a clear problem, a strong point of view, and a lot of iteration.


My Role
Product, Brand, Design, Strategy

Timeline
2025 – 2026

Stack
Next.js · Supabase · Claude API · Vercel

Screenshot of a professional job application and resume platform with sections on assessing fit, background, and application strategies, featuring search and scoring features.

claroapp.co: dark navy landing page with product preview. Built as a full marketing page, not just a logged-out shell.

Screenshot of a job tracking dashboard with sections for job roles, fit scores, statuses, and actions, showing two job entries for VP roles in branding and creative fields.

My Jobs: every scored role with fit score, pipeline status, and one-click access to Job Fit and Prep

Where it Started

My wife was getting nothing but silence

She has a strong background and was applying to roles and hearing nothing. Job boards surfaced volume. Generic AI tools gave generic advice. Nothing could tell her: here's how a recruiter is actually reading your background, and here's what to do about it. That gap felt solvable, so I built it.

I set out to solve a problem for one person. I kept going once I realized it wasn't specific to her at all.

I directed every decision: product strategy, information architecture, brand voice, design system, UX behavior. Claude Code implemented them precisely. Every session had a defined goal and explicit guardrails about what not to touch. The result is a production-deployed application I couldn't have written by hand. But everything it does came from decisions I made.

Product strategy

IA

Brand identity

AI tool direction

UX design

Design systems

Prompt engineering

Voice and tone


Product Strategy

Figure out the core thing. Then build around it.

The first real decision was figuring out what Claro was actually for. AI-powered tools tempt you to do everything. I landed on a clear center of gravity: job fit clarity. The simultaneous analysis of a candidate's profile against a specific role. Once you know your fit, what to emphasize, and what concern a recruiter is likely to raise, everything else has direction. Cover letters, outreach, and interview prep are all in the product, but they work because the fit assessment came first.

Screenshot of a digital profile page on a job platform with sections for background, jobs, and discover, displaying a professional profile focused on marketing and leadership roles.

Profile: role clusters, positioning risks, and a recommended LinkedIn headline

Screenshot of a job scoring platform showing a page titled 'My Jobs > Job Fit'. It displays an overall fit score of 9 out of 10 for a VP, Brand and Creative role, with detailed reasons for the score including fit categories like functional, seniority, industry, and keyword overlap. The left sidebar includes menu options and the user's email at the bottom.

Job Fit: 1–10 score with dimension breakdown and recruiter concern

Brand and Design

The product needed a point of view

The name came early. Claro, from the Spanish for "clear." Short, ownable, not tech-y. It should feel like a strategic advisory service, not a startup. The first version was called Signal and had a colder, more utilitarian look. The second version moved toward warm and editorial: off-white, serif type, considered spacing. Closer, but it still read as AI-generated. The third version is where it landed: Geist throughout, true white and dark navy, no serifs, no warmth. Confident and geometric. The kind of design that doesn't announce itself.


Before and After

Designing with AI: from warm editorial to confident geometric

The second version used a warm off-white palette, DM Serif Display for all display type, and an editorial aesthetic borrowed from print. It was considered and intentional. It still read as AI-generated. That combination had become a signature of AI-built products. That was the problem.

I used Claude Design to explore a new direction: answering questions about typeface, surface color, layout, and status palette before seeing a single mockup. The output was a high-fidelity prototype I could react to, iterate on, and hand off to Claude Code as a precise implementation reference.

A webpage with a beige background that features a motivational quote about knowing your fit before applying for jobs, a resume management section, scoring and tips for job applications, and a call-to-action to apply to fewer jobs. The page has sections for uploading resumes, scoring job descriptions, and application briefs, with some example job titles and scores.

Before: warm off-white, DM Serif Display, editorial aesthetic

Screenshot of a web page titled 'My Jobs' with job application tracking, including job titles, scores, and statuses. The left sidebar lists sections: My Jobs, Profile, Discover, Job Fit, Prep. The main area displays job roles with progress scores, application options, and actions like 'View Brief,' 'Go to Prep,' and 'Score a Job.'

Before: warm off-white interior, serif type, card-based job list

Screenshot of a website titled "Know your fit before you apply" with sections about job application tips, including uploading a resume, understanding market background, building a prep guide, and job fit scoring, all in a dark-themed layout.

After: dark navy landing, Geist, monochromatic system

Screenshot of a job application tracking webpage. The page is titled 'My Jobs' and shows two listed roles for VP, Brand and Creative, and VP, Global Brand and Creative. The interface has options to search, filter by stages, view fit scores, and actions like viewing, renaming, or removing jobs.

After: white interior, table layout, geometric type system


The Design Process

Claude Design as a creative direction tool

Before generating any mockups, Claude Design asked a series of questions: typeface direction, surface color, layout vibe, fit score treatment, card density, status palette. Answering those questions precisely (geometric sans, dark navy, Linear-style layout, open and breathable) produced a first pass that was already close to right.

The key moment was the surface comparison: dark landing page on the left, light on the right, same layout, one variable changed. The dark version was immediately right. That single decision, confirmed in seconds by seeing both options side by side, set the tone for the whole system. From there it was iteration, not exploration.

Comparison of dark and light website surface designs for a land pages with the title "Know your fit before you write a single word" on the dark background and a smaller version on the light background.

Surface comparison: the decision that set the tone for the whole system

A screenshot of a website or app interface showing a profile page of a professional or company, with sections including 'My Jobs,' 'Profile,' and a description of leadership and strategic goals for building high-performing teams and integrated campaigns.

Design decisions logged, prototype files generated alongside

Screenshot of a digital interface showing a job fit assessment page on the right side. The page features a score of 9 out of 10, with details on the scoring criteria, and a section for applying or scoring another job. The background is white with black and gray text, and there are sections for viewing application briefs and job details.

Surface transition canvas: dark entry, white working tool. A deliberate product decision.

Screenshot of a digital interface showing a professional profile or resume. The main focus is a pop-up window with a brief summary of a VP, Global Brand and Creative role. The background shows parts of a webpage with navigation links and some text content.

Your Brief: assembled from stored data, triggered from the Prep screen. Copy or email in one click.

UX Decisions

Navigation should reflect how people actually use the product

The original app had five sidebar nav items: My Jobs, Profile, Discover, Job Fit, and Prep. The problem was that Job Fit and Prep aren't destinations: they're things you do to a specific job. Treating them as top-level nav implied they were independent tools. They're not.

I removed them from the sidebar entirely. My Jobs, Profile, and Discover are the three destinations. Job Fit and Prep are accessed through the job workflow: View Fit from a job row, then Prep from Job Fit. A breadcrumb navigation on those screens shows where you are and lets you move between stages. The sidebar got simpler. The mental model got clearer.


Validation

Real feedback, applied immediately

The app has been in active use with real test users, one being a senior professional navigating a deliberate career move. Her feedback shaped the product more than any other input. The Prep tab originally showed all seven features at once. She found it overwhelming. I added progressive disclosure by stage. Her response: "so much better." The email-brief feature came from her pointing out that a brief is only useful if it's in her workflow when she's actually writing.

When I asked if she'd pay for it, she said yes. That's the signal that matters at this stage.

12

Claude API routes, all rate-limited and production-deployed

3

Sidebar destinations: My Jobs, Profile, Discover. Everything else is a workflow.

0

Lines of code written by hand


What This is About

The gap between having an idea and building a product is closing fast

The skills that make someone good at brand strategy, creative direction, or product leadership translate directly into building with AI. Knowing what you want, being specific about it, and being willing to iterate when you're wrong. The tools are different. The thinking is the same.

The constraint now is clarity of thinking, not access to implementation.