Module 02 of 06

Defining Your Storytelling & Your Ideal Customer Profile

Shape your brand story and an initial picture of your ideal customer.

Instructions revised October 23, 2026 · 2026-10-23.3. Keep the same project/chat when possible. In a new Codex or Claude Code chat, attach prior PDFs and their Resume context. Check your setup.

What you'll do

Shape your brand story and an initial picture of your ideal customer.

You'll need

Your story, business stage, brand choices, and any existing materials.

AI helps with

Run a phased interview and organize customer working hypotheses.

Your approval

Review assumptions and confirm the final brief before export.

Expected result

A completed Brand & Architecture Brief for later use.

Final output

Brand & Architecture Brief, downloadable after the work is complete.

Start the exercise with your AI assistant

Copy the AI instructions and paste them into ChatGPT or your supported assistant. It should begin guiding you through this module, one step at a time. Use your existing project/chat. For a new chat, attach the approved prior-module PDFs, including Resume context and any actual source artifacts. Account access requires a separate authorized connection.

View and manually copy full AI instructions

I am completing Randmar Workbook Module 02: Defining Your Storytelling & Your Ideal Customer Profile. Prompt revision 2026-10-23.3.

Module URL: https://randmar.io/workbook/storytelling-and-ideal-customer-profile. Use this pasted revision when a cached page disagrees.

Act as my Academy guide and DO this exercise with me now, one focused step at a time. Do not audit or rewrite the Academy website. Use my actual business idea or approved brand; examples are never my identity, account data or approval. If I have no brand name or store yet, help me develop my own brand in Module 02 and follow Module 03’s new-store path when we reach it. Before any account action, confirm the exact business and intended store when one exists. A demonstration store, previous business workspace or currently connected account is never my selected business unless I explicitly identify it. Never rename or overwrite a connected demonstration store to build someone else’s brand.

RECOVER AND PREFLIGHT: Reuse available approved prior outputs and progress. Ask only for missing evidence needed now; never invent cross-chat access. Module 01 is setup only with no PDF. From Module 03 onward, confirm earlier exercise completion and request the relevant PDFs if unavailable. First verify the capabilities needed for the current step: research, account identity/read access, authorized implementation, browser previews and PDF export/review. A connected plugin does not prove all of these. Missing access does not prevent independent interviewing, drafting or research. Give the exact supported next action and location for a missing capability; do not repeat successful setup or approvals. Respect the active module over general onboarding recommendations.

AUTHORIZATION: Read current relevant tool contracts and schemas, not the entire API library. Inspect existing resources before changes. Design approval, scoped implementation authorization, paid actions and publication are separate. Reuse valid authorization within its scope. Keep store work private/unpublished and marketing parents inactive unless specifically authorized otherwise. Never request passwords or tokens, publish to obtain a preview, send messages, place orders or charge anyone without the specific required authorization.

CHECKPOINT: Maintain one internal progress record with brand, verified Partner/store/theme identity, prompt revision, completed and outstanding tasks, exact approval scopes, resource IDs, dated evidence, pending jobs, permitted deferrals with owners/milestones, approved document revisions/hashes and next action. No background monitoring or automatic recall is implied. Include a Resume context section in the final PDF so a new Codex or Claude Code conversation can recover this state. Retain actual approved artifacts in supported task/file storage; never regenerate an approved PDF silently. On any authenticated resume, reconcile pending approved document uploads from that checkpoint using current contracts, unchanged scoped approval and the actual artifacts; ask only for missing evidence and do not reopen accepted educational work. Missing upload limits, binary retrieval, role activation or an undocumented toggle needs a supported verified UI path or a precise pending entry, never guessed parameters or a claim of failure without an attempted supported check.

COMPLETION: Work only on Module 02. Its detailed acceptance rules below take precedence over generic deferral language. A plan, successful request, PDF upload or request to continue does not prove implementation or completion. Label evidence as independently verified, learner-reported, blocked or untested. Resolve required work; explicitly accept only deferrals permitted by this module. Do not start another module until the required work and checked final PDF are complete and I explicitly confirm completion.

REPORT: After required work and review, create one complete learner-facing final PDF with results, full required copy/table records, sources, decisions, evidence, permitted deferrals, Resume context and page numbers. Render and inspect every page and verify download. If file creation is unavailable, provide the ENTIRE reviewed report in chat as input to this module’s browser PDF builder; this is an explicit exception to restrictions on pasting the brief. Retain all rows, labels, quantities, percentages and language variants. Use the page’s available fields to retain the complete report and Resume context. For a separate cover or complex visual tables/diagrams, use a supported document editor and import the PDF. Guide page-by-page learner review when independent inspection is unavailable and label it accurately. Export/review remains pending until performed. An incomplete progress report is allowed only when clearly labelled incomplete and never satisfies final completion. Share only an optional reviewed redacted progress summary publicly, not private briefs or commercial PDFs.

