Skip to content

Unofficial parody. The software is real. Unofficial parody of infloww.com. Not affiliated with Infloww. The software is real; the jokes are ours.

Inflowwww
Menu

All case studies

Fictional case studyExample Talent Co.

How Example Talent Co. onboards a new creator in one afternoon, with a checklist

14 creators, one checklist, and a software line item that rounds to zero because it is zero.

Fictional, and labelled so. Real users have not written in yet. Example Talent Co. does not exist, and neither do the people quoted. The feature names, routes and arithmetic are real, and the practice in the middle works. It parodies the case-study format on infloww.com/case-studies. Inflowwww is not affiliated with Infloww.

Per creator per month, times 14 creators, times 12 months
$0
Increase in software fees after onboarding creator number 14
0%
Steps on the onboarding checklist, all of them below
12
Demo calls attended before the first install
0

Example Talent Co. onboards a new creator in one afternoon because the whole process is a written, numbered checklist that anyone on the team can run. The checklist is below. Copy it. It works with Inflowwww, with another CRM, or with a shared document.

About

Example Talent Co. is a fictional agency with 14 creators, two managers and nine chatters. It runs its creators' OnlyFans accounts from one Inflowwww install on a rented server. The owner ran the install from the README one evening and has not been asked to sign anything since.

Challenge

New creators were onboarded by whichever manager was free. Each manager had a different order of steps in their head. Things went missing: a proxy not assigned, a chatter not told about a creator's limits, a welcome message left on the old default. Nobody was careless. The process just lived in two heads.

Solution

The managers wrote the process down once, as a numbered list, and agreed that a creator is not "live" until every box is ticked. The list lives in a shared document. Each new creator gets a copy with their name on it.

The 12 steps:

  1. Agreement on file. The signed management agreement, the split and the start date are saved before any login happens, along with the creator's written OK to run the tool on their account after reading the README's disclaimer: using it on a live OnlyFans account may violate OnlyFans' Terms of Service, and the risk sits with the creator's account.
  2. Identity and age checks. The platform's own verification is done by the creator, on the platform. The agency keeps a note that it is complete.
  3. Boundaries in writing. The creator lists what they will and will not do, sell or discuss. This list goes to every chatter on their account.
  4. Voice notes. Three to five lines on how the creator writes: greetings, words they use, words they never use.
  5. Session capture. The creator loads the Chrome extension from loginExtensionMulti/, logs in on onlyfans.com, clicks Copy curl and sends the text to the owner, who pastes it on the Creators page. The desktop app's own capture button does not work against this relay today.
  6. Add the account. It appears in Creators > Manage creators (/creators).
  7. Assign a proxy. One proxy per creator, set in Creators > Custom proxy (/creators/proxy).
  8. Assign the team. Chatters are added in Employees > Manage employees (/employees). A chatter-only session does not see the owner pages, such as Creators and Vault Pro.
  9. Scripts. The creator's approved openers and replies go into Growth > Scripts (/growth/scripts), checked against the boundaries list.
  10. Vault check. The manager reviews Growth > Vault Pro (/growth/vault-pro) with the creator and confirms what may be sent.
  11. First-week schedule. Posts and stories are planned in My Automations > Auto Post (/growth/auto-post) and Auto Story (/growth/auto-story), or posted by hand.
  12. Day-7 review. The manager and the creator spend 20 minutes on what felt right and what did not, and the boundaries list is updated.

Strategy

The rule is simple: the checklist is the source of truth, not the manager's memory. If a step turns out to be wrong, the team fixes the list, not just the one creator. Steps 3, 4 and 12 are the ones that matter most, and they are the ones that never needed software.

Operations

A manager runs the checklist with the creator on a call. The capture and the account setup take minutes. The boundaries and the voice notes take most of the afternoon, and that is the point. Chatters read the boundaries list before their first shift on a new account. The owner signs off on step 1 only.

There is no step for choosing a pricing tier.

Results

  • Every creator onboarded since the switch has a completed checklist on file.
  • Chatters start on a new account knowing its limits on day one.
  • The checklist has been edited four times. Each edit came from a day-7 review.

We make no claim about revenue. A checklist does not sell anything. It makes sure nothing important gets skipped while the people do the selling.

“We used to onboard from memory. Now we onboard from a list, and the list does not take holidays.”

Priya, operations lead, Example Talent Co. (fictional)

Copy the practice above. It works with any tool, including a spreadsheet.

Get started with Inflowwww today

Deploying it yourself means installing it once on a server you rent; after that, everyone works in a browser.

After the one-time setup (docker network create n8n_default, the state files and an .env), this is the install. Docker Engine 25+ with Compose 2.20+. 

docker compose up -d --build

Before chatters reach it from outside, read the security notes: today it belongs on a private network or a VPN, not on the open internet.

Using it on a live OnlyFans account may violate OnlyFans' Terms of Service; the risk sits with the creator's account. Read the disclaimer first.

Get Inflowwww on GitHub Read the Quick start