Before you start
What you will produce: a Wix page in draft, aligned with an audience, a marketing goal, a validated promise and a clear CTA. Prerequisites: a BAM project with your offer; a Wix account and a draft page; your existing elements (current site, sales deck, client notes, product screenshots, authorized testimonials).
BAM prepares the marketing context Wix cannot guess. Wix speeds up layout, sections and components. Your team controls the decisions and the publication.
No automatic integration: your validation is the bridge between the two.
Step 1 · Choose a page, a goal and an audience in BAM
Do not start in Wix. Start with the marketing decision: in your BAM project, phrase the page goal as a result, never as a format. Correct goal examples: get qualified demo requests from B2B agencies; make the value of a brand memory clear to SMBs without a structured marketing team; convert visitors interested in AI marketing into qualified leads; explain how the product fits a stack including Wix, CRM and emailing tools.
I want to create a Wix page [page type: home / offer / demo / case study] for [audience chosen from my personas] in order to [marketing goal]. Primary CTA: [expected visitor action]. Existing elements: [notes, current page, screenshots, authorized testimonials]. Prepare the page brief: problem, promise, key messages, authorized proofs, objections, structure, CTAs and claims not to make. Do not write the Wix prompt yet.
You must get from BAM: an explicitly chosen audience, a defensible promise, a list of actually available proofs, the priority objections, a page structure, and the limits to preserve.
Human checkpoint: the brief from JOHANNES completes this sentence for you: "This page must convince [persona] to do [action], because [your offer] solves [problem]." Move to Wix only if it rings true.
For example: for Claire, the site must show that an agency can keep one memory per client and prepare consistent FR/EN campaigns. For Nassim, a light launch machine, with no complex stack to master.
Step 2 · Have the BAM brief turned into a Wix prompt
Once the brief is validated, ask JOHANNES to convert it into an instruction Wix can use:
From the validated page brief for [page name], prepare a prompt ready to paste into Wix. Include the goal, the audience, the problem, the promise, the mandatory messages, the available proofs, the CTAs, the sections, the design and mobile rules, and the phrasings to avoid. Do not invent numbers, client results or features.
Here is the outline JOHANNES's prompt should follow, filled with your validated elements:
Create a [page type] page in order to [goal]. Audience: [your audience]. Problem: [the problem this audience faces]. Promise: [your validated promise]. Mandatory messages: [3 or 4 validated messages]. Primary CTA: [CTA]. Expected structure: [the sections listed in your brief]. Visual direction: [desired style], one accent color, mobile version first. Do not invent results, numbers, testimonials or integrations.
Step 3 · Ask Wix for one section at a time
Do not ask for a perfect page from the first prompt. Wix can generate a site or help create and adjust sections from natural language instructions: treat the result as a first proposal to check, never as a page ready to publish.
The simple rule: one intention validated in BAM = one Wix prompt = one section to review.
Create only the Hero section of this page. Title: [your validated title]. Supporting text: [one sentence from the brief]. Primary CTA: [CTA]. Secondary CTA: [optional]. Plan a zone for [your real screenshot or photo], and on mobile: text, CTA, then visual. Do not add claims, numbers or features that were not provided.
The expected result: a readable title tied to the problem, a visible primary button, a real place for your visual, no invented content, a clear mobile reading.
Step 4 · Build the workflow block, then check it in BAM
The workflow block is a proof element, not a decoration: it shows your three-step method and gives the visitor a reason to believe you.
Create a section titled [the title validated in your brief]. Present three steps of equal importance: [step 1], [step 2], [step 3], one sentence each, taken from the brief. Section goal: [what the visitor must understand]. Visual direction: three sober numbered blocks, a single column on mobile.
Here are the text and a screenshot of the Wix section I just created. Check the consistency with the [persona] audience, the fidelity to the validated messages, implicit or excessive promises, and mobile readability. Answer with: what is consistent, what must be fixed before publication, and the Wix correction prompt, without rewriting the whole page.
Step 5 · Have Wix fix things without reopening the strategy debate
This separation is essential: BAM decides the message, Wix improves the visual execution.
Keep the texts, CTAs and claims of this section. Change only [what must change: visual order / spacing / mobile readability / contrast]. Do not change the meaning of the messages, and do not add any promise, number, feature or testimonial.
This avoids a classic drift: Wix improves the rendering, then involuntarily changes or enriches the commercial promise.
Step 6 · Check the page before publishing
The final check is an explicit action in BAM, not a box ticked in passing:
I am about to publish this Wix page. Audience: [persona]. Goal: [goal]. Primary CTA: [CTA]. Page copy: [paste the texts]. Evaluate the clarity of the promise in the first screen, the answer to the audience's problem, the solidity of the proofs, the accuracy of the limits, and the consistency of the CTA with the goal. List the sentences to fix, then write the final publication checklist: mobile, links, form, metadata, accessibility.
Next step: the following pages
Once the first page is validated, do not build the whole site at once. The recommended commercial core, in this order:
- 1. Home: explain and orient. CTA "Discover BAM".
- 2. How BAM works: prove the workflow. CTA "See the brief → campaign workflow".
- 3. Agencies use case: the replicable multi-client method, for Claire (consulting director) and Mehdi (agency founder). CTA "Prepare a client campaign".
- 4. SMB use case: clarity without a heavy stack, for Nassim (SaaS SMB founder). CTA "Structure my marketing".
- 5. Demo or contact: turn interest into qualified requests. CTA "Start from an existing brief".
- 6. Resources: educate and capture contacts. CTA "Download a checklist".
- 7. Blog: build authority through concrete cases. CTA "Read a use case".
Claire must see that an agency can keep a memory per client and prepare coherent FR/EN campaigns. Nassim must see a light launch machine, without a complex stack to master.
Appendix · Who does what, step by step
BAM: clarify the goal, the audience, the promise, the proofs and the CTA. Wix AI: does not replace this strategic work. You: validate the direction.
BAM: produce the texts, the page structure, the messages and the proof rules. Wix AI: suggest section or layout variants. You: validate the phrasings.
BAM: describe the components, priorities and conversion constraints. Wix AI: generate or adapt sections, design, components and site elements. You: control the visual coherence.
BAM: provide a checklist of message, proof, CTA and journey. Wix AI: help fix some elements in the editor. You: validate mobile, forms, SEO and publication.
BAM: keep the validated context and content in your project. Wix: host and administer the site. You: decide to go live.
The team validates what gets published.
Two AIs at different moments, one rule of control.
Appendix · What not to say
- "BAM and Wix are automatically connected" (this integration does not exist).
- "The two AIs build the site on their own."
- "The site is published automatically by BAM."
- "Wix AI replaces the positioning work."
- "A coordinated workflow between strategy, content and implementation."
- "A BAM brief ready to be interpreted in Wix."
- "Faster construction, without automating brand decisions."
Appendix · Components, objections and extra prompts
Every page keeps the same progression (the problem, the answer, the proof, then the action) and draws from a deliberately limited library: a coherent site is recognizable by the repetition of its components.
Problem or result-oriented title, visible CTA, real screenshot or diagram, one micro-proof, mobile version built immediately.
One diagnostic sentence, three operational effects, an explicit transition to the answer.
The central grammar of the journey, on every key page.
Contrasting background, little text, one clear idea: "good content starts with a clear decision, not with a prompt".
An initial situation, a blocker, what BAM structures, the expected asset, a CTA.
"BAM structures and governs. Wix, your CRM, your emailing tool or your CMS keep activating." This block must stay exact: no unavailable connector.
One closing block, one goal, one primary button. No repeated "Learn more".
Create a use case page for [client segment] in order to [goal]. Title: [a problem-oriented title]. Problem: [what this segment faces daily]. Answer: [what your offer changes, in one sentence]. Expected sections: hero with a [CTA] CTA, concrete problems, [your three-step method], reassurance, FAQ, final CTA. Do not invent delays, results or integrations. Sober design, mobile version first.
Create a reassurance section titled [your trust line]. Three points: [who validates what], [what is kept and reused], [what your current tools keep doing]. Sober, factual style, no promise of total autonomy. Secondary CTA: [optional].
Appendix · Design, mobile and checklists
The design sells operational clarity, not a generic AI aesthetic: very readable hierarchy, plenty of space, annotated screenshots as proofs, one accent color, few card variants. No robots, glowing brains or fictional interfaces.
Mobile check after each section: title readable in three to five lines, CTA visible without horizontal scrolling, cards in a single column, screenshots understandable, sufficient contrast, useful decoration, problem → answer → action order kept, form usable without zooming.
Before publishing, tick:
- The marketing goal is phrased as a result and the primary audience is named.
- Every number, result, client or testimonial is validated, and the promises are demonstrable.
- The product limits are explicit and human validation is visible.
- No unavailable integration is announced.
- One primary CTA dominates and matches the visitor's real stage.
- The page is checked on mobile (links, form, metadata, language) as a Wix draft.
- The page is published only after human validation.
Appendix · Small glossary
- Brief: what you already know, even incomplete (notes, documents, constraints). BAM starts from there.
- Audience: the precise persona to convince, chosen among those of your project.
- Promise: the result the page can defend with proofs.
- Proof: a verifiable, authorized element (screenshot, validated testimonial, real example).
- CTA: the single action the page asks of the visitor.
- Campaign: the coherent set of assets serving one goal and one audience.