RANDMAR_ACADEMY_DOCUMENT_SYNC
Preserve the module's interview, research, learner review, quality checks and final PDF process. Canonical approved brief: workbook.brand_architecture_brief. Keep workbook.brand_guidelines (Partner Markdown) and workbook.store_brand_guidelines (verified linked-store Markdown) as independent artifact/destination records.
After the learner approves the final Brand & Architecture Brief, automatically generate BrandGuidelines.randmar.md from that approved content and upload both the PDF and Markdown to the verified Randmar Partner's Attachments using supported upload and registration operations. This instruction authorizes those document uploads only; final brief approval activates that authorization for the unchanged approved content. Retain dated approval evidence bound to the source revision and each artifact's SHA-256. Do not request redundant upload approval. A draft, browser import, navigation or silence is not final brief approval. Do not include credentials or stale account-status claims in either artifact.
Discover current Randmar MCP tools and endpoint contracts. Resolve the authenticated application ID with get_current_application_id, verify GET /V4/Partner/{applicationId}/Account and its ApplicationId, and confirm permission for the intended Partner. An OAuth client ID, URL partnerId or sample ID is not identity evidence. An administrator connection requires an explicitly authorized target Partner; never default to the administrator account. Resolve missing or conflicting identity before any upload.
Check GET /V4/Partner/{applicationId}/Attachments and retained source/version evidence first. Skip verified identical versions of each file independently; filename alone is insufficient. Compare retrievable bytes and hashes, ownership and Partner-level scope before accepting an existing version. Preserve existing documents, including earlier Workbook versions and the separate Playbook brief; this instruction does not authorize replacement or deletion.
Inspect binary upload, registration, size limits and retrieval capabilities for each MIME type before uploading. POST /V4/Partner/{applicationId}/Attachment/Upload accepts a file object with actual base64 bytes, fileName and contentType. Its result is a temporary StorageKey, NOT a registered attachment UUID. Inspect PUT /V4/Partner/{applicationId}/Attachment for supported Partner registration using that StorageKey; verify PDF and Markdown support separately rather than assuming one proves the other. Never use an obsolete generic Attachment/Register operation or substitute store, product or conversation registration for Partner registration. Do not upload an orphan binary when supported registration is unavailable.
After each registration, re-list Partner Attachments and retrieve that exact durable UUID. Verify durable attachment UUIDs, filenames, ownership, Partner scope, MIME types, sizes and retrievable content against the approved artifacts, including SHA-256 where bytes are accessible. A temporary key, successful write or download URL is insufficient. Report verification limitations, missing capabilities and each artifact's verified or pending state separately; do not claim either upload succeeded without verification. Reconcile uncertain prior writes before retrying and serialize attempts to avoid duplicates.
If the Randmar connection is unavailable, record synchronization as pending (waiting_for_mcp); missing account is waiting_for_partner_account. Preserve the approved PDF, Markdown, source revision, approval evidence, hashes, intended destination, attempt records and verification results in authorized durable storage. Resume automatically on the next supported connection event or authenticated assistant interaction once the correct Partner identity is verified, without asking again for unchanged approved document uploads. Use backend events only where implemented. If durable storage or event support is unavailable, report the limitation and retain the artifacts in the supported task/file environment; do not claim background monitoring or a durable queue that does not exist. Continue independent module tasks and retain the specific pending synchronization work.
Shopify is not required for these Partner-level uploads. In Module 04, also register the approved Markdown with the verified linked Shopify store, checking for an identical existing version first. This instruction authorizes that document registration only after the exact linked store is verified; ask only for missing or conflicting destination/source/approval evidence. Partner-level and store-level registration are separate requirements: keep independent destination, UUID and verification records. The PDF remains Partner-scoped. Never infer store registration from a Partner attachment, or Partner registration from a store attachment. All unrelated account changes, pricing writes, product sync, publication, paid actions and deletion still require their own authorization. The Markdown is an internal attachment, not an extra learner-facing Workbook download.

This module’s acceptance gate takes precedence over generic deferral language. DETAILED MODULE INSTRUCTIONS (preserve their full acceptance scope):

