UI design enquiries arrive in three flavours, and clients almost never know which one they want. A 'UX audit' often turns into a Figma component-library rebuild. A 'redesign' is usually two weeks of unblocking a Series B product team rather than a from-scratch reskin. A 'design system' is often just tokens and a button library, not a 12-component production-ready kit. A generic chatbot quotes 'design fees vary' and the senior designer's call goes wide before it goes anywhere.

SleekAI reads your engagement-type pages, case studies, and rate cards straight from wp_posts and ACF fields. When a Series B PM says 'we need a UI refresh on the dashboard', the bot asks what tools the team uses (Figma, Storybook, Tailwind, Chakra), how many designers are in-house, and whether the engineering team needs tokens delivered as a Tailwind config, CSS variables, or Style Dictionary output. It quotes your published ranges: 6,500 GBP for a 1-week audit, 18,000 GBP for a 3-week sprint, 42,000 GBP for a 6-week design system engagement, all anchored to your real past projects.

By the time the call happens, the senior designer knows it's a Series B B2B SaaS using Figma + Tailwind + Storybook, four engineers and no in-house designer, looking for a 3-week dashboard sprint plus token handoff. The conversation opens with workflow and outcomes, not 'tell me about your product'. Display conditions hide the bot from in-progress case studies and live for prospect routes only. Conversation logs in WordPress show which case studies pull in serious briefs.

UI design studios sell senior product-design hours, and the difference between an audit, a sprint, and a system engagement is rarely visible to clients before the call. A design lead spending 45 minutes with a Series B PM who wanted a 1-week audit but described it as a 'redesign' is half an hour of margin gone, and a design lead who walks into a sprint thinking it's a system engagement burns trust in the first proposal cycle. Engagement-shaping at the chat layer closes that gap.

The client arrives at the scoping call understanding that 18,000 GBP buys three weeks of focused sprint delivery and a Tailwind handoff, that an audit is a prioritised teardown and not a deliverable design, and that a system engagement needs at least one engineer who can review tokens during the build. Display conditions keep recruiters on /careers, current clients on /portal, and press on /case-studies out of the prospecting funnel. Multibot lets the studio run a different tone on the developer-tools landing pages versus the consumer mobile pages, and the calendar integration writes the brief into the proposal template, so the proposal can go out the same day the call ends.

Conversation logs stay in WordPress with page URL and visitor source attached, so the studio sees which case studies pull serious briefs and which pull window shoppers. The design lead's hour goes to engagements worth shaping a proposal for.