Co-op platform demos all look alike: a dashboard with a balance, a claim moving through an approval queue, a report with a bar chart. The differences that matter show up six months after signature, when a location tries to actually spend money and discovers the platform only manages the fund. These questions surface that early.
Is spend inside the system or beside it?
Ask: When a location wants to run a direct mail drop, where do they place the order? If the answer involves a separate vendor portal, an agency email, or "they upload the invoice afterward," the platform administers the fund but does not enable spend. That is the split most of this category is built on, and it is where reconciliation work lives. A claim gets approved in one system, the purchase happens somewhere else, and matching them becomes someone's job every month.
What does proof of performance actually require from the dealer?
Ask: Show me a completed claim. Count the attachments. Legacy manufacturer programs demand a paid media invoice (91% of plans we track), a tearsheet (89%), and often a notarized invoice (20%) or a broadcast affidavit (29%). A platform that still asks the dealer to gather these has digitized the paperwork without removing it. If the platform placed the buy, it already has the invoice and the proof. Ask why it is asking again.
How is creative compliance enforced?
Ask: Can a location produce an off-brand ad in this system, and if so, who catches it? "A reviewer approves each one" means a queue and a delay. "The templates do not allow it" means compliance is built into the tool. Ask to see the template editor from the location's point of view: what can they change, what is locked, and who decides.
How does purchase data get in?
Ask: Our accrual is a percent of dealer purchases. How does the platform learn what each dealer bought? Options range from an ERP integration to a monthly CSV upload to an administrator typing balances. All three can work. What matters is that the vendor names one and tells you who owns it. Half the manufacturer plans in our database accrue on purchases, and this is the integration most likely to stall an implementation.
Where does the money actually move?
Ask: When a claim is approved, does the platform pay the dealer, credit their account, or hand a file to our accounting team? Fund management platforms often stop at the file. That is fine if you know it going in and your finance team has a process on the other side. It is a surprise if you assumed "reimbursement" meant a payment.
What does a location see?
Ask for a login as a location manager, not an administrator. Can they see their balance today, what is pending, and what expires when? Can they spend from that screen? A platform that is excellent for corporate and opaque for the location will have low utilization, and unspent co-op is a brand that is not being advertised.
Who owns the data if we leave?
Ask: Can we export every location, balance, claim, creative asset, and transaction in a documented format at any time? The answer should be yes without a services engagement. If it is not, the platform's real lock-in is your own history.
The one-sentence test
After the demo, try to finish this sentence: "A location manager logs in, sees their balance, buys media or orders materials against it, and corporate sees the result, all in ______." If you cannot fill the blank with one system name, you are evaluating a fund manager and will need a second vendor for everything else.
Co-Op Command handles the fund, the spend, and the reporting in one system.
Request a Demo →