Brand Protection and MAP Monitoring: Should You Build or Buy a Service?
Two thresholds decide this, and the first is a question rather than a number: is your problem counterfeits or diversion through your own authorised channel?
On this page
Two thresholds decide this, and the first is a question rather than a number: is your problem counterfeits or diversion through your own authorised channel? If it is counterfeits, buy a service, because takedown workflows and platform relationships already exist and you will not beat them. The second threshold is roughly 50 unauthorised sellers across one or two marketplaces, below which a build is expensive infrastructure for a problem a service already handles. Above it, with diversion as the real issue, a detection and identity core runs $60,000 to $130,000 and a full enforcement platform runs $150,000 to $380,000.
When is off the shelf genuinely the right call here?
Buy if counterfeiting rather than authorised channel diversion is your core problem. Removing counterfeits through platform intellectual property programmes is a well solved service problem, and Red Points and MarqVision have both the takedown workflows and the volume relationships to do it faster than you would. Corsearch is credible where trademark work is the centre of the need. None of that is a compromise, it is the correct purchase.
Buy if you monitor one or two marketplaces, or if you have fewer than about 50 unauthorised sellers. At that scale the enforcement work is a person's afternoon rather than an engineering programme, and a build is infrastructure you will spend years maintaining for a queue you could read.
Keep using the brand programmes the marketplaces themselves operate, whatever else you decide. They cost nothing beyond your time, they are the fastest route on clear intellectual property grounds, and nothing you build should replace them. Any developer who proposes doing so has misunderstood the problem.
The clean test is whether you already know what to do with a violation once you see it. If the answer is send a notice through a platform programme and the listing comes down and stays down, monitoring is your only gap and a service fills it. The build case only opens when knowing what to do requires information the service cannot have, which in practice means your authorised dealer list, your regional price rules and your own shipment records.
When does a custom build actually pay off?
Two or more of these have to hold before the arithmetic works.
The first and strongest is that your main problem is diversion by your own authorised partners rather than counterfeiting. No external monitor can diagnose that, because diagnosing it requires reading a serial or lot code off a purchased unit and mapping it back through your own shipment records to the distributor or dealer it was sold to. That capability turns an anonymous listing into a named partner and a commercial conversation you can win, and it stops supply rather than removing one listing.
The second is that your advertised price policy has regional and promotional structure that generic monitoring keeps flagging incorrectly. A policy is rarely one price. It is a price per product, per region, per period, with promotional windows where the floor moves, exceptions for authorised clearance of discontinued lines, and explicit treatment of bundles. When a monitoring tool built for generic price tracking meets that, the report fills with false positives and your channel team stops opening it, which is the real failure.
The third is that sellers relist under new aliases faster than your process connects them. A seller who reappears under a different storefront name within days is not three offenders, and treating them as three means you send three first warnings and never escalate.
The fourth is that your authorised dealers are raising channel conflict as a commercial issue rather than a nuisance.
The fifth is ownership. The seller entity graph and the enforcement history compound in value every month, and that record is what makes a fourth notice a case rather than another letter. It should not sit inside a vendor you might change.
How do they compare on the things that matter in this industry?
Five things separate these options, and monitoring coverage is only one of them.
- Seller identity as a persistent entity. A service reports listings. A build can cluster storefronts into entities using signals that are expensive to change: shipping origin and handling times, photographs reused across storefronts and detected by perceptual hashing, description text fingerprints, return addresses, business names disclosed under the INFORM Consumers Act, and repricing behaviour patterns. Hold that cluster with an alias history and a full enforcement timeline and your fourth notice is addressed to someone you can prove you have warned three times.
- Policy expressiveness. This is the clearest configuration ceiling. A build can hold policy as versioned data with effective dates, product scope, regional scope and explicit bundle handling, and cite the exact clause on every violation record. That is what makes a report defensible and disputes short.
- Access to your own records. Serial traceback into shipment data is the capability no external service can offer, because it needs data you have never given them and should not.
- Coverage measurement. Ask any provider what share of listings for your products they actually saw last week. A report of 40 violations means nothing without a denominator, and coverage is the metric almost nobody produces.
- Contract economics. Read whether your agreement scales on brand, product count, marketplace coverage or takedown volume, then model it three years out. If you pay per takedown and offenders are rotating rather than falling, that line grows while the problem does not shrink.
Services win outright on speed, on takedown throughput and on platform relationships you cannot replicate. Those are real and they are why counterfeit work belongs with them.
What does total cost of ownership look like at your scale?
On the build side, start with the release one number rather than the programme total. A detection and identity core covering two or three marketplaces, listing to product matching with a human review queue, seller identity clustering and a violation queue with manual notice sending is $60,000 to $130,000 over 10 to 16 weeks. Image similarity infrastructure adds $18,000 to $45,000. Each additional marketplace adapter is roughly $12,000 to $20,000 even after matching and clustering exist. The first additional language is $15,000 to $30,000 and each one after is less.
Then the running costs, which most brands underestimate. Adapter maintenance is $3,000 to $9,000 per marketplace per year and it is the largest recurring line, because sources change structure and an adapter that silently degrades is worse than no adapter, since it reads as a quiet week. Image similarity compute and storage is $6,000 to $22,000 a year, scaling with listings collected rather than with your catalogue. Test buy budget is $8,000 to $30,000 a year for purchases, shipping and disposal, which is modest money producing the highest value output in the system. Support and enhancement is 15 to 20 percent of build cost annually, and the matching layer needs continuous tuning because sellers adapt.
Catalogue size matters far less than brands expect. Going from 50 products to 900 barely moves the matching build, because the work is in the signal stack rather than the row count. Marketplace count and language coverage are what move the number.
On the other side of the ledger, the honest comparison is not licence against build. It is margin erosion on diverted units plus the damage to a channel you built deliberately. A brand that loses two significant dealers in a year to channel conflict has usually lost more than the whole programme costs, and dealers leave quietly rather than complaining first.
What does the hybrid look like, and when is it the honest answer?
For most manufacturers with a dealer network, the hybrid is the answer and it is under sold.
Keep the service for what services are good at: counterfeit removal, high volume takedowns and the platform relationships behind them. Keep the marketplace brand programmes running. Then build the thin layer that only you can build, which is seller identity clustering against your own catalogue, the policy engine that knows your regional and promotional structure, and serial traceback into your shipment records. Feed the service with entity level cases rather than listing level complaints, and you improve its output as well as your own.
Sequencing inside the hybrid matters more than the arithmetic. Build coverage measurement in release one even though it produces no enforcement action, because without a denominator you cannot tell whether a quiet week is compliance or a broken adapter. Run identity clustering in observation mode for four to six weeks before anyone acts on it, and have your channel manager review the clusters against what they already suspect. A wrong merge caught in that window costs nothing. A wrong merge behind an escalation letter is a rebuttal from a legitimate reseller and a conversation with counsel.
Sequence the test buy workflow before the policy engine if diversion is your real problem. Serial traceback finds the leak. The policy engine reduces false positives, which matters, but it does not tell you where the product came from.
Which should you choose, by operator size and stage?
Brands with a counterfeit problem, any size. Buy a service. Red Points, MarqVision or Corsearch depending on whether takedown volume or trademark work dominates. Do not build.
One or two marketplaces, fewer than 50 unauthorised sellers. Buy, and use the marketplace brand programmes properly first, because most brands have not exhausted the free option before pricing the expensive one.
Three or more marketplaces with a dealer network and persistent relisters. Build the detection and identity core at $60,000 to $130,000, scoped to two marketplaces, one region and your top 50 products by revenue, with notices still sent by hand. Detection and identity are the hard parts. Sending an email is not.
Brands whose price policy has regional and promotional structure. Add the versioned policy engine, roughly $31,000, once the identity layer is trusted. Skip it in release one only if you genuinely run a single national price with no promotional periods.
Manufacturers who suspect diversion and can trace serials. Test buy workflow at around $22,000 plus serial to shipment traceback at around $29,000 is the highest value pair in this whole category. Confirm first that your shipment records actually carry serial or lot ranges, because if they do not, this waits on an upstream process change rather than on a budget.
When you are ready to turn this into a specification, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
Frequently asked questions
What does it cost to move off a monitoring service?
The software side is straightforward, because you are usually adding a layer rather than replacing a workflow. The part that does not move is the enforcement history: notices sent, responses, platform ticket references, outcomes and reappearances. Ask what you can export and in what format before you decide, and export it whether you leave or not.
That history is what makes escalation viable. A single takedown notice is administrative. A documented pattern of one entity relisting after repeated notices is a case, and rebuilding that pattern from screenshots after the fact is close to impossible.
What if our monitoring vendor changes how it prices?
Read which of brand, product count, marketplace coverage or takedown volume your agreement scales on, then model it against where you expect to be in three years. The uncomfortable case is per takedown pricing when your offender count is rotating rather than falling, because the line grows while the problem stays the same size.
That structure is also a reason to measure repeat offender rate rather than raw violation count. If offenders are rotating, you are paying more each year to stand still, and that is an argument for identity clustering rather than for a better rate.
How long before a build produces results?
Ten to 16 weeks for a first release covering collection, matching, identity clustering and a violation queue. Then plan four to six weeks of observation before anyone acts on the clusters.
The first genuinely useful output is not a lower violation count. It is a repeat offender rate that starts falling while the raw count stays flat, which is the signal that clustering is recognising relisters as one entity and escalation is landing. Expect that signal in the second quarter rather than the first month.
Is Red Points enough for our situation?
For counterfeit removal on one or two marketplaces with fewer than about 50 unauthorised sellers, yes, and it will be faster than anything you build because the takedown workflows and platform relationships already exist.
Where it strains is diversion through your own authorised channel, because diagnosing that needs your shipment records, and a price policy with regional and promotional structure, because generic monitoring keeps flagging correct prices as violations until your channel team stops reading the report. Neither is a criticism of the service, they are outside what any external monitor can see.
Does our catalogue size change the build cost much?
Far less than most brands expect. Going from 50 products to 900 barely moves the matching build, because the work sits in the signal stack rather than the row count.
What moves the number is marketplace count at roughly $12,000 to $20,000 per additional adapter, language coverage at $15,000 to $30,000 for the first extra language, and how many regional designations, suffixes and bundle configurations your products carry, since a suffix that distinguishes a European variant determines which regional price rule applies.
How much does test buy tracking and serial traceback add?
Around $22,000 for the test buy workflow with budget control and chain of custody, plus around $29,000 for serial to shipment traceback. Whether the second is buildable at all depends on whether your shipment records carry serial or lot ranges.
If they do not, the feature waits on an upstream process change and that conversation should happen before anyone quotes it. When it is buildable, the diversion report by authorised partner is the single most valuable output of the whole system, because it stops the supply rather than the listing.
Can we skip the policy engine to save money?
Only if you genuinely run a single national price with no promotional windows and no bundle question. In that case a simple threshold works and the versioned engine can wait until the policy grows.
Otherwise it is roughly $31,000 well spent, because it is what stops the violation report filling with false positives. Bundles deserve particular attention: a seller pairing your product with a cheap accessory can argue the price is not comparable, so say explicitly in the policy how bundles are treated and detect them rather than letting them fall out of the report.
Is enforcing an advertised price policy something software can decide?
No, and it should not try. In the United States advertised price policies are generally structured as unilateral policies a brand announces and enforces by choosing whom to deal with, rather than as agreements on resale price, and state law varies in its treatment. Other jurisdictions differ again.
Take the structure of your policy from antitrust counsel and then build software that supports exactly that structure, recording enforcement as a unilateral decision against the policy version in force at the time. Your system's records may one day be evidence about how the policy operated, which is a reason to keep negotiation out of it.
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.
Is a freelancer or an agency better for building an internal tool?
A solid freelancer works for a single-workflow tool under roughly $10,000, if you accept that one person holds all the knowledge. An agency earns its premium once the tool spans departments or integrations, because you get a developer, a designer, and a project manager plus continuity when someone leaves or gets sick. The hidden freelancer cost appears 18 months later when you need changes and the original builder has moved on, a rescue situation Digital Heroes is hired for regularly.
How long does it take to build an internal tool from scratch?
A working first version typically ships in 4 to 8 weeks, and larger multi-module tools run 10 to 16 weeks. Across Digital Heroes internal tool projects the schedule splits into roughly one week of process mapping, 3 to 6 weeks of build, and 1 to 2 weeks of testing with your actual staff. The most common delay is not development but waiting on the client for sample data and workflow decisions, so name one internal owner before kickoff.
Can a custom internal tool connect to QuickBooks, Salesforce, and the other software we already use?
Yes, and integrations are usually the strongest argument for going custom instead of chaining tools together with Zapier. QuickBooks, Salesforce, Shopify, Stripe, Slack, and Google Workspace all have mature APIs, and each integration typically adds $1,500 to $5,000 to a Digital Heroes build depending on how much two-way syncing you need. The honest caveat is legacy industry software without an API, which may need file-based imports instead of a live connection, so list every system in the first conversation.
Should we build the whole internal tool at once or start with an MVP?
Start with a version that fully replaces one workflow, ship it in 4 to 6 weeks, and let real usage set the roadmap. Internal tools have a captive audience, so you learn within days which features matter, and across Digital Heroes projects roughly a third of initially requested features never get built once staff work with version one. Phasing also spreads the spend: a $40,000 vision becomes a $15,000 phase one that starts paying for itself while phase two is scoped.
What tech stack should an internal tool be built with?
Boring and popular: a React or Next.js frontend, a Node.js or Python backend, and PostgreSQL covers the vast majority of internal tools and keeps future hiring easy. The stack matters far less than whether a different developer can pick the code up in two years, so require documentation as a deliverable and avoid anything exotic. Treat it as a red flag if an agency pushes a proprietary platform only they maintain, because that quietly converts your tool into a subscription to that agency.
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.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
At what point does Retool cost more than building a custom tool?
The crossover usually lands between 25 and 50 daily users. At Retool's published Business rates of $50 per standard user and $15 per end user monthly, a 40-person deployment with a typical seat mix runs roughly $9,000 to $15,000 per year, every year, while a comparable custom tool built once for $20,000 to $30,000 carries no per-seat fees and costs about 15 to 20 percent of the build price annually to maintain. On a three-year horizon, custom comes out ahead for most growing teams in Digital Heroes engagements.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
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.
Related guides
More from Ahaan.
Senior Android Engineer · Delhi · 1 post on the site
Published · Last updated .
