Marketing

Marketing is how we understand the market, shape how Feel Your Protocol is seen, and communicate why it is useful. The goal is to make a person want to try the product.

This page covers those three jobs. The product proposition, price, and channels people or agents arrive through (Distribution) have their own pages.

Listen for the problem. Show the thing that exists.

Understand the market

We do not have a research program. We have three small feedback surfaces, two of them already running.

Listen

The weekday X scan shows what protocol people are discussing. It is a weather report, not market research.

Talk

One-to-one launch conversations can surface the questions people would actually bring to the lab.

Observe

The private usage view can show which tools get called and where requests fail once the server has traffic.

The possible users are already named: protocol engineers, EIP authors, auditors, wallet and app engineers, and agent builders. That list comes from what the lab can honestly do; it is not evidence that each group wants it.

What matters next is not a broad survey. It is a small record of what we hear and what people do:

Question	Evidence we could keep
Which problems recur?	A short note from direct conversations and relevant X threads
Who returns after trying it?	Repeat calls in the usage view, without building a profile of the caller
Where does interest stop?	Could not connect, could not form the input, missing capability, or no repeat need
Which audience gets durable value?	A handful of concrete uses, not a persona invented in advance

Keep this light

No research theatre and no dashboard because marketing says there should be one. Write down repeated evidence; change the product or the message only when a pattern appears.

Shape the brand

The visual system already has a point of view. It is technical without looking like infrastructure documentation, and playful without making the protocol look trivial.

One recognisable system

Monospace type, topic colours, generated link cards, and the same visual language across the textbook, docs, roadmap, and social surfaces.

Competence you can click

An exploration is not a claim of expertise. It is an interactive example built on the same EthereumJS stack as the lab.

A human front

Technical cover art, Bro & Bruh comics, and short videos make a dense protocol change approachable.

Precision underneath

Pinned specs, provenance, boundaries, and honest gaps keep the playful surface from turning into hype.

The cover system is deliberately constrained: greyscale plus one topic colour, abstract technical illustration, one focal point. The broader interface carries the same topic colours and a code-first, cypherpunk tone. Comics and videos extend the identity without replacing the technical artefact.

The useful perception to protect is simple: playful on the surface, exact underneath.

That means:

• the token and x402 are never the headline;
• a new visual or post points to something that runs;
• the website and MCP describe the same capability and the same limit;
• no “oracle” language that promises archive state, historical backtesting, or anything else outside the lab.

Possible next checks:

• Does the first visit to the website, mcp-docs, and a future registry listing feel like the same product?
• Once the MCP is public, can one compact visual show prompt → tool → trace without becoming another explainer format?
• Are the comics widening the door while the video and MCP post carry the more technical reader, or are those roles only assumed?

Communicate what shipped

The existing loop is deliberately small. Each exploration produces the artefact and the communication around it; nothing is pre-produced just to fill a calendar.

Piece	Job	State
Comic	Stop the feed with a protocol-native joke and make the change memorable	Running
Short video	Explain what the EIP does and invite the viewer to test it against their own domain	Running
MCP post	Show one concrete prompt against the hosted server	After launch; exact shape open
X engagement	Keep listening and join a useful conversation between releases	Weekday scan; human decides and posts

The detailed voice and production rules stay in the comic, video, and engagement skills. Distribution owns where these pieces travel.

The operating rule

No artefact, no announcement. Silence is better than a generic post.

Changelog

Marketing Changelog

1. v0.92026-10-05Rebuilt around market understanding, brand perception, and communication that follows shipped work. Existing listening, visual identity, announcement arc, and honest gaps made explicit.
2. v0.82026-09-14Announcement tweets are shown at round-trip close after merge; comic and video skills still author the YAML.
3. v0.72026-09-10Engagement weather: high-stakes MCP complement (Base when it clears the bar); exploration add/sunset keeps the watchlist lexicon in sync.
4. v0.62026-09-10Engagement weather: always-on “what moved” search plus broader family queries; fewer overlapping searches.
5. v0.52026-09-10Engagement weather: cluster quotes/replies of the same story into one bullet.
6. v0.42026-09-10Engagement: memory-led follow-ups (events/controversies) instead of weekday-by-EIP rotation.
7. v0.32026-09-10Engagement cadence: one weekday-morning scan; clock lives in the Automation.
8. v0.22026-09-09Engagement loop — weather briefing plus reply/quote/retweet suggestions; rules in the x-engagement skill.
9. v0.12026-09-03Initial page — per-exploration announcement arc (comic + video today, MCP tweet after launch).