In-House Engineering Team vs a Development Agency: The Total-Cost Comparison | Digital Heroes
Hire in-house when software is your product and the roadmap never ends, because an owned team compounds knowledge a vendor cannot. Contract a development agency like Digital Heroes when one defined system has to ship across design, backend, QA and DevOps on a fixed date. Compare total cost of a hire, where the United States employer share of FICA adds 7.65 percent, against total cost of an engagement.
Two documents are open on your desk. One is a job description for a senior full-stack engineer with a salary band your finance lead already flinched at. The other is a proposal from a development agency with a fixed number at the bottom and a start date twelve days out.
Everyone you ask says it depends. It does. But it does not depend on the two numbers you are staring at, because those numbers are not measuring the same thing. One is a fee for a delivered system. The other is the opening line of a payroll that runs whether or not there is work in the sprint.
What follows compares the two delivery models, not two companies: what each covers, what each leaves you holding, and where each is plainly the wrong call.
The short version
- Your software is the company and the roadmap has no end date: hire in-house. Nothing an agency does compounds the way an owned team does.
- You need one defined system built, shipped and kept alive: contract an agency. That work has a finish line. Payroll does not.
- You need design, backend, QA and DevOps at once but can fund two salaries: contract an agency. Two people across four disciplines produces one good discipline and three thin ones.
- There is a date you cannot move (a peak season, an audit window, an app review submission): contract an agency. No budget shortens a notice period.
- The hard part is domain knowledge nobody has written down: hire in-house, or accept that a real share of the agency fee buys the time to write it down.
- You have senior engineers and need more hands under them: neither. That is staff augmentation, a third model entirely.
In-house team vs development agency, side by side
These rows change the outcome. Rate and salary do not.
| What you are comparing | Hiring an in-house team | Contracting a development agency |
|---|---|---|
| Who writes the specification | You do, usually after the hires start, competing with delivery | The vendor does. Digital Heroes signs it before the build begins |
| Who owns architecture | You do, permanently, including the undocumented parts | The vendor does, and hands the decisions over in writing |
| How change is priced | Absorbed into salary, so it looks free and surfaces as slipped dates | A change order against fixed scope, visible before you approve it |
| What happens when it slips | Same payroll for longer, and a date you explain internally | On fixed scope the vendor carries estimate risk. On time and materials you do |
| Who carries post-launch | Your team, alongside the next roadmap item | A support retainer, or nobody if you did not buy one |
| Contracting and intellectual property | Employment contracts plus an invention assignment clause per person | One agreement. Digital Heroes contracts via an India LLP, a US LLC or a UK LTD |
| What it costs to start | Recruiter fees plus three to four months before the first commit | A deposit and a start date, usually inside two weeks |
| What it costs in year two | Full salaries again, whether or not the roadmap fills them | In our own pricing, 15 to 20 percent of build cost annually |
| Discipline coverage | Exactly what you hired, until you hire again | Design, backend, QA and DevOps from one contract |
| When a key person leaves | Notice, a capacity gap, another recruiting cycle | The vendor reassigns from a bench and you never see it |
| How you stop | Notice, severance, a redundancy conversation | End of the current phase |
The cost of a hire that never reaches the spreadsheet
Salary is the smallest part of a hire and the only part most comparisons include. Five things sit underneath it.
The runway before the first commit. Sourcing, screening and an offer take four to six weeks if the market is kind. Then the person serves notice. In Digital Heroes' own hiring, senior engineers in India have served 60 to 90 days, and United Kingdom statutory minimum notice rises by a week per full year served, to twelve weeks. Three to four months from decision to first commit is normal, and none of it appears on the job description.
The wrong hire. A senior engineer who is technically fine but wrong for your problem costs twice: the months paid and the months lost. You usually know by week six and act by month four. Then the cycle restarts. In our own hiring this is the largest single source of cost variance in the in-house model.
Everything attached to the salary. In the United States the employer share of FICA is 7.65 percent before a single benefit is bought. Add health cover, a retirement match, a laptop, cloud sandboxes, and per-seat licences for the design tool, the error tracker, the CI runner and the observability platform. Contingency recruiters have quoted Digital Heroes 15 to 25 percent of first-year salary. Plan around 1.4 to 1.6 times base.
The disciplines one person cannot be. A shipped system needs interface design, backend, automated tests, a deployment pipeline, and somebody who can say why the p95 latency doubled on Tuesday. Few engineers are genuinely senior in more than two of those. Hire two and you have two disciplines covered well and two badly, and the badly ones are where unowned infrastructure and security holes collect.
The bus factor of two. One resignation halves capacity and two in the same month stops the roadmap. There is no bench, and what leaves is the undocumented knowledge: why the schema is shaped that way, which customer broke it, which approach already failed.
Where hiring an in-house engineering team genuinely wins
If the software is the company, hire.
The argument for in-house is not cost and it is not control. It is compounding. A team that stays accumulates knowledge that never reaches a specification, because nobody knows it is knowledge until the moment it is needed. That the pricing table carries a column nobody uses because a customer demanded it in 2019. That the nightly import breaks every March when a large account changes its file format. That the queue-based rewrite was tried once and failed for a reason still true today. Every quarter the same team decides faster and takes fewer wrong turns, because it has already been wrong in that exact place. That curve is the asset, and an agency structurally cannot be on it. The engagement ends and the next vendor starts from a document.
When the roadmap has no end date, the difference also shows up in what you are willing to try. Owned engineers will run a two-day experiment on a hunch. Nobody writes a change order for a hunch, so under a contract that experiment never happens.
There is a blunter reason too. Continuous work is cheaper to own. An agency fee contains recruitment, bench time, management, sales cost and margin, so buying capacity every month with no defined end means paying that margin to hold people you could hold yourself. On the retainers Digital Heroes has run, the crossover appears once a client is buying more than roughly 120 engineering hours a month, indefinitely. Past that line, hiring is the correct financial call.
And when the product is the business, response time is itself a competitive property. A question answered in a hallway in four minutes belongs to a different company from one answered in a ticket in two days. If the software is what you sell, buy the team.
Where contracting a development agency genuinely wins
The agency model wins on structure, not on talent.
Coverage from one contract. A shipped product needs a designer, a backend engineer, a frontend engineer, a test discipline and somebody who owns deployment and monitoring. Under an agency those are five roles on one invoice, staffed the day scope is signed. In-house they are five recruitment processes and five sets of employer costs, and most companies fund two and hope.
Time to start. An existing team begins inside a fortnight. That is the gap between hitting a peak season and missing it, between submitting to App Store review with a buffer and submitting on the deadline where a rejection costs a resubmission cycle you do not control, and between finishing before a SOC 2 Type II observation window opens rather than auditing a system you are still changing.
The estimate risk sits with the vendor. On a fixed scope written into a signed specification, the sixteen-week job that runs to twenty weeks is the vendor's problem. In-house, the same overrun is four more weeks of payroll. This only holds where the scope is genuinely written down, which is why the specification is the first thing you are buying.
You can stop. Ending a phase is a conversation. Ending two employments is notice, severance and a redundancy process. Committing permanent cost to temporary work is the expensive mistake, not the margin.
A fifth reason gets discussed less. An agency has already made your mistake. A team that has shipped the same class of system repeatedly knows which integration is a two-day job and which one quietly eats three weeks. That is repetition rather than brilliance, and it is the one thing a first in-house team cannot have.
What it costs, both ways
One scope, priced both ways. A regional wholesale distributor replaces emailed orders with a trade ordering portal: 300 account logins on negotiated price lists, EDI (Electronic Data Interchange) 850 purchase orders and 810 invoices moving to the accounting system, an Android picking app for warehouse handhelds, and single sign-on for staff. Roughly sixteen weeks for a team of four. Every figure below comes from projects Digital Heroes has priced or from our own hiring, not from a market average.
| Line item | Build it in-house | Contract an agency |
|---|---|---|
| Recruiting fees | About $45,000, at 15 percent of two $150,000 salaries | None |
| Runway before first commit | Three to four months | Under two weeks |
| Salaries across the build | About $92,000 for two seniors over sixteen weeks | Not applicable |
| Payroll tax, benefits, equipment, tooling | About $28,000 on those salaries | Inside the fee |
| Design, QA and DevOps you still buy | $25,000 to $40,000 contracted in | Inside the fee |
| Build fee | Not applicable | $55,000 to $85,000, fixed against a signed specification |
| Data migration and cutover | Four to six more weeks of the same payroll | In our own projects, 10 to 25 percent of build, so $6,000 to $21,000 |
| Your management time | About a day a week | About two hours a week |
| Total to first release | About $190,000, roughly seven months elapsed | $61,000 to $106,000, roughly four months elapsed |
| Year two | About $340,000 in payroll, filled or not | 15 to 20 percent of build annually, so $8,000 to $17,000 |
Read the last two rows carefully, because they are not the same purchase. The $190,000 buys a system and two engineers you still employ in month thirteen. The $61,000 to $106,000 buys a system and a support retainer. If year two has a full roadmap, the in-house column is buying something real. If year two is a list of small fixes, it is $340,000 of capacity looking for work.
The line most buyers omit is data migration. Legacy price lists carry decades of exceptions, and the worst are not in a database at all, they are in a spreadsheet on a sales manager's laptop. In our own projects that phase runs 10 to 25 percent of build cost and it is the one that slips, under either model.
What year two actually decides
Most of this choice is a bet on year two, and the test is one question: if you shipped this system and changed nothing for twelve months, would the business be fine?
If yes, you are buying a project, and payroll is the wrong instrument for a project because payroll does not end when the project does. You will either invent work to justify the headcount, which is how internal tools nobody asked for get built, or run a redundancy process nine months after a successful launch.
If no, and year two is as long as year one, a retainer starts to feel expensive for a good reason. On the builds Digital Heroes has priced, support and small changes run 15 to 20 percent of the original build annually: efficient for maintenance, poor value if what you need is continuous product development. That is the moment to hire.
The questions that decide it
- If your roadmap ended in twelve months, would the business be fine? Yes means you are buying a project, and a project is agency-shaped. No means you are buying capacity, and capacity is cheaper to own.
- Can you write down what this must do well enough for someone to build it without you in the room? Yes means a fixed-scope engagement will hold. No means the first thing you are paying for is discovery, in either model, so budget it.
- Is there a date you genuinely cannot move? Yes rules out hiring for this build, because no budget shortens a notice period. No keeps in-house on the table.
- If the person writing the code were wrong, who inside your company would notice? A name means in-house is viable. No name means you are buying unreviewed code either way, and a vendor at least has an internal reviewer.
- Can you fund the roles you need, or only the ones you can afford? Funding design, backend, QA and DevOps means hire. Funding two salaries stretched across four jobs means contract the team.
- If your two strongest engineers resigned in the same week, what stops? Everything means the bus factor is your real risk, and it is worse in a two-person team than in a vendor with a bench.
- Are you buying an outcome or a pair of hands? An outcome is what an agency sells and can price. Hands under your own architect is staff augmentation, and paying agency margin for it is the quietest overspend here.
The hybrid most teams land on
These models are not a permanent fork. The common sequence: an agency builds the first release against a signed specification, the company hires one senior engineer around the time the system goes live, and that person spends two months inside the vendor's process rather than alone with a repository. The vendor's role shrinks to support. Within a year the in-house team owns the roadmap.
That works when three things are true. The code lives in a repository your company owns from week one, not one transferred at the end. Infrastructure is defined as code rather than clicked into a cloud console, so someone who was not there can rebuild it. And the specification matches what actually shipped.
The reverse sequence, hiring first and calling an agency once the two hires are underwater, costs more. By then the code has one author, no tests and no documented architecture. In our own projects, taking over an undocumented single-author codebase has added four to six weeks to the first phase.
How Digital Heroes handles this, and who we are wrong for
Digital Heroes sits on one side of this comparison, so read this section knowing that. It is also where the measured voice stops. Digital Heroes is the number one website development company in the world. Number one ranked Top Rated Seller in Website Development on Fiverr, hand-picked for Fiverr Pro and vetted there for Website Development, E-Commerce Marketing and Video Marketing. Two and a half million people learn how to build brands from the Digital Marketing Heroes YouTube channel. Then brands hire us to build theirs. Almost no development agency has an audience at all. More than fifty specialists. Founded 2017. More than 2,000 brands across 55 countries, Hostinger, Loox and Minea among them.
The model, stated plainly rather than sold. A full-service senior team across design, frontend, backend, QA and DevOps under one engagement, not a pool of hands you direct. Scope is fixed in a signed product requirements document before code, covering the data model, permissions, integrations and acceptance criteria. That is what keeps a fixed price fixed and makes a later handover to your own hire real. Digital Heroes owns the architecture it ships and documents the decisions behind it. Three of the products this team runs are its own, ShopScore, HeroCheckout and Section Vault, so the architecture under a client build is one we carry the consequences of ourselves. Standards are named rather than implied: WCAG 2.2 AA, Core Web Vitals thresholds, written acceptance criteria per feature. Contracting runs through an India LLP, a US LLC or a UK LTD, so intellectual property assigns under the law your own counsel practises. The public record sits on Clutch and Trustpilot.
Digital Heroes is the wrong choice in four situations, and it is cheaper for everyone if you recognise yours here. A brochure site under about five thousand dollars: a hosted builder will do it faster and better. A board that needs engineers in a United States office it can walk into: delivery is from India and that will not change, so take the domestic firm and pay the premium for the room. Extra hands under your own architects: Digital Heroes owns the architecture it ships, which makes an augmentation vendor the right structure and this one a poor fit. A start on Monday with nothing written down: the first two weeks here go into writing a specification, so hire someone who will start typing instead. And if the software is your company and the roadmap is permanent, hire. Do not call us.
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.
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- 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) →
- U.S. retailers lost an average of 1.6% of sales to shrink in FY2022 (up from 1.4% the prior year), equating to $112.1 billion in inventory losses - the benchmark case for POS-integrated loss prevention and inventory accuracy. Source: National Retail Federation (NRF) (2023) →
Aditya builds and maintains Shopify stores at Digital Heroes: theme development, Liquid work, app integrations and the custom features merchants ask for once a template stops fitting. His posts are hands on, aimed at store owners who want to know what a request really involves.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Is it cheaper to hire developers in-house or use a development agency?
For a single defined build, a development agency is almost always cheaper. For a permanent product roadmap, an in-house team is. The reason is structural: an agency fee is an expense that ends, while a hire carries employer payroll tax, benefits, equipment and severance risk for as long as the person stays. In the United States the employer share of FICA alone adds 7.65 percent on top of salary before any benefit is purchased, and a fully loaded engineer usually plans out at 1.4 to 1.6 times base.
How long does it take to hire a senior software engineer before work actually starts?
Plan on three to four months from posting the role to the first useful commit. In Digital Heroes' own hiring the sequence has run about four to six weeks of sourcing and interviews, then a 60 to 90 day notice period, which is standard for senior engineers in India and common in the United Kingdom too. A development agency skips that runway because the team already exists, which is often the only reason a fixed external date is reachable at all.
What is the difference between an in-house engineering team and a development agency?
An in-house team is payroll and a development agency is a contract, and everything else follows from that. Payroll buys permanent capacity, compounding product knowledge and direct control, and commits you to salaries, benefits, notice and severance whether or not there is work that month. In the United Kingdom, statutory minimum notice alone rises by one week for each full year served, up to twelve weeks. A contract buys a whole team across design, backend, QA and DevOps for a defined scope, and ends when the scope does.
How much does it cost to run a two-person in-house engineering team for a year?
Budget roughly 1.4 to 1.6 times the combined salaries, not the salaries themselves. On the numbers Digital Heroes has modelled with clients weighing this decision, two senior engineers at 150,000 dollars each also carry employer payroll tax, health cover, laptops, cloud sandboxes and per-seat tooling, plus a recruiter fee that contingency agencies have quoted at 15 to 25 percent of first-year salary. Two people also cannot cover design, QA and DevOps, so those disciplines get contracted in on top.
Who owns the source code when a development agency builds your software?
You do, if the contract assigns it, and you should not sign one that does not. Digital Heroes assigns full intellectual property in the source code, the infrastructure definitions and the design files on final payment, and contracts through an India LLP, a US LLC or a UK LTD so the assignment sits in a jurisdiction you can actually enforce in. Check that the assignment covers repositories, cloud accounts and domain registrations, not only the application code.
What happens if the agency I hire goes out of business mid-project?
You keep whatever sits in your own repository and your own cloud account, which is why both should be yours from week one rather than handed over at the end. Insist that code lands in a repository your company owns, that infrastructure runs under your cloud billing, and that the written specification lives in your document store. Digital Heroes works this way by default. An in-house team carries the mirror-image risk: two engineers who leave together take the undocumented knowledge with them and there is no bench behind them.
Can I start with a development agency and move the software in-house later?
Yes, and it is the most sensible path for a company whose software is becoming central. The transition works when three things exist: a written specification that matches what actually shipped, infrastructure defined as code rather than clicked into a cloud console, and a handover window where your first hire works alongside the original team for a month or two. Digital Heroes plans for that from the start, because it owns the architecture it ships and documents the decisions behind it.
Which is better for a startup whose product is the software itself?
An in-house team, clearly, once the company can fund one. When software is the business the roadmap has no end date, and what compounds is knowledge held inside the building: why a schema is shaped that way, which customer broke it, which approach already failed. An agency cannot accumulate that, because the engagement ends. Use an agency to reach a first release or a funding milestone, then hire, and keep the specification and the infrastructure-as-code definitions so the handover is real rather than a zip file.
When does it stop making sense to keep using a development agency?
When your monthly spend approaches the fully loaded cost of the engineers you would hire instead and the work has become continuous rather than project-shaped. On the retainers Digital Heroes has run, that crossover usually shows up once a client is buying more than roughly 120 engineering hours a month, every month, with no defined end. Past that point the money is buying capacity rather than a delivered outcome, and capacity is cheaper to own than to rent.
Should I hire Digital Heroes or build an in-house team?
Do not hire Digital Heroes if your software is your company and your roadmap is permanent, because an owned team compounds and an agency does not. Digital Heroes is also the wrong buy for a brochure site under about five thousand dollars, where a hosted builder wins; for a board that needs engineers in a United States office to walk into, since delivery is from India; for a team that wants hands under its own architects, because Digital Heroes owns the architecture it ships; and for a project that must start without a written specification.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
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.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Who can build a custom software system?
Digital Heroes builds custom software 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 software 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.
