Example walkthroughs

An agency puts a client business on White label

The partner: a design agency that runs websites and social posts for local clients on monthly retainers. The business: Rhône Roastery, a coffee truck in Lyon.

1. The pitch is the build. In the first meeting, the account lead types the owner's own words, "A coffee truck in Lyon.", and the team reads it back as a plan: the business named Rhône Roastery Mobile, 8 pages including Menu, Locations and Catering, and an ordering plugin for the menu. The owner watches the site take shape before anyone has signed anything. Building it is free.
2. The agency sets its own price. The agency pays $369 a month for up to eight client businesses on White label, $46.13 each, and $25 a month for each one after the eighth. What it charges the coffee truck is its own decision, on its own invoice. We never see it and we never contact the client.
3. The business goes under the agency's brand. In Settings, White label, the agency saves its name, logo and colors, adds its sending domain, and enters the owner's email for the weekly report. Its clients log into a dashboard on its own address.
4. The yes stays with the agency. Every week the team plans the work toward a goal and drafts the posts, pages and offers. Each piece waits under Waiting for you, with the work of every client business in one queue, and the agency approves it from the dashboard or from WhatsApp.
5. Monday, the report. The owner gets the week's report in plain language, by email, from the agency's domain and under its name: what sold, what got traffic and what to do next.

What to take from it: nothing to prepare before the meeting, a price that is the agency's own, and an owner who hears from the agency every Monday.

A hosting company adds a build button to its panel

The partner: a regional hosting company with a WordPress plan. The business: Earth & Fire, a ceramics studio in Lisbon selling handmade tableware online, with delivery in Europe and pickup at the studio.

1. One button where customers start a site. The host adds "Build my business with AI" next to its site tools. The button opens the free build with the host's partner code and its own customer number: dashboard.wpmaven.ai/create?ref=WPM-P-…&pref=CUSTOMER-NUMBER.
2. The customer builds it free. The studio owner describes the business in a few sentences and watches the team build the store, its shop page and its products. No card is asked for.
3. If they keep it, they pay us. The owner starts with $1 for the first week, one time only, then picks a plan. They pay on their own card, through our checkout, and we handle billing, refunds and support.
4. The host earns 20%. Every month, for as long as the customer stays, the host earns 20% of what we collect from them, net of tax and card fees. On a $69 plan paid in the United States, that is $13.34 a month. The host's Partner program page shows the customer by the host's own customer number, with every payment and the exact figures.
5. The month closes on the 1st. The statement shows what was earned and what a refund took back, and our team sends the payout by bank transfer and marks it paid on the same page. The host never invoices us and never sends us money on this route.

The $13.34: it is the calculation of the share on one $69 payment in the United States, not an expected income. What a host earns depends on how many of its customers subscribe, which nobody can know before the launch.

A freelancer hands a client the approvals

The partner: a freelance marketer on White label who runs a few client businesses and does not want to be the bottleneck. The business: Kinetic Room, a physiotherapy practice with appointment requests online.

1. The practice is built from a description. Two therapists, 45-minute appointments booked online, the services, the team and the address, and no online payments: the build follows the sentence.
2. The practice approves its own posts. On her Team members page, the freelancer chooses "Hand a client their approvals" and invites the practice manager for that one business. The invitation goes out from the freelancer's own domain, in her brand. The manager signs in with a code sent by email, with no password to create.
3. The client sees that business's approvals and nothing else. The manager approves, rejects or asks for changes in her own words. Nothing is published until she says yes.
4. The freelancer keeps the overview. Every decision is in her audit log, and the work still sits in her own queue, so she can step in.

What to take from it: the yes can sit with whoever knows the business best, and the person who set it up still sees everything.

A software company connects through the connector

The partner: a company that makes an assistant for service businesses. The business: House Call Cycles, a mobile bike mechanic in Dublin who repairs bikes at the customer's door.

1. The owner makes a token. In the WPMaven dashboard, Settings, Connect your AI, the mechanic creates a token for the assistant and pastes it into the partner's product.
2. The product reads before it writes. It calls get_site_info and get_action_status on the connector: the site, the plan and the actions left this month. Reading is free.
3. It drafts, and the owner decides. When the mechanic opens new repair slots, the assistant writes a post about them as a draft, which is free. The mechanic reads it and tells the assistant to publish it, which uses one action.
4. Nothing else is reachable. The token works on that owner's sites only, on posts and pages only, and the owner can revoke it at once.

The reference: every tool, rule and error is in the API reference.

Your own story

Running WPMaven with your clients or customers? Tell your named contact. With your permission, and with your real numbers and nothing else, we write it up together, and Featured partners get theirs first (see the rewards terms).