Most people ops engagements split by company stage rather than service line. Seed-stage clients need a first set of policies and an HRIS picked. Series A and B clients need an org design, comp banding, and a performance system. Late-stage clients need scale playbooks, manager training, and people analytics. A single contact form forces all three into the same flow. SleekAI runs the right conversation for each stage on the page itself, so the engagement lands shaped from message one.

The bot reads your engagement playbooks, your fee model, and your case studies from WordPress (post types, ACF fields, taxonomies, the data-source wizard handles each). When a Series A founder asks about org design, the bot describes the typical engagement (role architecture, levelling, manager toolkit), quotes the fee range, and surfaces case studies by company size. When a 200-person company asks about manager training, the bot routes to the leadership lead with the right context.

BYO API key means OpenAI, Anthropic, Google, or OpenRouter and you pay only your provider. Conversation logs stay in WordPress with model name, token usage, and page URL, so the firm sees which stage pages generate which inquiries and where the next sample case study or playbook would do the most good.

People ops consulting is a domain where the same words mean different things at different company sizes. "Org design" at a 30-person Series A means "draw your first real org chart and define how roles relate to each other." "Org design" at a 500-person Series D means "untangle five years of organic structure into a coherent operating model." Both clients land on the same services page, and a generic contact form treats them the same. The result is a scoping call that opens with twenty minutes of "so what stage are you at?" before anyone can actually talk about the work.

A chatbot that identifies stage in the first two messages and runs the right qualifying conversation for each replaces that twenty minutes of every call. The pain anchor is the second big win. People ops engagements almost always trigger off a specific pain: comp confusion, attrition, a botched performance cycle, a failed manager promotion, a scale moment where the org broke.

A bot that asks "what's pushing the timing?" early in the conversation surfaces the actual pain rather than the generic problem statement that the contact form would catch. The scoping call then opens on the real issue with the relevant case study already in context, and the partner walks in with the picture drawn. The domain routing layer matters more than it looks.

Most people ops firms have a comp lead, an org design lead, a leadership development lead, and someone on people analytics. Each one runs a different style of scoping call. A bot that routes by domain to the right lead, with the conversation transcript attached, means the scoping call is with the person who actually does the work rather than a generalist partner who then re-routes internally.

That single change cuts a week off most engagement starts. And because the conversation logs sit in WordPress with the model name, token usage, and page URL captured, the firm gets a structured view of which stage pages generate which kinds of inquiries, which is the kind of marketing intelligence that turns the website from a brochure into a real intake system.