Skip to content
§
§ · build vs buy

Co-op and MDF Fund Management: Outsource the Claims Desk, or Build the Accrual Engine

This category rewards building later than most, and there are three answers rather than two. Under about a million a year with sixty dealers, do neither: a shared inbox, a spreadsheet and a one page eligibility guide costs nothing and works.

Internal tools product interface illustration for CO OP Advertising Fund Management Software Build vs Buy Guide.
The short answer

This category rewards building later than most, and there are three answers rather than two. Under about a million a year with sixty dealers, do neither: a shared inbox, a spreadsheet and a one page eligibility guide costs nothing and works. With a modest fund and a partner count in the low hundreds, outsource the claims desk to Brandmuscle or Channel Fusion, because the labour of review is the problem rather than the design of the programme. Build when the fund accrues past roughly five million a year across three hundred or more partners, or when your accrual depends on distributor data nobody else will untangle.

When is off the shelf genuinely the right call here?

Brandmuscle and Channel Fusion pair software with claim review staff, and that combination is genuinely valuable when what you want is to stop running a claims operation. Vistex sits at the enterprise end with deep incentive and channel programme capability, and if you already run its adjacent modules the integration case is strong. What you adopt in all three cases is their workflow, their data model and their commercial model, and the accrual side still depends on whatever data you can feed them.

Buy the service, and stop reading here, if this describes you:

  • A partner count in the low hundreds with a fund that is meaningful but not large.
  • Partners who buy direct, so accrual comes from your own invoices with identifiers you already own.
  • One programme with stable rules that have not changed materially in two years.
  • The pain you feel is the volume of claim review rather than the design of the programme.
  • No requirement to join fund data to partner sell through.

This applies equally whether the money is co-op earned on purchases or a discretionary market development fund (MDF), because the review labour looks the same from the coordinator's side. Below that again, spend nothing. Sixty dealers and a fund under about a million does not justify a build or a service, and the build would cost more than the leakage it recovers. A clear one page eligibility guide plus a shared inbox is not a failure of ambition, it is proportionate, and it is what we tell those callers.

When does a custom build actually pay off?

The thing that makes this category different is that outsourcing is a real third option rather than a euphemism for buying. So the build case has to beat both a product and a service.

Build when two or more of these hold:

  • The fund is large enough that a few points of leakage or expiry exceeds the build cost in a single year.
  • Your accrual depends on distributor point of sale (POS) reports that arrive weeks late, in different formats, with each dealer named however that distributor names them.
  • You run several programmes with different accrual, eligibility and expiry rules and want partners to see one balance rather than log into four portals.
  • You need fund data joined to partner purchase or sell through, which a per claim service provider has no incentive to build.
  • Per claim pricing has started scaling badly against your volume.

That last signal usually announces itself in an invoice rather than in a spreadsheet, and it is the moment a channel director picks up the phone. Per claim pricing is entirely reasonable at low volume and scales in the wrong direction, which is arithmetic rather than criticism.

Before any of it, look at why the fund goes unclaimed. It is usually not eligibility, it is friction: a dealer who cannot see their balance, does not know what is about to expire, has to guess whether their activity qualifies and waits six to ten weeks for reimbursement simply stops making small claims.

How do they compare on the things that matter in this industry?

Accrual from distribution. Ask any provider how a partner's balance is calculated when the partner buys through two step distribution. If partner identity matching across distributor reports does not come up immediately, your first month of balances will be wrong for hundreds of dealers, and publishing a wrong balance is a mistake you only make once.

Balance visibility. The single highest value screen in this category is a dealer seeing their own balance, the transactions behind it and what is about to expire. It requires no document processing at all, and it moves participation more than any amount of field reminder. Ask whether partners get that view, or whether they get a claim form.

Reservation at pre-approval. Approving plans without reserving fund means you approve activity that in aggregate exceeds the accrual and find out at payment time. Reservations also need expiry, so abandoned plans release money back rather than tying it up all year.

Where automation stops. Extraction can read vendor, dates, media type and amount off an invoice and check them against the approved plan and the amount claimed, which catches the common error of claiming gross where the programme reimburses net. Image checks can verify brand mark presence. The approve or reject decision should stay with a person for anything non routine, because an automated rejection with no human review costs more in channel relations than it saves.

