Where an AI marketing platform fits in a larger SOP: a website launch and lead handling template

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

Short answer: An AI marketing platform (software that drafts and publishes web pages, forms and follow-up messages for you) belongs inside your existing marketing SOP, a standard operating procedure, which is a written list of steps with one owner per step. Treat the platform as one step with a clear input, a clear output and a human review gate after it. Everything else, such as the brief, the approval, the lead handling and the review date, stays with named people. A fill-in website launch template follows.

Ranjit Bhinge

You are putting an AI tool into your marketing work and need the written process around it, so it does not become the one step nobody checks.

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.

Do not write a separate process for the AI platform. Put it into the process you already use to launch a page or a site, as the step where drafts are produced, and surround it with steps that people own. This page gives you a website launch SOP you can copy, with the AI step and its review gates already placed. It does not choose a platform for you. It is for a business or agency of roughly 3 to 30 people, and it works with any tool that builds pages or writes copy.

Two nearby pages cover related ground. Where an AI creative tool fits in a larger SOP handles images and video. This one handles web pages, forms and lead follow-up. For the basics of writing a procedure, read how to write an SOP.

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

What every SOP needs

Sources differ on the exact sections, and no single formal standard applies to a small business. Templates from software vendors, universities and health bodies agree on a core set, which I use here:

  • Purpose: one sentence on why the SOP exists.
  • Scope: where it applies and where it does not.
  • Roles: job titles, not first names, so the SOP survives staff changes.
  • Numbered steps: each with an owner, the tool used and the expected output.
  • Decision points: where the answer is yes or no and what happens next.
  • Document control: version number, date, approver and next review date.

The one that most small SOPs miss is the last. An SOP with no owner and no review date goes out of date, and then people stop trusting all your SOPs. See how to keep SOPs up to date.

The website launch SOP: steps and owners

Copy this table into your document and replace the brackets. Roles are examples: in a very small team one person holds several.

#StepOwnerInputOutput
1Write the brief: audience, offer, one action you want, proof you have[Marketing lead]Customer questions, past jobsOne-page brief
2Check the claims list: which facts, prices and results may appear[Owner or manager]BriefApproved facts list
3AI step: produce drafts with the AI marketing platform[Marketing lead]Brief and approved facts list onlyOne or two draft pages, with the prompt saved
4Human review gate: facts, tone, claims, links, accessibility basics[Reviewer, not the person who ran step 3]Draft pagesMarked-up pages or sign-off
5Set up the form and lead path (see lead handling below)[Operations]Final form fieldsWorking form that writes to the CRM
6Test on a phone: speed, form, links, tracking[Operations]Staging or preview pageTest log with pass or fail
7Final approval and publish[Owner or approver]Test logLive page
8Submit the sitemap, request indexing for key pages, record the launch date[Marketing lead]Live URLSearch Console submission noted
9Check at day 7 and day 30: leads, replies, errors[Marketing lead]Form log, CRMShort report and changes
10Review the SOP itself[SOP owner]Notes from steps 1 to 9New version and next review date

A filled-in example of step 3

Here is how the AI step might read once it is written down. The names and tool are placeholders, so replace them with your own:

  • Step: 3, produce draft pages.
  • Owner: the marketing lead. Backup: the operations manager.
  • Tool and workspace: [platform name], the shared company workspace, two named users.
  • Input: the one-page brief and the approved facts list, both attached to the task.
  • Output: up to two draft pages in preview mode only, with the prompt pasted into the task.
  • Stop rule: if the draft contains a figure that is not on the facts list, it goes back to step 3 once. A second failure goes to the owner.
  • Done when: the reviewer in step 4 has the drafts and the prompt.

Where the AI platform sits, and how to write that step

Step 3 is the only step where the platform acts. Write it in the same way as every other step, with a strict input and a strict output.

  • Input: the brief and the approved facts list. Say that nothing else goes in. If someone pastes in a competitor's page or a client's private document, you will not be able to check where the wording came from.
  • Action: name the platform, the workspace and who may use it, and save the prompt or instruction you gave it.
  • Output: a draft, never a published page. Where the platform can publish by itself, switch that off for this SOP or require a person to press publish.
  • Record: date, tool name, version or model if shown, and the prompt, saved with the page.

Anything the platform does after launch, such as sending follow-up messages, should also be written as a step with an owner and a stop rule (who can switch it off, and how). Many platforms let you connect a form to a CRM or email; whatever it does automatically needs a line in the SOP.

Review gates: what the human must check

AI drafts can contain wrong facts. Google's own guidance on generative AI content says outputs may contain inaccuracies, which it calls hallucinations, and that producing many pages without adding value can break its scaled content abuse policy, whatever method made them. So write the gates as a checklist the reviewer signs.

GateThe reviewer confirmsFail if
FactsEvery price, hour, address, licence and number matches the approved facts listAny figure appears that is not on the list
Claims and proofResults, awards and testimonials are real and permitted. See claims and testimonials on websitesA claim cannot be backed up
VoicePlain, matches your other pages, no invented storiesIt reads like anyone's website
DisclosureIf you tell customers AI is used, the wording is right. See AI disclosure on websitesThe wording says one thing and your practice is another
ValueEach page answers a real customer question and is not a copy of a sibling pageYou are publishing many near-identical pages
Links and formsEvery link opens, every button works, the form submitsAnything fails on a phone test

