Referral partner
Use this when the client should own billing, support, and the assistant account. You make the introduction, keep the implementation boundary clear, and avoid becoming the client’s support desk by accident.
Agency and consultant guide
Add useful AI support to a client site without adding a new mess.
A grounded website assistant can be a useful add-on for a web build, but the commercial model matters. Decide whether the client should own the account or whether your agency will package the assistant into an ongoing service.
Disclosure: this independent guide includes a SiteMind referral link. If you start a paid subscription through it, I may earn a recurring commission at no extra cost to you. The provider’s partner page describes referral and reseller options; confirm current rates, eligibility, billing, and obligations inside the partner account before making a client promise.
Provider-published economics to verify
- SiteMind’s public partner materials currently show 20% to 35% recurring monthly commissions on the partner page; the Partner Hub sign-in page advertises 25% to 35% recurring and a 30-day cookie window. It also shows a Growth-plan example of $17.25 per month at a 25% rate for one active customer.
- Its reseller example uses SiteMind’s published $25, $69, and $149 monthly plans and says agencies set their own client retainer pricing.
- The public pages say partner accounts have no setup fee or credit-card requirement, but approval, payout, billing, and white-label terms should still be confirmed in the account before you sell the offer.
These are provider examples, not guaranteed earnings. Revenue depends on qualified traffic, paid retention, support work, refunds, and the rate in force when a payment clears. Read the public partner terms and Partner Hub terms.
Agency or reseller setup
Use this when your agency already sells website maintenance or marketing retainers. Confirm the white-label, account-access, invoicing, and support rules before bundling it into a recurring offer.
1. Sell the outcome, not “an AI chatbot”
Define the first job: answering documented service questions, qualifying an inquiry, routing a support request, or helping visitors find a policy. Avoid promising autonomous expertise.
2. Choose who owns the source material
Assign responsibility for prices, hours, services, policies, and stale pages. The assistant can only be as reliable as the content someone is willing to review.
3. Keep the handoff visible
Give visitors a real contact route and tell the assistant when to stop. Test sensitive, urgent, and undocumented questions before the client invites traffic.
4. Write the commercial boundary
Put setup, source maintenance, human review, analytics, usage limits, renewals, cancellation, and support ownership into the proposal. “Included” should mean something specific.
5. Verify the exit path
Document account ownership, export or removal steps, domain control, access changes, and what remains on the site if the client ends the service or leaves your agency.