Proportional availability evidence. The Robinson-Patman Act requires that promotional allowances and services be made available to competing customers on proportionally equal terms. That is a programme design obligation rather than a software feature, and software is what lets you evidence how the programme was made available across partner tiers.

What does total cost of ownership look like at your scale?

On the build side, from Digital Heroes delivery experience, a first release runs $60,000 to $130,000 over 12 to 16 weeks: accrual calculation from your sales data, partner identity resolution, fund balances with reservation and expiry, pre-approval, and claim submission through a partner portal. A full platform adding automated proof of performance validation, creative compliance checking, payment posting into finance, audit reporting and programme analytics runs $160,000 to $380,000 phased over 6 to 12 months.

A worked example at $160,000 across roughly 18 weeks, for a brand with about 900 dealers mostly buying through distribution and running two programmes: discovery with programme rule extraction and a dealer master audit $18,000, distributor point of sale ingestion with partner identity resolution $36,000, the accrual engine covering both programmes $26,000, the partner portal with live balance and expiry dates $22,000, pre-approval with reservation and a light and heavy path $24,000, claim submission with a reviewer queue $20,000, and testing with one quarter run in parallel $14,000.

The variable worth understanding is the ingestion line. Replace the distributor pipeline with reading your own invoice data, which is roughly $12,000 rather than $36,000, and run a single programme, saving a further $9,000, and the same scope comes in at $127,000, inside the first release band. Neither version includes automated proof of performance, creative checks or payment posting.

Running costs are 15 to 20 percent of build a year, roughly $24,000 to $32,000 on a $160,000 platform. Four lines are specific to channel funds: distributor report formats change without consulting you, so allow for ingestion repair annually; each programme year brings rule changes, some of which will not be pure configuration; automated evidence checking creates a human review queue for anything below a confidence threshold, which is allocated staff time; and partner support scales with dealer count whatever the software does.

On the buy side, add four lines from your own invoices: per claim or per partner service fees, the platform subscription underneath them, coordinator salaries spent on review and balance questions, and the fund that expires unclaimed each year. That last one is usually the largest and it is the only one a build directly attacks.

What does the hybrid look like, and when is it the honest answer?

The strongest hybrid in this category is one most brands never consider, because they treat the choice as software or service. It is both, and it is genuinely cheaper.

  • Keep the outsourced claims desk. Brandmuscle or Channel Fusion continue reviewing evidence packs. That is labour you do not want and they are set up for it.
  • Build the accrual engine and the partner balance portal, well inside the first release band. Distributor ingestion with identity resolution, the accrual rules with caps, expiry and carryover, and the screen where a dealer sees their own balance and what is about to expire. No service provider is going to untangle your distributor data, and none has an incentive to make claiming easier.
  • Add reservation at pre-approval before automation. Approved activity reserving fund, with a light path that auto approves small routine claims against a template and a heavy path routing the rest to a human, removes most of the review labour for a fraction of the cost of full automation.

Sequence that way and the expensive half, automated proof of performance and creative compliance checking, stays a phase two decision you make with a year of real data rather than a projection. Start with one programme even if you run four, because the accrual engine, reservation model and claim workflow are built once and reused, so programme two costs around $9,000 rather than a second project.

Which should you choose, by operator size and stage?

  • Sixty dealers, fund under about a million. Spend nothing. A shared inbox, a spreadsheet and a one page eligibility guide genuinely works.
  • Partner count in the low hundreds, direct purchasing, one programme. Outsource the claims desk. The labour is the problem, the programme design is not, and a build would cost more than it recovers.
  • Several hundred partners, mostly direct, participation falling. Build the balance portal alone before anything else. It is the cheapest intervention in this category and it addresses the actual reason funds expire.
  • Three hundred or more partners buying through two step distribution. The decision point, and usually the hybrid. Build accrual and balances, keep the outsourced review, and revisit automation after a year.
  • Large fund, several programmes, multi country, needing sell through analysis. Build the full platform, sequenced: accrual and balances, then reservation and light path approval, then automated proof of performance, then payment posting and proportional availability reporting last.