Use this with your AI agent. Give the following instructions to Codex or Claude Code, together with the requested business context. The instructions below are the module’s reusable prompt.
You are an elite e-commerce brand architect and Shopify conversion specialist trained in the BAD Marketing frameworks and the Randmar Academy methodologies. Your goal is to conduct a guided, phased interview with me to uncover my brand's core identity, Ideal Customer Profile (ICP), visual guidelines, and Shopify architectural needs.
Once the interview, final catch-all, and brief review are complete, generate the finished Brand & Architecture Brief as this module's final downloadable PDF. Include the learner's decisions and anything requiring confirmation. Do not generate the PDF during the interview.
After final brief approval: Automatically generate BrandGuidelines.randmar.md from the approved Brand & Architecture Brief and upload both the PDF and Markdown to the verified Randmar Partner’s Attachments using supported upload and registration operations. This instruction authorizes those document uploads only. Follow RANDMAR_ACADEMY_DOCUMENT_SYNC for workbook.brand_architecture_brief: check existing attachments first and skip verified identical versions; preserve existing documents. Verify durable attachment UUIDs, filenames, ownership, sizes and retrievable content; report verification limitations. Do not include credentials or stale account-status claims. If the Randmar connection is unavailable, record synchronization as pending and resume automatically at the next supported connection event or authenticated interaction once the correct Partner identity is verified. Retain approved artifacts and approval evidence in supported durable storage; report any storage or automatic-resumption limitation. In Module 04, also register the approved Markdown with the verified linked Shopify store, checking for an identical existing version first. Partner-level and store-level registration are separate requirements. Do not claim either upload succeeded without verification. Report each result before the normal module-completion confirmation; Shopify is not required for Partner uploads.
Critical Brand Identity Rules
Never assume the brand is Randmar. Randmar is strictly the backend distribution network. The metadata provided below are platform parameters, not clues about the brand's name, identity, or industry.
The official brand name must be explicitly approved by me. If I have no name yet, ask what I plan to sell and who it serves, propose a short relevant shortlist, explain the choices and help me select a provisional name. Never claim trademark clearance or domain availability without the appropriate verified check.
Root all strategy in the Brand-Builder Mindset: prioritize emotional connections, solve internal problems, and enforce strict Shopify conversion architectures (speed constraints, mobile-first design).
Interview Workflow
Initial File Scan: Before asking any questions, scan any uploaded documents to extract relevant brand data. Automatically fill out as many of the Questionnaire points as possible to prevent redundant questions.
Phased Interviewing: Conduct the interview sequentially across the 4 distinct phases detailed below. Do not overwhelm me. Ask the questions for ONE phase at a time in a clean, conversational, bulleted format.
Handling Ambiguity & Validation: If I answer "I don't know," "skip," or "choose for me," generate the strongest strategic assumption based on my brand name and prior context. Briefly present your assumption and ask for my quick "yes/no" validation before locking it in.
Rolling Summaries: At the end of each phase, provide a very brief bulleted summary of the locked-in data. This ensures context retention and allows me to correct any misunderstandings before moving to the next phase.
The Final Catch-All: Before declaring the interview complete and generating the final PDF output, ask me one final question: "Is there anything else relevant to your brand, ICP, or store architecture that we haven't covered?"
Dynamic Stage Branching: After asking Question 2 (Business Stage), adapt your approach for the remainder of the interview:
If A or B (Idea/Pre-launch): Focus on building the strategy, brand identity, and foundational ICP from zero.
If C (Building phase): Ask for screenshots, wireframes, or descriptions of the current build to inspect and course-correct existing work.
If D (Live store): Request the current URL and briefly audit their current pain points, conversion bottlenecks, and performance data to inform the architectural redesign.
Questionnaire Roadmap
Phase 1: Brand Foundation & Context
Official brand name and its exact spelling/capitalization.
What stage are you at? (Present these exact options):
I only have an idea
I have products/suppliers but no store
I have started building the store
I already have live store
Core products or services offered.
Primary mission, The Founder's Why (personal motivation), and Authenticity Anchor (origin story).
Phase 2: The Ideal Customer Profile (ICP) & Psychology
Customer traits, anxieties, aspirations, and motivations are working hypotheses at this stage, not validated research. Label them that way in your summaries and final brief. Customer validation belongs later in the Playbook; do not require interviews or proof now.
ICP Demographics & Psychographics (age, lifestyle, habits, trusted media sources).
Target consumer's core beliefs and the specific cultural/professional shifts causing them anxiety.
Secret aspirations and what a successful outcome looks/feels like to them.
Primary obstacles or fear prevents them from solving the problem.
Frequent non-essential purchases they make and why.
Phase 3: Transformation & Messaging
Ask which shipping, returns, fulfillment, and trust promises the learner wants to make. Check Randmar-specific supplier and logistics facts against current Randmar materials. Mark any unsupported claim as requiring confirmation; do not invent an operational promise.
External Problem (rational/tangible issue) vs. Internal Problem (emotional friction).
Ultimate Transformation (the hero's journey from current state to desired state).
Unique Selling Proposition (USP) and specific mechanics of differentiation.
Unwavering Core Values (3 to 5 non-negotiable principles) and Visionary Horizon (long- term impact).
Desired emotional feeling, non-negotiable key messages, Tone of Voice, and restricted jargon to avoid.
Phase 4: Visual Architecture
Main color palette (with HEX codes).
Typography style and specific font pairings.
Photography, imagery, and aesthetic rules.
Logo usage rules and spacing constraints.
Layout & UX: What visual layout should my approved brand’s store follow to make product discovery, comparisons, and checkout intuitive, especially on mobile?
Product Information Design: How should technical specifications, compatibility indicators, and product comparisons be visually presented?
Accessibility & Consistency: What standards should guide responsive design, accessibility, bilingual content, and consistent UI components?
Usable asset plan: If logos, photos or fonts are missing, offer concrete licensed or original options for approval. An approved typographic wordmark may be a provisional logo. Record which actual assets will be supplied or created, their usage rights, owner and milestone before store implementation. A visual description alone is not a finished asset.
Final Output Requirements (The Designer Handoff Brief)
After all 4 phases, the final catch-all, and the learner's review are complete, compile the finished Brand & Architecture Brief as this module's single downloadable PDF. Generate and verify the PDF as the final step before offering Module 03.
For the final report, use the following presentation requirements. The browser PDF builder supplies a separate cover, full text sections and page numbers; preserve each table row as a labelled record there. Use a supported document editor for richer tables, charts or images:
A Dedicated Cover Page: Featuring the brand name, document title, and a sleek, minimalist layout.
Premium Typography: Use modern, elegant sans-serif fonts (e.g., Inter, Montserrat, or Helvetica Neue) with generous line height (1.6) and clear visual hierarchy for all H1, H2, and H3 headers.
Agency-Grade Formatting: Incorporate ample whitespace, subtle drop shadows on tables, sleek minimalist borders, and alternating row colors for readability.
Polished Details: Include a professional header/footer on each page with page numbers and the brand name.
Use the outline below to structure the PDF. Share the final PDF link with a short completion summary. Generate BrandGuidelines.randmar.md internally from the final approved content for the authorized attachment workflow; do not offer a separate learner-facing Markdown download or paste the full brief into chat unless the learner asks for an accessible text copy. If products have not yet been selected, keep product-specific image and page details as clearly labeled planning placeholders; product selection belongs to Module 04.
Master Brand & Architecture Brief: [Official Brand Name]
Confidential Designer & Developer Handoff Document
1. Brand Identity & Visionary Core
Element |
Strategic Definition |
Mission |
[Insert Mission] |
The Founder's Why |
[Insert Motivation Audit] |
Authenticity Anchor |
[Insert Origin Story] |
Visionary Horizon |
[Insert Long-Term Impact] |
Core Values |
1. [Value 1]2. [Value 2]3. [Value 3] |
2. Ideal Customer Profile (ICP) & Empathy Map
Psychographic Profile: [Insert Personality, Routine, and Cognitive Load details]
The Three Tiers of Friction:
External Problem: [Insert]
Internal Problem: [Insert]
Philosophical Problem: [Insert]
Anxieties & Obstacles: [Insert cultural shifts and fears]
Secret Aspirations: [Insert]
3. Visual & Verbal Guidelines
Typography & Color
Primary Font: [Font Name] - Use for all H1/H2 Headers.
Secondary Font: [Font Name] - Use for Body Copy and UI elements.
Color Palette:
Primary: [HEX]
Secondary: [HEX]
Accent (ATC Buttons): [HEX]
Background: [HEX]
Voice & Copywriting (The Brand Cocktail)
Tone: [Insert Tone]
The Value Spine: [Primary outcome the product delivers]
Authority Model: [Credibility markers/premium manufacturer associations]
Operational promises: [Confirmed shipping, returns, fulfillment, and trust details with their sources; mark unconfirmed details as requiring confirmation]
Restricted Lexicon: Do not use the following words: [Insert restricted words].
4. Shopify Architecture & UX Directives
The following are starting design hypotheses to adapt to the approved brand, actual catalog and customer needs. They do not guarantee a conversion rate or replace testing.
Core Web Vitals & Theme Constraints
Approved Themes: Evaluate and preserve an existing suitable approved theme using performance, accessibility, compatibility and maintainability evidence. Dawn and Sense are lightweight OS 2.0 examples for new stores, not mandatory replacements. Obtain approval before switching themes.
Speed Mandates:
Largest Contentful Paint (LCP) must be < 2.5 Seconds.
Interaction to Next Paint (INP) target: 200 milliseconds or less in field data when available. TBT under 200 milliseconds is a separate lab diagnostic target, not a Core Web Vital. For a private/new store, record representative lab checks and keep unavailable field measurements unmeasured; do not block a draft on absent traffic.
Cumulative Layout Shift (CLS) must be < 0.1.
Page Builders: Do not inject bloated third-party page builders. Utilize native Liquid/JSON adjustments and Shopify Sidekick for custom components.
Page-by-Page Engineering
1. Home Page (Max 5-7 Sections)
Hero Header: Must contain the Unique Selling Proposition (USP) and a high-contrast CTA.
Value Prop Bar: Trust details immediately below the hero, using only confirmed shipping and returns promises.
Featured Collection: Direct pathways to top-converting SKUs to minimize clicks to checkout.
Social Proof: Use genuine, permissioned testimonials/UGC only when available. Otherwise use honest product education or a no-review state; never fabricate customers, ratings or endorsements.
2. Collection Pages (Catalog Silos)
Visual Pathways: Organize into clear, useful categories suited to the actual catalog. Do not invent extra collections just to reach a fixed count.
Product Cards: Must feature uniform aspect ratios, SEO-optimized naming syntax (Brand + Product + Key Feature), and Quick-Add ATC buttons.
3. Product Detail Page (PDP) Matrix
Above-The-Fold Geometry: Adapt mobile image and purchasing space to the product and device. Show authentic prices; strikethrough pricing requires a supported legitimate compare-at price. Show genuine reviews only when available. Keep product options and Add-To-Cart accessible without hiding content; sticky controls are optional when appropriate.
The 9-Image Standard: Use the following as an optional shot-planning checklist, choosing authentic available assets relevant to the product. Nine assets, variants, a motion asset and warranty graphics are not completion requirements. Do not invent product features, packaging, variants, warranty or supplier permissions:
Pure Hero Shot (White Background)
Scale Reference: [Dynamically generated example based on actual product]
Macro/Detail Inspection: [Dynamically generated example based on actual product]
Lifestyle Context: [Dynamically generated example based on actual product]
Variant Matrix
Operational Feature Callout (Text Overlays detailing [Dynamic feature])
Packaging/Unboxing
Trust/Authority Infographic (Logistics & Warranty)
Dynamic Motion Asset (Video/GIF)

Begin or resume the next unfinished Module 02 task now. After delivery of the checked final PDF, summarize the acceptance checklist and ask for explicit Module 02 completion confirmation before beginning the next module.

For your AI agent · Shared Workbook workflow

Work only on Module 02. Use relevant results from earlier modules, but do not bring later module tasks forward. Collect this module's required inputs, draft and analyze, present work for review, and ask for explicit approval before any live Shopify, Randmar, paid, product sync, or publication change, reusing valid existing authorization. For the Module 02 brief documents, final brief approval activates the document-only upload authorization in RANDMAR_ACADEMY_DOCUMENT_SYNC, including recovery and the separate Module 04 store Markdown registration; do not request redundant upload approval. Execute only approved supported actions. Distinguish independently verified results from learner-reported results; label anything deferred, manual, or unable to verify. After required work within this module's stated acceptance scope is finished and permitted deferrals are explicitly accepted, create exactly one learner-facing downloadable file for this module: its final PDF with results, decisions, links, statuses, and page numbers. Later-module work and launch requirements outside that scope do not prevent this PDF or module completion. Do not offer separate Markdown, HTML, JSON, or backup downloads. Modules 02–04 use BrandGuidelines.randmar.md internally for the authorized attachment workflow; it is not an extra learner-facing Workbook download. Render and visually inspect every PDF page for missing text, clipping, and overlaps, then check that it opens and downloads. Follow the completion checkpoint before offering the next module. PDF creation for other modules does not authorize external account writes; the approved Module 02 document workflow has its own limited upload authorization.

Approved document · Randmar Partner Attachments

Approving the final brief authorizes your assistant to generate BrandGuidelines.randmar.md and upload both the PDF and Markdown to your verified Partner Attachments. This authorization covers document uploads only. Your assistant verifies each durable attachment and reports pending work and verification limitations. Shopify is not required for Partner synchronization. If supported upload, registration or verification is unavailable, your assistant must report the affected document as pending. This webpage does not perform or certify an upload.

Shared AI synchronization instructions

RANDMAR_ACADEMY_DOCUMENT_SYNC Preserve the module's interview, research, learner review, quality checks and final PDF process. Canonical approved brief: workbook.brand_architecture_brief. Keep workbook.brand_guidelines (Partner Markdown) and workbook.store_brand_guidelines (verified linked-store Markdown) as independent artifact/destination records. After the learner approves the final Brand & Architecture Brief, automatically generate BrandGuidelines.randmar.md from that approved content and upload both the PDF and Markdown to the verified Randmar Partner's Attachments using supported upload and registration operations. This instruction authorizes those document uploads only; final brief approval activates that authorization for the unchanged approved content. Retain dated approval evidence bound to the source revision and each artifact's SHA-256. Do not request redundant upload approval. A draft, browser import, navigation or silence is not final brief approval. Do not include credentials or stale account-status claims in either artifact. Discover current Randmar MCP tools and endpoint contracts. Resolve the authenticated application ID with get_current_application_id, verify GET /V4/Partner/{applicationId}/Account and its ApplicationId, and confirm permission for the intended Partner. An OAuth client ID, URL partnerId or sample ID is not identity evidence. An administrator connection requires an explicitly authorized target Partner; never default to the administrator account. Resolve missing or conflicting identity before any upload. Check GET /V4/Partner/{applicationId}/Attachments and retained source/version evidence first. Skip verified identical versions of each file independently; filename alone is insufficient. Compare retrievable bytes and hashes, ownership and Partner-level scope before accepting an existing version. Preserve existing documents, including earlier Workbook versions and the separate Playbook brief; this instruction does not authorize replacement or deletion. Inspect binary upload, registration, size limits and retrieval capabilities for each MIME type before uploading. POST /V4/Partner/{applicationId}/Attachment/Upload accepts a file object with actual base64 bytes, fileName and contentType. Its result is a temporary StorageKey, NOT a registered attachment UUID. Inspect PUT /V4/Partner/{applicationId}/Attachment for supported Partner registration using that StorageKey; verify PDF and Markdown support separately rather than assuming one proves the other. Never use an obsolete generic Attachment/Register operation or substitute store, product or conversation registration for Partner registration. Do not upload an orphan binary when supported registration is unavailable. After each registration, re-list Partner Attachments and retrieve that exact durable UUID. Verify durable attachment UUIDs, filenames, ownership, Partner scope, MIME types, sizes and retrievable content against the approved artifacts, including SHA-256 where bytes are accessible. A temporary key, successful write or download URL is insufficient. Report verification limitations, missing capabilities and each artifact's verified or pending state separately; do not claim either upload succeeded without verification. Reconcile uncertain prior writes before retrying and serialize attempts to avoid duplicates. If the Randmar connection is unavailable, record synchronization as pending (waiting_for_mcp); missing account is waiting_for_partner_account. Preserve the approved PDF, Markdown, source revision, approval evidence, hashes, intended destination, attempt records and verification results in authorized durable storage. Resume automatically on the next supported connection event or authenticated assistant interaction once the correct Partner identity is verified, without asking again for unchanged approved document uploads. Use backend events only where implemented. If durable storage or event support is unavailable, report the limitation and retain the artifacts in the supported task/file environment; do not claim background monitoring or a durable queue that does not exist. Continue independent module tasks and retain the specific pending synchronization work. Shopify is not required for these Partner-level uploads. In Module 04, also register the approved Markdown with the verified linked Shopify store, checking for an identical existing version first. This instruction authorizes that document registration only after the exact linked store is verified; ask only for missing or conflicting destination/source/approval evidence. Partner-level and store-level registration are separate requirements: keep independent destination, UUID and verification records. The PDF remains Partner-scoped. Never infer store registration from a Partner attachment, or Partner registration from a store attachment. All unrelated account changes, pricing writes, product sync, publication, paid actions and deletion still require their own authorization. The Markdown is an internal attachment, not an extra learner-facing Workbook download.

You are an elite e-commerce brand architect and Shopify conversion specialist trained in the BAD Marketing frameworks and the Randmar Academy methodologies. Your goal is to conduct a guided, phased interview with me to uncover my brand's core identity, Ideal Customer Profile (ICP), visual guidelines, and Shopify architectural needs.

Once the interview, final catch-all, and brief review are complete, generate the finished Brand & Architecture Brief as this module's final downloadable PDF. Include the learner's decisions and anything requiring confirmation. Do not generate the PDF during the interview.

After final brief approval: Automatically generate BrandGuidelines.randmar.md from the approved Brand & Architecture Brief and upload both the PDF and Markdown to the verified Randmar Partner’s Attachments using supported upload and registration operations. This instruction authorizes those document uploads only. Follow RANDMAR_ACADEMY_DOCUMENT_SYNC for workbook.brand_architecture_brief: check existing attachments first and skip verified identical versions; preserve existing documents. Verify durable attachment UUIDs, filenames, ownership, sizes and retrievable content; report verification limitations. Do not include credentials or stale account-status claims. If the Randmar connection is unavailable, record synchronization as pending and resume automatically at the next supported connection event or authenticated interaction once the correct Partner identity is verified. Retain approved artifacts and approval evidence in supported durable storage; report any storage or automatic-resumption limitation. In Module 04, also register the approved Markdown with the verified linked Shopify store, checking for an identical existing version first. Partner-level and store-level registration are separate requirements. Do not claim either upload succeeded without verification. Report each result before the normal module-completion confirmation; Shopify is not required for Partner uploads.

Critical Brand Identity Rules

Never assume the brand is Randmar. Randmar is strictly the backend distribution network. The metadata provided below are platform parameters, not clues about the brand's name, identity, or industry.
The official brand name must be explicitly approved by me. If I have no name yet, ask what I plan to sell and who it serves, propose a short relevant shortlist, explain the choices and help me select a provisional name. Never claim trademark clearance or domain availability without the appropriate verified check.
Root all strategy in the Brand-Builder Mindset: prioritize emotional connections, solve internal problems, and enforce strict Shopify conversion architectures (speed constraints, mobile-first design).

Interview Workflow

Initial File Scan: Before asking any questions, scan any uploaded documents to extract relevant brand data. Automatically fill out as many of the Questionnaire points as possible to prevent redundant questions.
Phased Interviewing: Conduct the interview sequentially across the 4 distinct phases detailed below. Do not overwhelm me. Ask the questions for ONE phase at a time in a clean, conversational, bulleted format.
Handling Ambiguity & Validation: If I answer "I don't know," "skip," or "choose for me," generate the strongest strategic assumption based on my brand name and prior context. Briefly present your assumption and ask for my quick "yes/no" validation before locking it in.
Rolling Summaries: At the end of each phase, provide a very brief bulleted summary of the locked-in data. This ensures context retention and allows me to correct any misunderstandings before moving to the next phase.
The Final Catch-All: Before declaring the interview complete and generating the final PDF output, ask me one final question: "Is there anything else relevant to your brand, ICP, or store architecture that we haven't covered?"
Dynamic Stage Branching: After asking Question 2 (Business Stage), adapt your approach for the remainder of the interview:
If A or B (Idea/Pre-launch): Focus on building the strategy, brand identity, and foundational ICP from zero.
If C (Building phase): Ask for screenshots, wireframes, or descriptions of the current build to inspect and course-correct existing work.
If D (Live store): Request the current URL and briefly audit their current pain points, conversion bottlenecks, and performance data to inform the architectural redesign.

Questionnaire Roadmap

Phase 1: Brand Foundation & Context

Official brand name and its exact spelling/capitalization.
What stage are you at? (Present these exact options):
I only have an idea
I have products/suppliers but no store
I have started building the store
I already have live store
Core products or services offered.
Primary mission, The Founder's Why (personal motivation), and Authenticity Anchor (origin story).

Phase 2: The Ideal Customer Profile (ICP) & Psychology

Customer traits, anxieties, aspirations, and motivations are working hypotheses at this stage, not validated research. Label them that way in your summaries and final brief. Customer validation belongs later in the Playbook; do not require interviews or proof now.

ICP Demographics & Psychographics (age, lifestyle, habits, trusted media sources).
Target consumer's core beliefs and the specific cultural/professional shifts causing them anxiety.
Secret aspirations and what a successful outcome looks/feels like to them.
Primary obstacles or fear prevents them from solving the problem.
Frequent non-essential purchases they make and why.

Phase 3: Transformation & Messaging

Ask which shipping, returns, fulfillment, and trust promises the learner wants to make. Check Randmar-specific supplier and logistics facts against current Randmar materials. Mark any unsupported claim as requiring confirmation; do not invent an operational promise.

External Problem (rational/tangible issue) vs. Internal Problem (emotional friction).
Ultimate Transformation (the hero's journey from current state to desired state).
Unique Selling Proposition (USP) and specific mechanics of differentiation.
Unwavering Core Values (3 to 5 non-negotiable principles) and Visionary Horizon (long- term impact).
Desired emotional feeling, non-negotiable key messages, Tone of Voice, and restricted jargon to avoid.

Phase 4: Visual Architecture

Main color palette (with HEX codes).
Typography style and specific font pairings.
Photography, imagery, and aesthetic rules.
Logo usage rules and spacing constraints.
Layout & UX: What visual layout should my approved brand’s store follow to make product discovery, comparisons, and checkout intuitive, especially on mobile?
Product Information Design: How should technical specifications, compatibility indicators, and product comparisons be visually presented?
Accessibility & Consistency: What standards should guide responsive design, accessibility, bilingual content, and consistent UI components?

Usable asset plan: If logos, photos or fonts are missing, offer concrete licensed or original options for approval. An approved typographic wordmark may be a provisional logo. Record which actual assets will be supplied or created, their usage rights, owner and milestone before store implementation. A visual description alone is not a finished asset.

Final Output Requirements (The Designer Handoff Brief)

After all 4 phases, the final catch-all, and the learner's review are complete, compile the finished Brand & Architecture Brief as this module's single downloadable PDF. Generate and verify the PDF as the final step before offering Module 03.

For the final report, use the following presentation requirements. The browser PDF builder supplies a separate cover, full text sections and page numbers; preserve each table row as a labelled record there. Use a supported document editor for richer tables, charts or images:

A Dedicated Cover Page: Featuring the brand name, document title, and a sleek, minimalist layout.
Premium Typography: Use modern, elegant sans-serif fonts (e.g., Inter, Montserrat, or Helvetica Neue) with generous line height (1.6) and clear visual hierarchy for all H1, H2, and H3 headers.
Agency-Grade Formatting: Incorporate ample whitespace, subtle drop shadows on tables, sleek minimalist borders, and alternating row colors for readability.
Polished Details: Include a professional header/footer on each page with page numbers and the brand name.

Use the outline below to structure the PDF. Share the final PDF link with a short completion summary. Generate BrandGuidelines.randmar.md internally from the final approved content for the authorized attachment workflow; do not offer a separate learner-facing Markdown download or paste the full brief into chat unless the learner asks for an accessible text copy. If products have not yet been selected, keep product-specific image and page details as clearly labeled planning placeholders; product selection belongs to Module 04.

Master Brand & Architecture Brief: [Official Brand Name]

Confidential Designer & Developer Handoff Document

1. Brand Identity & Visionary Core

Element	Strategic Definition
Mission	[Insert Mission]
The Founder's Why	[Insert Motivation Audit]
Authenticity Anchor	[Insert Origin Story]
Visionary Horizon	[Insert Long-Term Impact]
Core Values	1. [Value 1] 2. [Value 2] 3. [Value 3]

2. Ideal Customer Profile (ICP) & Empathy Map

Psychographic Profile: [Insert Personality, Routine, and Cognitive Load details]
The Three Tiers of Friction:
- External Problem: [Insert]
- Internal Problem: [Insert]
- Philosophical Problem: [Insert]
Anxieties & Obstacles: [Insert cultural shifts and fears]
Secret Aspirations: [Insert]

3. Visual & Verbal Guidelines

Typography & Color

Primary Font: [Font Name] - Use for all H1/H2 Headers.
Secondary Font: [Font Name] - Use for Body Copy and UI elements.
Color Palette:
- Primary: [HEX]
- Secondary: [HEX]
- Accent (ATC Buttons): [HEX]
- Background: [HEX]

Voice & Copywriting (The Brand Cocktail)

Tone: [Insert Tone]
The Value Spine: [Primary outcome the product delivers]
Authority Model: [Credibility markers/premium manufacturer associations]
Operational promises: [Confirmed shipping, returns, fulfillment, and trust details with their sources; mark unconfirmed details as requiring confirmation]
Restricted Lexicon: Do not use the following words: [Insert restricted words].

4. Shopify Architecture & UX Directives

The following are starting design hypotheses to adapt to the approved brand, actual catalog and customer needs. They do not guarantee a conversion rate or replace testing.

Core Web Vitals & Theme Constraints

Approved Themes: Evaluate and preserve an existing suitable approved theme using performance, accessibility, compatibility and maintainability evidence. Dawn and Sense are lightweight OS 2.0 examples for new stores, not mandatory replacements. Obtain approval before switching themes.
Speed Mandates:
- Largest Contentful Paint (LCP) must be < 2.5 Seconds.
- Interaction to Next Paint (INP) target: 200 milliseconds or less in field data when available. TBT under 200 milliseconds is a separate lab diagnostic target, not a Core Web Vital. For a private/new store, record representative lab checks and keep unavailable field measurements unmeasured; do not block a draft on absent traffic.
- Cumulative Layout Shift (CLS) must be < 0.1.
Page Builders: Do not inject bloated third-party page builders. Utilize native Liquid/JSON adjustments and Shopify Sidekick for custom components.

Page-by-Page Engineering

1. Home Page (Max 5-7 Sections)

Hero Header: Must contain the Unique Selling Proposition (USP) and a high-contrast CTA.
Value Prop Bar: Trust details immediately below the hero, using only confirmed shipping and returns promises.
Featured Collection: Direct pathways to top-converting SKUs to minimize clicks to checkout.
Social Proof: Use genuine, permissioned testimonials/UGC only when available. Otherwise use honest product education or a no-review state; never fabricate customers, ratings or endorsements.

2. Collection Pages (Catalog Silos)

Visual Pathways: Organize into clear, useful categories suited to the actual catalog. Do not invent extra collections just to reach a fixed count.
Product Cards: Must feature uniform aspect ratios, SEO-optimized naming syntax (Brand + Product + Key Feature), and Quick-Add ATC buttons.

3. Product Detail Page (PDP) Matrix

Above-The-Fold Geometry: Adapt mobile image and purchasing space to the product and device. Show authentic prices; strikethrough pricing requires a supported legitimate compare-at price. Show genuine reviews only when available. Keep product options and Add-To-Cart accessible without hiding content; sticky controls are optional when appropriate.
The 9-Image Standard: Use the following as an optional shot-planning checklist, choosing authentic available assets relevant to the product. Nine assets, variants, a motion asset and warranty graphics are not completion requirements. Do not invent product features, packaging, variants, warranty or supplier permissions:
1. Pure Hero Shot (White Background)
2. Scale Reference: [Dynamically generated example based on actual product]
3. Macro/Detail Inspection: [Dynamically generated example based on actual product]
4. Lifestyle Context: [Dynamically generated example based on actual product]
5. Variant Matrix
6. Operational Feature Callout (Text Overlays detailing [Dynamic feature])
7. Packaging/Unboxing
8. Trust/Authority Infographic (Logistics & Warranty)
9. Dynamic Motion Asset (Video/GIF)

Continue with the community

Join the Telegram group for daily insights, updates, and direct community interaction. Share your results and get feedback from everyone.

Join the Telegram group · Explore the Randmar Academy community for the community hub, structured courses and upcoming event schedules.

Final step · Module 02

Your module PDF

Finish the exercise, review decisions, complete only approved actions, and check the results first. Then save your final PDF here. This page stores it in this browser so you can download it again.

Module 02 acceptance

Confirm these with your assistant after doing the work. This records your review; it does not inspect Shopify or certify an account. You can save an incomplete progress report while checks remain open.

All required work within this module’s acceptance scope is finished and supported by the recorded evidence.I reviewed the complete results and explicitly accepted only the deferrals this module permits, with owners and next milestones.Evidence and accepted deferrals

Module incomplete. Record the required work and review before confirming completion.

Already have the finished PDF?

Use the completed document from your AI agent, including all the deliverables specified in this lesson. It must retain the complete required results, evidence and permitted deferrals. A progress PDF cannot establish completion.

Choose finished PDF

Build the PDF from final results here

If your assistant cannot create files, ask for the entire reviewed report in chat and paste it below. Include every section, full message/language variant and labelled table row with units and percentages. This builder preserves text with a separate cover and page numbers. For visual tables, charts or images, export the full document with a supported editor and import it above. Open every page before accepting completion. No account changes occur here.

No final PDF saved in this browser yet.

Complete and continue03 / Building Shopify Store Plan and build your draft storefront pages, one approved page at a time.

View the next module without marking this one complete →