658: Andy Bell on Working with Clients, Writing, and Building Courses for Web Builders

What It Covers

Andy Bell discusses his agency Set Studio's browser-first design approach, delivering prototypes instead of Figma files to clients, and building Piccalilli as a publisher for practical web development courses focused on battle-tested techniques over bleeding-edge features.

Key Questions Answered

• •Client Control Through Process: Set Studio maintains project control by delivering designs only in browser prototypes with Loom explanations, never sending static Figma files. They conduct long discovery phases to understand requirements, then present direction rather than asking permission, which prevents clients from derailing projects with uninformed decisions.
• •Decision Log System: For challenging clients, implement a read-only decision log documenting who made each decision, when, and what was decided. This creates accountability, makes stakeholders think before deciding, and provides grounds to increase budget when clients reverse their own documented decisions, especially useful with multiple decision-makers who communicate poorly.
• •Design Token Architecture: Build themeable systems using semantic design tokens that reference core tokens through CSS custom properties with double fallbacks. This allows complete brand customization by changing a few variables rather than writing specific override CSS, making future redesigns or multi-brand implementations significantly faster to implement and maintain.
• •Browser-Native Layout Philosophy: Use flexible layout systems with CSS Grid and Flexbox that work with browser capabilities rather than fighting them. Let the browser handle responsive behavior through hints and bounds instead of rigid breakpoint-based layouts. Design decisions often change in-browser because what works in Figma doesn't always feel right when implemented with actual web behavior.
• •Publication Standards for Trust: Only recommend techniques after battle-testing them in real client projects, not theoretical demos. This approach builds reader trust by ensuring all published content represents proven, production-ready solutions. Avoid covering bleeding-edge features until they have genuine use cases and stable browser support, focusing on immediately applicable knowledge over novelty.