NATIVOone system · one record
The system

One record. Four layers. Four areas.

Everything the agency produces is captured once, recorded in one place and read from there. The Record row is the product; everything above feeds it, everything below is read from it, and the spine keeps it honest.

Sales
Marketing
Operations
Finance
GovernanceRulings — every rule the agency runs on, in plain wordsRatify — below a threshold the record posts by rule; above it, a named person signsChecks — what passed, what is flagged, what we cannot see yet
Capture
Platform payouts and statistics
Ad spend, traffic, partner invoices
Hours, rosters, terms on file
Banks, cards, wallets, PSPs
Record
Turnover per creator, by the terms in force
Spend attributed to the creator it served
Pay calculated from terms × hours
Every rail tied to its statement
Reporting
Who's driving, who's dragging
Paid vs delivered, ROAS on a cash basis
Who earns their cost
Cash by rail, P&L by entity and group
Outputs
Weekly report
Partner statements
Pay runs, payout evidence
Monthly pack, the accountant's import
How the record is kept

Rules you ruled once. A person who signs.

Rulings

Every rule the agency runs on, written once, in plain words: who is paid what, on which terms, from which rail; which traffic partner serves which creator; what counts as revenue on each deal type. Numbered, dated, in your words. The record derives from them.

Ratify

Below a threshold the record posts by rule. Above it, a named person answers Y or N in the app, and the answer becomes a rule for next time. Silence is never an approval: an unanswered item appears on the month's report with its money and its owner.

Checks

Thirty-odd checks every month, each with an owner and the money involved: every rail ties to its statement; calculated pay equals paid pay; no payment booked twice; the month re-runs to the same books. "Cannot see" is a real answer, named, never hidden.

WhoBooksRegisters new partiesRulesSigns
The systemTransfers between your own accounts, same entity and currency———
Your deputyBookings and revenue lines up to $5,000YesProposes—
A directorAbove $5,000 · between entities · anything outside terms—Confirms every rule—
The controller———The month, every month

The thresholds are the starting policy. They tighten only after two clean closes, never on trust. Terms changes are never confirmed without a director's word.

The monthly pack

Every lever, every month — on sample figures

What the pack holds, drawn from the sample agency. Three layers: the agency's P&L against its benchmark, the fan economics behind it, and every creator's own P&L.

Agency P&L · August · consolidated · USD
LineAugustBenchmark / movs bench
Revenue
Fixed-fee deals356,200341,800+14,400
Commission deals84,90096,300−11,400
Chat agency and referral27,82031,200−3,380
Total revenue468,920469,300−380
Direct costs
Creator fees(36,400)(33,900)−2,500
Traffic, by partner(182,300)(196,100)+13,800
Chat team(58,700)(55,400)−3,300
Gross profit · 40.9%191,520183,900+7,620
Overhead
Management and operations(51,666)(49,800)−1,866
Software, rent, professional(23,937)(22,100)−1,837
Bank, card and wallet fees(6,719)(6,200)−519
Operating profit · 23.3%109,198105,800+3,398

Benchmark = average of the closed months, August included. Every line opens the rows behind it. Sample figures.

Fan economics · August · sample
2.9×ROAS, cash basis
68.4%take rate
$1.72traffic CAC
$5.10LTV per new fan
2.97×LTV : CAC
2.4%sub → spender
$48.20ARPPU
6.1%whale share
11.4%m+1 retention, by cohort
3.1×LTV:CAC, March cohort to date
34%spend on auction ads
19%affiliate-delivered fans

Traffic on a cash-paid basis; the tracker is used for attribution only. m+1 retention by cohort month, never re-indexed. Cohort vintages carry cumulative value per new fan at each month-end.

Creator economics

Each creator's P&L for the month and the year to date: revenue by her deal, her fee, the traffic bought for her, the chatters who sold for her, contribution, margin, ROAS on allocated traffic, LTV:CAC and whale share. Sorted by contribution; the loss-makers in red.

Replace · connect

What goes, what stays

ReplacesConnects
The payout spreadsheet and the split calculatorBanks and cards: Mercury, Wise, Metro, Revolut, Spanish banks
The tracker as the source of truthPaxum, Cosmo and your wallets — TRC20, ERC20
The monthly rebuild for the accountantInfloww and Hubstaff, or their equivalents
"Management accounts" nobody signsYour accountant's Xero or the gestoría's ledger, as a generated import
Compared

Where each option stops

CapabilitySpreadsheetsAgency toolsOutsourced bookkeeperNATIVO
Every rail reconciled to the bank, crypto included◐–◐●
One record across entities and currencies––◐●
Turnover, spend and pay tied to platform statistics and hours–◐–●
Payouts calculated from the terms on file, calculated vs paid◐●–●
Every USDT payout with hash, payee and value on the day–◐–●
Monthly close with P&L, balance sheet and cash flow, signed––●●
Daily cash and turnover, by 9am, on your phone–◐–●
Rulings and thresholds: who signs what, enforced–◐–●
Monthly checks report, including what cannot be seen–––●
Same exports, same books, every run–––●
The company owns the data and the system●––●
Accountant files from these books––●●

● yes · ◐ partial or by hand · – no. If you run one rail and need splits and a portal, a $121-a-month tool is fine. If the numbers have to tie across rails, entities and people, that is NATIVO.

Why it is yours

The record lives in a store you own, on a server you control.

We build it and run it for the first months; you keep it. Every figure traces to a source line. Export is complete and in open formats. Your accountant files from it; we never file. That is why the Build is charged and the running cost is low.