Subcontractor Prequalification Software: Buy TradeTapp, or Build the Model and the Gate?
Annual volume and entity count decide this. A single operating company under roughly $150M with a conventional trade base and no self perform work should buy: TradeTapp or COMPASS by Bespoke Metrics will do the job for a fraction of a build.
On this page
Annual volume and entity count decide this. A single operating company under roughly $150M with a conventional trade base and no self perform work should buy: TradeTapp or COMPASS by Bespoke Metrics will do the job for a fraction of a build. Past that, and certainly once you run several operating companies or joint ventures where aggregate exposure is invisible, a build starts to earn its keep at $60,000 to $130,000 for a first release. Most contractors reading this fall on the buy side, and the ones who do not usually already know it because a package default has cost them a fee.
When is off the shelf genuinely the right call here?
If you are a single operating company under roughly $150M in annual volume, with a conventional trade base and no self perform work, buy. TradeTapp is a reasonable answer, particularly if your teams already live in Autodesk Construction Cloud, and COMPASS by Bespoke Metrics does a serious job on financial analysis if that is the part you want done properly. Either costs a fraction of a build, and at that volume a build would be automating a process that has not yet strained.
Keep ISNetworld, Avetta or Highwire alongside, and do not attempt to reproduce them. They are compliance and safety qualification networks. They confirm that a contractor has submitted required documents and that their safety record clears a threshold, which is genuinely useful and frequently mandated by your own clients. Rebuilding a safety compliance network is not a project any contractor should fund. That part of the problem is not broken, and your subcontractors already maintain profiles there.
There is a third reason to buy that has nothing to do with size. If nobody internally will own the scoring model, buy. A custom system needs a risk committee willing to argue about weights once a year and to change them after a package goes wrong. Where that appetite does not exist, a configured commercial tool used properly beats a custom platform used badly, and costs far less to walk away from.
The honest test is whether a general model prices your risk closely enough. If your subcontractor base looks broadly like everybody else's, a general model built across a wide contractor population will be about as good as anything you would commission, and it arrives next month rather than next quarter.
When does a custom build actually pay off?
Two conditions do most of the work here, and both are structural rather than a matter of taste.
The first is multiple operating companies or joint ventures. Aggregate exposure is the number that causes defaults, and it is the number that lives nowhere. Individual project managers know what a subcontractor is carrying on their job. Nobody knows what that same firm is carrying across seven live jobs, three operating companies and two joint ventures, particularly when it appears under three slightly different legal names. No purchased platform resolves that for you, because it does not hold your commitment ledger.
The second is trade mix. A general scoring model represents a general view of contractor risk, and your view is not general. A curtain wall subcontractor with heavy material buyout carries different working capital pressure than a labour heavy framing subcontractor. If you self perform concrete, your concrete subcontractors are a smaller and more scrutinised group. If you build data centres, an electrical subcontractor's ability to secure gear is worth more in the model than the experience modification rate, which is a safety measure being asked to stand in for a supply chain question.
There is a third trigger that is about workflow rather than analysis. In most contractors we have worked with, prequalification produces a report while bid lists are built somewhere else: in an estimating system, in an estimator's head, or from the firms who called that week. Limits exist as numbers on a page rather than as a gate at the point of invitation. If you need the score to block an invitation inside your own estimating process, you will have to own that piece.
And there is the blunt trigger. If a package default has already cost you a fee, you know the arithmetic and this page is not telling you anything new.
How do they compare on the things that matter in this industry?
Feature grids are not much use here, because the differences that decide the outcome sit in a small number of specific places.
- Scoring model ownership. Commercial platforms compute a financial capacity score using a defensible general method. Changing how that method weights working capital against backlog to capacity, by trade, is not something you control. A build gives you weights your risk committee can argue about and change without a support ticket, which is the only way a model improves after a default.
- Aggregate exposure across entities. This is the clearest configuration ceiling. Resolving one subcontractor across three operating companies, two joint ventures and three legal name variants, then netting awarded value against billed to date and retention held, is your data problem. A vendor can hold what you type in. It cannot compute what it cannot see.
- Enforcement at the point of invitation. A purchased tool produces a status an estimator can choose to consult. A build can refuse the invitation, allow it with a flag and a named approver, or block it outright, and record which. That difference is the whole distance between analytics and a control.
- Financial statement intake. Statements arrive as audits, reviews, compilations, accounting exports and occasional scans. Extraction of the balance sheet, income statement and work in progress schedule, with the assurance level recorded, exists on both sides of this decision. Buying it is usually cheaper unless you need fields the vendor does not capture.
- Renewal cadence. Annual renewal is the shared weakness. Inside that window a subcontractor can triple its backlog, lose its largest customer or have a judgment entered. Whether you buy or build, the fix is event triggers rather than a calendar.
- Data portability. Ask any vendor how you export full history, including scores, the weights in force at scoring time, and the documents behind them. If the answer is a report rather than a data extract, you are renting your own risk history.
- Per seat and per volume economics. Subscription pricing in this category is usually tied to volume or subcontractor count, which means it grows exactly as you do. A built layer does not, which is why the comparison changes shape somewhere past $150M and again in a rollup.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience, intake, financial extraction and a configurable scoring model runs $60,000 to $95,000. A first release that adds single project and aggregate exposure limits enforced at bid invitation runs $95,000 to $130,000 and ships in ten to sixteen weeks. A full platform with construction enterprise resource planning integration, consolidated multi entity exposure, continuous monitoring and a subcontractor portal runs $150,000 to $350,000 across six to twelve months.
The two largest drivers inside those bands are predictable. Construction ERP integration costs $25,000 to $55,000 per system, and Viewpoint Vista, CMiC and Sage 300 CRE each have their own data model and access constraints, so price the platform you actually run. Multiple operating companies and joint ventures add $25,000 to $55,000, mostly in entity resolution and in supporting more than one scoring model.
On the running side, budget 15 to 18 percent of build cost a year for support and iteration, $3,000 to $8,000 for hosting of confidential financial documents, $4,000 to $10,000 for integration maintenance and $2,000 to $6,000 for extraction processing. The line most estimates omit entirely is monitoring data at $5,000 to $20,000 a year, because lien, judgment and licence feeds are paid subscriptions in their own right and they do not become free because you built the interface around them. On a $112,000 first release the all in annual figure lands near $31,000 to $50,000.
Set that against what you already spend: your subscription, any separate certificate tracking service, and twenty to forty minutes of staff time per subcontractor per renewal across several hundred firms. Then set it against the one event that decides the case, a single package default, where completion premium, schedule, stacked trade claims and lost fee together dwarf the whole programme.
What does the hybrid look like, and when is it the honest answer?
In this category the hybrid is not a compromise, it is the usual recommendation. Keep the safety network and, in many cases, keep the commercial prequalification platform. Build the two pieces neither will ever do for you: consolidated exposure across your entities, and the gate at bid invitation.
That split works because the boundaries are clean. ISNetworld or Avetta continues to hold safety qualification, and you consume its status through a feed rather than duplicating a questionnaire your subcontractors have already completed forty times. Your commercial platform, if you keep it, continues to do financial analysis. Your own layer holds the commitment ledger position per subcontractor across operating companies, applies your limits, and sits at the moment an estimator adds a firm to a bid list. That is roughly a $60,000 to $95,000 piece rather than a full platform, and it is the part that changes behaviour.
The sequencing that works is equally specific. Start with your top two trades by risk exposure and your live bid list, run the gate in advisory mode for two to three weeks so estimators see flags without being blocked, then switch enforcement on with a named override approver. Estimators who watched the gate be right for a fortnight accept the block. Estimators blocked on day one route around it, and you have bought an expensive report.
Keep self reported exposure in phase one. It is imperfect and it is enough to prove the model. Add the ERP feed once the scoring is settled.
Which should you choose, by operator size and stage?
Under roughly $150M, one operating company, conventional trades: buy. TradeTapp or COMPASS plus whichever safety network your clients require. Spend the difference on getting somebody to actually read the financial statements.
Roughly $150M to $400M, one or two entities: buy, then measure two things. Count the staff hours spent keying financial data each renewal cycle, and count how many bid invitations in the last quarter went to subcontractors whose file was more than twelve months old. If the second number is uncomfortable, build the gate and the exposure calculation only, and keep the platform you have.
Above roughly $400M, or more than one operating company: build. Consolidated exposure is the whole case and no product will assemble it. Start with the invitation gate on self reported exposure.
Private equity backed rollups, and self perform heavy contractors regardless of volume: build, and build the scoring model first. Imposing one risk standard across acquired contractors who each brought their own habits is exactly what a configured product cannot do, and a general model built across a broad contractor population is pricing a population a self perform contractor does not have.
When you are ready to turn this into a specification, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- ITIF's 2025 report documents that SMEs operate at roughly 60% of large-firm productivity in advanced economies (citing McKinsey), that CRM platforms deliver a 25-40% improvement in customer retention and a 15-30% boost in sales, and that digital advertising returns about $8 in profit per dollar spent on Google Search and Ads. Source: Information Technology and Innovation Foundation (ITIF) (2025) →
- Salesforce research indicates sales reps spend only about 30% of their time actively selling, with much of the rest lost to administrative work including manual CRM data entry and updates. Source: Salesforce (2024) →
- Only about 30% of digital transformations succeed at meeting their objectives, but getting six critical success factors in place (leadership commitment, talent, agile culture, progress monitoring, clear strategy, and a modernized platform) raises the odds of success from 30% to 80%. Source: Boston Consulting Group (BCG) (2020) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
Frequently asked questions
Is TradeTapp or COMPASS enough, or should we build?
For a single operating company under roughly $150M in annual volume with a conventional trade base, they are a sensible buy and reproducing them is a poor use of capital. COMPASS in particular does serious financial analysis.
They strain in three situations: when your trade mix means a general scoring model misprices your real risk, when several operating companies and joint ventures need consolidated exposure that no vendor can see, and when you need the score to block an invitation inside your own estimating workflow rather than sit in a separate portal.
What does it cost to switch away from our prequalification platform later?
The cost is almost entirely in the subcontractor population, not the data. Your firms have profiles, uploaded statements and completed questionnaires in the incumbent, and asking several hundred of them to redo that work is the expensive part and the part they resent.
Reduce it by asking, before you sign or renew, exactly how you extract full history: scores, the weights in force when each score was calculated, and the source documents. If the answer is a formatted report rather than a data extract, price a migration into your decision now rather than discovering it in year three.
What happens if the incumbent changes its pricing model?
Pricing in this category is usually tied to annual volume or approved subcontractor count, which means it grows exactly as you do. Model it against your projected volume in three years rather than today's, because that projection changes the answer more than any single price rise.
The practical protection is not a contract clause, it is holding your own scoring history and exposure calculation. Once those live in a system you own, a repricing becomes a commercial decision rather than a hostage situation, because what you would be leaving behind is a questionnaire rather than your risk model.
How long does a custom prequalification build take?
Ten to sixteen weeks for a first release covering intake, extraction, your scoring model and single plus aggregate limits enforced at bid invitation. A full platform with ERP integration, multi entity exposure, monitoring and a subcontractor portal phases across six to twelve months.
Adoption depends on sequence more than duration. Two to three weeks of advisory mode where estimators see flags without being blocked, then enforcement with a named override approver. Historic file migration runs in the background behind the live system rather than gating go live.
Do we still need ISNetworld if we build?
Almost certainly yes, and that is the right architecture rather than a failure of the build. ISNetworld, Avetta and Highwire answer a compliance and safety question, they answer it well, and many of your clients contractually require one of them.
They are not answering whether a firm has the working capital and bonding headroom to carry your $12M package through a six month cash gap. Consume their status through a feed, budget $12,000 to $25,000 for that integration, and spend your build money on the question nobody else is answering.
Can we build only the bid invitation gate and keep everything else?
Yes, and for a lot of contractors it is the right first move. The gate plus the exposure calculation is the smallest piece that changes behaviour, because it is the only part that can refuse an action rather than describe one.
Run it on self reported exposure to start with. That is imperfect and it is enough to prove whether your estimators will work inside a gate at all, which is the real risk in this project. Add the ERP feed and the full scoring model once you have a quarter of real invitations behind you.
How much does construction ERP integration add?
Budget $25,000 to $55,000 per system. Viewpoint Vista, CMiC and Sage 300 CRE each carry their own data model, access constraints and upgrade cadence, so price the specific platform you run rather than assuming a generic connector exists.
It matters because without live commitment and billing data, aggregate exposure depends on project managers maintaining a spreadsheet, and in our experience that stops around month three no matter how well the rollout was communicated. Budget $4,000 to $10,000 a year afterwards, since ERP vendors revise their interfaces on their own schedule.
Our risk manager already knows which subcontractors are shaky. Why build anything?
Because that judgement is usually good, and it is unwritten, unauditable and it leaves when they do. It also does not scale to a bid list of sixty invitations across eleven trades on a job that person has never worked.
A build does not replace the judgement, and any developer who claims it predicts defaults is selling you something. It writes the judgement down as weights, applies it consistently, and puts the limit at the point of invitation instead of in a report nobody opens. If your risk manager will not sit through the argument about weights, buy instead.
Will a custom internal tool scale as our company grows?
Yes, provided it sits on a standard stack with a real database: PostgreSQL comfortably handles millions of records, and adding users costs hosting pennies rather than per-seat fees. The real scaling risks are organizational, not technical: new departments want features, processes change, and the tool needs a budget line to evolve. Set aside a small quarterly improvement budget instead of treating launch as the finish line, and the tool stays useful for a decade rather than getting rebuilt every two years.
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.
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.
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.
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.
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.
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.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
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 Sofia.
Senior Brand Identity Designer · New-york · 5 posts on the site
Published · Last updated .
