Vlozi Website Content Audit and Conversion Copy

Status: draft source of truth
Created: 2026-05-13
Scope: apps/website marketing pages, product pages, pricing copy, nav/footer, and claims verified against local docs/code.

Goal

Rewrite the website content so it is:

• accurate against the actual Vlozi product surface in this repo;
• SEO-ready for product and category searches;
• conversion-focused for founders and small SaaS teams;
• specific enough to be trusted, without inventing social proof or roadmap guarantees.

Primary positioning:

Vlozi is a credit-powered growth platform for SaaS teams: blog, newsletter, AI chatbot, social content, contacts, and media in one dashboard.

Primary conversion promise:

Start with free credits. Use any tool. Pay for output, not access.

Verification Summary

Verified sources:

• Blog: docs/blog/blog-service.md, apps/blog-service/src/routes/*, packages/blog-sdk.
• Newsletter: docs/newsletter/templates.md, apps/newsletter-service/src/routes/*, apps/newsletter-service/src/db/schema.ts.
• Chatbot: docs/chat-engine/api-spec.md, apps/chat-engine/src/routes/*.
• Content Engine: docs/content-engine/api-spec.md, apps/content-engine/src/routes/*.
• Contacts/Leads: docs/contact-intelligence/api-spec.md, apps/contact-intelligence/src/routes/*.
• Media: apps/media-service/src/routes/*, packages/core-database/src/seed.ts.
• Billing and credits: packages/core-types/src/credit-costs.ts, packages/core-database/src/seed.ts, billing page implementation.

Key verified product facts:

• Blog supports drafts, publishing, unpublishing, scheduling, categories, tags, search/filter/sort, public API, SDK rendering, SEO fields, and server-rendered HTML.
• Newsletter supports subscribers, imports, segments, templates, reusable sections, campaigns, scheduled/sent/cancelled states, unsubscribe/confirm flows, open/click/bounce/failure stats, and render variables.
• Chatbot supports widget messages, WhatsApp/Telegram/channel connections, bot config/persona, sessions, human replies, assignment, resolution, and escalation.
• Content Engine supports social connections, campaigns, labels, slots, recurring schedules, OAuth flows, and per-platform publishing.
• Contact Intelligence supports contacts, profiles, context retrieval, memory ingestion, moods, outreach records, exports, and analytics.
• Media supports presigned upload, URL ingestion, upload completion, file listing/stats, soft delete, restore, permanent delete, archive emptying, and internal resolve.
• Billing plans and credit packs are seeded in packages/core-database/src/seed.ts.

Important correction:

• Website copy currently says or implies "1 credit per newsletter recipient." The shared cost registry says EMAIL_SEND_THOUSANDTHS: 200, meaning 1 credit covers 5 emails. Use "1 credit per 5 emails" or "0.2 credits per recipient" in new copy.

High-Risk Website Claims to Fix

SEO Strategy

Use one clear keyword cluster per page:

• Home: "SaaS growth platform", "credit-based SaaS tools", "blog newsletter chatbot for SaaS".
• Products: "modular SaaS growth tools", "credit-powered tools", "SaaS marketing tools".
• Blog product: "headless blog CMS", "Next.js blog SDK", "SaaS blog engine".
• Newsletter product: "email newsletter platform", "newsletter campaigns", "subscriber segments".
• Chatbot product: "AI chatbot for SaaS", "website chat widget", "WhatsApp Telegram chatbot".
• Content Engine product: "social media scheduling tool", "content calendar", "social publishing API".
• Leads product: "contact intelligence", "customer memory", "lead context".
• Media product: "media library for SaaS", "R2 media uploads", "asset management".
• Pricing: "credit-based pricing", "pay per use SaaS tools", "SaaS growth stack pricing".

Every page should include:

• one H1 with the main keyword;
• one direct product promise in the first paragraph;
• 3 to 6 feature sections with implementation-backed claims;
• one objection-handling FAQ block;
• one CTA above the fold and one at the end.

Global Navigation Copy

Recommended nav:

• Products
• Pricing
• Blog
• Docs
• Contact

Recommended CTAs:

• Primary: Start free
• Secondary: Sign in

Remove "Feedback" from the primary nav on desktop if conversion is the goal. Keep tool requests inside /products.

Footer Copy

Replace current footer body:

The credit-powered growth platform for SaaS teams. Publish content, send newsletters, answer customers, manage contacts, and store media from one dashboard.

Footer links should only point to existing pages or pages created before launch:

• Product: Products, Pricing, Blog, Changelog
• Company: Contact, Careers
• Resources: Documentation
• Legal: Privacy, Terms only after pages exist

Replace "All Systems Operational" with:

Beta platform

until a real status page exists.

Home Page Rewrite

Meta title:

Vlozi | Credit-Powered Growth Platform for SaaS Teams

Meta description:

Vlozi brings blog publishing, newsletters, AI chatbot, social content, contacts, and media into one credit-powered dashboard. Start free and pay for output, not access.

H1:

The growth platform billed by what you ship.

Hero subcopy:

Vlozi gives SaaS teams a blog, newsletter, AI chatbot, social content engine, contacts, and media library in one dashboard. Start with free credits, use any tool, and pay only when you publish, send, reply, or store more.

Hero CTAs:

• Start free
• Explore products

Hero trust line:

No card to start. Every plan can access every current tool. Credits work across the platform.

Problem section:

Most small teams do not need another subscription. They need fewer dashboards.

A blog lives in one tool. Email in another. Chat in another. Contacts in a spreadsheet. Media in a storage bucket. Every new workflow adds one more login, one more bill, and one more place where customer context gets lost.

Solution section:

Vlozi keeps the growth layer together.

Publish posts, send campaigns, answer customers, schedule social content, manage contacts, and reuse media from a shared platform. One wallet powers every tool, so you can start small and add more when the work demands it.

Feature cards:

1. Blog publishing
   Write, schedule, categorize, tag, and publish SEO-ready posts from a dashboard. Serve them through the public API or the React/Next.js SDK.

2. Newsletter campaigns
   Manage subscribers, segments, templates, reusable sections, campaign sends, confirmations, unsubscribes, and delivery metrics.

3. AI chatbot
   Run a website chat widget and connect messaging channels. Configure persona, manage sessions, escalate to a human, and keep conversation history.

4. Social content engine
   Connect social accounts, organize campaigns, label content, schedule slots, and publish across platforms.

5. Contact intelligence
   Maintain contact profiles, memory, mood, relationship context, outreach records, exports, and analytics.

6. Media library
   Upload, ingest, list, restore, delete, and resolve media files for use across Vlozi tools.

Credit section:

Credits are the common unit across Vlozi.

Blog publishes, AI replies, content publishes, email sends, and capacity add-ons draw from the same wallet. You are not choosing which features you are allowed to use. You are choosing how much output you need.

Recommended rate card:

Final CTA:

Start with the tools you need today.

Use free credits to try the platform. Add a subscription or packs when your output grows.

CTA: Start free

Products Page Rewrite

Meta title:

Vlozi Products | Blog, Newsletter, AI Chatbot, Social, Contacts, Media

Meta description:

Explore Vlozi's credit-powered product catalog: headless blog, newsletter campaigns, AI chatbot, content scheduling, contact intelligence, and media management.

H1:

One wallet. A growing catalog of SaaS growth tools.

Subcopy:

Use credits across every current Vlozi module. Start with one tool, add more when your workflow grows, and request what your team needs next.

How it works:

1. Pick a module
   Start with blog, newsletter, chatbot, content, contacts, or media.

2. Spend credits
   Credits are used when work happens: publishing, sending, replying, or extending capacity.

3. Expand without migration
   New modules use the same account, dashboard, and credit wallet.

Product card copy:

Blog

Tagline: Headless blog publishing for SaaS teams.

Bullets:

• Draft, publish, unpublish, and schedule posts.
• Organize content with categories, tags, search, and filters.
• Serve posts through public APIs or the @vlozi/blog SDK.

Newsletter

Tagline: Email campaigns, subscribers, templates, and segments in one place.

Bullets:

• Import and manage subscribers with tags and metadata.
• Build templates, sections, campaigns, and scheduled sends.
• Track delivery, opens, clicks, bounces, failures, and unsubscribes.

AI Chatbot

Tagline: Customer chat across your site and messaging channels.

Bullets:

• Configure bot persona, fallback behavior, model, and channels.
• Handle website widget conversations and messaging channel sessions.
• Escalate, assign, reply manually, and resolve conversations.

Content Engine

Tagline: Plan and publish social content from a campaign calendar.

Bullets:

• Connect social accounts through OAuth.
• Create campaigns, labels, slots, and recurring schedules.
• Publish per platform and refund failed publish attempts.

Contacts

Tagline: Contact context and memory for customer-aware workflows.

Bullets:

• Create contacts from interactions and manage profiles.
• Store memories, moods, engagement context, and exports.
• Use outreach records and analytics to understand relationship health.

Media

Tagline: A shared media library for every Vlozi workflow.

Bullets:

• Upload through presigned URLs or ingest external URLs.
• List, archive, restore, permanently delete, and resolve files.
• Store images, GIFs, AVIF, video files, SVGs, and PDFs within size limits.

Request-a-tool section:

Need a module that is not in the catalog yet?

Tell us what workflow is blocking your team. Product requests from this page should go straight into a separate "tool request" bucket so they can inform the roadmap.

CTA: Request a tool

Blog Product Page Rewrite

Meta title:

Headless Blog CMS for SaaS | Vlozi Blog

Meta description:

Vlozi Blog is a headless blog engine with dashboard publishing, scheduling, categories, tags, SEO fields, public APIs, and React/Next.js SDK components.

H1:

Headless blog publishing your team can manage without code changes.

Opening:

Vlozi Blog gives SaaS teams a production blog without building a CMS from scratch. Create drafts, schedule posts, manage categories and tags, and deliver published content through an API or React/Next.js SDK.

Feature sections:

• Dashboard publishing: create drafts, save edits, publish, unpublish, schedule, and delete posts.
• Content organization: categories, tags, tenant-scoped slugs, search, filters, and sort controls.
• SEO fields: title, description, excerpt, featured image, and server-rendered public HTML.
• Public delivery: published post list, post detail, categories, and tags available through API-key protected public routes.
• SDK integration: use @vlozi/blog components and helpers in a customer site.
• Tenant isolation: every post, category, and tag is scoped to the workspace.

Credit copy:

Publishing a blog post costs 10 credits. Drafting, editing, organizing, and keeping published posts online are not charged per view.

FAQ:

• Can I publish on my existing website?
  Yes. Use the public API or the @vlozi/blog SDK to render posts in your own app.

• Can I schedule posts?
  Yes. Posts support a scheduled state and scheduledFor timestamp.

• Can I organize posts by category and tag?
  Yes. Categories and tags are first-class tenant-scoped resources.

Newsletter Product Page Rewrite

Meta title:

Newsletter Campaign Software for SaaS | Vlozi Newsletter

Meta description:

Create email templates, manage subscribers, build segments, schedule campaigns, and track newsletter delivery metrics with Vlozi.

H1:

Newsletter campaigns connected to the rest of your growth stack.

Opening:

Vlozi Newsletter helps teams manage subscribers, segments, templates, reusable sections, campaigns, and delivery results without adding another disconnected email tool.

Feature sections:

• Subscriber management: create subscribers, import lists, tag users, store metadata, unsubscribe, and delete records.
• Segmentation: build named segments from filters such as tags, status, and subscription date.
• Template system: use HTML templates, block-authored templates, variables, preview text, and reusable sections.
• Campaign workflow: draft, schedule, send, cancel, and inspect campaigns.
• Deliverability records: track sent, delivered, opened, clicked, bounced, failed, and unsubscribed totals.
• Consent flows: public subscribe, unsubscribe, and confirm endpoints.

Credit copy:

Email usage is priced at 1 credit per 5 emails sent. Large campaigns are charged before fan-out so a campaign does not fail halfway through because credits run out.

FAQ:

• Can I import subscribers?
  Yes. Subscriber import is implemented in the newsletter routes.

• Are templates live-linked to campaigns?
  No. Campaigns snapshot template content when created, so scheduled sends remain deterministic.

• Does Vlozi reject unknown template variables?
  No. Unknown variables are preserved and logged; the editor should warn before save.

AI Chatbot Product Page Rewrite

Meta title:

AI Chatbot for SaaS Websites and Messaging Channels | Vlozi Chatbot

Meta description:

Configure an AI chatbot, connect website and messaging channels, manage sessions, escalate to humans, and keep customer context in Vlozi.

H1:

An AI chatbot that can hand off when a human should take over.

Opening:

Vlozi Chatbot gives teams a configurable bot for website and messaging conversations. Set the bot persona, connect channels, stream widget replies, and manage escalations from a unified inbox.

Feature sections:

• Website widget: receive widget messages and stream responses.
• Channel management: manage channel integrations including WhatsApp and Telegram infrastructure.
• Bot configuration: set persona prompt, fallback message, active model, creativity, and lead-capture rules.
• Unified inbox: list sessions, inspect message history, send manual replies, assign owners, resolve, and escalate.
• Service delegation: knowledge and contact context are delegated to AI Brain and Contact Intelligence.
• Billing: AI chat is token-based with a minimum per-turn floor.

FAQ:

• Does it support human handoff?
  Yes. Sessions can be escalated, assigned, manually replied to, and resolved.

• Is every reply a fixed credit cost?
  No. AI chat is token-based, with model rates and a minimum floor.

• Can I use WhatsApp or Telegram?
  The channel infrastructure exists for WhatsApp and Telegram. Public copy should avoid saying "one-click" unless the dashboard flow is verified.

Content Engine Product Page Rewrite

Meta title:

Social Content Calendar and Publishing Engine | Vlozi Content Engine

Meta description:

Plan campaigns, connect social accounts, schedule content slots, and publish social posts with Vlozi Content Engine.

H1:

Plan social content, schedule slots, and publish per platform.

Opening:

Vlozi Content Engine turns content operations into a campaign calendar. Connect social accounts, organize campaigns and labels, schedule slots, and publish to each selected platform.

Feature sections:

• Social connections: authorize, list, and disconnect social accounts.
• Campaigns: create, update, archive, and inspect campaign work.
• Labels: organize content with workspace labels.
• Slots: schedule specific content work for specific times.
• Recurring schedules: create repeatable patterns for ongoing publishing.
• Credit fairness: each successful platform publish costs 1 credit; failed publishes are refunded according to the shared cost comments.

FAQ:

• Is scheduling free?
  Scheduling itself is free. Successful platform publishes consume credits.

• Does one post to five platforms cost one credit?
  No. It costs one credit per successful platform publish.

• Should copy say "AI generation"?
  Avoid this as a primary claim unless the dashboard generation flow is verified.

Contacts Product Page Rewrite

Meta title:

Contact Intelligence and Customer Memory for SaaS | Vlozi Contacts

Meta description:

Build customer-aware workflows with contact profiles, memories, mood context, outreach records, analytics, export, and deletion controls.

H1:

Customer context your chatbot and team can actually use.

Opening:

Vlozi Contacts stores the customer context behind conversations: contact profiles, memories, mood, engagement state, outreach, and exports. It gives the chatbot and team a shared view of the relationship.

Feature sections:

• Contact profiles: create, list, view, export, and delete contacts.
• Context retrieval: return relevant memories, mood, relationship stage, and recent state for a contact.
• Memory ingestion: process user messages and AI responses into memory and state updates.
• Mood and relationship analytics: inspect mood trends, churn indicators, and engagement state.
• Outreach: create, list, cancel, and configure proactive outreach records.
• Privacy controls: export and delete contact data.

FAQ:

• Is this a full CRM?
  Not yet. Position it as contact intelligence and memory, not a full sales CRM.

• Does it support GDPR-style export/delete?
  The service has contact export and delete endpoints. Use "export and delete controls" rather than broad compliance promises.

• Does it score leads?
  Use "engagement and churn-risk analytics" unless a lead scoring model is verified.

Media Product Page Rewrite

Meta title:

Media Library and File Uploads for SaaS | Vlozi Media

Meta description:

Upload, ingest, organize, restore, delete, and resolve media files with Vlozi's shared media service.

H1:

A shared media library for the files your growth stack uses.

Opening:

Vlozi Media gives teams a central place to upload and reuse assets across product workflows. Upload files directly, ingest external URLs, track status, and manage archived files.

Feature sections:

• Presigned uploads: generate R2 upload URLs and complete uploads after transfer.
• URL ingestion: mirror approved external URLs into Vlozi storage.
• File management: list files, view stats, soft delete, bulk delete, restore, and permanently delete.
• Internal resolve: services can resolve media records for rendering.
• Supported formats: JPEG, PNG, WebP, GIF, SVG, AVIF, MP4, WebM, and PDF.
• Limits: uploads are capped at 10 MB by current service code.

FAQ:

• Does Vlozi transcode video?
  Do not claim transcoding. Current code stores accepted video files.

• Does Vlozi auto-crop images?
  Do not claim smart cropping until implemented.

• Can files be deleted?
  Yes. The service supports soft delete, restore, permanent delete, and archive emptying.

Pricing Page Rewrite

Meta title:

Vlozi Pricing | Credit-Based Pricing for SaaS Growth Tools

Meta description:

Vlozi uses one credit wallet across blog, newsletter, chatbot, content, contacts, and media. Start free, subscribe for steady usage, or buy packs for spikes.

H1:

Every current tool, one credit wallet.

Subcopy:

Start free, then choose the credit model that matches how you ship. Subscriptions cover steady monthly output. Packs cover spikes and irregular usage.

Free section:

Free signup includes 100 credits. No card required.

Use them on any current Vlozi tool. They are best for testing the workflow, publishing a first post, trying chat, or sending a small campaign.

Important wording:

• Use "free signup credits" instead of "Free plan credits every month" unless free monthly refill is intentionally implemented.
• Use "every current tool" instead of "every feature forever."

Plan section:

Paid plans increase monthly credits and workspace capacity: seats, API keys, custom roles, storage, custom domains, and support.

Rate card:

FAQ correction:

• "What if I run out?" should say: "new paid actions may pause until credits are added." Do not promise emails at 80% unless implemented.
• "Refunds" should be removed unless policy is confirmed.
• "GST invoices" can stay only if billing/invoice flow is confirmed for Razorpay.

Contact Page Rewrite

Meta title:

Contact Vlozi | Sales, Support, and Product Requests

Meta description:

Contact the Vlozi team for product questions, support, pricing, partnerships, and custom setup.

H1:

Talk to the Vlozi team.

Subcopy:

Have a product question, support issue, pricing request, or setup need? Send us the details and we will route it to the right place.

Form subjects:

• Product question
• Technical support
• Pricing or billing
• Setup help
• Partnership
• Tool request

Remove until verified:

• "our engineers are standing by"
• "we basically live on Discord"
• "Join 5k+ developers"
• San Francisco HQ language unless legally true

If the form is not wired, do not show a fake form. Use:

Email us at hello@vlozi.app or sign in and use dashboard support.

Early Access Page Rewrite

Current page risk: form prevents default and does not submit. It also claims "1,000+ engineers already on the waitlist" without local proof.

Recommended H1:

Start with Vlozi beta.

Subcopy:

Create a workspace, claim free credits, and try the current catalog: blog, newsletter, chatbot, content, contacts, and media.

Benefits:

• Free credits to test real workflows.
• Access to the current Vlozi tool catalog.
• Product requests from beta users help shape what ships next.

CTA:

Start free

Remove:

• "Limited spots available" unless enforced.
• "Founding member pricing" unless locked in billing policy.
• "Invite link within 24 hours" unless there is an invite workflow.
• "1,000+ engineers" unless backed by a real count.

Careers Page Rewrite

Current page risk: job posts may not be real openings and use inflated language.

Recommended H1:

Help build Vlozi.

Subcopy:

We are building a credit-powered growth platform across publishing, messaging, content, contacts, media, and AI infrastructure.

If roles are real, use:

• Role title
• Remote/onsite
• Employment type
• What the person will own
• How to apply

If roles are speculative, use:

We are not hiring for a fixed role right now, but we want to meet strong engineers, designers, and growth operators who care about developer tools and SaaS infrastructure.

Remove:

• "technical alchemist"
• overly specific architecture claims in job descriptions unless recruiting for those exact systems
• fake apply flow if it only links to the generic contact page

Changelog Page Rewrite

Current page risk: marked "Dummy data" in code and contains old LogicSpike naming.

Recommended H1:

Product changelog

Subcopy:

Updates to Vlozi products, SDKs, platform billing, and infrastructure.

Rules:

• Only include shipped changes.
• Link each entry to docs or package changelog when possible.
• Use Vlozi naming, not LogicSpike public naming.
• Avoid "cutting-edge infrastructure" generic CTA.

Entry template:

### [Product or package] [version/date]
 
What changed:
- Specific shipped change.
- User-visible impact.
- Migration note, if any.
 
Status: shipped

Site-Wide Copy Rules

Use:

• "current tools" instead of "every future feature";
• "credit wallet" instead of "coins" on public marketing pages;
• "SaaS teams", "founders", and "small teams" instead of only "developers";
• exact credit costs only when verified in CREDIT_COSTS or seed data;
• "beta" when the claim is not mature enough for enterprise language.

Avoid:

• "no-code" as the main category;
• "all systems operational" without status monitoring;
• social proof numbers without a data source;
• compliance claims such as SOC 2, GDPR-ready, SLA, or data residency unless implemented and approved;
• roadmap promises like "Slack coming soon" without committed public roadmap;
• fake forms that do not submit.

Implementation Priority

1. Fix pricing copy for email credits.
2. Replace product page detail copy with verified claims.
3. Remove fake/unverified social proof from contact and early-access pages.
4. Fix or remove non-submitting forms.
5. Remove footer links to missing routes or create the pages.
6. Add page-specific metadata for /products, /pricing, /contact, /early-access, /careers, and /changelog.
7. Replace stale apps/website/lib/constants.ts product/FAQ content or delete unused exports.

Suggested Page Build Order

1. Home: update hero, product summaries, credit section, and final CTA.
2. Pricing: correct rate card and FAQ.
3. Products: update cards and product detail content from this document.
4. Contact and early access: remove fake claims and wire forms.
5. Footer/nav: remove dead links and tighten the brand promise.
6. Changelog/careers: decide if public pages should exist before launch.