Eddie, thank you for being so thorough with all of your duties and all that you’ve been working on. I’m so grateful that you were a part of our team. You really helped to shape this project and give us a foundation for how to move forward. I appreciate all of the time and effort that you put in. I wanted to make sure that I took the time to thank you for all of the effort that you put into getting us in a good place because I couldn’t have gotten to this point without you here.
Okay, is there anything else you want to go through?
It's looking really, really good, Eddie. I'm so happy that you understand this space — you know how to manipulate this space. It's such a relief to know somebody has this skill set. I'm so glad I found you. Thank you.
Client: Thank you for jumping on this call today. Eddie and thank you for your patience. I love your temperament. Ed: Ah, thank you.
Client: Alright, we’ll talk soon
https://youtu.be/kic6QtIe7fw?si=rwCyN_xku9g1rg4B
<aside> 📸
| Category | Strategic Detail |
|---|---|
| Client Name | CJ Harris (Founder, Guapify) |
| Industry | Financial Education Media / Black Wealth-Building |
| The Challenge | "Template Friction"—transforming a generic, institutional Mighty Networks interface into a culturally authentic "safe space" that didn't feel "corporate." |
| The Solution | Implementation of a "Dark Mode" branded interface, topic-based space taxonomy, and a curated Linktree hub for multi-channel content (YouTube/Podcasts). |
| Certifications | HubSpot Content Marketing (Repurposing), Canva Design School (Visual Hierarchy), Meta Blueprint (Mobile UI), HubSpot Inbound (Segmentation). |
| The Impact | Launched a centralized "Wealth Hub" that replaced scattered social links with a single, high-fidelity destination for Black financial literacy. |
| The Tech | Mighty Networks (Community Hosting), Linktree (Link-in-Bio), Google Drive (Asset Management), Video Transcript Editing. |
| The Results & ROI | Reclaimed strategic capacity for the founder via a 30-minute weekly maintenance playbook and established a "For Us, By Us" digital environment. |
| </aside> |
<aside> ⚠️
</aside>
<aside>
CJ Harris had built Guapify as financial education media brand with growing YouTube presence, podcast content, and social media following—but lacked centralized community space where audience could connect, learn, and build relationships around shared wealth-building interests. Mighty Networks offered infrastructure, but default templates felt generic, institutional, and disconnected from Guapify's hip, conversational brand voice.
"I always want things to sound conversational. It should never sound like we're real corporate," CJ explained during our design review. "It's for us by us, talking to each other. I always want this to feel like a safe space. It doesn't have to have this generic 'come one, come all' kind of feel. It's a safe space for us to talk the way we talk."
This opening statement revealed the fundamental tension: Mighty Networks provided robust community features, but visual defaults and interface patterns screamed "corporate learning platform" rather than "Black millennial wealth community." CJ needed transformation from out-of-the-box template to custom-branded experience reflecting Guapify's cultural identity.
The Visual Brand Disconnect:
"Eddie, I love that you made it a background," CJ noted, reviewing the dark mode interface I'd implemented. "That looks really nighttime and cool. I know other kids love black backgrounds these days."
But immediately followed with design critique: "The only thing about the black is that the word Guapify in the upper left hand corner is getting lost. So we need some variations of that."
This revealed core challenge: Mighty Networks allowed customization, but required navigating visual hierarchy (logo visibility against dark backgrounds), color scheme consistency, typography choices, and image selection—all while maintaining platform's built-in interface elements.
The User Onboarding Complexity:
"What I was hoping is when they come on to the website, we're asking a series of questions," CJ explained. "Based on how they answer these questions, we help to guide them to the type of content that would be most relevant for them, so that we make those suggestions. It's almost like we are gathering data on our user as soon as they walk through the door."
This represented sophisticated onboarding vision: personalized content routing based on user interests—directing someone interested in real estate to home ownership spaces, investment enthusiasts to stock market discussions, student loan borrowers to debt payoff communities.
But Mighty Networks didn't offer built-in conditional logic for automatic space assignment based on intake questionnaire responses. CJ envisioned Typeform-style onboarding → algorithmic space suggestions. Platform reality: manual space selection or blanket auto-enrollment.
The Welcome Video Content Challenge:
When reviewing the welcome page with embedded video, CJ noted: "I love this. Let me ask you—the copy that you have, is that basically the same thing that I'm saying, or how did you come up with the copy you're featuring there?"
"I took the transcript from the video and then I re-edited it to an extent," I explained.
"Okay, good to know. It's not just the same thing that you said," CJ confirmed, then added: "I was thinking the next interview should be me, and that interview will be what we feature there, because I feel like this is an old interview. Kea's gonna do an interview with me around the community, and hopefully we can cut something that will be compelling enough for us to feature there."
This revealed content lifecycle management challenge: welcome video featured outdated interview, requiring replacement workflow (schedule new interview → edit → embed) plus ongoing content governance as community evolved.
The Topic-Based Space Architecture:
"Part of the gathering of their information is that we also ask what are their topics of interest," CJ explained. "Because I want people's topics—the things that they're interested in—to follow them and be a part of their profile, so that we can start creating communities of people that are also interested in investment. These people are interested in real estate. You know what I mean? I want them to see each other and know each other and start to become a community within our community."
This articulated vision for nested community structure:
But Mighty Networks space architecture required careful taxonomy—too many spaces fragmented conversation, too few created overwhelming general feed. Finding balance between specificity and critical mass challenged community design.
The Stock Photo Problem:
"Where did you get those pictures from, Eddie?" CJ asked, reviewing header images.
"I got them from Canva," I replied.
"Okay, did I give you access to a folder full of stills?" CJ asked.
"Was it on Dropbox?" I asked.
"No, I think it's on the Google Drive. Let me get you some stills that I have. Are these public domain, like anyone can use these?" CJ probed.
"Free to use," I confirmed.
"All right, let me get you these shots that I did pay for though. It's a folder full of stills that might be useful—a bit hipper and less generic feeling."
This exchange revealed visual authenticity gap: Canva stock photos featuring diverse people technically checked representation boxes, but lacked cultural specificity and brand personality Guapify required. CJ had commissioned custom photography but hadn't provided asset access—creating placeholder aesthetic until real brand imagery replaced generic stock.
The Link Consolidation Challenge:
Later in conversation, we discussed Linktree strategy for consolidating Guapify's scattered digital presence:
"Can you show me again what we will get when you click the link?" CJ asked.
I showed the Linktree structure organizing:
"So under Guapify Originals, you clicked that? So that's just going to keep getting longer and longer with all the original content?" CJ asked.
"Depends. My thought process was the latest ones always come up at the top," I explained. "So maybe you can have like the top five every time or the top six. You can always have a link that leads to the full category."
"Yeah, I prefer consolidating it so there's not so much information," CJ confirmed.
This revealed content curation vs. comprehensiveness tension: Linktree could theoretically list every YouTube video, but visual real estate limitations demanded editorial selection (top 3-5 pieces) with "See More" category links—requiring ongoing content governance as new episodes published.
The Manual Update Reality:
"So to update it on a regular basis, right?" CJ asked about Linktree maintenance.
"Yeah, just someone has to update the latest one," I confirmed.
"There's no automation where this happens automatically, right? It has to physically be done?" CJ clarified.
"Okay. It's probably a 30-minute process," I estimated.
"Right, can you add that to the to-do list of duties?" CJ requested.
This pragmatic exchange acknowledged platform limitations requiring manual workflows—Linktree couldn't auto-pull latest YouTube uploads, requiring weekly content manager updates to feature newest episodes.
</aside>
<aside> 💡
</aside>
<aside>
I conducted multi-phase Mighty Networks customization including dark mode interface implementation, custom header graphics for topic spaces, welcome page video integration with transcript editing, topic-based community architecture, Linktree link-in-bio consolidation, and comprehensive job duty documentation for successor handoff.
Rather than accepting Mighty Networks' default light interface, I activated dark mode and customized visual elements for brand consistency.
The Initial Implementation:
"I love that you made it a background," CJ said, reviewing the black interface. "That looks really nighttime and cool."
This represented platform customization beyond defaults—Mighty Networks offered dark mode as user preference setting, but I identified it as brand-aligned aesthetic choice and documented activation instructions for new members.
The Logo Visibility Fix:
"The only thing about the black is that the word Guapify in the upper left hand corner is getting lost," CJ noted. "So we need some variations of that."
The Strategic Decision:
"Let me find, let me figure out if there is a white version of that logo," CJ said, problem-solving the contrast issue.
This demonstrated iterative design process: implement dark aesthetic → identify contrast problem → source white logo variation → swap assets for visibility.
The User Control Acknowledgment:
When CJ asked "Is there a way for us to make that default look so that that's what the user sees automatically?" I explained platform limitations:
"I don't think so because I think it's a user preference. So they have to choose it automatically. But we can tell them how to go about it. We can just add a simple tutorial."
This balanced brand vision (everyone sees dark mode) with platform reality (user-controlled preference)—solution: onboarding tutorial showing dark mode activation.
The community's first impression required compelling video introduction with supporting copy.
The Content Curation:
"I took the transcript from the video and then I re-edited it to an extent," I explained when CJ asked about welcome page copy.
This demonstrated transcript repurposing methodology—rather than writing generic "Welcome to our community!" copy, I extracted actual spoken content from existing Guapify video, edited for clarity/concision, and positioned as authentic brand voice introduction.
The Content Governance Pathway:
"I was thinking the next interview should be me," CJ explained, "and that interview will be what we feature there, because I feel like this is an old interview. Kea's gonna do an interview with me around the community."
This established content lifecycle workflow:
<aside>
</aside>