Lesson 12 of 12 · 3 min read

What comes first when you redesign an AI product?

Cut what it does before you redraw how it looks. Complexity first, then the core patterns, then the surface, because a fresh coat of paint on an AI product that does too much makes the excess look intentional. Polish is the last step of a redesign, not the first.

Diagram: a crowded CRM narrows in three steps, cut, rethink, and refine, to one follow-up with a Send button; polish comes last.
Cut first, rethink second, and polish last. When the surface itself is the defect, polish can’t wait.

A CRM for one person starts by cutting

Chris Halaska is building YouSpot, a CRM for one-person companies, with HubSpot’s co-founder, and redesigning it in public. YouSpot reads email, calendar, and LinkedIn to remember who you know.

Most CRMs are built for teams: pipelines, seats, handoffs, reporting. A founder needs almost none of that. He lists three priorities. The order below is mine, not his.

YouSpot’s three priorities, in the order I’d take them
  1. Cut complexitywhat it doesTake out what a team product brought and one person never needs
  2. Rethink patternshow it worksRemake the few interactions everything else repeats
  3. Refresh the UIhow it looksLast, so the new surface fits a smaller product

The pattern is where the agent meets the person

In Agent Review, my simulated story of an agent building a product, an account manager archives three customers at once, and one still active goes with them. A coding agent built three working fixes in an afternoon.

Relay’s customer list in Agent Review with a confirmation bar: Archive 3 customers? Northside Trucking is active. Cancel and Archive 3 customers sit beside it.
From my work Agent Review, a simulated story. One of the three fixes: confirm first, and name the active customer. See Agent Review
Three agent-built fixes for one pattern, and the cost of each
  1. Undo afterone press, but only if someone notices in time
  2. Confirm firsta pop-up every batch, likely clicked through
  3. Review firstnames the active customer before anything goes

All three passed the automated tests. Choosing between them was a pattern decision, and no amount of visual polish would have made it for me.

Relationships raise the stakes on every pattern

Take how close you are to a contact. Do you set it, or does the CRM infer it from your email? I think that’s the redesign’s real question: what the product may conclude about someone’s relationships on its own.

The order is the design.

That’s the last idea in The Shift, my twelve lessons on design once AI agents do the work.

Check yourself

What does your product do that its smallest customer never needs?

That’s the first cut. Redesigning it first only makes it harder to remove later.

Which conclusions does your AI draw about people without asking them?

Each is a pattern decision. Make it on purpose, and let the person see and change what was inferred.

The idea: Chris Halaska, redesigning YouSpot in public. The example: Agent Review, a simulated story, on this site.