How Does IsMyGirl Work? The Agency-Run Creator Model

IsMyGirl is associated with the managed-creator model, where an operator signs creators, helps run their accounts and keeps a defined share of what they earn. The fan-facing product looks like any creator subscription site. The difference is behind the screen: a team shares the work of posting, messaging, scheduling and payouts, and the software has to say who can do what.

This guide explains that model in general terms: the roles, the inbox workflow, the disclosure question, the way money is divided and the contract points that decide whether creators stay. It does not describe any named company's current terms, which change; read those directly before you rely on them. If you want to run your own roster rather than join someone else's, an IsMyGirl clone for agencies gives you the platform for that model under your brand.

What the managed model is

On a standard creator site, the creator owns the account and does the work. In a managed model the creator still owns the relationship with fans in a legal and commercial sense, but an operator provides services around it: account setup, content scheduling, pricing, fan messaging, promotion, reporting and often payouts. In return the operator takes an agreed share.

The model exists because some creators prefer to produce content and leave the repetitive work, such as answering a large inbox, to others. It also exists because some operators run it as a business: recruiting, coaching and staffing across many creators. Both points matter for the software, which is why a white-label IsMyGirl clone script is built around roles and a split ledger. A tool designed for one person cannot safely be shared by five without sharing a password, and shared passwords are the first thing that goes wrong.

It helps to compare it with two neighbors. A talent network in the live-streaming world works similarly, with the platform approving agencies and agencies recruiting hosts; how live streaming agencies work covers that version. A pure subscription site such as the one described in how OnlyFans works leaves the services to the creator or to any helper the creator hires outside the platform.

Roles and who does what

Five parties appear in nearly every managed setup. The table lists them with the access each needs. The principle is least privilege: nobody should see more than the job requires.

Separating these duties is cheap on day one and painful after a payout mistake. A new hire on the inbox who never sees the payout ledger cannot leak it, and an auditor can see exactly who held which permission at any time. The IsMyGirl clone features page lists the access scopes the platform ships with.

How a managed creator is onboarded

A sound onboarding record is the foundation of everything later. In order:

1. Recruit and agree terms. The agency and the creator settle the split, expenses, term and exit rules in writing.
2. Verify identity and age. The creator submits documents and a selfie check, and a reviewer approves the account. See age and identity verification options for what to collect.
3. Record consent. Consent to the contract, to staff access and to any use of likeness is stored against the account with a timestamp.
4. Set the split and permissions. The platform share, manager share and creator share are configured, and staff are assigned to the account.
5. Configure payouts. Payout method, minimum balance, schedule and approver are set before any money arrives.
6. Publish. Only after the steps above does the creator go live to fans.

Run a small pilot first. Five creators you know well will teach you more about workload, template quality and payout timing than fifty you barely know. The sibling guide OnlyFans agency software covers the back-office tools for this stage in detail.

The inbox and staff workflow

Messaging is where the managed model earns its margin. Fans who message get replies, replies lead to tips and paid unlocks, and a fast reply is a reason to renew. A single creator cannot answer a large inbox around the clock, so staff share it.

How the inbox is shared

The safe pattern is delegated access: each staff member logs in with their own credentials and acts on behalf of an assigned creator. The alternative, sharing the creator's password, makes it impossible to say who did what, breaks two-factor protection and is often against the host platform's terms. Separate logins are safer and make later disputes easier to resolve.

Inside the inbox, staff typically use:

• Templates for greetings, answers to common questions and welcome messages, written in the creator's voice and approved by the creator.
• Saved lists that group fans by behavior, such as recent buyers, expiring subscribers or high spenders.
• Scheduled sends for campaigns, reminders about a locked set, or a welcome sequence for new subscribers.
• Notes and tags so the next operator on shift knows context.
• Escalation to the creator for anything that needs the creator personally, such as a live session or a custom request.

Logs and quality control

Because several people act for one creator, an audit trail matters. Record who sent what, who changed a price and who approved a payout. Review a sample of conversations each week against a written standard: accurate claims, no pressure tactics, no promises the creator cannot keep, and correct handling of refund requests. Quality problems in the inbox become refund requests and disputes later; the chargeback guide at how to reduce chargebacks on a membership platform covers that link in detail.

Disclosure: what fans are told

The hardest policy question in this model is whether and how to tell fans that someone other than the creator may be writing to them. There is no universal rule, and a few things shape the answer.

A workable approach is a plain statement in the profile or terms that the creator's team may assist with messages, plus a hard rule that real-time sessions are the creator's own. Whatever you choose, apply it the same way to every creator and write it into the creator contract. This is not legal advice; ask counsel in each market where you sell.

How money moves

