Freelance developers lose most leads on the same gap: a founder lands on the site, can't tell in under two minutes whether the developer has shipped something close to what they need, and bounces to the next person on the Twitter list. The portfolio page is rarely organized by stack and scope, the rate sheet is half hidden, and the contact form asks for a project brief that nobody writes well on first contact. SleekAI reads the portfolio, the stack pages, and the rate sheet, then answers the three real questions: "do you ship in my stack, have you done something my size, and what's the realistic budget."

The data path is plain WordPress. Portfolio entries live as a custom post type with ACF fields for primary stack (Next.js, Rails, Laravel, Phoenix, Django), database, hosting, project scope (MVP, feature build, audit, ongoing), duration, and outcome. Service pages describe how the developer scopes, prices, and ships. The data-source wizard maps it into context, so the bot answers "shipped a Next.js plus Postgres MVP in 6 weeks, $22k fixed-scope" rather than "contact me for a quote."

Routing handles the post-qualifier step. MVP projects route to a structured intake form, feature builds for existing apps go to a different form, audits or one-off rescues go to a third, and out-of-scope inquiries (no-budget, wrong stack) get a polite redirect to a starter template. Conversation logs in wp_posts become a quiet feed of which stacks and project sizes founders keep asking about, useful signal for what to build a portfolio entry around next.

Freelance developers usually have two failure modes on their own site. The first is the portfolio gap: a founder lands looking for a Next.js plus Postgres MVP shipper, but the portfolio grid is organized chronologically and mixes Rails monoliths with Next.js MVPs without any stack labels. The founder scans for two minutes, can't confirm the developer ships in their stack, and bounces.

The second is the budget gap: the rate sheet is half hidden or missing, the contact form asks for a project brief that nobody writes well cold, and the developer ends up running scoping calls with prospects who don't have the budget for a real project. Both failures are conversion leaks, and both are about the same problem: the site presents work in a developer-friendly order rather than a buyer-friendly order. A semantic chatbot fixes the gap because it reads the portfolio CPT's structured fields and answers a project-shaped question with a project-shaped reply.

The Next.js MVP founder gets the Next.js MVP example with the timeline and fixed-scope number. The Rails feature-build prospect gets the Rails work. Routing pulls the second lever.

Different project types deserve different intake flows, and a chatbot that asks two qualifying questions and sends each prospect to the right form converts a meaningfully higher share of the same traffic. Deep-work protection is the quiet third benefit. Freelance developers ship more code when the inbox is filtered, and filtering happens upstream of the inbox by the bot.

The developer wakes up to a daily digest of three real briefs instead of forty mixed messages, and the rest of the day is for shipping. Over a year that compounding focus is usually worth more than the chatbot license cost in a single week of recovered time.