Learn with O.J. — Branding & Marketing Reference

Last updated: March 18, 2026

This is a single-source reference for all branding, marketing, and positioning material developed across conversations. Use this to inform website redesign, LinkedIn content, LinkedIn company page, and future marketing efforts.

1. BRAND IDENTITY

The Name: O.J.

The name is the brand. It's a childhood nickname that became a strategic asset.

Origin story (elevator pitch version): "I started going by O.J. on my resume because my full name wasn't getting callbacks. The moment I switched, hiring managers started calling just to ask about the name. That's when I learned: being memorable isn't optional, it's strategy. Now I help other engineers figure out theirs."

Validated punchline: "People ask me why I go by O.J. and the short answer is branding. The long answer: book a session." — Got laughs from the 1909 brand mentor AND an external marketing company owner. Two independent validations. This one is proven.

The juice angle is the lane. Validated by the brand mentor at 1909 and the marketing company connection. Lean into beverage/juice metaphors. Avoid the O.J. Simpson angle entirely for now (too dark/edgy for early-stage client acquisition per marketing company feedback).

Organic proof it's working: A guy at 1909 greeted you with "Hey O.J. the juice is loose!" — the name is sticking and people are already riffing on it unprompted.

Brand Mentor Guidance (from 1909 AWL)

Brands that aren't memorable are commodities
Laughter is the metric. If a line makes people laugh, it eases the anxiety your customers are feeling
Generate a big messy list of ideas, sit with them, then come back with a machete and ruthlessly edit down to the best
You could lean into the juice angle with things like "O.J. will give you the juice"

Validated Brand Toolkit

Asset	Status
"Short answer: branding. Long answer: book a session."	Validated (2 independent laughs)
The juice angle (beverage metaphors)	Validated (brand mentor + marketing connection)
Origin story (callbacks after name change)	Validated (natural conversation starter)
"O.J. the juice is loose"	Organic (someone said it unprompted)
Fresh Squeeze (product name candidate)	Strong candidate, not yet validated externally

Brand Personality Keywords

Source: AWL Session 5 workshop exercise (facilitated by branding mentor). Framework: Pick 5 keywords that describe your brand personality. 4 should be expected/natural, 1 should be weird/unexpected to create tension. The tension is the sweet spot that makes the brand memorable.

The Five: Collaborative. Real. Experienced. Irreverent. Determined.

Keyword	What It Does	Evidence
Collaborative	The core of what you sell. This is the through-line across everything.	Kirk called you "the team member I didn't know I needed." Mickey said the most useful thing was learning how to collaborate. Your former boss said "one of the most collaborative and positive team members I've worked with" and hired you twice.
Real	Does the work of both "authentic" and "no-bs" without sounding like a therapy session or a LinkedIn cliche.	You admit you don't know the answer and figure it out in front of clients. Kirk said that blew him away: "you have decades of experience but still are real enough to admit you don't know all the answers and aren't afraid to show how you get to the answer."
Experienced	Earns the trust. It's not bragging when it's the reason someone should hire you.	20+ years, leveled up twice (senior SWE to senior SRE), startup to Fortune 100 (smart TV apps competing with Netflix to American Express).
Irreverent	The weird one. Creates the tension that makes the brand memorable. Engineers trust people who don't take themselves too seriously because the ones who do are usually the ones who can't actually do the work.	The juice branding, the unhinged mastermind answers that got laughs and contact info, Kirk workshopping slogans unprompted on the customer interview call, "it's always DNS."
Determined	Has a story behind it that makes it sticky. Maps to the purpose statement about what gets you through the hard days.	When your future Amex boss asked for one word to describe yourself before he hired you, you said "determined." That's a proof point baked into a brand keyword.

The tension: Irreverent + Determined. She's funny but she doesn't quit. That's the diamond. It means the brand can be playful and approachable (juice puns, unhinged mastermind answers, casual tone) without ever feeling lightweight, because underneath the humor is someone with 20+ years of showing up and getting it done.

