For agenciesBy roster size

What breaks next, and roughly when.

Four things go wrong as an agency grows, and they go wrong in a fairly predictable order. None of them is a software problem until the moment it is: each one starts as a habit that works perfectly well and ends as an argument nobody can settle.

This is the order they arrive in, the one thing to put in place before each one does, and what the plan at that size covers. The prices live on the pricing page. This is the operational half of the same question.

Book a demoSee the plans

The four things that break, in order.

Roster size is the clock rather than the cause. What actually changes at each step is how many people hold a piece of the record, and how far the copy in somebody’s head can drift from the one in the system before anybody notices.

1–10

Your first staff, and your first payroll that is not your own.Starter, $349

Somebody who is not you gets paid out of a document you maintain yourself.When it was your own account the record was your memory, and that was fine. The moment another person works a shift and gets paid for it, the person keeping the record and the person being paid from it are two people with different recollections of the same Tuesday. Almost every agency arrives here carrying the same three artefacts: a shared creator password, a rota in a group chat, and a spreadsheet assembled at month end out of a dashboard that never quite matched the Statements page. Each one works right up until the first argument, and then all three fail at once.The first thing to set upGive every chatter their own login, this week rather than eventually. The shared creator password stops existing, and what each person can see is scoped to the creators they are assigned. Everything else on this page is easier afterwards and most of it is impossible before.
10–25

A second layer of management, and chargebacks that have become a rate.Growth, $849

Somebody manages on your behalf, and a second version of the truth appears.One team lead is enough to change the shape of the problem. Coverage stops being something you check and becomes something you are told about. Performance arrives as a summary rather than as a shift. And when a chatter disagrees with their pay the conversation now has three people in it, two of whom are recalling the same month differently. Volume changes the other half: at this size chargebacks stop being events and start being a rate, which means that if reversals surface after the pay run rather than before it, you are systematically paying commission on money you did not keep.The first thing to set upMove reversal detection ahead of the pay run. A chargeback gets tied to the fan across every creator they touched and surfaces before the period closes, which is the difference between an adjustment and a clawback conversation.
25–75

Month end as an assembly job, and your brand as part of the pitch.Pro $1,699, Agency $2,999

Reporting becomes somebody’s week, and access quietly sprawls.Two things go at once. Month end turns into an assembly exercise that occupies somebody senior for days, because the roll-up and the detail come from different places and have to be reconciled by hand before anyone can act on either. And access spreads: people who left still have logins, people who stayed have more reach than their job needs, and nobody can say precisely who did what to which account. The second change is external. A creator considering a move, or a partner considering a deal, now judges you partly on what your operation looks like from the inside.The first thing to set upOne ledger, roll-up down to the single sale, with seats audited by name. Going from a roster total to the shift that produced it should not mean switching tools or switching definitions, and revoking somebody should be one action that leaves their audit trail with you.
75+

The platform questions are settled. The operational ones are not.Enterprise, custom

The questions stop being about the software.At this size you have seen a record layer work on a smaller roster or you would not be having the conversation. What is left is operational: how a migration of that many accounts is sequenced without a reporting gap, who is accountable when something stalls at three in the morning, what happens to your data if either of us walks away, and what is actually contractual rather than merely intended. Those are not questions a plan tier answers honestly, so they get answered in writing instead, per agreement, and the answers are the deliverable.The first thing to set upAgree the migration sequence and its rollback point before anything is connected. The honest shape is a parallel period where both systems run and you compare them, and that period is measured in weeks rather than days.

The bands are the published plans, which are set by roster size and never by what your creators earn. The full table, including the per-creator figure at a full roster, is on the pricing page.

The order to do it in

Five steps, and the order matters more than the speed. Two and three are what decide whether four tells you anything.

Step oneConnect the accountsEarnings reconcile against each creator’s own Statements page — the page OnlyFans actually pays from — so your baseline is the number that corresponds to money arriving rather than an estimate from the activity feed.
Step twoGive every chatter their own loginThe one to do first. Their actions are recorded under their own name rather than the account’s, which is the whole basis of everything below it. If the shared password survives this step, nothing after it is evidence.
Step threePut the rota in, even a loose oneIt does not have to be precise to be useful. Once shifts exist, revenue lands on them, and credit stops being a matter of who remembers what.
Step fourRun one period in parallelKeep the spreadsheet you already maintain and compare the two line by line before you rely on either. Where they disagree, the Statements page settles it, and you find out which of your existing numbers were wrong.
Step fiveLock the periodThe first month that cannot be quietly edited afterwards is also, reliably, the first month nobody argues about. Every change made after the lock is appended to an audit trail rather than overwriting what was there.

Three things are metered. Nothing else is.

This matters more as you grow than the headline price does, because it decides whether hiring costs you anything. It does not.

Counted against your plan
  • Connected creator accountsThe number on your roster, which is what sets the band in the first place.
  • Live session hoursScales with the tier.
  • Assisted draftsScales with the tier.
Never counted
  • Team seatsChatters, team leads and creator logins are unlimited on every agency plan. Adding a person never changes the bill.
  • Data syncsIncluding the daily pull, which does not stop even when an allowance does.
  • ExportsThe payroll file and the raw record, as often as you want them, including on the way out.

A limit behaves the same way at every size: a warning at eighty per cent of an allowance, a clear stop at a hundred with the upgrade on the same screen, and live sessions already running are allowed to finish — only new ones are refused. Your tier’s exact allowance numbers are confirmed in writing before you pay, so the bill cannot surprise you in either direction.

Past seventy-five, what goes in writing.

A plan tier cannot answer these honestly, so it does not try. They are agreed per contract, and the agreement is the thing you are actually buying at this size.

Uptime and incident commitments
Data export and deletion on exit
Where your data is processed
The migration sequence, and its rollback point
Who is on the other end of an escalation
White label on your own subdomain, with the API wired into what you already run

What we will not do is agree to a term we cannot currently meet in order to close an agreement. That is the same standard applied to every number on this site, and at this size it is the one thing worth checking us on. We are also not going to show you a logo wall or a customer count: FanOptik is early, and a roster this size deserves to know that before signing rather than after. What is on offer instead is a pilot on your real accounts, with every rule that produces a number written down in advance.

What none of this does, at any size.

The limits that do not change as you grow
  • It does not tell you whether your rates are fair. It makes the rate you chose visible and traceable, which tends to make an unfair one more obvious rather than less — but the number is yours to set.
  • It cannot reconstruct the months you ran before you connected. The record starts when you start, and the first clean month is the first month you run on it.
  • The hard part is habit rather than software. If nobody clocks in, the coverage map shows an empty slot, which is exactly what it should do — and getting people to clock in is still a management job.
And three that surprise people later
  • It is not an accounting system and it never moves your money, at any tier including enterprise. We compute what is owed and produce the export; the payment happens on your own rail, deliberately.
  • White label is your brand on our software. Not a rebuild, not your own codebase, and not a claim that the product is yours — it means your creators and staff see your name rather than ours.
  • A contractual uptime guarantee is not part of the published plans. Uptime is published publicly and you can watch it before you commit, but an SLA with terms attached is an enterprise conversation rather than a checkbox on a tier.

Set it up before the argument, not after it.

A 20 minute walkthrough, then 14 days on your real roster, reconciled against your own Statements pages. No card required, and the export is yours either way.

Book a demoSee the plans

FanOptik

Analytics and chatting for OnlyFans agencies and independent creators. Measured across the whole roster, with every figure graded by where it came from.

© 2026 FanOptik. All rights reserved. · Built for agencies that would rather measure the roster than estimate it.