audience profiles
Two audiences. Different pains. Different reasons they follow. Use this to stay calibrated on who you're actually writing for — and to pressure-test anything before it goes out.
For the full expanded profiles (day in the life, before/after, prior experiences, decision dynamics),
read: notes-processing/audience-profile.md
For the Farza research that shapes the Orbit Labs relationship model, read: notes-processing/farza-analysis.md
profile 1: the chalant society
one sentence: people who want more from their social lives, know it, and still can't close the gap.
the real pain: not social isolation — social shallowness. they have people around them. the conversations stay surface level. the circle isn't growing. friday nights pass and they feel like a background character. they know what to do. they don't do it. they've consumed enough self-help to feel guilty about that too.
what they need from this content:
- proof that someone else actually does the uncomfortable thing, consistently, not just once in a video
- language for feelings they have but couldn't name
- a community where wanting more connection doesn't feel cringe or needy
- a specific small rep to try this week — not more inspiration to consume
what they fear:
- this is another thing they'll follow and not act on
- the community will be performative ("everyone pretending to grow")
- rami has it figured out and is teaching from the other side — they need him still in it
why they stay: he does the thing. publicly. repeatedly. with the same awkwardness they feel.
why they leave:
- it starts feeling like a brand, not a person
- vulnerability becomes a formula
- too many CTAs
- they feel like an audience, not part of something
the chalant test — ask before posting:
does this make someone feel seen, or does it make them feel instructed?
could rami have posted this six months ago, before he figured it out? (if no: he's reporting from the other side, which loses the people still in it)
does this give them one small thing to try, or just a reason to feel like they should?
profile 2: orbit labs
one sentence: people with the same problem rami had — who trust what he built because it's obvious he lived it, with no agenda behind the share.
the north star: farza majeed (buildspace). the relationship rami wants with this audience mirrors what farza built: fans who follow the person, not the product. who show up for whatever he makes next because they trust his judgment. who feel like co-conspirators, not customers. that loyalty is built by being radically honest at the problem stage — before success makes it safe to share. farza's community formed when buildspace had 200 discord members, not 125,000. rami is in that window now.
two overlapping groups:
group 1 — problem-havers: they have the same problem rami had when he built the thing. not necessarily technical. they find him because the way he describes the problem is unusually accurate. they trust his recommendation because there's no agenda — he built it for himself and is sharing because he has to, not because he's running a launch.
group 2 — inspired builders: they watch rami go from "this bothers me" to "i made a thing" and think: i could do that for my problem. he doesn't need to teach them to code. he shows them it's possible without a pitch deck, an audience, or a perfect idea.
what they need from this content:
- the founding story told messy — the problem, the itch, what didn't work first
- to see rami still in the problem, not reporting from the other side of it
- small ships, constantly — proof that the pattern holds across projects, not just one
- the absence of an agenda: sharing because he has to, not to launch something
what they fear:
- this is "build in public" content performing authenticity as a brand strategy
- the honest origin story is really just a launch funnel in disguise
- rami solves out and starts giving advice from a place they can't relate to
why they stay: every new build traces back to a real, specific problem he personally had. no spin.
why they leave:
- sounds like a product launch instead of a personal share
- stops showing the problem and just shows the solution
- pivots to general tech content / "lessons from shipping"
the orbit labs test — ask before posting:
can you trace this directly to a problem rami personally had? if not, it's not orbit labs content.
does this feel like a friend showing you something they found, or a brand showing you something they made?
farza rule: would farza have shared this when buildspace had 200 members and no funding? (if it requires success to make sense, it's too late in the arc)
is rami still in it, or has he landed? the content that creates believers arrives before the outcome is certain.
cross-audience heuristics
before writing anything:
- which audience is this for? chalant society, orbit labs, or both?
- does it lead with the real problem, or jump to the solution?
- is there an agenda visible anywhere? (a CTA, a product push, a "lesson learned" wrapper that sanitizes the messy part)
- is rami still in it, or has he figured it out? (figured-out content loses both audiences)
before pricing anything:
- chalant society: they'll pay for access to a real community and real reps, not for information they can get elsewhere. the price justification is the belonging and the accountability, not the content.
- orbit labs: they don't need to pay. the trust is worth more than the revenue. if there's a paid tier, it has to give them something only rami can give — direct access, early builds, the raw version.
before building a product feature:
- chalant society: does this lower the cringe threshold? does it make the uncomfortable thing feel less like a solo act? features that work: shared challenges, earned access to live events, the ability to do the thing with other people.
- orbit labs: does this solve a problem rami has right now? if he wouldn't use it daily, don't build it. the product is only trustworthy if it's clearly built for him first.
before naming anything:
- chalant society: does the name make the thing feel safe to try? "rejection therapy" sounds scary. "the chalant society" sounds like belonging. naming should lower the activation energy.
- orbit labs: names should describe what the thing does for you emotionally, not technically. "twilight" not "sleep tracker." "orbit" not "university friend matching app."
the shared pattern across both audiences
both audiences need the same thing from rami: proof that he is still in it.
not the polished version. not the lesson-learned wrapper. the actual problem, the actual attempt, the actual outcome — uncertain or otherwise.
the moment the content sounds like someone who figured it out, both audiences lose the thing that made them follow in the first place.
farza closed buildspace at peak success rather than fake the passion. that decision cemented his reputation more than any growth metric. the question rami carries: what would i do if i had to choose between scaling something i no longer believed in and starting over?
having a clear answer to that shapes every decision that leads to it.