🚀 Early Access: FREE full access to All Workflows and AI Prompt Systems! No credit card required.

Market Awareness Stage Analysis

Map audience awareness stages and create stage-specific messaging, content, CTAs, and conversion recommendations.

Marketing - Customer Research - Market Awareness Stage Analysis

Who it's for

Marketing teams, Content strategists, Product marketers, Growth teams, Founders

Get Ready

Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.

How to use this prompt

1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

Workflow Prompt

				
					You are a market awareness strategist. Analyse an audience and create messaging and conversion guidance by awareness stage.

### Required Input
- Product or Offer: [Describe what is being sold. Example: “Cybersecurity training platform for remote teams.”]
- Target Audience: [Describe the audience. Example: “Operations and HR leaders at distributed companies.”]
- Audience Evidence: [Paste customer research, sales notes, survey answers, reviews, analytics observations, or market assumptions. Example: “Many prospects know security training is required but delay implementation.”]
- Primary Goal: [Example: “Improve campaign messaging, landing page structure, or nurture content.”]
- Current Messaging: [Paste existing positioning or page copy if available. Example: “Make compliance training simple for every employee.”]
- Conversion Path: [Describe the desired next step. Example: “Download guide, book demo, start free trial, request quote.”]

### Input Validation
Review the inputs before producing the analysis. If audience evidence is missing, the target audience is too broad, or the goal is unclear, ask specific clarification questions. Pause until the required context is provided.

### Instructions
Classify the audience across awareness stages: unaware, problem aware, solution aware, product aware, and most aware. Explain which stages are most likely present and what signals indicate each stage.

For each stage, identify what the audience understands, what they do not yet believe, what questions they are asking, and what message would move them forward. Match persuasion to the stage. Early-stage audiences need problem recognition and education; later-stage audiences need proof, differentiation, urgency, and risk reduction.

Evaluate current messaging against likely awareness stages. Identify where it may be too advanced, too basic, too product-focused, too vague, or missing the customer’s actual concern.

Translate the analysis into campaign and conversion recommendations. Provide stage-specific messaging angles, content formats, proof assets, CTAs, landing page sections, and nurture ideas. Keep recommendations practical for a small team.

### Output
Create a complete market awareness stage analysis with these sections:

1. Awareness Summary
- Likely awareness stage distribution
- Primary stage to prioritise
- Biggest messaging mismatch
- Recommended strategic focus

2. Stage-by-Stage Analysis
For each relevant stage include:
- What the audience currently believes
- What they need to understand next
- Main objection or barrier
- Best message angle
- Proof needed
- Suitable CTA
- Content formats to use

3. Current Messaging Assessment
Evaluate:
- Fit with audience awareness
- Missing education
- Missing proof
- Overly advanced assumptions
- Weak or unclear claims

4. Messaging Recommendations
Provide:
- Headline angles by stage
- Landing page section recommendations
- Email nurture themes
- Ad or social angles
- Sales enablement notes

5. Conversion Path Recommendations
For each stage recommend:
- Best next step
- Offer type
- CTA wording direction
- Expected conversion behaviour

6. Action Plan
Create a prioritised table with:
- Action
- Awareness stage served
- Why it matters
- Effort level
- Expected impact
- First implementation step

Ensure the output matches message, content, and CTA to audience readiness.

Optional advanced instructions

				
					Include three example headline angles for the highest-priority awareness stage.

Example output

1. Awareness Summary

Likely Awareness Stage Distribution:
- Unaware: 10% (Operating manual systems, blissfully ignorant of development resource leak).
- Problem-Aware: 45% (Frustrated by engineering backlogs and alert fatigue, but assume it’s an unfixable cost of doing business).
- Solution-Aware: 30% (Actively seeking visual engines or external APIs, but overwhelmed by technical claims).
- Product-Aware: 12% (Evaluating our sandbox infrastructure against legacy black-box competitors).
- Most Aware: 3% (In active negotiations, verifying final SOC2 data privacy and processing latency metrics).
Primary Stage to Prioritise: Problem-Aware. This group represents the largest market share with immediate conversion velocity. They are in acute pain but haven’t actively quantified the structural engineering tax they pay every sprint to maintain internal transaction-checking logic.
Biggest Messaging Mismatch: Speaking to Problem-Aware audiences with Most-Aware product features. Forcing prospects to evaluate complex, nuanced dashboard interfaces or specific data pipeline models before validating their core frustration (the engineering bottleneck) creates massive cognitive friction.
Recommended Strategic Focus: Position the platform as a structural liberation utility. Shift marketing assets to explicitly bridge the gap between operational responsibility and infrastructure autonomy, moving users smoothly from “I am stuck in a developer queue” to “I can run this myself inside a sandboxed ecosystem.”

2. Stage-by-Stage Analysis

Stage 1: Problem-Aware (Frustrated but Resigned)

What the Audience Currently Believes: They believe that waiting 3–4 weeks for internal developers to adjust a transaction verification rule is an unalterable reality of managing scaling risk infrastructure.
What They Need to Understand Next: They must recognize that transaction monitoring infrastructure can be split into a secure, visual standalone framework that lets non-technical compliance leads build rules independently without breaking core application code.
Main Objection or Barrier: Complete disbelief that any tool can bypass developer code deployments while satisfying security parameters.
Best Message Angle: “Stop trading engineering sprint hours for basic compliance workflow changes.”
Proof Needed: Simple, highly visual step-by-step workflow canvas diagrams that illustrate the separation of the data transmission engine from the operational logic tier.
Suitable CTA: [See How Visual Workflow Automation Saves Engineering Hours]
Content Formats to Use: Metric-driven baseline calculations, short technical explainer loops, and interactive breakdown essays.

Stage 2: Solution-Aware (Evaluating the Landscape)

What the Audience Currently Believes: They understand that visual rule builders and API tracking integrations exist, but they assume onboarding a new platform will require an intensive, multi-month engineering commitment.
What They Need to Understand Next: Connecting our system requires no deep database redesigns or custom programming hooks; it operates seamlessly via standard REST webhooks that deploy in under 15 minutes.
Main Objection or Barrier: Fear that integrating an external logic loop will add unacceptable millisecond delays to their core checkout speeds.
Best Message Angle: “Built for Operations. Approved by Engineering. Ultra-low-latency deployment.”
Proof Needed: Live, verifiable network latency graphs confirming average transaction processing speeds of less than 15ms.
Suitable CTA: [Explore the Developer Setup Guide]
Content Formats to Use: Un-gated developer documentation, technical architecture maps, and API payload blueprints.

Stage 3: Product-Aware (Comparing the Options)

What the Audience Currently Believes: They know our product name and are actively comparing our feature lists against legacy enterprise tools or automated, black-box AI platforms.
What They Need to Understand Next: AI automation without clear explanation logic is a severe compliance risk during a regulatory audit. They need deterministic, explicit step-by-step audit histories to protect their professional standing.
Main Objection or Barrier: Data privacy anxieties and concerns about transferring live, unencrypted client transaction payloads to our cloud server.
Best Message Angle: “Deterministic logic trails over mysterious black-box AI algorithms.”
Proof Needed: Formal SOC2 Type II certifications, GDPR validation packets, and downloadable unedited compliance history logs.
Suitable CTA: [Initialize Free Developer Sandbox Workspace]
Content Formats to Use: Direct competitor comparison grids, product sandbox previews, and downloadable data security packets.

3. Current Messaging Assessment

Fit with Audience Awareness: Current generic statements like “Make automated transaction tracking simple” land poorly because they speak directly to Most-Aware buyers while alienating Problem-Aware leads who are searching for resource relief, not generic “simplicity.”
Missing Education: The copy completely skips defining the root operational problem: **the engineering sprint tax**. It assumes the buyer is already looking for software features rather than investigating how to reclaim developer autonomy.
Missing Proof: There is a clear absence of raw technical metrics (latency benchmarks, setup tracking metrics, webhook deployment counts) needed to satisfy the engineering gatekeepers who inevitably review the purchase.
Overly Advanced Assumptions: The messaging frequently highlights advanced data-routing capabilities before proving that an analyst can safely update basic conditional logic lines without deploying code.
Weak or Unclear Claims: Promising “AI efficiency” actually triggers skepticism among compliance directors who require explainable tracking histories rather than mysterious, unaccountable scoring paths.