How to use these keywords: Every piece of content, every client interaction, every marketing decision should feel like it could be described by at least 2-3 of these words. If something you're writing feels flat, check if it's missing the irreverence. If something feels too jokey, check if it's grounded in the experience and determination. The keywords are guardrails, not a checklist.

2. POSITIONING & MESSAGING

The Introduction (two versions, both used on the Lucie/Sara discovery call that closed a deal)

Short version (casual conversations, networking, 1:1s): "I'm O.J., founder of Learn with O.J. and I'm a working engineer helping other engineers level up. My goal is to show others the way to build careers that compound while I help companies move fast without breaking things."

Long version (B2B, establishing expertise with businesses): "Hi, I'm O.J., founder of Learn with O.J. and I'm a working engineer helping other engineers level up. I have over 20 years of software engineering experience from startups building smart TV apps competing with Netflix to Fortune 100 organizations like American Express. I leveled up twice myself, from senior software engineer to senior site reliability engineer and my goal is to show others the way to build careers that compound while I help companies move fast without breaking things."

The short version establishes credibility (working engineer), the offer (helping engineers level up), the vision (careers that compound), and the B2B angle (move fast without breaking things) in two sentences. The long version adds the range (startup to Fortune 100), the name recognition (Netflix, American Express), and the specific career trajectory (leveled up twice) that businesses need to hear up front before they trust you with their team.

Core Positioning Statements

For individual engineers (B2C): Experienced software and infrastructure engineers who haven't gotten the title yet, who are doing senior-level work but can't figure out how the game actually works.

For companies (B2B): A working engineer who helps teams ship faster without sacrificing quality, through training, upskilling, and operational guidance.

The "working engineer" brand: This is the through-line that ties everything together. You're not a coach from the sidelines. You're still actively doing the work and that's what gives you credibility. "Working engineer" only works if you're actually working.

Language Rules

Use "software and infrastructure engineers" not just "engineers" (LinkedIn audience framing)
Use "experienced engineers who haven't gotten the title yet" not "mid-career" engineers
No em dashes in your voice
Combine parallel short sentences with "and" not periods
Use "how" over "why" for systemic critique
Pronoun over repeated name

The Core Offering Shift: From Mentoring to Operational Career Intelligence

Source conversation: https://claude.ai/chat/ac3ed89e-fac1-4f0f-944a-73a1399d1b45

This was the pivotal conversation that reframed the entire business. O.J. was describing her competitive landscape and mentioned that people who work with her say what she offers isn't common, and that when it came up that she's friends with all her former bosses and most former colleagues, people looked at her like she had two heads. The realization:

What you're selling is something closer to operational career intelligence. How to actually function inside an organization in a way that gets you promoted and gets people wanting to work with you.

The "friends with all my former bosses" thing isn't a personality quirk. It's the output of a very specific set of skills:

How you communicate across power dynamics
How you build trust with people who evaluate you
How you navigate organizational politics without being political
How you make yourself visible without self-promoting

These are the skills that separate engineers who are technically senior from engineers who actually get the title. Almost nobody in this space teaches that, and the people who try usually come from an HR or coaching background and don't have the credibility of someone who's done it twice as an IC.

The key reframe: The technical bar is table stakes. How you operate inside the org is what determines whether you clear it.

The term "professional operating skills" does heavy lifting because it immediately separates Learn with O.J. from both the technical interview prep crowd and the generic career coaching crowd. It frames what you do as skills-based rather than personality-based, which matters for engineers because they think in terms of skills they can acquire and not "just be more confident" or "network more."

Pair "friends with all my former bosses" with "That's not luck. It's a skillset." This reframes what could sound braggy into a teachable, aspirational insight.

The competitive landscape positioning:

