Start here when the real question is not “do I want AI?” but “which deployable agent should run this problem first, and which smaller skill pack should support it afterward?”
The deployable smart operator for lead follow-up, quiet quotes, aging estimates, and the repeated revenue leak where nobody clearly owns the next step.
Best for: the first repeated revenue leak.
Olivia, the Personal Assistant Operator
The hosted owner-side agent for priorities, follow-through, notes, and weekly operating rhythm.
Best for: owner-side clarity, rhythm, and follow-through.
Deploy OliviaRiley, the Content Engine Operator
The hosted content agent for turning offers, FAQs, proof, and customer wins into a calmer weekly content rhythm.
Best for: content built from real offers, FAQs, and wins.
Deploy RileySophie, the FAQ Operator
The hosted support-side agent for repeat-question support, saved answers, and cleaner support-side routing.
Best for: repeat-question support and reusable answers.
Deploy SophieUse the narrower packs when the problem is re-engagement, quote-stage hesitation, or a smaller follow-up bottleneck inside Martha’s world.
Best for: stalled warm leads and quote-stage friction.
Use these when inbox control, meeting follow-through, or weekly owner rhythm needs narrower help around Olivia.
Best for: tighter operating rhythm without upgrading the whole stack.
Use this when the broader content operator is not the issue and the real need is turning one useful source into several cleaner posts faster.
Best for: execution-led content bottlenecks after the main strategy is clear.
Use these when repeated customer questions, reply quality, or public review handling becomes the sharper support bottleneck.
Best for: support cleanup before or around a broader hosted rollout.
Use this when proposal quality, conversion messaging, or a narrower workflow friction becomes the real issue.
Best for: cleaner proposal output without changing the whole sales stack.