Communities and partnerships: reach people through people they already trust

You find a Slack group full of people who might buy your product, and the temptation is immediate: introduce yourself, explain what you built and add a link while everyone is looking. In most communities, that is the fastest way to make your first contribution your last.

The group existed before you arrived. Its members are there to exchange advice, complain about their work and help each other. If you join those conversations, you can learn how customers describe the problem and meet people who want more help. If you arrive with a sales post, you have confused access with permission.

Partnerships work by the same rule. A newsletter writer, agency or complementary product has spent time building a relationship with its audience. They may share that access when the collaboration gives those people something they want. “We should partner” gives them no reason to do so.

Choose the route you are ready for

Communities and partnerships cover several very different amounts of work. Your first decision is whether you need to join something that already exists, test one collaboration or operate a program of your own.

If you are early, you will probably belong in one of the first two rows. An owned communityA community the founder or company operates. It requires an independent reason for members to return, plus moderation and ongoing support. creates another job, complete with moderationThe work of applying community rules, handling harmful behavior and deciding what members may post or share., member support and the occasional argument about something nobody had considered controversial until 11:43pm.

Find two or three rooms worth joining

A communityA group whose members gather around a shared job, interest, identity or problem. In this chapter, “community” usually means an existing Slack group, Discord server, forum or professional group. deserves your time when the people you want to understand are present and discussing a problem connected to your product. Size gives very little help here. A focused group of 400 operations leads may tell you far more than a general startup server with 40,000 members and nine channels devoted to self-promotion.

Four checks are enough for a first pass:

Public pages and searchable discussions can support this research. Private conversations and member details stay private. Where the rules are vague, the moderator's answer outranks a growth tactic from the internet.

Give it a month

A month is long enough to see whether you can become a recognizable contributor. It doesn't guarantee leads; a weekly sales target would encourage exactly the behavior that gets you muted.

Tincture uses 90/10 as a rough check: most activity should help someone without requiring them to buy. It isn't a law of community mathematics. If you have to debate whether a post falls inside the promotional 10%, the moderator may already have made the decision for you.

Discord's current Community Guidelines prohibit spam and unsolicited bulk messages. Its ethical community growth guidance says joining a server doesn't give advertisers consent to mass-DM its members. A private reply makes sense after a request for more information or a relevant public exchange. Scraping the member list and sending 200 “personal” introductions is cold outreach with an additional breach of trust.

Find a partner with the same customer

A partnership becomes plausible when both businesses help the same person and their offers solve adjacent problems. The exact relationship can vary.

Audience size comes after fit. A newsletter read by 2,000 suitable people may beat a general publication with 100,000 subscribers, although you won't know until readers register, ask, try or buy.

Your first list needs ten plausible partners. Three deserve deeper research; one gets a drafted proposal. The obvious favorite may still turn out to be a poor fit.

Make one specific proposal

The opening request should explain the customer benefit, the proposed contribution and the small amount of work required from the partner. “I think our audiences overlap” leaves the recipient to invent the collaboration for you.

For a bookkeeping product used by creative agencies, a proposal to an agency operations newsletter might read:

Your readers have asked several questions about chasing project costs across spreadsheets. I can run a 30-minute teardown of three anonymized workflows and give attendees the worksheet afterwards. I would prepare and deliver it; you would choose the submitted examples and invite your readers. If it goes well, we can decide whether a written guide is worth doing next.

The proposal contains one event and one review. Nobody has promised a strategic alliance before finding out whether twelve people attend.

Write down the pilot before it starts

A lightweight collaboration can still produce messy assumptions. One page is enough to record them.

Commission depends on the product. A $39 self-serve tool and a $20,000 service have different margins, sales work and refund risk. The terms need to work for both businesses.

