mdcraft.ai Positioning and Messaging#

Product thesis#

mdcraft.ai should be positioned as the finishing layer for markdown-heavy workflows.

The market does not need another basic converter. It needs a product that takes raw markdown from AI tools, IDEs, GitHub, Notion, or note apps and turns it into exports that look intentional, polished, and safe to share. It also needs a trustworthy way to recover clean markdown from existing text-first PDFs without pretending every document can be converted perfectly.

Category definition#

mdcraft.ai is a beautiful and reliable markdown document workflow.

That framing matters because:

• converter sounds disposable and free.
• editor suggests replacing the user's existing writing tools.
• document workflow lets the brand own quality, trust, templates, review, and automation.

Core promise#

Turn raw markdown into polished documents, and recover usable markdown from messy files.

Pricing position#

• Launch with one public paid plan: Pro at $8/month
• Sell Pro around unlimited access, polish, and repeat professional use
• Keep Enterprise contact-led later instead of treating it as a launch plan
• Do not lead the paid message with reverse-conversion beta limits

Primary differentiators#

1. Output quality over format count
   • Most competitors are either technically broad or visually polished.
   • mdcraft.ai should win by making PDF exports look obviously better than browser extensions and generic converters.
2. Preview/export parity
   • The preview should closely match the exported result.
   • Users should not need a separate print-debugging workflow.
3. Honest reverse conversion
   • PDF -> Markdown should launch with clear scope and a manual review pass.
   • The product should never imply perfect extraction on complex layouts.
4. AI-native workflow fit
   • The product should assume markdown often comes from ChatGPT, Claude, Cursor, GitHub Copilot, or internal AI tools.
   • The headline use case is turning AI output into something presentable.

Ideal customer profiles#

ICP 1: AI power users#

• People who create reports, PRDs, memos, specs, or documentation with AI tools.
• They care about speed, polish, and low-friction sharing.
• They are highly likely to try a browser-based tool if the output looks professional.

ICP 2: Developers and docs-as-code teams#

• They already use markdown every day.
• They care about code blocks, tables, Mermaid, math, links, and repeatable exports.
• They will pay if the output is reliable and easier than Pandoc or ad hoc scripts.

ICP 3: Consultants and product teams#

• They need stakeholder-ready documents, not just raw markdown files.
• They value clean typography, branded templates, and fast export.
• They are a strong fit for paid tiers and future team features.

Growth audience: Students and educators#

• Large top-of-funnel audience with real usage frequency.
• Good fit for the free tier and word-of-mouth adoption.
• Lower willingness to pay, so they should not define the premium roadmap.

Jobs to be done#

Forward conversion jobs#

• Turn rough markdown into a polished PDF I can send externally.
• Keep code, tables, math, diagrams, and images readable in the final document.

Reverse conversion jobs#

• Recover markdown from a text-first PDF so I can edit or reuse it.
• Turn a static file into something AI tools, docs systems, or editors can work with again.
• Avoid hours of cleanup after copy-pasting from a PDF.

Homepage messaging#

Hero options#

Option A:

Turn raw Markdown into polished documents.

Subhead:

Export beautiful PDFs, then recover clean Markdown from text-first PDFs when you need to work backwards.

Option B:

The professional workflow for Markdown exports and recovery.

Subhead:

Built for AI users, developers, teams, and anyone who needs Markdown to look polished outside the editor.

Option C:

Beautiful Markdown documents, without the toolchain pain.

Subhead:

Create client-ready PDFs and recover usable Markdown from existing files in one workflow.

Messaging pillars#

Pillar 1: Beautiful by default#

• Notion-like readability
• Print-safe page breaks
• Great code blocks, tables, math, and diagrams
• Clean typography and spacing

Pillar 2: Reliable enough to trust#

• Preview closely matches export
• Stable PDF rendering
• Scoped reverse conversion with review

Pillar 3: Built for modern workflows#

• Works well with AI-generated markdown
• No CLI or desktop setup required
• Faster than manual cleanup in Docs or Word

Objection handling#

"Why not just use Pandoc?"#

Pandoc is powerful, but most users do not want a templating and CLI problem. mdcraft.ai should sell speed, polish, and simplicity.

"Why not use a VS Code extension?"#

Extensions solve basic export. They do not usually solve design quality, consistent templates, or reverse conversion workflows for non-technical recipients.

"Why not use Notion?"#

Notion is a workspace. mdcraft.ai is the fastest way to go from markdown input to a polished output, regardless of where the content was written.

Suggested homepage section order#

1. Hero: polish + two-way workflow
2. Social proof/problem statement: AI and markdown are colliding
3. Core workflows: Markdown -> PDF, PDF -> Markdown beta, review-first studio flow
4. Quality differentiators: tables, code, math, Mermaid, pagination
5. Template system
6. Audience-specific use cases
7. Pricing
8. FAQ and privacy statement

Tone and brand#

• Crisp, modern, professional
• More premium than playful
• Confident, but careful not to overclaim reverse-conversion accuracy
• Outcome-driven rather than feature-list heavy