# How We Built the Brand Building JOJO wasn’t a marketing campaign — it was an accidental ritual summoning. **☕ Brainstorms Fueled by Red Bull & Regret** We locked ourselves in a Discord room with nothing but Figma tabs, crypto Twitter open, and industrial amounts of caffeine. Every idea was welcome — except “make it serious.” We rejected professionalism like a STD test from an ex. > “What if the hero was a used condom with emotional damage?”\ > “Bro. Yes.” This wasn't branding. This was **emotional graffiti** on the walls of the blockchain. *** **🍑 Writing Erotic Lore in Google Docs** Imagine five grown adults professionally typing: > “JOJO moaned as the Solana pump thrusted into his latex soul.” ### **The lore wasn’t *****written***** — it was *****exorcised.*** \ Every line had to balance chaos with cohesion, filth with finesse. We debated whether JOJO should cry during sex scenes. We created lore arcs with storyboards that belonged in an HBO parody. And yes, we Googled “how do condoms feel emotions?”. Don’t judge us. *** **🧠 Memes + Market Research = JOJO DNA** We studied memecoins like war generals and hentai addicts. Frog fatigue was real. The market was oversaturated with animals and anime girls. But **no one** had a condom. We A/B tested taglines like: * “Unwrap your destiny.” * “Ribbed for market penetration.” * “The only rubber you want in your wallet.” JOJO was engineered from the deepest corners of Reddit and the horniest sections of Telegram.\ He was built not just to go viral — but to stick. Like... well, you get it. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://jojo-the-wasted.gitbook.io/cum/how-we-built-the-brand.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.