Training your team on an AI website platform in one week: a five day plan

By Ranjit Bhinge, founder of Blur Studio · Updated · 8 min read

Short answer: You can get a small web team productive on a new AI website platform (a tool where you describe or point to a site and an AI agent builds and edits it) in one week if you give each day one job: learn the tool, rebuild a real small site, learn the review standards, practise launching, and then hand over a site as a test. The week ends with a written procedure (an SOP, or standard operating procedure) so the next hire does not start from zero.

Ranjit Bhinge

The tool takes a day to learn. The review standards take the rest of the week, and they are what protect your clients.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Plan the week around outcomes, not tool tours. By Friday each person should have built a small site, passed a review against your written standards, launched it to a test address, and written down what they would do differently. The plan below is built for a team of 3 to 10 people at a 10 to 30 person agency, and it works for any AI website platform. I use Ploy, an AI platform that builds and hosts marketing websites, as the running example because its docs are public, but swap in your own tool.

This page may contain affiliate links from which Blur Studio earns commissions.

Facts about Ploy are as of November 2026 and come from its public pricing page and docs. Check them before you rely on them. Standards listed here are information, not legal advice.

Before day one: five things to set up

  1. One owner. A single person runs the week, sets the standards and signs off. Without an owner, training turns into everyone doing their own thing.
  2. A practice account. Use a separate account or workspace for training, never a client's. Ploy's Free plan gives 500 AI credits a day up to 2,000 and publishes to a ploy.build address, but it does not include collaborators, so a team that wants to share one workspace needs a paid plan. Ploy's docs say Starter, Pro and Enterprise allow inviting collaborators with no stated limit. Check Ploy's pricing page for current plans.
  3. Roles and access. Ploy's docs describe three roles: Owner (organisation-level control, including People and billing), Admin (elevated permissions, including deleting workspaces) and Member (standard collaboration). By default every role can reach every workspace. Limiting a Member to chosen workspaces is available on request. Decide who is what before day one.
  4. A training site brief. Pick a real but low-risk small site to rebuild, such as your own agency's one-page site, or a friendly local business that has agreed in writing. Never train on a live client site.
  5. A credit budget. Ploy's AI credits are shared across the organisation, do not carry over, and have no published price per action, so measure what the week costs you and write it down.

The five day plan

DayGoalEveryone doesPass
1Understand the toolWalk through setup, the chat with the AI agent, preview versus published, versions and how to roll backEach person publishes one test page to the practice address and restores an earlier version
2Rebuild a real sitePoint the tool at the training site's address, review the plan it shows, build 4 to 6 pagesPages match the brand, nothing invented, links work
3Review standardsRun the review checklist below on a colleague's build and write up fixesReviewer finds and logs at least the planted errors, author fixes them
4Launch mechanicsForms, analytics, domain and redirects on a practice domainA test form reaches a real inbox and events show in analytics
5Handover testTrain a colleague playing the client to make one edit, then write the SOPThe "client" completes an edit with no help, and the SOP is reviewed

Day 1: learn the tool by using it

Skip long slideshows. Give each person a 90 minute guided run. Ploy's quick start docs describe the onboarding as: confirm your website (or none), choose goals, choose a design approach, finish setup, take a short tour, then a first chat, where the first page is published once to a ploy.build address and migrations wait for your approval. After that, teach five habits:

  • Ask for a plan first. For anything big, ask the agent to show its plan and the expected credit use before it builds.
  • Preview before you publish. Publishing and previewing are separate steps. Make "preview, review, then publish" the rule.
  • Know the undo. Ploy's docs say every publish is a saved snapshot and you can restore under Versions, then publish. Have each person practise it once.
  • Keep auto-publish off for clients. Ploy's docs describe an auto-publish setting, where its AI can publish changes without you pressing the button. Its blog recommends a "preview only" mode if you use it. For client sites I would keep a person in the publishing step.
  • Know the limits. Ploy's own docs say a migration is a rebuild and not an identical copy, and that forms, plugins, shortcodes and custom code "may need separate work". Teach people to check those first.

Day 2: rebuild a real site

Real content teaches faster than lorem ipsum. Have each person rebuild the same small site, so that on day 3 you can compare outputs. Keep a shared notes file with three headings: what worked, what the AI got wrong, and what I would ask differently next time. The "got wrong" list becomes the core of your review checklist.

Day 3: review standards

This is the most important day. AI tools produce confident, polished pages that can carry wrong facts. Google's guidance on AI content says output can contain errors (it calls them hallucinations) and that you should fact-check and review it before publishing. Use the checklist in the next section, and plant three deliberate errors in a practice page (a wrong phone number, a broken link and an invented claim) so the reviewers learn what finding them feels like.

Day 4: launch mechanics

Walk the whole path on a practice domain: connect the domain, check the certificate, test redirects, test the form, check analytics. Ploy's docs note that DNS (the records that point a domain at a host) can take up to 24 hours to take effect, and that its analytics do not add a cookie banner, so a consent tool is the team's job. Forms in Ploy store text only, so decide how you will handle file uploads and spam protection. Practice a rollback.

Day 5: the handover test

Ask one person to act as the client. A teammate who built the site trains them to make one edit, publish and roll back. If the "client" cannot do it unaided, the training material is not ready. Then write the SOP together (next section).

Review standards: copy-ready checklist

Give every build a pass or fail against these. A fail on any line blocks launch.

  1. Facts. Every name, number, address, price and claim matches the client's own source. A named person has signed this line.
  2. Invented content. No made-up reviews, awards, staff or case studies.
  3. Links and buttons. Every link works and every call to action goes where it says.
  4. Forms. A test submission reaches the right inbox, not spam. The success message appears.
  5. Speed. On a phone, the main content appears within 2.5 seconds (Google's web.dev target for Largest Contentful Paint at the 75th percentile of visits), and the page reacts to taps within 200 milliseconds.
  6. Accessibility basics. Keyboard-only walkthrough works, focus is visible, contrast is readable, and tap targets are at least 24 by 24 pixels, per WCAG 2.2 (the Web Content Accessibility Guidelines, the W3C's accessibility standard).
  7. Search basics. Page titles, descriptions, headings, a sitemap (a list of pages for search engines) and redirects (automatic forwards from an old address to a new one) for any changed web address.
  8. Tracking. Form submits and call clicks show up as events.
  9. Privacy. Privacy policy exists, and the consent banner (if needed) is wired. Check local law.
  10. Rollback. The reviewer has restored the previous version once.

Mark the review in a sheet: reviewer name, date, pass or fail by line, and fixes. For a fuller list, see the quality control checklist for AI-built websites, and for the process of reviewing changes before they go live, see how to review website changes before they go live.

Turn the week into an SOP and training

A week of training is wasted if it lives only in people's heads. Write the SOP on day 5 while it is fresh. Keep it short: purpose, who does what, the steps with screenshots, the review checklist, and what to do when something goes wrong. For basics on writing procedures, see how to manage SOPs for a small business.

Where do you keep it? For a team of 10 to 30, a shared document folder can be enough, and a free option works well at first. See the best SOP software for small business and free alternatives to Trainual. A dedicated tool becomes worth it when you need to assign lessons, track who finished them and run quizzes. Trainual is a platform for writing a company's processes, policies and training and assigning them to staff with completion tracking. Per its pricing page, it does not list plan prices (it says price varies by team size and features and sends you to a demo), lists Core, Pro, Premium and Enterprise plans, mentions a one-time $1,000 implementation fee in its FAQ, and says it is best suited to companies with 25 to 1,000 employees. That last point means a 10 person agency may be below its sweet spot, so only choose it if you need assigned training with tracking. Check Trainual's own page for current terms. For setup, see how to set up Trainual for a 15 person team.

Common ways the week goes wrong

  • Training on a live client site. Fix: practice accounts only.
  • Everyone learns a different way. Fix: one owner, one shared notes file, one checklist.
  • Trusting the output. Fix: planted errors on day 3 and a named reviewer on every launch.
  • Credit surprises. Fix: ask for the plan and expected use first, and log week cost.
  • Skipping handover. Fix: the day 5 client test.
  • No SOP. Fix: write it on day 5 and review it again after the first real client job.

Who should skip this plan

  • Teams that will not be using the platform for more than one or two sites. Train one person instead.
  • Agencies with no review habit today. Build the review first, and train on the tool second.
  • Teams that need a specific feature the platform lacks, such as an online store. Ploy, for example, has no storefront or checkout of its own per its comparison page.

How I'd approach this

I would run the week with two people first, not the whole team, and use them as trainers for the rest. Monday: the guided run and the practice site. Tuesday: rebuild. Wednesday: planted-error review. Thursday: launch mechanics. Friday: handover test and the SOP, with the review checklist stored where everyone can find it. The following week, each trained person builds one real, low-risk client page with a reviewer, and you update the SOP with what you learn.

Decision rule: if the team passes the day 3 review and the day 5 handover test, roll it out to client work. If not, repeat the weak day before taking a client on. Blur Studio can build the custom version, such as an internal tool that checks AI-drafted pages against your checklist before a person reviews them. See what a custom build includes.

For a closer look, see where an AI marketing platform fits in a larger SOP.

Questions people ask

How long does it take to train a team on an AI website builder?

One focused week gets a small team to a working level if each day has one outcome: tool basics, a real rebuild, review standards, launch mechanics and a handover test. Real fluency comes after the first few client jobs.

Should we train on a client's live site?

No. Use your own site or a friendly low-risk business that has agreed in writing, on a practice account. Mistakes in training should never reach a client.

What review standards should we use for AI-built sites?

Check facts against the client's source, remove invented content, test links and forms, check speed on a phone, run basic accessibility checks, confirm search basics and tracking, and test a rollback. See the quality control checklist for AI-built websites.

Do we need a paid plan for training?

It depends on the tool. Ploy's Free plan has no collaborator invites and publishes to a ploy.build address, so a team sharing one workspace needs a paid plan. Check Ploy's pricing page for current plans and limits.

Do we need Trainual to write the SOP?

No. A shared document is enough for a small team. Trainual is worth considering when you need assigned lessons with completion tracking. Its pricing page lists no prices, mentions a $1,000 one-time implementation fee and says it suits 25 to 1,000 employees. See free alternatives to Trainual.

How do we stop AI mistakes reaching clients?

Make a named person responsible for facts on every page, plant errors in training so reviewers know what to look for, and keep a person in the publishing step. Google's guidance says AI output should be reviewed before publishing.

What should the handover test cover?

One teammate plays the client. They should make an edit, publish it and roll it back with no help. If they cannot, fix the training material before you hand over a real site.

How do we control credit costs while training?

Use one practice workspace, ask the tool for its plan and expected credit use before big tasks, and record the week's usage. Ploy publishes no price per action, so measure your own use. See Ploy pricing explained.

More in this topic: Websites: agency delivery, quality control and margins (10 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…