For agency work, the client signs off at step 7 or earlier. See client approval for AI-written pages and the content approval process.

Step 8 in detail: telling Google about the new page

Google's documentation says crawling can take from a few days to a few weeks, and a request does not guarantee that a page appears in search. For a handful of pages, the URL Inspection tool in Search Console lets you request indexing, and it has daily limits per property. For many pages, or a new site, a sitemap is the better route, and Google suggests keeping the last-modified dates accurate. Google also says small sites of about 500 pages or fewer may not need a sitemap if every page can be reached by links from the home page. Write the one you use into the SOP, with the date you did it, so day 30 has something to check against.

Lead handling: the second half of the SOP

A launch SOP that stops at "publish" is half a process. Add a short second SOP, or a section, for what happens when someone fills in the form:

  1. The form writes to the CRM (customer relationship management tool, where you keep contacts). See building the lead capture flow.
  2. The assigned person is alerted within the time you set.
  3. They reply, and the reply is logged.
  4. If there is no reply in your target time, the backup person is alerted.
  5. Once a week someone compares form submissions with CRM records.

Fallbacks: when the platform is down or the draft is poor

  • If the platform is down, who writes the page by hand, and where is the last good copy kept?
  • If a draft fails the review gate twice, the owner decides whether to rewrite it manually. Do not let a third AI attempt run on without a human decision.
  • If you must roll back a live page, name the person who can do it and where the previous version is.

Where to keep it: a document, a wiki or an SOP tool

For a team under about 10, a shared document is fine if you put an owner and a review date on it. A wiki such as Notion (a workspace app for notes and documents) adds search and page history. An SOP tool adds assignments and proof that people read the SOP.

Trainual is an example of that last kind: software for writing a team's procedures, assigning them to people and tracking who has completed them. It suits you when you onboard often, work with freelancers, or must show a client that your team knows the AI rules. Its pricing page publishes no plan prices and says they depend on team size and features, and it points visitors to a demo rather than a self-serve sign-up. It also lists a one-time $1,000 implementation fee, so ask for a quote and compare it with free options first. Its FAQ says access continues to the end of the billing cycle after you cancel, and that an account can be paused for up to three months. Its published limits include version history of 30 days on the Core plan and 90 days on Pro, which matters if you want to see who changed an SOP and when. It lists best fit as teams of about 25 to 1,000 people. For smaller teams see free alternatives to Trainual and Trainual pricing.

What to check at day 7 and day 30

  • Day 7: did the form send every test and real submission to the CRM, did each lead get a named owner, and did the first replies go out within your target?
  • Day 30: how many leads came from the page, how many were answered in time, and which questions did visitors ask that the page does not answer yet?
  • Both: compare form submissions with CRM records, and look for pages Google has not indexed yet.

Write the result in two or three lines under the SOP's version history. After two launches you will have a record of what actually goes wrong, and that is more useful than any template.

Test the SOP before you rely on it

Ask someone who did not write it to run the launch SOP on a small, low-risk page. Pass: they finish it using only the document, every step has an owner who knows they own it, and the review gate catches at least one fault you planted on purpose (for example a wrong price). Fail: they have to ask you what a step means, or nobody caught the planted fault. Fix the document, not the person.

Who should skip this

If you publish one page a quarter and the same person does everything, a half-page checklist is enough. Write the full SOP once a second person touches the work, or a client asks how you control AI use.

How I'd approach this

Start small. This week: copy the ten-step table, fill in names, and put a review date on it. Run it on your next real page, with the review gate done by someone other than the person who ran the AI step. After the launch, change the three things that annoyed people and write the new version number. Keep the saved prompts, because they become your best training material for the next hire. For the one-time setup of a tool to hold it, see setting up Trainual for a 15-person team, or keep it in a shared document until the process settles. If you want the custom version, with AI agents that use your business knowledge, connections to your CRM and calendar, and ongoing care, Blur Studio builds it: see the business page.

Questions people ask

What is a marketing SOP?

A marketing SOP is a written, step-by-step procedure for a repeat marketing task, such as launching a page or handling a lead, with an owner for each step. See how to write an SOP.

Where should an AI tool go in my process?

As one step with a defined input and output, followed by a human review gate. Do not let it publish alone. See the creative tool version of this SOP.

Who should review AI-written pages?

Someone who did not run the AI step and who has the approved facts list. For agency work, the client signs off before publishing. See client approval for AI-written pages.

What should I record about each AI draft?

The date, the tool, the model or version if shown, the prompt, who reviewed it and the sign-off date. Saved prompts also help new staff.

Do I need special software for SOPs?

No. A shared document with an owner and review date works for small teams. See free SOP software and SOP software for small business when you outgrow it.

How often should I review the SOP?

After the first real use, then at least every six months or whenever a tool or a person changes. Put the next review date on the document.

Does Google penalise AI-written pages?

Google's guidance says it judges content by its value, not how it was made, and that mass-producing pages without adding value can break its spam policy on scaled content. Check Google's current guidance on generative AI content.

More in this topic: Websites: custom builds, portals, lead capture and site care (9 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…