A discovery call with a founder is one of the most asymmetric pieces of time in any practice. It costs the fractional CTO an hour and costs the founder real focus. When the engagement isn't a fit (wrong stack, wrong stage, budget half the floor) both sides lose that hour and the founder leaves with no useful next step. SleekAI runs the qualifying conversation on the site itself so the calls that hit your calendar are the ones where the work is real.

The bot reads your engagement models, your typical retainers, your case studies, and your technical focus from WordPress (post types, ACF fields, taxonomies, the data-source wizard maps each). When a Series A founder asks about a CTO-as-a-service engagement, the bot quotes the monthly retainer range, describes the days-per-week shape, and surfaces case studies in their stack and stage by taxonomy. When the founder is pre-seed with a $3,000 budget, it says so politely and points to advisory hours or a referral list.

BYO API key means OpenAI, Anthropic, Google, or OpenRouter and you pay only your provider. Conversation logs stay in your WordPress install with model name, token usage, and page URL, so you can see which pages generate which inquiries. The bot is the qualifying conversation a senior advisor would run if they had time on every visit, which is to say, never.

Fractional CTO work has a brutal economic shape. The work itself is highly leveraged: one experienced operator can shape an engineering org in two days a week for less than the cost of a senior hire. But the inquiry pipeline is the inverse.

Every discovery call is an hour of the most expensive time in the practice, and a non-trivial fraction of those calls are with founders who can't afford the retainer, are at the wrong stage, or are in a stack the operator doesn't work in. Pushing qualification upstream onto the website changes that math fundamentally. A bot that asks the same questions a senior advisor would ask in the first five minutes (stage, stack, urgency, budget, decision-makers) does not do anything magical.

It just does the work consistently, and at 11pm when the founder is browsing CTO sites trying to figure out whether to hire or fractionalize. The stage filter is the most important piece. Pre-seed founders almost always need advisory hours rather than a fractional CTO, and a bot that gently routes them there leaves a much better impression than a calendar invite for a call that ends in "sorry, you're not ready for us." Series A through B founders are usually the sweet spot, and for them the bot's job is to confirm fit, surface relevant case studies, and book the call with full context attached.

Series C and up generally need an interim placement, which is a different engagement and a different conversation, and the bot routes accordingly. The case-study matching layer is the multiplier. Most fractional CTO sites accumulate a decade of wins across stacks and stages, and a visitor will not dig through every one.

A bot that surfaces the relevant proof at the moment of doubt, fintech proof for a fintech founder, infra-cost proof for someone bleeding on AWS, dramatically compresses the consideration cycle. And because the conversation logs sit in WordPress with the model name and token usage, the cost-per-qualified-lead picture is visible from day one. That measurability is what makes the system worth running.