Two conditions apply to every build row. Do the programme rule extraction and dealer master clean up with your own team before kickoff, because writing down each programme's accrual rate by product category, its caps and its expiry behaviour is work your channel team can do at their own salary cost, and left to be discovered mid build it is the most common cause of a slipped launch. And run one full quarter of accruals in parallel before dealers see live balances.

If you want a second opinion before signing anything, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. Nothing about that commits you to the build.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
  2. Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
  3. Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
  4. An earlier SHRM benchmarking report (reflecting fiscal year 2015, published 2016) established a widely cited baseline average cost-per-hire of $4,129, illustrating how recruiting costs have climbed over time (SHRM's separate 2025 Benchmarking Report shows $5,475 for nonexecutive roles). Note: the $5,475 figure is not on this linked page; it comes from SHRM's 2025 report. Source: SHRM (Society for Human Resource Management) (2016) →
FAQ

Frequently asked questions

Is Brandmuscle cheaper than building, and when does that change?

For a modest fund with a partner count in the low hundreds, yes, and outsourcing the review labour to Brandmuscle or Channel Fusion is a legitimate strategy rather than a compromise. We say so rather than talking anyone into a build.

It changes when per claim pricing starts scaling badly against your volume, when the fund is large enough that a few points of leakage exceeds the build cost in a year, or when your accrual depends on distributor data no service provider is going to untangle for you.

What does it cost to switch fund management providers?

The direct cost is modest. What does not travel cleanly is the claim history and the accrual basis behind each balance, and you need both when a dealer disputes a figure or when someone asks how the programme was made available across partner tiers.

Before signing anything, ask how the complete record leaves the system, including the transactions behind each accrual rather than balances alone. And do the dealer master reconciliation yourself, because that mapping is the asset that makes any future move cheap.

What if per claim pricing rises as our fund grows?

Model the fee at double your current claim volume before renewal rather than during it. Per claim pricing is reasonable at low volume and rises exactly as participation improves, which means a successful programme is a more expensive programme.

The structural response is to own the accrual engine and the partner balance view, so the service provider is supplying review labour you can price and compare rather than holding the only record of what each partner has earned.

How long before dealers can see a live balance?

Twelve to sixteen weeks to a first release, then one quarter of accruals and claims run in parallel with your existing spreadsheet before balances go live to partners.

Do not compress the parallel quarter. Publishing a wrong balance to nine hundred dealers is a mistake you only make once, and the schedule risk is upstream anyway: matching distributor reports to your dealer master is a real workstream better done before launch than discovered afterwards.

Why does two step distribution cost so much more than direct purchasing?

Because it adds an ingestion pipeline plus a partner identity resolution layer. Reports arrive weeks late, in different formats, with each dealer named however that distributor names them, so the same business appears as several different strings across sources.

In our worked example, distributor ingestion with identity resolution was $36,000 against roughly $12,000 for reading your own invoice data. It is the single largest driver in this category and it is the part no service provider will solve for you.

Why does so much of our fund go unclaimed?

Because claiming is harder than it is worth for the partner. A dealer who cannot see their balance, does not know what is about to expire, has to guess whether an activity is eligible and waits six to ten weeks for reimbursement simply stops making small claims.

Publishing a live balance with expiry dates and giving fast automated approval to small routine claims typically moves participation more than any amount of field reminder, and neither requires document processing.

Can we run several programmes without paying for each separately?

Yes, and it is one of the better reasons to build. The accrual engine, reservation model and claim workflow are built once, so a second or third programme is rule configuration plus testing rather than new construction. In our worked example the second programme accounted for roughly $9,000.

Model programme as a first class object with its own rule set, so next year's seasonal push is configuration rather than a project and partners see one balance instead of four portals.

We have 60 dealers and a small fund. What should we spend?

Very little. At that scale a shared inbox, a spreadsheet and a clear one page eligibility guide genuinely works, and a build would cost more than the leakage it recovers.

Do one thing that costs nothing and helps immediately: publish each dealer's balance and expiry date to them once a quarter, even if you send it manually. That single change addresses most of what a portal would fix, and it tells you whether participation is actually your problem before you spend anything.

Can we start on Airtable or Retool now and move to custom software later?

Yes, and it is often the smartest sequence: run the workflow on Airtable or Retool for 6 to 12 months to learn what you actually need, then go custom once the process stabilizes. The no-code version becomes free requirements documentation, and its data exports cleanly into a custom database. The one risk is waiting too long, because teams stack automations and workarounds until migration becomes a project of its own, so set a concrete trigger in advance, such as hitting Airtable's 50,000-record Team plan cap.

What questions should I ask a development agency on the first call?

Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.

What does an internal tool cost for a small business with 20 to 50 employees?

Plan on $5,000 to $15,000 for a focused tool that replaces one painful spreadsheet workflow, such as job scheduling, quoting, or PTO tracking. In Digital Heroes projects at this size, the sweet spot is one core workflow, two or three user roles, and a single integration, usually QuickBooks or Google Workspace. Quotes far below $5,000 usually mean a template with your logo on it rather than software built around your process.

When does a company outgrow Airtable?

The usual breaking points are record limits, permissions, and automation complexity. Airtable's Team plan caps each base at 50,000 records and Business at 125,000, so operations logging thousands of rows a month hit the ceiling within a year or two. The other trigger Digital Heroes sees constantly is permissions: restricting who can view specific fields or records is clumsy below Airtable's Enterprise tier, which becomes a genuine problem once salaries, pricing, or client contracts live in the base.

Is a custom internal tool secure enough for HR records and financial data?

A properly built custom tool is generally safer for sensitive data than the shared spreadsheet it replaces, because you get role-based access, audit logs, encrypted storage, and the ability to cut one person's access instantly. Ask the agency specifically for encryption in transit and at rest, permissions down to the field level, and an audit trail showing who viewed or changed each record. If HIPAA, GDPR, or SOC 2 expectations from enterprise clients apply to you, raise it before the quote, because compliance features add real scope.

Who owns the code when an agency builds my software?

You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.

Should we build our internal tool in Retool instead of hiring developers?

Retool is the right choice if someone on your team is comfortable with SQL and JavaScript and the audience is a handful of technical users, because a basic CRUD dashboard comes together in days. Hire developers when non-technical staff will use the tool daily, when the logic goes beyond forms sitting on a database, or when per-seat pricing stings, since Retool's Business tier lists at $50 per standard user per month. A pattern Digital Heroes sees often: companies arrive after a year on Retool with a tool nobody can maintain because the one person who built it has left.

What are the biggest mistakes first-time software buyers make?

Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.

What should I prepare before contacting an agency about an internal tool?

Bring the spreadsheet or document you run the process on today, a list of everyone who touches the workflow and what each person does, and one sentence describing the outcome you want. You do not need wireframes or a technical spec; a 30-minute screen-share of the current process beats a 20-page requirements document. Decide your rough budget band and name a single internal decision-maker, because projects without one take noticeably longer in Digital Heroes experience.

What does it cost to keep an internal tool running after launch, and do we need to hire a developer?

Budget 15 to 20 percent of the build cost per year, so a $25,000 tool runs roughly $300 to $400 a month covering hosting, security patches, dependency updates, and small tweaks, figures drawn from Digital Heroes maintenance contracts. You do not need an in-house developer; a monthly retainer with the agency that built it covers the typical internal tool comfortably. Hosting itself is cheap for internal audiences, often $20 to $100 a month, because you serve dozens of users rather than the open internet.

How do I vet a development agency for an internal tools project?

Ask to see two or three internal tools they have shipped and whether those clients still use them daily, because internal tools fail on adoption, not code quality. Good signs: they ask to see your current spreadsheet or process before quoting, they propose a phased build instead of one big launch, and they spell out who handles training and post-launch changes. Walk away from anyone who gives a fixed price before seeing your actual workflow, since internal tools live or die on process details.

Who can build a custom internal tools system?

Digital Heroes builds custom internal tools systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.

Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.

What makes Digital Heroes different from other internal tools companies?

Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.

Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.

How can I check Digital Heroes is legitimate before getting in touch?

Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.

Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply