The Marketing category in AIUNIFY PROS SUITE contains ten subscriber-facing tools:
The Sidebar routes these tools to /email, /google-ads, /facebook-ads, /landing-page, /sales-pitch, /marketing-plan, /competitor-analysis, /ab-test-copy, /buyer-persona, and /pricing-page-copy.
The current Marketing category contains one specialized workspace:
AI Email Assistant
The other nine use the shared:
Standard AI Generator Workspace
documented in Chapter 12.
The specialized Tool is:
Email Assistant
It provides dedicated fields, Email Types, Preview, and Edit modes rather than one generic Prompt box.
The following use Standard ToolPage:
These Marketing tools primarily generate:
They do not, by themselves, source-verify execution of:
This distinction is important throughout Chapter 34.
Navigate to:
Sidebar → Marketing → Email Assistant
Route:
/email
The Email route explicitly checks the PROS SUITE authentication session.
If authentication is unavailable, the current route redirects toward:
/login.
The page is titled:
AI Email Assistant
with:
“Craft professional emails for various purposes including cold outreach, responses, and follow-ups.”
The left-side Card is:
Email Details
with:
“Fill in the details to generate your professional email.”
The first required field is:
Email Type *
Current Email Types are:
The interface describes Cold Outreach as:
Reach out to new contacts.
Follow Up is:
Follow up on previous conversations.
Response is intended to:
Reply to received emails.
Introduction is:
Introduce yourself or others.
Thank You is intended to:
Express gratitude professionally.
Meeting Request is:
Request meetings or calls.
The next required field is:
Recipient *
with the example:
“e.g., John Smith, CEO of TechCorp”.
The Recipient field is ordinary text.
The interface does not require an address such as:
name@example.com
You can identify the recipient by:
Because Recipient is a free-text Prompt field, there is no current validation for whether it is a deliverable email address.
The third field is:
Subject (Optional).
If Subject is empty, the generation Prompt explicitly tells AI:
“Please suggest an appropriate subject.”
If you already have a Subject, enter it before generating.
It is inserted into the AI Prompt.
The final required field is:
Context/Purpose *.
Current guidance:
“Describe the purpose of your email, what you want to achieve, any relevant background information...”
Use Context/Purpose to explain:
Generation currently requires:
Subject is optional.
Current Error:
Error
with:
“Please fill in all required fields.”
Primary action:
Generate Email.
While the AI response is active:
Generating....
The AI receives:
followed by:
“Please create a professional, engaging, and appropriate email.”
Unlike Standard ToolPage Marketing tools, Email Assistant uses a dedicated Email system instruction telling the AI to create messages that are:
Generation is identified as:
email
to the shared AI streaming system.
Because Email Assistant uses useGeminiStream, the current selected PROS SUITE AI Model is submitted with its request.
The shared stream also forwards non-empty configured provider API Keys.
Therefore, Chapters 10 and 11 apply to Email Assistant's AI-generation path.
Email content appears progressively while generation is active.
The right Card is titled:
Generated Email
with:
“Your AI-generated professional email will appear here.”
Before generation:
Your professional email will appear here.
The default output Tab is:
Preview.
The generated Email is displayed using AIUNIFY's Markdown Renderer.
A second Tab is:
Edit.
After generation completes, the Edit Tab contains an editable Textarea holding the generated Email.
This makes Email Assistant different from most Standard Marketing tools.
While AI generation is still active, the Edit Textarea is:
read-only.
Editing modifies the current browser component's generated Email state.
No Save action is source-verified.
After streaming finishes, Preview uses the current generated Email state.
Therefore, edits made in Edit mode are reflected when you return to Preview.
Unlike Standard ToolPage, the current Email workspace does not expose a dedicated:
Copy
button.
There is no built-in Email Download action.
The presence of the Send icon does not mean the workspace sends Email.
No outbound Email-delivery action exists in this page.
The current Email Assistant does not connect a Gmail inbox.
It does not connect Outlook/Microsoft 365.
No SMTP Server configuration exists in this page.
The workspace has no dedicated:
inputs.
You cannot attach files to the generated Email from this page.
There is no Send Later or scheduled-delivery function.
No dedicated saved Email Signature field exists.
If a signature is needed, request it in Context or add it in Edit mode.
The six Email Types are generation categories, not persistent user Templates.
No source-verified historical Email archive exists in this page.
A new successful generation updates the current generated Email.
Preserve important edited copy before creating another version.
Current fallback:
Error
with the returned message or:
“Failed to generate email. Please try again.”
The current feature catalogue lists:
Email Assistant — 15 Tokens.
Unlike Standard ToolPage, the specialized Email workspace does not display:
15 tokens per use
beside Generate Email.
Treat 15 Tokens as the current catalogue/default reference.
Include:
Include:
Paste or summarize the incoming Email in Context/Purpose and explain how you want to respond.
Include:
Nine Chapter 34 tools use the shared ToolPage component.
That means they share:
The left Card is titled:
Input
with:
“Describe what you want to generate.”
Primary action:
Generate
and while processing:
Generating...
Inside the Prompt box:
Ctrl + Enter
starts generation.
The adjacent Reset icon clears the current Input and local Output state and returns focus to the Prompt field.
If generation is attempted without useful text:
Input required
with:
“Please enter a prompt to continue.”
ToolPage creates a simple system instruction using:
rather than using a specialized form for these nine tools.
Therefore, detailed instructions in your Prompt are especially important.
The right Card is:
Output
with:
“Generated content will appear here.”
Content appears progressively through the shared AI stream.
Select the Copy icon.
Current confirmation:
Copied!
with:
Content copied to clipboard.
Select Download to save the generated result as plain text.
Download format:
.txt
Pattern:
[tool-id]-output.txt.
The Standard Marketing tools do not provide an Email-style Edit Tab.
There is no persistent Save action.
No universal generation-history list is provided.
Standard Marketing tools use the shared selected AI Model.
Configured provider Keys are forwarded when present.
Standard ToolPage calculates its base cost in this order:
aiLimits settingWhen the selected Model is identified as OpenAI, the ToolPage displays:
1.5× the Base Cost, rounded upward.
Navigate to:
Sidebar → Marketing → Google Ads
Route:
/google-ads
Google Ads Copy Generator.
“Create high-converting Google Ads copy that drives clicks.”
“Describe your product/service, target audience, and unique selling points...”
Google Ads for an online course platform.
Ad copy for a local plumbing service.
Search ads for an e-commerce clothing store.
Current catalogue/default:
15 Tokens.
For stronger results, specify:
For example:
“Create 10 headline options and 4 description options for a Google Search campaign...”
It does not connect to a Google Ads account.
The Tool does not create:
There is no source-verified Google Keyword Planner integration.
It does not retrieve current:
There are no:
execution fields.
The Tool does not programmatically validate generated Headlines/Descriptions against current Google Ads field limits.
Verify final copy before campaign entry.
No Google Search-results-style ad Preview is built into the page.
Navigate to:
Sidebar → Marketing → Facebook Ads
Route:
/facebook-ads
Facebook Ads Copy Generator.
“Create scroll-stopping Facebook ad copy that converts.”
“Describe your offer, target audience, and the action you want users to take...”
Facebook ad for a weight loss program.
Ad copy for a SaaS free trial.
Retargeting ad for abandoned cart recovery.
Current default:
15 Tokens.
Specify:
For example:
“Generate Primary Text, Headline, Description, and CTA recommendations.”
The Tool does not connect to Meta Ads Manager.
Generated text is not automatically turned into a Facebook or Instagram Ad campaign.
The page does not configure:
There is no Meta Pixel setup.
No spend/budget controls exist.
This specific Tool creates ad copy only.
Use AI Marketing media tools separately for visual creative.
It does not show:
Navigate to:
Sidebar → Marketing → Landing Page
Route:
/landing-page
Landing Page Copy Generator.
“Create persuasive landing page copy that converts visitors into customers.”
“Describe your product/service, target audience, and key benefits...”
Landing page for a project management SaaS.
Sales page for an online fitness coaching program.
Lead generation page for a marketing agency.
Current default:
25 Tokens.
Include:
For example:
“Create Hero, Problem, Solution, Benefits, Features, Social Proof, FAQ, and Final CTA sections.”
This Tool does not build an actual website.
Its purpose is Landing Page copy, not a source-verified coded Landing Page.
It does not publish to a Domain.
No hosting workflow exists here.
No Lead Form is created.
It does not configure Stripe, PayPal, or checkout components.
The Tool does not measure performance of the generated copy after publication.
Navigate to:
Sidebar → Marketing → Sales Pitch
Route:
/sales-pitch
Sales Pitch Generator.
“Create compelling sales pitches that close deals.”
“Describe your product/service, target customer, and their pain points...”
Sales pitch for enterprise software to CTOs.
Pitch for a consulting service to small businesses.
Elevator pitch for a startup seeking investors.
Current default:
20 Tokens.
Include:
Useful requests include:
The Tool does not place Calls.
It does not automatically create CRM Leads or Opportunities.
It does not send the Pitch by Email.
A sales Pitch is generated as text.
It is not automatically converted to:
Standard ToolPage does not perform source-verified live research into the prospect.
Supply accurate prospect information yourself.
Navigate to:
Sidebar → Marketing → Marketing Plan
Route:
/marketing-plan
Marketing Plan Generator.
“Create comprehensive marketing plans with strategies and tactics.”
“Describe your business, target market, goals, and budget...”
Marketing plan for launching a new mobile app.
Q4 marketing strategy for an e-commerce store.
Content marketing plan for a B2B SaaS company.
Current default:
35 Tokens.
Supply:
A useful Prompt can request:
The Tool can recommend allocation but does not spend or move Marketing funds.
It does not launch the recommended campaigns.
The generated plan does not create Tasks, Owners, Deadlines, or workflow records elsewhere automatically.
Generated KPIs are recommendations.
The Tool does not automatically connect Analytics sources.
This Standard ToolPage does not source-verify external browsing or live research.
Any current market statistics should be independently verified.
Treat it as a planning draft requiring business review rather than audited market intelligence.
Navigate to:
Sidebar → Marketing → Competitor Analysis
Route:
/competitor-analysis
Competitor Analysis Generator.
“Analyze competitors and identify strategic opportunities.”
“List your competitors and describe your industry/market...”
Analyze competitors in the project management software space.
Compare my coffee shop to Starbucks and local cafes.
Competitive analysis for a new fintech app.
Current default:
30 Tokens.
This Tool uses Standard ToolPage.
The standard request sends:
but no browsing or competitor-research Tool is passed.
Therefore:
Competitor Analysis is not source-verified as live web research.
Entering a competitor Name does not source-verify automatic crawling of its Website.
The Tool does not independently fetch a competitor's current pricing.
It does not verify competitor features against their live sites.
No live competitor social monitoring exists in this workspace.
It does not query Meta or Google Ad Libraries.
The Tool does not retrieve competitor:
Provide known facts such as:
and ask AI to structure the strategic analysis.
Do not publish AI-generated competitor claims without independent verification.
Navigate to:
Sidebar → Marketing → A/B Test Copy
Route:
/ab-test-copy
A/B Test Copy Generator.
The Tool generates:
“multiple copy variants for split testing — headlines, CTAs, descriptions, and subject lines with hypothesis framing.”
“Describe what you're testing, target audience, and current copy (if any)...”
“Generate 3 headline variants for a SaaS landing page targeting small business owners.”
“Create 4 CTA button variations for a free trial signup with different urgency levels.”
“Write 3 email subject line variants for a product launch announcement to test open rates.”
The A/B Test route passes:
15 Tokens
as its local fallback.
However, the current shared feature catalogue assigns:
20 Tokens.
Standard ToolPage calculates:
live AI limit → feature catalogue → route fallback.
Therefore, absent a live aiLimits override, the current effective Standard ToolPage base reference is:
20 Tokens
rather than the route's 15-Token fallback.
If the A/B Test page displays a different amount, use the amount shown in the live interface.
It generates textual variants and, when requested, hypothesis framing.
There is no traffic allocation engine.
It does not collect conversions for Variant A vs. Variant B.
There is no source-verified:
The Tool cannot declare a real winning variant unless you provide actual test results and ask it to analyze them as text.
It does not automatically replace copy on your Website.
It does not send different Email variants to subscriber groups.
Include:
For clearer experiments, request variants designed around one primary difference, such as:
rather than changing everything simultaneously.
Navigate to:
Sidebar → Marketing → Buyer Persona
Route:
/buyer-persona
Buyer Persona Creator.
The Tool is designed to build Personas containing:
“Describe your product/service, industry, and what you know about your target customers...”
“Create a buyer persona for a B2B project management tool targeting mid-size tech companies.”
“Build 2 distinct buyer personas for a premium fitness app: casual users vs serious athletes.”
“Generate a detailed persona for the decision-maker who buys enterprise cybersecurity solutions.”
The route and feature catalogue currently agree on:
20 Tokens.
Provide verified information about:
The Tool creates a synthesized Persona from the information provided.
It does not automatically analyze your CRM.
No direct customer-table import exists.
There is no dedicated survey-file upload.
The Tool does not automatically ingest:
If you have not supplied real customer research, AI-generated demographic details should be treated as hypotheses.
A stronger workflow is:
Generate Persona → Compare Against Real Customer Data → Correct Assumptions → Refine Messaging
Navigate to:
Sidebar → Marketing → Pricing Page Copy
Route:
/pricing-page-copy
Pricing Page Copy.
The Tool creates Pricing Page content including:
“Describe your product, pricing tiers, and key features for each plan...”
“Write pricing page copy for a 3-tier SaaS email marketing tool: Free, Pro ($29/mo), Enterprise.”
“Create a feature comparison table copy for a cloud storage product with 4 plans.”
“Generate a pricing FAQ section that addresses common objections for a $99/mo design tool.”
Current default:
20 Tokens.
Provide:
AI should not be allowed to invent:
Use exact current values in your Prompt.
The Tool does not read your live subscription database.
It does not configure Stripe or another payment processor.
It does not create or edit actual PROS SUITE subscription Plans.
The generated copy is text.
It does not update your Website.
Writing that a Plan includes a feature does not technically assign that Tool to the Plan.
No recurring-billing rules are created.
No coupon or promotion engine is exposed.
A useful Prompt can ask for:
| ToolCurrent Base Reference | |
| Email Assistant | 15 Tokens |
| Google Ads | 15 Tokens |
| Facebook Ads | 15 Tokens |
| Landing Page | 25 Tokens |
| Sales Pitch | 20 Tokens |
| Marketing Plan | 35 Tokens |
| Competitor Analysis | 30 Tokens |
| A/B Test Copy | 20 Tokens effective catalogue reference |
| Buyer Persona | 20 Tokens |
| Pricing Page Copy | 20 Tokens |
The feature catalogue supplies these base values, including the 20-Token catalogue value for A/B Test Copy.
For the nine Standard ToolPage tools, a live AI-limit setting can override the catalogue value.
If no such setting exists, the feature catalogue takes precedence over the route fallback.
Standard ToolPage applies the displayed 1.5× OpenAI multiplier to its calculated base amount.
Email Assistant does not use Standard ToolPage and does not display this cost calculation in its own interface.
Its current catalogue reference remains 15 Tokens.
All nine Standard tools use the shared Model and provider-key streaming path.
Email Assistant also uses the same streaming hook.
The shared request includes:
model: selectedModel
or its fallback.
The request also sends the current manual-model state.
Configured provider Keys are added as:
x-provider-key-[provider]
headers.
Changing the AI Model changes generation behavior.
It does not connect:
All nine Standard tools support:
Email Assistant supports:
but no source-verified dedicated Copy or Download buttons.
There is no persistent user project/history workflow in ToolPage.
No persistent history is established there either.
For Standard tools, download important final outputs when desired.
A fresh generation replaces the active visible stream/output.
Preserve approved versions externally.
| ToolSpecialized InputsCopyTXT DownloadEdit OutputExecutes Marketing | |||||
| Email Assistant | Yes | No dedicated button | No | Yes | No |
| Google Ads | No | Yes | Yes | No | No |
| Facebook Ads | No | Yes | Yes | No | No |
| Landing Page | No | Yes | Yes | No | No |
| Sales Pitch | No | Yes | Yes | No | No |
| Marketing Plan | No | Yes | Yes | No | No |
| Competitor Analysis | No | Yes | Yes | No | No |
| A/B Test Copy | No | Yes | Yes | No | No |
| Buyer Persona | No | Yes | Yes | No | No |
| Pricing Page Copy | No | Yes | Yes | No | No |
| ToolGenerates Analysis/CopySource-Verified Live External Research | ||
| Email Assistant | Yes | No |
| Google Ads | Yes | No |
| Facebook Ads | Yes | No |
| Landing Page | Yes | No |
| Sales Pitch | Yes | No |
| Marketing Plan | Yes | No |
| Competitor Analysis | Yes | No |
| A/B Test Copy | Yes | No |
| Buyer Persona | Yes | No |
| Pricing Page Copy | Yes | No |
| FunctionChapter 34 Tool Executes It? | |
| Send Email | No |
| Launch Google Ad | No |
| Launch Facebook Ad | No |
| Publish Landing Page | No |
| Make Sales Call | No |
| Launch Marketing Campaign | No |
| Crawl Competitor Sites | No |
| Run A/B Traffic Experiment | No |
| Import CRM Customer Data | No |
| Change Live Pricing | No |
A generic request such as:
“Write a sales Email”
usually provides less useful direction than:
Recipient + business problem + value proposition + desired CTA + relationship context.
Email Assistant has no dedicated Tone selector.
Write instructions such as:
inside Context/Purpose.
Check:
before using the Email.
Even when AI suggests the Subject, verify that it accurately represents the Email.
Use the Edit Tab to remove:
Use Google/Facebook Ads Generators for copy creation.
Campaign configuration remains a separate operation.
Request several:
for review.
Specify whether the audience is:
Never let AI invent a:
Generated copy is not source-verified as automatically compliant with current advertising policies.
Review before campaign launch.
Examples:
This makes the generated content easier to transfer into a Landing Page builder.
Do not allow AI to fabricate:
Include common buyer objections in your Prompt.
A CTO Pitch should differ from a small-business-owner Pitch.
The strongest Pitch usually centers the buyer's situation before explaining the product.
You can ask for:
as additional generated copy.
Tell the AI whether the CTA should be:
Include:
so the plan is not unrealistically broad.
Request measurable KPIs for each recommended strategy.
Ask the AI to identify assumptions that still require validation.
Any market-size or industry statistics generated from model knowledge should be verified separately.
The more accurate your source information, the more useful the structured comparison.
Ask for sections such as:
Known Facts
Likely Strategic Implications
Assumptions to Verify
Do not present unsupported negative statements about competitors as facts.
Competitive conditions can change.
A generated analysis is not a continuous monitoring system.
Tell the AI whether the test is intended to improve:
Example:
“Changing the CTA from feature-focused to outcome-focused will increase demo clicks because buyers care more about revenue impact than software functionality.”
AI-generated variants are candidates.
Real performance must come from actual testing.
Improve Persona accuracy using:
For B2B products, the person buying the system may not be the daily user.
Ask for separate Personas when needed.
For enterprise sales, consider asking for:
Paste the exact current:
before generating.
Ask the AI to explain why one Plan is appropriate for one customer type and another Plan for another.
Explicitly tell the AI:
“Do not invent any pricing, discounts, guarantees, or included features.”
Pricing FAQs can touch:
Verify those statements against actual company policy.
Confirm:
Subject is optional.
If left blank, the Prompt requests an appropriate suggested Subject.
The Edit Textarea is intentionally read-only while streaming.
Email Assistant is a writing workspace.
No delivery integration is source-verified.
There is no dedicated Copy button in this specialized workspace.
Use the Edit area/browser text selection as needed.
No Download control exists on the current Email page.
Enter non-whitespace text.
Standard ToolPage reports:
Error
with the returned Error or:
“Failed to generate content. Please try again.”
Standard Marketing outputs are rendered, not editable.
Copy them into an editor if revisions are required.
No universal Save/History system exists for these ToolPage generators.
These are generation tools.
Publishing/execution must occur separately.
The current Tool does not source-verify live web research.
Supply updated information in the Prompt and independently verify important facts.
That can be correct.
The route contains a 15-Token fallback, but the current feature catalogue assigns 20 Tokens and ToolPage gives the catalogue precedence unless a live AI-limit override exists.
That is expected.
It generates variants; it does not run live split tests.
Provide exact pricing directly in the Prompt and regenerate.
Never rely on the AI to infer current Plan pricing.
Provide the real feature matrix.
Generating copy does not change Plan entitlements.
The source verifies:
The source does not establish:
The source verifies:
It does not establish:
The source verifies:
It does not establish:
The source verifies:
It does not establish:
The source verifies:
It does not establish:
The source verifies:
It does not establish:
The source verifies:
It does not establish:
The source verifies:
It does not establish:
The source verifies:
It does not establish:
The source verifies:
It does not establish:
A strong operating sequence across Chapter 34 is:
Define the Buyer
→ Use Buyer Persona to Structure the Audience
→ Use Competitor Analysis to Organize Known Competitive Information
→ Create the Marketing Plan
→ Build the Sales Pitch and Positioning
→ Generate Landing Page Copy
→ Generate Google/Facebook Ad Variations
→ Generate Email Outreach
→ Generate A/B Test Variants
→ Create Pricing Page Copy
→ Verify All Facts, Prices, Claims, and Competitor Information
→ Copy/Download Approved Content
→ Move the approved material into the appropriate execution systems
AIUNIFY PROS SUITE's Marketing category currently contains ten content, strategy, and sales-message generation tools. The Sidebar defines Email Assistant, Google Ads, Facebook Ads, Landing Page, Sales Pitch, Marketing Plan, Competitor Analysis, A/B Test Copy, Buyer Persona, and Pricing Page Copy as the current Marketing workflow.
AI Email Assistant is the only specialized workspace in this chapter. It provides six Email Types—Cold Outreach, Follow Up, Response, Introduction, Thank You, and Meeting Request—together with Recipient, optional Subject, and required Context/Purpose fields.
Its generated Email can be viewed in Preview or changed in an Edit Textarea after streaming completes. The page does not currently provide Email delivery, Gmail/Outlook connection, SMTP, CC/BCC, attachments, scheduled sending, dedicated Copy, Download, or persistent Email history.
The other nine Marketing Tools use the Standard ToolPage. They therefore share authenticated access, a single Prompt input, Ctrl+Enter generation, examples, streaming Markdown output, Copy, TXT Download, selected Model behavior, provider API-Key support, current Token display, and no universal Save/History system.
The current base Token references are:
Standard ToolPage can override these with a live aiLimits configuration and applies its displayed OpenAI multiplier when applicable.
The A/B Test Tool contains a noteworthy current-version discrepancy: its route passes a 15-Token fallback, while the feature catalogue assigns 20 Tokens. Since ToolPage prioritizes the feature catalogue ahead of the route fallback, the present default base is 20 Tokens unless a live AI-limit setting overrides it.
The most important operational boundary in Chapter 34 is:
These are Marketing Intelligence and Content Generation Tools—not Marketing Execution Platforms.
Google Ads Copy does not launch Google Ads. Facebook Ads Copy does not launch Meta campaigns. Landing Page Copy does not publish a Website. Sales Pitch does not contact a prospect. Marketing Plan does not execute campaigns. Competitor Analysis does not perform source-verified live web research. A/B Test Copy does not run an experiment. Buyer Persona does not automatically analyze CRM/customer data. Pricing Page Copy does not change subscription billing.
The recommended operating principle is:
Provide Accurate Business Inputs → Generate → Review → Verify → Refine → Copy/Download → Execute Through the Appropriate Operational System