In a managed setup each payment must be divided between at least three parties, and every division must be traceable. A payments provider that supports multi-party platforms describes the general shape: a platform can take payments itself and then move parts to others, or have the seller take payments directly with the platform collecting a fee. Stripe's Connect charge types page sets out those options and notes who bears refunds, chargebacks and processing fees under each. Treat it as a description of how the money flow can be structured; whether a given provider accepts your content category is a separate question covered in payment processors for subscription sites.

Here is a labelled example with invented numbers. A fan pays 100 for a month of subscription plus a locked set. The payment processor takes a fee, the platform keeps a share, the agency takes a share and the creator receives the rest.

If you operate the platform yourself, the platform share and the agency share belong to the same business, which changes your margin and the decision on how to set the creator's number. Creator revenue split models for agencies works through the structures, and the IsMyGirl clone business model page shows where a managed operator earns.

Payout timing and approval

Creators request withdrawals against their balance, a finance approver checks the balance, verification status and any open reports, and then releases or holds the payment. Settings that matter are the payout interval, the minimum balance and the holding period. Stripe's payout schedule documentation shows the usual options: manual payouts, daily with a delay, weekly on set days, or monthly on set dates. A short holding period gives you time to see refunds and disputes before money leaves; creator payout schedules discusses how to choose one.

Contracts, ownership and exit

Most creator disputes with agencies are about terms, not software. A contract should cover the points below, and each side should take independent legal advice.

• Services: what the agency does and what the creator must supply.
• Split and costs: percentage by revenue type, what is deducted first, and who pays for tools, ads and promotions.
• Reporting: how often statements are issued and what they show.
• Payment dates: when each period closes and when money arrives.
• Content and likeness: who owns uploads, and what the agency may reuse.
• Account and fan data: who holds logins and customer lists, and what happens to them on exit.
• Term and notice: how long it runs and how either side ends it.
• Disputes: how disagreements and chargebacks are handled, and whether clawbacks apply.

The employment status of everyone involved is its own question. In the United States, the IRS describes three groups of evidence for telling a contractor from an employee: behavioral control, financial control and the relationship of the parties, and it stresses that no single factor decides. Its contractor or employee guidance is a good starting point for a US operator; other countries use different tests. A creator whose agency dictates hours, scripts and methods may look less like an independent contractor than the contract says.

For creators weighing an agency, the risk is concentration of control. An agency that holds the passwords, the fan list and the payout account holds the creator's business. For operators, the matching risk is a reputation for exactly that. Clear exit terms, creator-visible statements and separate logins are both fair and good business. See creator terms, takedowns and content ownership for the content side.

A typical week in the managed model

Seeing the rhythm makes the roles concrete. The schedule below is an invented example for a small roster, not a prescription.

The pattern shows why the software has to be built around handovers. Work passes between people several times a day, and each handover is a place for a mistake, a missed promise or a leak of information. Notes, assignments and logs are the glue.

Where the model goes wrong

• Overpromising. Messages that promise things the creator never agreed to lead to refund requests and complaints.
• Opaque money. Creators who cannot see how their number was reached assume the worst, and eventually leave.
• Shared credentials. One leaked password exposes every conversation and, on a host platform, can put the whole account at risk.
• Burnout. Chat operators on long shifts write worse messages; staff hours need modeling before you promise a split.
• Weak records. Without consent and verification logs, a dispute with a creator, a fan or a processor becomes one person's word against another's.

What an agency platform needs

Whether you rent access to someone else's platform or run your own, the requirements are the same. The table maps each to what to look for.

The last row is where renting and owning differ most. A hosted service usually lacks the split and staff tooling a managed model needs and holds the fan relationship on its own terms. A platform built for the model, with the source code in your hands, lets you change split logic, add a verification vendor or adjust regional rules yourself. We deliver the apps, admin panel and source code under your brand, and if your agreement needs a structure the standard screens do not show, we set it up for your build and confirm the scope with you at kickoff on our contact page. Compliance, contracts and staffing remain yours.

Questions to ask before you join or build

1. Who owns the account, the fan list and the data, and what happens to them on exit?
2. Is every split and deduction visible to the creator in each statement?
3. Do staff use separate logins with scoped access?
4. What are fans told about who is writing to them, and does the host platform allow it?
5. How are refunds and disputes allocated between agency and creator?
6. Who approves payouts, and how long do they take?
7. What is the notice period, and are ongoing subscriptions handled fairly on exit?
8. What are the identity, age and moderation duties, and who performs them?

If you can answer those eight in writing, you understand the model well enough to run it or to judge an offer. To build the platform side, start with the managed roster features and the how it works page, then price it with the published figure on our pricing page.