Marketing Page, Agent Readiness, and Lessons Learned

Part 10: Marketing Page, Agent Readiness, and Lessons Learned

The marketing page stopped being “just a landing page” the moment it had to explain a privacy product honestly.

That was the real constraint.

It is easy to make a homepage that sounds impressive. It is harder to make one that says what the product is, what it is good at, where its limits are, and how an agent or crawler should understand it without turning the whole site into noise.

This chapter is about that work.

The first change was not visual

The first useful improvement was clarifying the message.

The page moved toward a simpler framing:

• a private space for your thinking
• your ideas stay yours
• mind maps and notes only you can read by design

That sounds like copywriting, but it was really product clarification.

The page had to explain why this product exists:

• mind maps reveal structure, not only text
• structure can be highly sensitive
• privacy is not a badge, it changes how freely people can think

Once that was clear, other decisions got easier.

The hard part was honesty

Privacy products are full of vague promises.

So the page had to say the inconvenient parts out loud:

• there is no admin backdoor
• there is no hidden password recovery for existing encrypted vault contents
• on-premise installation does not suddenly mean readable admin-side access

That honesty changed more than the FAQ.

It affected:

• the hero copy
• the pricing section
• the on-premise description
• the feedback form wording
• the comparison section

The lesson was simple: if the security model matters, marketing copy cannot fight it.

Showing the product mattered

The page also needed to show the interface, not just describe it.

So the hero moved toward a screenshot slideshow instead of a more abstract placeholder image. That made the page more concrete immediately.

The slideshow ended up using a few practical rules:

• keep it near the top
• let it auto-advance slowly
• keep controls minimal
• use a cleaner light presentation in light mode
• keep a darker frame in dark mode so the screenshots do not float awkwardly

This was not a huge engineering task, but it changed the page from “statement” to “product.”

Navigation had to stay on-page

Another improvement was adding topbar navigation for sections like:

• pricing
• security
• compare

The important detail was that this should stay on the same page and scroll to the relevant section instead of pretending every subsection needs its own separate route for humans.

At the same time, the page still needed machine-readable summaries for agents.

That is where the agent-readiness work became useful.

Agent readiness was mostly structure

After reading Cloudflare’s work on agent readiness, the lesson was not “add hype words about AI.”

The lesson was structure.

Useful improvements included:

• a richer robots.txt
• an expanded sitemap.xml
• a root llms.txt
• a fuller llms-full.txt
• a concise index.md
• section-specific markdown summaries like pricing/index.md, security/index.md, and compare/index.md
• response Link headers pointing to those resources
• a small hidden page directive telling agents to prefer markdown resources

None of that changes the visual design much.

But it changes how efficiently machines can understand the project.

That matters more than it used to.

Path-based blog URLs were part of the same problem

The builder blog originally lived behind hash routes.

That worked for humans, but it was weak for indexing and weak for agent consumption.

Moving published posts to real path-based routes was the cleaner solution.

The markdown article files were already public. The missing piece was giving the human-facing pages proper paths too.

This is a good example of a broader rule:

If a piece of content matters, it should have a stable URL.

Comparison copy had to stay disciplined

The comparison section was another place where the page could have become sloppy.

It is tempting to promise that every competitor is unsafe or unserious.

That would be weak marketing.

The better version was narrower:

• many products optimize for collaboration first
• many products keep recovery convenience and admin visibility available
• MindMapVault is for the case where private structure matters more than those trade-offs

That is a sharper and more defensible statement.

What I would keep doing this way

This work reinforced a few rules I would reuse:

• explain the trust model in plain language
• keep the visuals concrete
• avoid fake enterprise promises
• give both humans and agents a cleaner reading path
• publish markdown wherever it helps reduce ambiguity

What this changed in practice

By the end, the marketing page was doing several jobs better than before:

• it explained the product more clearly
• it showed the product earlier
• it exposed pricing and comparison more directly
• it gave crawlers and agents better public resources
• it aligned the page copy with the actual zero-knowledge model

That does not make the page “finished.”

But it did make it more honest, more legible, and more useful.

And for a privacy product, that is probably a better goal than trying to sound bigger than the software really is.