Software Asset Management Software: Custom Build vs Off-the-Shelf
Buy. For almost every estate, Flexera One, Snow or the ServiceNow module already handles discovery, normalisation and the publisher catalogue better than you will.
On this page
Buy. For almost every estate, Flexera One, Snow or the ServiceNow module already handles discovery, normalisation and the publisher catalogue better than you will. Build only the entitlement register and the calculation engine, and only for the two or three publishers whose contracts differ from published policy. Full replacement earns its cost above roughly 25,000 managed devices carrying five contested metrics.
What the off-the-shelf software asset management products actually do well
Start with the honest part. Flexera One, Snow Software, ServiceNow Software Asset Management and USU all carry a publisher content library, and that library is the reason to pay them. Recognising that a scanned executable is one edition of one product from one publisher, across tens of thousands of titles and every version they have ever shipped, is a decade of unglamorous cataloguing with no competitive value to you. Rebuilding it is the most expensive mistake available in this category.
They are also good at the parts nobody writes case studies about. Normalising raw inventory from several discovery agents into a single product record. Handling the noise where a Windows registry entry and an executable header disagree about a version. Keeping up as publishers rename editions at each release. ServiceNow is the sensible pick when your configuration management database already lives there, because the software asset management module inherits your existing asset relationships instead of asking you to rebuild them. Certero and Lansweeper sit lower on price and are a fair answer for a smaller estate on a simple stack.
So the buy case is strong, and we say it before anything else: most organisations should buy. Under roughly 500 employees, with a stack of cloud subscriptions and two or three on-premises products, a discovery tool, a tidy contract folder and one disciplined spreadsheet are proportionate. A build there would be theatre. Even at several thousand devices, buying the platform and paying for a good implementation beats writing your own catalogue. The build question here is never about replacing those products. It is about the one thing they structurally cannot do.
Where custom versus off the shelf really divides: entitlements and the cluster
A licence position is deployment minus entitlement. Every platform on the market is excellent at the first half and generic about the second, because their calculation engines encode the publisher's published rules while your actual position is decided by your contracts.
Work through what that means. Oracle counts processors through a core factor table, so identical workloads licence differently on two chip families. Microsoft SQL Server per core licensing carries a minimum core count for each virtual machine, which means a two vCPU database is not a two core licence. IBM sub-capacity terms apply only if the IBM License Metric Tool is deployed and reporting continuously, so a monitoring gap converts your position to full capacity retroactively. SAP publishes a digital access model that counts documents rather than users for indirect use. None of that is exotic and all of it is contract specific.
Then virtualisation. Where live migration is enabled across a cluster, several publishers hold that licensing must cover every host the workload could run on, not the hosts it did run on. Whether that reading binds you is a question for your licensing counsel and it is frequently disputed. A packaged tool encodes one interpretation and hands you a number with false confidence. You need both numbers, your defensible position and the publisher's likely claim, computed from the same data with cluster history behind each.
The second structural gap is time. An audit letter asks about a period, not about today. If your tool only shows current state, you cannot reproduce where you stood eighteen months ago, and the maximum position becomes the figure you concede by default.
The arithmetic: per-device subscriptions versus the cost to build
Run this with your own numbers rather than ours. Take last year's platform renewal invoice, add the implementation and the consultancy days spent interpreting your contracts, and divide by managed devices. That figure per device per year is your real unit cost, and it is usually two or three times what the licence line alone suggests.
Now a worked example with inputs you should replace. Say that division gives $14 per device per year across 6,000 devices, so $84,000 a year, and say a proportionate build lands at $110,000 with $20,000 a year to keep. In year one the platform is cheaper. By the end of year two the build has cost $130,000 against $168,000. The crossover in that example arrives during the second year at roughly 5,500 devices, and every device added afterwards widens the gap, because a build does not charge you per endpoint.
Two corrections keep that arithmetic honest. The build in the example is a partial build. It replaces the entitlement register and the calculation engine, not the discovery catalogue, so you are still paying something for normalisation. And per device pricing is not the only shape on the market. Where a platform prices by publishers modelled or by module, your crossover is a publisher count rather than a device count, usually around five contested publishers.
For most enterprises the deciding number is neither. It is the size of a single settlement demand from your largest publisher. When one audit outcome could exceed the whole project, this stops being a subscription comparison.
What a custom build actually costs, including the lines nobody quotes
From Digital Heroes delivery experience, a first release covering a structured entitlement register built from your real contracts, ingestion from your existing discovery tools with virtualisation topology, and calculated positions for your two or three highest risk publishers runs $70,000 to $150,000 and ships in 12 to 18 weeks. Adding drift alerting, historical position snapshots, an audit evidence pack, renewal scenario modelling and the remaining publishers takes it to $200,000 to $480,000 across 8 to 14 months.
Data migration is its own line and it is the one that surprises people. Budget 10 to 25 percent of the build. Here it is not a database copy: it is a person with licensing knowledge reading twenty years of master agreements, ordering documents, amendments and true-up letters, then confirming every extracted entitlement against its source page. Document extraction gives you a first pass. Anyone selling a fully automated contract to entitlement pipeline is selling you a liability, because a wrong entitlement nobody checked is worse than no record at all. If your ordering documents from the 2000s exist only as scanned images, sit at the top of that range.
Year two runs 15 to 20 percent of build cost annually. That covers publisher metric changes, and they do change: subscription models that count employees rather than installations are a different counting problem from anything an install based discovery tool was designed for. It also covers your own estate moving. Hosting is modest by comparison, driven by evidence retention rather than compute, and it grows every year because audit records must stay producible.
The four situations where building wins
Build when at least two of these describe you. When three do, it is close to obvious.
- Regulatory and contractual fit. You are certifying against ISO/IEC 19770-1 for IT asset management, you need software identification tag handling under 19770-2, or your software controls sit inside a Sarbanes-Oxley scope where an auditor wants the derivation rather than the number. Packaged reporting gives you a figure. Evidence work needs the inputs, the rule version and the reasoning stored together.
- Scale economics. Per device or per publisher pricing has crossed the line described above and keeps widening. Growth by acquisition accelerates it, because each acquired estate adds devices at full rate while contributing contract lineages the platform cannot express.
- A workflow that is your competitive advantage. If you sell software asset management as a service, your entitlement model and interpretation library are the product, and renting them caps what you can charge. The same holds if your licensing position is a negotiating asset rather than a compliance chore.
- Integration sprawl across three or more systems. Microsoft Intune, Configuration Manager, Tanium or Lansweeper, VMware vCenter, the cloud provider inventories, your ServiceNow configuration management database, and a human resources (HR) system for employee counts. Each counts a different population and names things differently. When four teams reconcile that by hand every quarter, the reconciliation is the system and it should be built rather than repeated.
Digital Heroes is the wrong firm for you if you want a packaged platform configured and nothing written. We build. If configuration is genuinely the job, hire a licensing consultancy and keep the difference.
How to decide in a week, and whether it is worth building
Run one test and give it five working days. Pick the publisher whose audit would hurt most. Ask one person to assemble the complete entitlement record for that publisher from source documents only, meaning agreements, ordering documents and amendments, then compute the licensable position with the derivation written down. Time it honestly and record every place they had to guess.
Whatever that takes is your real audit response time, and the guesses are your build specification. Two days and three assumptions means buy the platform and stop reading. Five days and fifteen assumptions means the entitlement layer is worth owning. Repeat the exercise for one virtual cluster and see whether anyone can produce the host history at all.
Then buy a paid discovery phase rather than a build. At Digital Heroes that means a signed product requirements document before any code exists, covering the data model, the metric calculators in scope, permissions and acceptance criteria. You keep that specification whether or not you continue with us, and you can hand it to any other firm on your shortlist. It is the only reliable way to make four quotes comparable, because today each firm is pricing a different thing.
We are an India LLP with US LLC and UK LTD entities, so intellectual property assigns under your own law rather than across a border. More than fifty specialists, over 2,000 projects, and a named team you meet before signing. We run our own products, ShopScore, HeroCheckout and Section Vault, so architecture choices land on our revenue too. Check us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
- Sensor Tower's State of Mobile 2026 reports that global users spent 5.3 trillion hours in iOS and Google Play apps in 2025 (+3.8% YoY), roughly 3.6 hours per day per mobile user. (Note: the page does not itself contrast app time vs. mobile-browser time, so the 'overwhelming majority of time in apps vs browsers' framing is not directly supported by this source.). Source: Sensor Tower (2026) →
- Workers can expect 39% of their existing skill sets to be transformed or become outdated over 2025-2030; 77% of employers plan to upskill their workforce, and 63% identify skill gaps as the biggest barrier to business transformation. Source: World Economic Forum (2025) →
Frequently asked questions
How much does it cost to build custom software asset management software?
A first release covering a structured entitlement register, ingestion from your existing discovery tools with virtualisation topology, and calculated positions for your highest risk publishers runs $70,000 to $150,000 in Digital Heroes delivery experience. A full platform with drift alerting, historical snapshots and an audit evidence pack runs $200,000 to $480,000. Contract condition drives the range more than device count does, because scanned agreements from the 2000s need human reading.
How long before a custom entitlement system is actually usable?
Twelve to eighteen weeks for a first release covering one or two publishers end to end, then roughly four to six weeks per additional publisher because the second costs a fraction of the first. The slow part is not engineering. It is getting someone with authority to settle interpretation questions about your own contracts, which usually needs a standing weekly hour with procurement and legal booked before kickoff.
Who owns the code and the entitlement data if an agency builds it?
You should hold the repository, the cloud accounts and the unrestricted right to hire another firm, agreed in writing before kickoff. At Digital Heroes the client owns the code from the first commit, and because we operate India LLP, US LLC and UK LTD entities, the assignment happens under your own jurisdiction. There is little sense in reducing publisher dependence by creating a new dependence on a developer.
What happens if a publisher audit lands while the build is unfinished?
You answer it the way you would have answered it anyway, with your existing platform export plus manual contract assembly, and you pause new feature work to point the half-built entitlement register at that one publisher. Teams that have a partial register are usually better off than teams with none, because the contract reading is already done. Tell your developer the audit clause response window on day one.
Can we keep Flexera or Snow and build only part of this?
Yes, and for large estates that hybrid is what we recommend. Keep the commercial tool for discovery, normalisation and the product recognition catalogue, which is worth every penny and would be foolish to rebuild. Build the entitlement model and the calculation engine for the three to five agreements where your negotiated terms differ from published policy. That split usually costs less than two years of an expanded platform tier.
What are the alternatives to a full platform for a mid-sized estate?
For a few thousand devices on a conventional stack, a discovery tool plus a well kept contract register in a shared workspace, reviewed quarterly by a named owner, covers most of the risk. Sassafras and Open iT handle specific niches such as engineering application metering. An annual review by an independent licensing adviser is cheaper than either a platform tier or a build and often finds more.
Should we build if we are growing by acquisition?
Acquisitions push you toward building, but not immediately. Each acquired entity brings its own contract lineage, its own affiliate definitions deciding whether the new subsidiary is even covered, and an estate that arrives at full per device pricing. Model one acquisition through your current platform first. If the entitlement history cannot be expressed without free text notes, that is your signal, and it usually appears by the second deal.
What is the difference between discovery data and an entitlement record?
Discovery tells you what is installed and running. An entitlement tells you what you are permitted to deploy: a quantity, under a metric, from a specific ordering document, with effective and expiry dates, permitted versions and editions, and restrictions such as territory or development and test exclusions. The compliance position is the gap between them. Most organisations have invested heavily in the first and almost nothing in the second.
Can document extraction read our contracts into the system automatically?
It can produce candidate records, pulling product names, quantities, metrics and dates out of ordering documents into a review queue. It cannot decide what an ambiguous clause means, and that decision is where the value sits. Insist on a human confirming every entitlement against a linked source page. Treat any developer promising a fully automated pipeline as someone who has not defended an audit.
What happens if a publisher changes its licensing metric after we build?
You edit a rule and version it, which is the reason to build calculators as configurable, testable logic rather than fixed code paths. Metrics do move, and recent shifts toward per employee subscription counting caught estates that had not changed at all. Store every computed position with the rule version that produced it, so an old position stays reproducible even after the current rule has been replaced.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
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.
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.
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.
How do we migrate years of spreadsheet or Airtable data into a new internal tool?
Migration is a standard part of the build, not a separate project: the agency writes import scripts that clean, deduplicate, and map your existing rows into the new database. On typical spreadsheet and Airtable histories, Digital Heroes budgets 3 to 10 extra days, most of it spent resolving inconsistencies like the same customer spelled four different ways. The safe sequence is a trial migration first, a review of flagged conflicts with your team, then final cutover over a weekend so nobody loses a working day.
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 Kabir.
Director of Mobile Engineering · Delhi · 2 posts on the site
Published · Last updated .