4. Messaging Recommendations

Headline Angles by Stage

Problem-Aware: “Your compliance team owns the transaction KPIs. Why do you have to wait on engineering sprints just to adjust your rules?”
Solution-Aware: “The visual transaction builder that deploys via pre-built webhooks in under 15 minutes—zero database migrations required.”
Product-Aware: “Why high-volume fintech operations choose our explainable visual rules over mysterious, black-box AI models.”

Landing Page Section Recommendations

The Pain Validation Block (Upper Fold): Frame a contrasting layout pitting the traditional “Jira engineering backlog delay loop” against our instant, visual validation workspace.
The Developer Safety Zone (Middle Fold): Dedicate an entire architectural section explicitly for the CTO, showcasing copy-paste code hooks, sub-15ms processing benchmarks, and direct data isolation guarantees.
The Audit Traceability Screen (Lower Fold): Provide a large, unedited screenshot of an automated execution log showing exactly how clear, deterministic paths are rendered for regulatory review.

Email Nurture Themes

Email 1 (Problem-Aware): “Calculating the Hidden Monthly Development Cost of Maintaining In-House Transaction Rule Frameworks.” Focus entirely on resource economics.
Email 2 (Solution-Aware): “Defeating the Checkout Latency Monster: How to Chain External API Triggers in Under 15ms.” Focus on technical safety and system speed.
Email 3 (Product-Aware): “The External Compliance Audit Playbook: How to Export Explainable Rule Paths Instantly.” Focus on audit protection and professional safety.

5. Conversion Path Recommendations

Target Awareness Stage	Best Next Step	Offer Type	CTA Wording Direction	Expected Conversion Behaviour
Problem-Aware	Review Resource Math	Un-gated Internal TCO Calculator	`[Calculate Your Engineering Sprint Tax →]`	High volume click-throughs; low-intent download tracking profile build.
Solution-Aware	Examine Architecture	Technical Integration Blueprints Pack	`[Download API & Latency Benchmarks]`	Corporate email registrations; profile classification as active technical lead evaluator.
Product-Aware	Hands-On Testing	Risk-Free Open Developer Sandbox	`[Initialize Free Sandbox Workspace]`	Direct developer environment spin-ups using synthetic test payloads.

6. Action Plan

Action	Awareness Stage Served	Why It Matters	Effort Level	Expected Impact	First Implementation Step
Rewrite Hero Block copy to focus on engineering sprint relief.	Problem-Aware	Directly addresses the primary top-of-funnel friction point causing long deal sales cycles.	🟢 Low	🔥 High lift in trial generation velocity	Draft three copy options using the phrase “Stop waiting on developer queues.”
Publish unedited API network latency benchmarks upfront.	Solution-Aware	Neutralizes the developer gatekeeper objection before it stalls an active sales opportunity.	🟡 Medium	⚡ Faster progression past tech reviews	Extract network execution time records from our testing suite logs.
Embed security verification badges directly inside form layers.	Product-Aware	Lowers data privacy anxieties right at the point of trial registration.	🟢 Low	📉 Lower registration drop-offs	Place SOC2 Type II and GDPR validation asset links inside the sign-up panel layout.
Build a interactive workflow simulator page.	Solution / Product	Proves our rule builder’s drag-and-drop capability without forcing account integration setup.	🔴 High	📈 Boost in product-fit confidence levels	Design a front-end mock layout of the rule canvas using synthetic test objects.

When to reuse this workflow

Customer Sentiment Analysis

Analyse customer sentiment themes and turn emotional feedback into business recommendations.

Marketing, Customer Research

Survey Analysis Framework

Turn customer survey responses into clear themes, insights, opportunities, and next actions.

Marketing, Customer Research

Lost Customer Analysis

Analyse why customers left and convert churn feedback into retention and win-back actions.

Unlock the full library.

Get access to all workflows, across every sector, with structured systems built for better results.