Category	Players	What They Sell
Platform marketplaces	MentorCruise, Topmate, IGotAnOffer	Pedigree (ex-FAANG mentors, transactional sessions)
Content-to-coaching pipeline	Ana Pedra, Taro, NeetCode	Specialized technical knowledge (certs, system design, LeetCode)
Newsletter/brand-to-advisory	Gergely Orosz, Jordan Cutler, Luca Rossi	Thought leadership at scale (don't do 1:1)
Learn with O.J.	O.J.	Professional operating skills for engineers outside Big Tech

Learn with O.J. serves the engineers those platforms overlook: the majority who work at mid-size companies, healthcare orgs, fintechs, agencies, and startups without formal engineering ladders or promotion packets. The advice that works at Google doesn't translate to a 200-person fintech.

Three competitive differentiators:

Professional operating skills, not just technical skills
Built for engineers outside the Big Tech bubble
Relational, not transactional (ongoing mentorship, not one-off sessions)

Case Study 1: The Kubernetes Story (Conflict Navigation)

The worst three months of O.J.'s career turned into a decade of compounding trust. Asked to join an infra team to help build a managed Kubernetes solution where the dev team wanted AWS and the infra team wanted Docker EE. Zero compromise. Classic "throw it over the wall" culture. O.J. was seen as the evil dev planted to push AWS.

Instead of picking a side, she proposed demoing both solutions and evaluating which one actually fits. That one decision changed everything because it told the infra team she wasn't there to steamroll them.

AWS won on merit. But the real results showed up over years: the boss from that project hired her again years later (strongest LinkedIn recommendation she's received), Kirk (one of the infra engineers) recently became a mentoring client, Curtis (the CIO) sponsored a Women's Code and Coffee meetup at company HQ and drove forward a 20/20 program placing 30+ community college students into full-time jobs that's still running.

Use this as: The high-stakes, dramatic proof point. Conflict navigation, trust-building across organizational lines, compounding career results.

Case Study 2: The Amex Intern Story (Talent Development)

At American Express, 6 out of 6 interns who rotated through O.J.'s team chose to stay on her team permanently and cited her specifically as the reason. Her boss gave her the highest score that year because of it.

What she did was deceptively simple: treated interns like colleagues who needed more explicit clarity up front and casual check-ins (not hovering). Created a standing invitation to ask questions so junior people didn't feel weird reaching out to someone senior. The Zack story: she saw a match between a person and a ticket he was perfect for but didn't volunteer for, named it explicitly ("that one is perfect for you"), and removed the risk ("if you get swamped, I'll make time to help you"). He nailed it without needing help.

Three things in 30 seconds: saw a match the person couldn't see themselves, named it explicitly so he didn't have to self-advocate, and offered a safety net that made him say yes.

Use this as: The quiet, repeatable proof point. Creating conditions where people thrive. More relatable than the K8s story for LinkedIn because most engineers have been in a room where a junior person didn't volunteer for something they were perfect for.

The "Career That Compounds" Metaphor

V2 of the positioning copy introduced "career that compounds" as the central metaphor, replacing the ladder-climbing framing. The kind of career where former bosses hire you again, where the colleague who thought you were the enemy becomes a client years later, where the executive you impressed shows up to sponsor your community work a decade down the line. The promotion is often a side effect. The compounding career is the goal.

Full positioning copy (v1 and v2) available as separate documents generated from this conversation.

The Anti-Gatekeeping Philosophy

"Information wants to be free." Rooted in community college experience. Access to senior-level SWE and SRE tech knowledge shouldn't be gated. The long-term vision is Khan Academy for adult professionals in technology, free-to-access and open source, funded by personalized services.

3. TAGLINES & ONE-LINERS (The Big List)

Status: This is the raw brainstorm list. Needs the machete pass. Items marked ✓ have been validated externally.

Taglines

O.J. will give you the juice.
Freshly squeezed career advice.
Career growth, freshly squeezed.
The juice is worth the squeeze.
Squeeze more out of your career.
You already have the pulp. I just help you squeeze.
Not from concentrate. 100% real talk.
Part of a complete career breakfast.
Vitamin C: Career, Code, Confidence.

LinkedIn hooks

"Most engineers are sitting on $30k+ in unrealized salary. Let me give you the juice."
"Hi, I'm O.J. Yes, like the drink. And I'm here to help you squeeze more out of your engineering career."
"Why O.J.? Because every hiring manager who asked me that question remembered my name. That's the point."
✓ "Engineers keep asking me how I went from no callbacks to multiple offers. Short answer: branding. Long answer: book a session."

Product/service naming candidates

Fresh Squeeze (30-min resume review or quick session, low commitment entry point)
Extra Pulp (deep-dive career strategy session or multi-session package)
The Squeeze (method name: "I put your resume through The Squeeze")
From Concentrate (workshop or intensive)
The Juicery (resource hub or newsletter)
The Juice Box (content series or toolkit)
Pulp (raw, unfiltered career advice content)

4. PROOF POINTS & CLIENT STORIES

Story 1: Luisa (Web Dev Referral) — Trust Conversion

The arc: Friend-of-a-friend referral. Came in defensive, only wanted price information, asked O.J. to sign an aggressive NDA before sharing anything. By the end of the call: "I want to work with you no matter what. Tell me what I need to do."

The pivot moment: Luisa said "I don't know what to do if that happens" (if O.J. couldn't help). O.J. said: "I don't leave my clients wondering what to do next. We'll work together to make sure you're not stuck and at least have a path forward with or without me."

What it proves: People don't just buy a service, they buy trust. Trust is built by showing up and knowing your stuff. O.J.'s consistency across every client interaction (mentee, web dev client, training client) is the brand in action.

Current status: NDA revision pending. Last contact was two weeks ago (Feb 13). Follow-up needed: reply to last email and send a text.

Story 2: Lucie & Sara (Guiltless.ai) — B2B Training Deal

The arc: Lucie (founder of Guiltless.ai) approached O.J. at 1909. Pain point: can't ship fast enough, overseas engineers aren't delivering quality. Objected to O.J.'s hourly rate (equivalent to a month of one of her engineers). O.J.'s response: "You're not paying for an hour of my time. You're paying for an hour plus over 20 years of professional software experience plus all the extra unpaid time I spend working on projects to keep up with the latest technology."

Discovery call with CTO Sara closed the deal for AI-assisted development training for the team.

The introduction that landed: "I'm O.J., founder of Learn with O.J. and I'm a working engineer helping other engineers level up. My goal is to show others the way to build careers that compound while I help companies move fast without breaking things."

What it proves: The brand works for B2B too. "Working engineer helping other engineers" scales from 1:1 mentorship to team training. The rate objection reframe works.

Story 3: Kirk — From Adversary to Client (The Kubernetes Story Full Circle)

Kirk was one of the infra engineers on the Kubernetes project where O.J. was seen as the enemy. Years later, he became her mentoring client. Services delivered: layoff coaching, pair programming (PowerShell), comprehensive resume review using 8-stage methodology.

Customer interview results (AWL program): Kirk described his problem not as "stuck below senior level" but as being given a task by a senior technical worker and not understanding the full scope of what was actually being asked. A framing gap, not a knowledge gap. He tried everything first (Stack Overflow, Microsoft docs, AI chatbots, googling) and none of it worked because he was solving the wrong problem entirely.

The golden question: "She's not some consultant, she's your team member." He workshopped slogans unprompted because he felt that strongly about it. This is marketing copy written by a customer.

Trust signal: He said he knew O.J. wouldn't care about hurting his feelings, and he could come to her without risking the dynamic at work. The "safe third party" angle.

Pricing signal: Didn't blink at $200, said $100 would be too low. Suggested a free 15-minute intro call (mirroring the best professional he ever hired, his lawyer).

What it proves: The compounding career in action. The person who once saw you as the enemy is now paying you for help. That's the ultimate proof that professional operating skills work.

Story 4: The Amex Intern Story — Creating Conditions for People to Thrive

See full case study in Section 2 (The Core Offering Shift). 6 out of 6 interns chose O.J.'s team. Boss gave highest score. The Zack story is a 30-second masterclass in talent development.

What it proves: You don't have to do anything dramatic. Treating people like colleagues, creating standing invitations to ask questions, and seeing potential others can't see in themselves is a repeatable, teachable skill.

Story 5: Kay (1909 Fellow Founder) — Real-Time Troubleshooting

The arc: Kay, a fellow founder and former engineer (20+ years experience, hired 30 junior devs, runs a venture studio), was having DNS propagation issues with a Squarespace-hosted site. O.J. diagnosed the issue in real time: explained TTL expiration, debunked the "48 hours" CYA, walked him through using dig/nslookup against specific resolvers, and suggested managing DNS through a dedicated provider. Problem solved.

What it proves: "Building a business about helping engineers level up, and then immediately helping an engineer solve a problem in real time? That's the brand. Working engineer helping other engineers." This was used in the Week 1 #BuildInPublic post.

Story 6: AWL Workshop — Instant Credibility

The arc: During the orientation when founders had to describe their customer and problem, O.J. was so clear and concise that the presenter stopped and told the group to give snaps. O.J. said "yeah, I know. I lived it."

What it proves: The problem statement is dialed in. The lived experience is the differentiator.

Story 7: Ethan (Red River Web Design / Red River Automation) — Peer Discovery Conversation

The arc: Met at BEN Visitor's Day. Ethan runs a web development shop (redriverwebdesign.com) and an AI automation business (redriverautomation.com). Former banker turned self-taught developer (Python then JavaScript, 2019-2025 in Boston). He's the "web dev" member in the BEN group and O.J. would take the "software engineer" spot. After an initial phone chat, they did a structured discovery conversation that turned into a 1-hour deep dive covering business models, collaboration, shared interests in graph RAG and memory systems, AI tooling, documentation culture, anti-gatekeeping philosophy, and speculative fiction.

How he described what O.J. does (the golden question): "Two lines of business. One is business to professional where you are coaching engineers in specific problems, professional support, and larger infrastructure consulting on the other." He separated B2C and B2B unprompted, which means the messaging is landing with technical peers.

His collaboration model: Does NOT want an agency/markup model. Prefers to refer clients directly to specialists and collaborate independently, each paid by the client. He brought a cybersecurity specialist onto a project this way (education platform handling minor student data). This means O.J.'s $325/hr rate would be billed directly to clients, no middleman friction.

Pricing signal: His projects range $1K-$35K. He charges $100/hr dev, $150/hr consulting. Most projects land $2K-$6K. Wants to push toward more consulting for sub-$5K projects and take larger projects as a developer. His client budgets can support specialist rates.

The infrastructure gap he confirmed: He's a frontend engineer using Supabase as a backend crutch. His biggest project (multi-tenant education platform with social media features for student homework, COPPA-level security requirements) probably would have gone better with an infrastructure person from the start. That's exactly O.J.'s lane.

Trust-building process: Mirrors BEN structure. Meet several times, see examples of work, help with something small before something large. "Trust but verify." O.J. offered free AWS help for quick questions with a clear boundary: if it requires building something or pairing, that's paid. That's the "small thing" that builds toward paid collaboration.

The BEN referral question (recurring theme): Both Ethan and Lance surfaced the same question: how does O.J. communicate value to a room of solopreneurs and small businesses who aren't typical infrastructure clients? Ethan's suggestion: figure out what you can do for the people in that room specifically. The referral path is indirect: O.J. refers web/AI/automation work to Ethan, Ethan refers infrastructure and engineer coaching to O.J.

What he wants from the relationship: Regular nerding-out sessions after BEN meetings. He also mentioned Dan wants to start a lunch club for sharing what people are working on (no selling, just learning). Ethan explicitly said he wants O.J. to join the group.

Shared interests surfaced: Graph RAG, memory graphs (neo4j-style), multi-agent systems, vector databases for codebase documentation, anti-gatekeeping in tech education, speculative fiction (hopepunk specifically). O.J. mentioned a research paper about three memory architecture approaches (orchestrator-based, agent-initiated, and memory-driven routing) during the conversation and the overlap with her own projects. Ethan supplied the term "multi-hop reasoning" to describe the kind of graph traversal O.J. was trying to articulate (surfacing 2nd and 3rd degree connections and the patterns between them). He also mentioned a tool or paper he'd seen where someone was using Claude to auto-generate graphs and run Monte Carlo-style simulations at the graph level.

Additional signals:

He tested O.J.'s AI guide on the spot and committed to reading it that day and giving feedback. Warm lead for B2B content funnel and free product feedback from a technical peer.
He has a client (teacher building the education platform) who could be a mathbliss.com connection. O.J. asked for the intro and he was receptive.
He organically surfaced the idea to buy learningwithoj.com as a redirect. Domain acquisition action item.
"Truth over feelings" came up as a shared developer value, reinforcing what Kirk said about knowing O.J. wouldn't care about hurting his feelings. Directness as trust signal is now a pattern across three discovery conversations.
The "anti-gatekeeping" philosophy resonated with him. He bridged from non-tech to tech himself and understands the exclusion. He called it out explicitly: "their opinion in the meeting is just as valid as yours."

What it proves: O.J.'s positioning lands with technical peers, not just clients. The dual B2C/B2B framing is clear enough that someone who's only had a few conversations can articulate it back accurately. And the collaboration model (independent billing, direct referrals, trust-first) is how technical founders actually want to work together.

5. CURRENT LOGO & VISUAL IDENTITY

Current logo: Black laptop opening with orange gradient pages inside like a book. Stack Overflow vibe. Created when the business was focused primarily on the learning platform concept.

Assessment: May not align with current brand direction. The juice/O.J. angle, the "working engineer" positioning, and the dual B2C/B2B offering have evolved significantly since the logo was created. Worth revisiting as part of the website redesign.

Considerations for visual refresh:

The juice angle opens up a whole color palette (orange, citrus tones)
The current tech/book metaphor served the original "Khan Academy" vision but may be too narrow now
Whatever the visual identity becomes, it needs to work across: website, LinkedIn profile, LinkedIn company page, business cards, presentation decks, client-facing documents

6. LINKEDIN PRESENCE

Personal Profile

Bio/headline direction: "I have been a developer for over 2 decades and have leveled up to senior twice, first as a Senior SWE then as a Senior SRE. My passion is helping engineers grow through 1:1 mentor sessions, resume and code reviews, interview prep, and practical career guidance."

Comment Voice Guide

Comment patterns that work for you:

Lead with validation of the original post's point, then add a specific detail or experience that extends it
Keep to 2-4 sentences max
End with a question or observation that invites further conversation only when it feels natural, not every time
You don't do empty agreement and you don't do hot takes for the sake of engagement
Your comments should read like a colleague adding to a conversation, not a founder trying to be visible

The "outside Big Tech" angle: Your natural comment strategy is grounding Big Tech advice in how things actually play out at companies without formal engineering ladders. When creators like Jordan Cutler post about leveling up, your comment brings the perspective of the 200-person fintech or the healthcare org. That's the comment that makes engineers at those companies think "finally, someone who gets my situation."

What not to sound like in comments:

No "This!" or "Love this!" openers
No emoji-heavy reactions
No turning someone else's post into a pitch for your services
No "as someone who..." humble-brag framing
No lecturing or correcting the original poster unless they're genuinely wrong about something that matters
No generic motivational responses ("keep going!" "so inspiring!")

Your expertise zones for commenting (topics where your voice carries the most weight):

Career growth without formal ladders or promotion packets
DevOps/SRE culture and practices
Navigating org politics as an IC without being political
Mentorship and talent development (the Amex intern pattern)
The gap between doing senior work and getting the title
AI-assisted development workflows and tooling
Anti-gatekeeping in tech education
Resume and interview strategy for engineers outside Big Tech
Building trust across organizational lines (the Kubernetes pattern)

Content Strategy

Weekly themes:

Monday: #MentorMonday (mentorship, career advice, paying it forward)
Tuesday: #TechTuesday (hands-on tech, homelab, DevOps/SRE topics)
Wednesday: #BuildInPublic (AWL workshop recaps while program is running)
Thursday-Friday: Open (news, career insights, industry trends, lighter posts)

Target audience:

Primary: Experienced software and infrastructure engineers who haven't gotten the title yet
Secondary: Junior engineers looking to level up, senior/staff/principal engineers
Emerging: Founders and small companies needing engineering training/upskilling (B2B)
Referral channel: BEN (Business Expansion Network) members. Ethan (web dev/AI automation), Santiago (CIO, Kubernetes need), recruiters in the group who talk to engineers looking for jobs. O.J. holds the "software engineer" spot.

Style guide (things to avoid):

Bullet points unless explicitly needed
AI-sounding phrases like "You're not X. You're Y."
LinkedIn-template energy (emojis, numbered lists, "I did a thing" humble brags)
Overexplaining after sharing a file or resource
Em dashes
The word "mid-career" (use "experienced engineers who haven't gotten the title yet")

Company Page

Created primarily so the LinkedIn profile would look sharp with a logo. Needs actual content strategy now that the business has traction and a B2B angle.

7. SERVICE OFFERINGS

Current (Active)

Service	Target	Description
1:1 Mentor Sessions	Individual engineers	Career guidance, pair programming, code review
Resume Review (8-stage methodology)	Individual engineers	Feedback Letter + Premium Report
Interview Prep	Individual engineers	Mock interviews, technical prep
AI-Assisted Development Training	Companies/teams	Upskilling teams to leverage AI tools in their specific stack
Freelance SWE/SRE (selective)	Companies	Contract engineering work

In Development

Service	Target	Description
Tailoring Blueprint	Individual engineers	Job application optimization
Path to Prod	Companies/individuals	Transform vibecoded MVPs into production-ready apps
Free learning platform	Everyone	Khan Academy for adult professionals in technology (long-term vision)

Product Naming Candidates (Juice Theme)

Fresh Squeeze: Quick 30-min session, low commitment entry point
Extra Pulp: Deep-dive, multi-session package
The Squeeze: The resume review method
From Concentrate: Workshop or intensive

8. KEY QUOTES & SOUND BITES

These are things O.J. has said that landed well and should be reused in marketing:

"You're not paying for an hour of my time. You're paying for an hour plus over 20 years of professional software experience plus all the extra unpaid time I spend working on projects to keep up with the latest technology."
"I don't leave my clients wondering what to do next."
"Yeah, I know. I lived it." (on understanding the customer's pain)
"Working engineer helping other engineers." (the brand in one line)
"I'm O.J., founder of Learn with O.J. and I'm a working engineer helping other engineers level up. My goal is to show others the way to build careers that compound while I help companies move fast without breaking things."
"People ask me why I go by O.J. and the short answer is branding. The long answer: book a session."
"Two lines of business. Professional support on one side and larger infrastructure consulting on the other." (Ethan, peer discovery conversation, describing what O.J. does to a client)

9. ACTION ITEMS

Immediate

Follow up with Luisa (2 weeks since last contact, NDA revision pending). Reply to last email + send a text.
Collect Kirk and Mickey customer interview results for marketing copy (especially: "If you were telling another engineer about what I do, what would you say?")
Send Ethan follow-up message with memory graph resources, vector database/codebase documentation references, and the hopepunk book rec (Becky Chambers)
Ask Ethan for intro to his teacher client (education platform) for mathbliss.com research
Get Ethan's feedback on the AI guide PDF
Buy learningwithoj.com and set up redirect to learnwithoj.com
Complete BEN membership signup (check email from Lance or Bryan)

Website Redesign

Decide if current logo (black laptop/orange book pages) still fits the evolved brand
Incorporate the juice/O.J. theme into visual design
Add B2B positioning (team training, AI-assisted development) alongside B2C (individual mentorship)
Add proof points/testimonials as they come in from customer interviews
The introduction that closed the Lucie deal should be prominent on the site

Update personal profile headline/bio to reflect current positioning
Develop company page content strategy (not just a logo placeholder)
Continue weekly content cadence with established themes
Use customer interview quotes as social proof in posts

Brand Development

Do the machete pass on the tagline/one-liner list (keep only what gets laughs)
Test "Fresh Squeeze" and other product names with real people
Consider visual identity refresh aligned with juice theme
Document new proof points and client stories as they happen

10. DISCOVERY CONVERSATIONS — CROSS-INTERVIEW PATTERNS

Three discovery conversations completed as of March 2026. Patterns emerging:

How people describe what O.J. does (nobody says "mentor"):

Kirk: "She's not some consultant, she's your team member."
Mickey: "Thorough, deeply investigates, doesn't jump to conclusions."
Ethan: "Professional support on one side and larger infrastructure consulting on the other."

Directness as a trust signal (3 for 3):

Kirk: "I knew you didn't give a shit about hurting my feelings."
Mickey: Values full engagement at higher price points.
Ethan: "Truth over feelings." Called it a shared developer value.

Pricing signals (converging upward):

Kirk: $200 no flinch, $100 too low.
Mickey: Anchored at $225-250 for "real help."
Ethan: Charges $100/hr dev, $150/hr consulting himself. His clients' project budgets ($2K-$35K) can support specialist rates. Prefers direct billing, no markup.

Anti-gatekeeping resonance (2 for 3):

Mickey: Valued learning how to collaborate across different styles.
Ethan: Explicitly called out anti-gatekeeping. Bridged from non-tech to tech himself. Said "their opinion in the meeting is just as valid as yours."

The "safe third party" pattern:

Kirk: Could come to O.J. without risking work dynamics.
Ethan: Brought in a cybersecurity specialist the same way, as an independent expert the client works with directly.

11. KEY CONVERSATION LINKS & DOCUMENTS

Conversations:

Offering Shift / Operational Career Intelligence: https://claude.ai/chat/ac3ed89e-fac1-4f0f-944a-73a1399d1b45
AWL Workshop + Branding: https://claude.ai/chat/b95e19da-3bb1-4324-b9c9-cc227513c78c
Lucie/Guiltless.ai Training Deal: https://claude.ai/chat/676be388-7135-4928-a51d-174601e82d21
Luisa/Web Dev Client: https://claude.ai/chat/ed3cef8b-b2a2-4a82-a7cd-962d5460ea98
LinkedIn Style Guide + Content: https://claude.ai/chat/1ee076de-3e73-4364-a3a5-13f246bb2c38
First Customer Validation: https://claude.ai/chat/96be9448-b626-4722-b231-824bc9c04094
DevOps Pivot Story (Mentor Monday): https://claude.ai/chat/76e5aa5e-dc4d-44c4-9744-dc21207df6dc
Business Overview: https://claude.ai/chat/c990bfb4-9d96-4347-afa2-e644af8f031f

Documents generated from the offering shift conversation:

learn_with_oj_positioning_copy.md (v1: professional operating skills framing)
learn_with_oj_positioning_copy_v2.md (v2: "career that compounds" central metaphor, added case studies, improved outreach templates)
linkedin_post_kubernetes_story_v1.md (draft LinkedIn post for the K8s conflict navigation story)

Learn With Oj Branding Reference