Unchanged
Discovery and art direction
Still your judgement, your client relationship, your positioning work. An agent has no opinion worth billing for here.
For agencies and freelancers
Ship the build phase in days. Keep the paper trail.
The part of a project you can compress is the middle: design system, templates, page structures, content model, forms. WPPilot Pro drives 53 integration families across the builders your clients already run, with per-client credentials and an approval gate you control.
Where the hours go
Compress the middle. Leave the ends alone.
Every week off a project cycle is another slot in the quarter. The trick is knowing which weeks are actually compressible.
Days, not weeks
The build phase
Design system, header and footer templates, page structures, content model, archive templates, forms. This is where a brief replaces a fortnight of assembly.
Unchanged
Review and launch
Responsive checks, content accuracy, performance, accessibility and the client walkthrough. Faster input does not mean skipping the output check.
Portfolio hygiene
Six rules for client work.
Speed on one site is a demo. Speed across thirty sites without an incident is a business, and the difference is entirely in how you set it up.
What Pro adds- One WordPress user per client site, scoped to the role the work needs, not a shared admin account across the portfolio.
- Staging first, always. Run the brief, review in the native editor, then repeat the run against production with the same input.
- Turn on the approval queue for any site more than one person can drive. Writes park until a human releases them.
- Keep the safety profile at Production Safe unless a specific task genuinely needs WP-CLI or PHP, then put it back.
- Treat the change record as a deliverable. A client asking what changed last Tuesday is a reasonable question with an exact answer.
- Version your briefs the way you version starter themes. The brief is the reusable asset, not the output.
The reusable asset
Your briefs become your starter kit.
Studios used to compete on their starter theme. The equivalent now is a library of briefs that reliably produce the structure your team expects.
Standardise the structure
A house brief that always produces the same page architecture, template set and naming means any team member can pick up any project without reading the whole site first.
Swap only what changes
Industry, page list, art direction and proof are the variables. Everything else, the design system step, the template step, the review list, stays constant across clients.
Keep the fact discipline
Briefs mark unverified claims rather than filling them in. On client work that habit is worth more than the speed, because an invented statistic is your liability, not the agent's.
Hand over something readable
The change record, the review list and the brief itself are all artefacts you can attach to a handover document. They make the work legible to whoever maintains it next.
Answering the client
Three questions you will get asked.
Have the answers ready before the first invoice, not after the first incident.
Where does our content go?
Nowhere new by default. The plugin runs on the client's own WordPress install. Content reaches an AI provider only through the client you connect, so name that provider in your contract.
What changed on our site?
The change record answers it per write, with a before-and-after. This is the question that makes shared admin accounts indefensible.
Can it do something we did not approve?
Under Production Safe, code execution, filesystem access, database access and user creation are not available at all. With the approval queue on, even permitted writes wait for a human.
Questions
Running this across a portfolio.
How much time does this actually save?
The savings are concentrated in the repeatable middle of a project: building the design system, the templates, the page structures, the content model and the forms. Discovery, art direction and the client conversation are unchanged, and those were always the valuable parts.
Can a junior run this safely on a client site?
That is what the profiles and the approval queue are for. Give juniors Production Safe with the queue enabled, and every write parks for a senior to release. The agent still does the work; the sign-off stays where you want it.
How do we handle credentials across many clients?
One dedicated WordPress user per client site, with the minimum role that supports the work. Never a shared admin account across a portfolio. The change ledger is only useful if it can name who acted.
Do we have to tell clients we used AI?
That is a commercial decision, not a technical one. What matters is that you can answer the question that follows it: what exactly changed, when and by whom. The change record gives you that answer.
Can we reuse a brief across clients?
Yes, and that is where a studio pulls ahead. A refined project brief is a reusable asset. The same way a starter theme was. Swap the industry, pages and art direction; keep the structure that has worked.
What about white-labelling?
The plugin runs on the client's site under their WordPress install. There is no external service in the middle holding their content, which is usually the harder question in a procurement conversation.
Building for a specific outcome? See the seven build paths.
Your site · your policy · your AI client
One brief per project. Not one afternoon per section.
Start on a single client site with the approval queue enabled, then roll the brief you refined across the rest of the portfolio.