Collab maxxing: turn open conversations into collabs

This is the log play twitter/collabMaxxing. Before anything else, call the log MCP tool getGuide({ useCase: "twitter/collabMaxxing" }): it returns this page and makes it the session's play, so every log tool's answer says which step you are on and a send with no play loaded is refused (rules 157, 158). Then follow the steps in order.

Draft every message from that person's own thread and matt's real replies (voice with no text, search), never from memory, and never send two that read alike (sameAsSent).

Network maxing gets people talking to the owner. Collab maxxing turns those conversations into something you can work on together. Everything the owner builds is open source and he earns nothing from it. So the collab is the deal: he builds their system with them and makes content about doing it, they get the outcome, and they back the work. Money is the last thing in the conversation, never the first. It comes as a small ask once they're keen, or a retainer the owner prices himself.

The owner runs it across everyone already talking to him, the new people from networkMaxing.md, the friends with open threads and the missed openings nobody answered. On X it works the same in the old DM inbox and X Chat, and on Discord it works through discordRead and discordSendLive.

How the owner asks for it: "position a collab first then be like just a few quid so i can make a video about it", "start network maxxing and collab maxxing and trying to see what hes doing get him to reveal it all", "follow up on <someone> and the other people, small commitment from deals, not just new people but already open convos", "respond with the collabmaxxing", "selling the outcome", "let him name it", "check in with <someone> whats good there he is keen but isnt liquid", "just be nice to them there the poor people", "ask <someone> if i could become a contributor", "look on my twitter for missed opportunities".

Run it from a fresh context

Say: "go on docs/useCases/twitter/collabMaxxing.md", and say who it's for this round (everyone open, the missed openings, one person). The agent reads this page and README.md, loads getGuide({ topic: "xSending" }) (and getGuide({ topic: "discord" }) for Discord), and runs the steps.

The steps

What to know

• The pitch, in the owner's words: he builds open source and earns nothing from it, so collab so he can make a few quid, they get the outcome and he makes content about it. Frame it as joining the crew: his systems find, warm and book people, and someone still has to be on the other end of the call.
• Sell the outcome, not the tool. Ask what they'd want in 6 months and how it should feel. "Let him name it" means let them say what it's worth before the owner sets a number. A price or retainer is always the owner's call. Once, a contact's retainer was held at the owner's own figure after it came out what that contact charges their own clients.
• Learn the model from people who run it. A contact who runs an agency once explained theirs: a big retainer up front, then a smaller retainer plus rev share. Some clients pay a small retainer plus rev share from day one, because the agency owns most of their sales process. Answer people who explain things like that, because it's how the owner prices his own collabs.
• Never run the script on a friend. A friend once worked out the chat was automated. What gave it away: a discovery-question ladder in 15 minutes, money asked before they raised it, every reply 40 to 90 s after their message and ending on a question, and a queued line landing over their question. With friends: one question at most, vary the timing and length, never send while their newer message is unanswered, and hand money talk to the owner.
• Skint is not a no. When someone says they can't pay, don't push for a figure. One contact was "keen but isnt liquid". The check-in said no rush, when the money's there it's there, still keen to build something, and they came back keen and offered to make content on it for their own market. Another said they were in survive mode, and got a kind message and nothing asked.
• Collabs go both ways. Asking to contribute to someone else's open source counts too. The owner once asked another open source maintainer to be a contributor, opening on the maintainer's own reply to his post.
• Missed openings are the cheapest wins. Someone who explained their model, said they're hiring, or said "lets do it", and never got an answer. Find them in step 1 before reaching for new people.
• Never ask the people the owner has ruled out for money (in the agent memory). Never send the same message twice: check the thread before a resend. Memes go as media, never as a raw link.
• Every send counts against the account's writes for the day, each line one write. Space people out and never act in quick succession. Any refusal stops the run (rule 94).