In the United States, the FTC's endorsement guidance requires a material connectionThe FTC's term for a relationship that could affect how an audience judges an endorsement. Payment, free products, employment and family relationships can qualify. to be disclosed clearly. Payment, free products and affiliateA person or business paid when somebody they refer completes an agreed action, usually a purchase. The agreement needs to say what earns payment and how the referral is tracked. income can all create that connection. Other countries apply their own rules, and the platform or community may be stricter.

Measure the two routes differently

A community can teach you something before it sends a customer. A partner pilotA limited collaboration used to test whether two businesses work well together and whether the partner introduces suitable customers. has a clearer commercial job, so it needs a route from the partner to a customer action.

Record the source at first contact so you aren't relying on memory three months later. The 30-day review checks delivery and early response. The 90-day review asks whether the people introduced by the partner paid and stayed.

Large B2B partnership surveys study companies earning tens of millions of dollars a year, so they don't give you a sensible pass mark. Five introductions from a small agency could support your product more than 5,000 low-intent visits; the actions after the introduction decide whether the route deserves another test.

Leave your own community until people need one

An owned community is ready when members have a recurring reason to help one another. You also need time to moderate it and a plan for harmful or private discussions. A year is a sensible minimum horizon because community value grows through repeated interaction.

If every conversation depends on you supplying another post, you have created a demanding content channel with a login screen. Existing communities will usually give you the learning and relationships sooner.

A formal affiliate or referral program belongs later too. Manual referrals should first show that partners introduce the right customers, those customers pay, and they remain customers at a similar rate to people from other sources. Software and commission tiers do very little for a route that hasn't produced those actions by hand.

A community and partner test

In this example, you sell Ledgerly, a fictional cash-flow tool for small creative agencies. You choose one agency-operations Slack group and a private community for studio owners. The general startup groups are larger, but agency owners rarely discuss cash-flow operations there.

During the first month, you answer questions about project deposits and late supplier invoices. You share one moderator-approved worksheet and record the language members use for the weekly cash problem. Two people ask to compare their process privately; one agrees to a product interview.

Your partner list contains ten accountants, agency coaches, operations newsletters and project-management consultants. A newsletter with 2,400 agency readers becomes the first priority because its archive shows repeated questions about project costs. You draft the workflow teardown proposal above and set a 30-day delivery review followed by a 90-day customer review.

If you sell to consumers, you might use the same method with a focused parenting group and a pediatric sleep consultant, provided the community rules allow commercial members and your health claims stay within your evidence. The audience and safeguards change; the test stays small.

Prepare your community and partnership test record

Use the community and partnership test record with your customer definition, positioning and any communities or partners you have already considered.

I'm preparing a community and partnership test. Use my attached record,
customer definition, positioning and supplied research.

Don't join a community, publish, message anybody, contact a partner, agree
terms or invent private information.

1. Assess the communities I've supplied. Check whether my intended customer is
   active, relevant problems recur, I can contribute from experience and the
   rules permit my participation. Mark anything that can't be verified.
2. Recommend no more than three communities for a 30-day test. Record the
   rules, recurring questions and one contribution I could prepare for each.
3. Draft those contributions in my voice. Don't add a product link unless the
   community rules and context clearly support one.
4. Research the ten supplied partner candidates using public information.
   Compare customer overlap, what I can contribute, what the partner receives,
   the work required and any access or reputation risk.
5. Prioritize three candidates and explain the choice using observed facts.
6. Draft one small pilot proposal for the strongest fit. Give it one customer
   benefit, a clear division of work and a review point.
7. Prepare a one-page pilot sheet covering contribution, audience, customer
   route, rights, disclosure, money, attribution, review and exit.
8. Create blank 30- and 90-day review tables. Keep community learning separate
   from partner-sourced trials, inquiries, customers and retention.

Return standard Markdown in my first person. Separate supplied facts, public
research, assumptions and unknowns. Stop with the prepared record for my review.

Once the three community profiles and contribution drafts are prepared, that side is ready for review. The partner side is ready when you have researched ten candidates and drafted one proposal. The review tables stay blank until there is something to record. You still decide whether to enter the room or send the email.