{"id":5845,"date":"2026-11-19T13:46:00","date_gmt":"2026-11-19T16:46:00","guid":{"rendered":"https:\/\/nextage.com.br\/blog\/?p=5845"},"modified":"2026-11-19T13:46:00","modified_gmt":"2026-11-19T16:46:00","slug":"technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board","status":"publish","type":"post","link":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/","title":{"rendered":"Technical Debt: How to Quantify It in Financial Terms and Present It to the Board"},"content":{"rendered":"<p dir=\"ltr\">Technical debt is the future cost of rework that a company takes on when it chooses a faster or simpler solution today instead of a more durable one. For the CTO who needs budget, explaining the concept is rarely the hard part. The hard part is translating it into the language of the people who decide: money, deadlines, risk and return.<\/p>\n<p dir=\"ltr\">This guide proposes a method for that translation: separate the cost of fixing the debt (the principal) from the cost of living with it (the interest), calculate both with your own company\u2019s data, and take the numbers to the board with a clear decision to ask for. It is useful for CTOs and CIOs, for the IT manager who prepares the material, and for the CFO who will evaluate it.<\/p>\n<p dir=\"ltr\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5846\" src=\"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-scaled.avif\" alt=\"Technical debt: man in a white shirt, in a dark room at night, holding printed pages and looking intently at a growing blue bar chart on a monitor.\" width=\"2560\" height=\"1709\" srcset=\"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-scaled.avif 2560w, https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-300x200.avif 300w, https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-1024x683.avif 1024w, https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-768x513.avif 768w, https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-1536x1025.avif 1536w, https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-2048x1367.avif 2048w, https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-150x100.avif 150w, https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-330x220.avif 330w, https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-420x280.avif 420w, https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-1-510x340.avif 510w\" sizes=\"auto, (max-width: 2560px) 100vw, 2560px\" \/><\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">What is technical debt?<\/h2>\n<p dir=\"ltr\">Technical debt is the accumulation of shortcuts, temporary fixes and design decisions that make every future change slower, more expensive or riskier. As with a financial debt, there is a principal (the effort to fix it) and there is interest (the extra effort paid on every change while the problem remains).<\/p>\n<p dir=\"ltr\">The metaphor helps the CFO, but it has a limit: technical debt has no contract, no maturity date and no fixed rate. Interest varies with how often the affected code is changed. A problematic module that nobody touches costs little; the same problem at the core of the order system costs a lot every month.<\/p>\n<p dir=\"ltr\">Nor is every debt a mistake. Martin Fowler\u2019s <a href=\"https:\/\/martinfowler.com\/bliki\/TechnicalDebtQuadrant.html\" target=\"_blank\" rel=\"noopener\">technical debt quadrant<\/a> uses two axes: debt can be deliberate or inadvertent, prudent or reckless. Taking a conscious shortcut to meet a market deadline, with a plan to fix it, is prudent debt (a business decision). Shipping poor code through lack of knowledge or care is reckless debt. The distinction matters because it guides what to pay first.<\/p>\n<p dir=\"ltr\">It is also worth separating technical debt from legacy systems. A system can be old and healthy, or new and already indebted. \u201cLegacy\u201d describes age and technology; \u201cdebt\u201d describes the accumulated cost of changing what exists.<\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">Why should the board care about technical debt?<\/h2>\n<p dir=\"ltr\">The board should care because technical debt consumes delivery capacity: part of the budget and of the team\u2019s hours stops producing new products and goes to maintaining what already exists. It is a recurring cost, invisible in financial reports, that limits how fast the company can respond to the market.<\/p>\n<p dir=\"ltr\">The available numbers are international and, in large part, based on perception; they give an order of magnitude, not a target for your company. In a July 2020 survey of 50 CIOs at financial services and technology companies with revenue above US$ 1 billion, <a href=\"https:\/\/www.mckinsey.com\/capabilities\/operations\/our-insights\/tech-debt-reclaiming-tech-equity\" target=\"_blank\" rel=\"noopener\">McKinsey<\/a> reported that executives estimated technical debt at 20% to 40% of the value of their entire technology estate (before depreciation). In the same survey, 10% to 20% of the technology budget set aside for new products was diverted to resolving debt issues.<\/p>\n<p dir=\"ltr\">At the developer level, the <a href=\"https:\/\/stripe.com\/files\/reports\/the-developer-coefficient.pdf\" target=\"_blank\" rel=\"noopener\">Developer Coefficient<\/a> report, commissioned by Stripe in 2018, found that in a 41.1-hour week respondents spent on average 13.5 hours on technical debt and 3.8 hours on bad code: 17.3 hours, or about 42% of their time. These are hours reported by the developers themselves, not measured.<\/p>\n<p dir=\"ltr\">At the macro level, <a href=\"https:\/\/www.it-cisq.org\/press-releases\/12-06-22\" target=\"_blank\" rel=\"noopener\">CISQ<\/a> estimated the cost of poor-quality software in the United States at US$ 2.41 trillion in 2022, of which about US$ 1.52 trillion would correspond to accumulated technical debt. This is a national estimate, sponsored by vendors, and should not be applied to a single company.<\/p>\n<p dir=\"ltr\">What the sources have in common: the cost exists, it is relevant, and it rarely appears under its own name in the budget. <a href=\"https:\/\/www.mckinsey.com\/capabilities\/mckinsey-digital\/our-insights\/demystifying-digital-dark-matter-a-new-standard-to-tame-technical-debt\" target=\"_blank\" rel=\"noopener\">McKinsey recommends<\/a> giving the CEO and the board transparency on the real cost, with the CFO and the CIO agreeing on priorities. That is exactly what the rest of this article helps you do.<\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">What types of technical debt exist, and what should you pay first?<\/h2>\n<p dir=\"ltr\">Technical debt is not limited to code. It falls into six main types: code, architecture, dependencies, tests, infrastructure and documentation. To decide what to pay first, combine two criteria: how often the affected area is changed, and where the debt sits in Fowler\u2019s quadrant.<\/p>\n<ul dir=\"ltr\">\n<li><strong>Code:<\/strong> duplication, long and complex functions, business rules scattered around (known as <em>code smells<\/em>).<\/li>\n<li><strong>Architecture:<\/strong> excessive coupling, modules that cannot be changed without affecting others, decisions that limit scale.<\/li>\n<li><strong>Dependencies:<\/strong> outdated libraries, frameworks and platforms, or ones without support, with security risk.<\/li>\n<li><strong>Tests:<\/strong> low coverage, fragile or manual tests; every change becomes a bet.<\/li>\n<li><strong>Infrastructure:<\/strong> manual deployment, environments that differ from each other, no automation.<\/li>\n<li><strong>Documentation:<\/strong> knowledge that exists only in the heads of a few people.<\/li>\n<\/ul>\n<p dir=\"ltr\">A practical rule: reckless debt in frequently changed code comes first, because the interest is high and the cause tends to repeat. Prudent debt in rarely changed code can wait, because the interest is low. Paying everything at once is almost never feasible or necessary.<\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">How do you quantify technical debt in financial terms?<\/h2>\n<p dir=\"ltr\">To calculate technical debt in money, separate the principal (the cost of eliminating the debt) from the interest (the annual cost of living with it) and compare the two. Interest has three components: extra maintenance hours, incident costs and the cost of delayed deliveries. All of them can come from data the company already has.<\/p>\n<p dir=\"ltr\"><em>Method proposed by NextAge (an editorial proposal, not a market standard):<\/em><\/p>\n<div dir=\"ltr\">\n<table>\n<thead>\n<tr>\n<th scope=\"col\">Component<\/th>\n<th scope=\"col\">What it measures<\/th>\n<th scope=\"col\">Internal data source<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Principal<\/td>\n<td>Effort to eliminate the debt (hours \u00d7 fully loaded hourly cost)<\/td>\n<td>Team estimate, supported by static analysis when available<\/td>\n<\/tr>\n<tr>\n<td>Maintenance interest<\/td>\n<td>Extra hours spent each month working around the debt<\/td>\n<td>Time tracking, rework tags on tickets<\/td>\n<\/tr>\n<tr>\n<td>Incident cost<\/td>\n<td>Incidents attributable to the debt \u00d7 average cost per incident<\/td>\n<td>Incident log, lost revenue, response hours<\/td>\n<\/tr>\n<tr>\n<td>Cost of delay<\/td>\n<td>Deliveries postponed because of the debt \u00d7 monthly value of the delivery<\/td>\n<td>Roadmap, business estimate with the user area<\/td>\n<\/tr>\n<tr>\n<td>Risk (optional)<\/td>\n<td>Exposure from unsupported or vulnerable components<\/td>\n<td>Dependency inventory, risk analysis<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p dir=\"ltr\">The two central formulas are:<\/p>\n<p dir=\"ltr\"><strong>Annual interest = (H_extra \u00d7 C_hour \u00d7 12) + (N_inc \u00d7 C_inc) + (D_deliveries \u00d7 V_monthly)<\/strong><\/p>\n<p dir=\"ltr\">Where H_extra is the extra maintenance hours per month, C_hour is the fully loaded hourly cost (salary, charges and overhead), N_inc is the number of incidents per year attributable to the debt, C_inc is the average cost per incident, D_deliveries is the total months of delay accumulated across deliveries, and V_monthly is the monthly value of a delivery.<\/p>\n<p dir=\"ltr\"><strong>Payback (months) = Principal \u00f7 (Avoided interest \u00f7 12)<\/strong><\/p>\n<p dir=\"ltr\">Payback tells you in how many months the investment to pay off the debt is recovered by the interest that stops being charged. One essential caution: do not assume 100% of the interest will be avoided. Use ranges (a conservative scenario and a likely scenario) instead of a single number.<\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">Worked example: how much does a technical debt cost? (hypothetical figures)<\/h2>\n<p dir=\"ltr\">The example below is hypothetical, created to illustrate the method; it does not represent client or market data. Values are in Brazilian reais (R$). Consider a legacy order system maintained by a team of 8 developers, with a fully loaded hourly cost of R$ 120.<\/p>\n<div dir=\"ltr\">\n<table>\n<thead>\n<tr>\n<th scope=\"col\">Item<\/th>\n<th scope=\"col\">Assumption<\/th>\n<th scope=\"col\">Value<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Maintenance interest<\/td>\n<td>8 people \u00d7 8 h per week \u00d7 52 weeks \u00d7 R$ 120<\/td>\n<td>R$ 399,360 per year<\/td>\n<\/tr>\n<tr>\n<td>Incident cost<\/td>\n<td>6 incidents per year \u00d7 R$ 25,000<\/td>\n<td>R$ 150,000 per year<\/td>\n<\/tr>\n<tr>\n<td>Cost of delay<\/td>\n<td>3 deliveries postponed by 2 months each \u00d7 R$ 40,000 per month<\/td>\n<td>R$ 240,000 per year<\/td>\n<\/tr>\n<tr>\n<td><strong>Total interest<\/strong><\/td>\n<td>Sum of the three<\/td>\n<td><strong>R$ 789,360 per year<\/strong><\/td>\n<\/tr>\n<tr>\n<td>Principal<\/td>\n<td>7,500 hours \u00d7 R$ 120<\/td>\n<td>R$ 900,000<\/td>\n<\/tr>\n<tr>\n<td>Avoided interest (60% scenario)<\/td>\n<td>60% of R$ 789,360<\/td>\n<td>R$ 473,616 per year<\/td>\n<\/tr>\n<tr>\n<td>Payback<\/td>\n<td>R$ 900,000 \u00f7 (R$ 473,616 \u00f7 12)<\/td>\n<td>about 23 months<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p dir=\"ltr\">How to read it for the board: in this example, the debt costs almost R$ 800,000 per year in interest; paying it off entirely would require R$ 900,000 and would pay for itself in a little under two years, in the 60% avoided-interest scenario.<\/p>\n<p dir=\"ltr\">There is also a didactic conclusion: paying everything at once can have a long payback. Prioritizing the modules with the highest ratio between interest and principal shortens the period, because the return arrives sooner. If, in this same system, 20% of the code concentrated most of the interest, attacking only that slice could deliver a much shorter payback. That is the argument CFOs tend to value: staged investment with measurable return.<\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">Where do you get the data to calculate technical debt?<\/h2>\n<p dir=\"ltr\">The data comes from four sources: time tracking, tickets and incidents, the roadmap and static code analysis. None requires a new tool to get started; what matters is tagging rework consistently and agreeing with the business on the value of delayed deliveries.<\/p>\n<ul dir=\"ltr\">\n<li><strong>Time tracking:<\/strong> create a tag for rework and maintenance caused by known problems; add it up by month.<\/li>\n<li><strong>Tickets and incidents:<\/strong> record the root cause and classify the ones attributable to debt; use the average response cost and, where available, lost revenue.<\/li>\n<li><strong>Roadmap:<\/strong> list the deliveries that were postponed or became more expensive, and ask the user area for an estimate of each one\u2019s monthly value.<\/li>\n<li><strong>Static analysis:<\/strong> tools such as SonarQube estimate the effort to fix maintainability issues. According to the <a href=\"https:\/\/community.sonarsource.com\/t\/how-does-technical-debt-being-calculated\/38455\" target=\"_blank\" rel=\"noopener\">documentation cited by Sonar\u2019s support team<\/a>, technical debt is the estimated effort to fix those issues, and the debt ratio is the remediation cost divided by the development cost. There is an important limit: the measurement covers debt in code, not in architecture, infrastructure or dependencies.<\/li>\n<\/ul>\n<p dir=\"ltr\">A good practice is to combine the team\u2019s estimate (which knows the context) with automated measurement (which provides consistency).<\/p>\n<p dir=\"ltr\">When operations are supported by a partner, part of this data already exists. In NextAge\u2019s <a href=\"https:\/\/nextage.com.br\/en\/services\/application-managed-services\/\" target=\"_blank\" rel=\"noopener\">Application Managed Services<\/a>, for example, one third of the contracted package is dedicated to monitoring, technical governance and tracking of operational indicators, which can feed the calculation of incidents and rework hours.<\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">How do you present technical debt to the board?<\/h2>\n<p dir=\"ltr\">Present technical debt to the board as an investment decision: start with the business impact, show the current cost (the interest), present options with consequences and ask for a specific decision. Avoid opening with code quality; the board decides based on results, risk and timing.<\/p>\n<p dir=\"ltr\"><a href=\"https:\/\/www.cio.com\/article\/3614037\/how-to-talk-to-your-board-about-tech-debt.html\" target=\"_blank\" rel=\"noopener\">CIO.com<\/a> recommends opening the conversation with business outcomes rather than technical details, and bringing the board three options with their consequences. Building on that idea, NextAge proposes a five-step script (an editorial proposal):<\/p>\n<ol dir=\"ltr\">\n<li><strong>Start with the effect on the business.<\/strong> Use a sentence such as: \u201cToday, X% of the team\u2019s capacity goes to maintaining what already exists, which delays Y deliveries in this year\u2019s plan.\u201d<\/li>\n<li><strong>Show the current cost in money.<\/strong> Present annual interest as a range (conservative and likely), with the assumptions in view.<\/li>\n<li><strong>Present three options with consequences.<\/strong> Do not pay (and what happens to interest and risk), pay partially (prioritizing the highest return) and pay in full (with the corresponding payback).<\/li>\n<li><strong>Show the risk.<\/strong> Unsupported components, vulnerabilities and dependence on key people that can turn into an incident with financial or regulatory impact.<\/li>\n<li><strong>Ask for a decision.<\/strong> For example: reserve 15% to 20% of the team\u2019s capacity each quarter to pay the prioritized debt, with a target and a quarterly report.<\/li>\n<\/ol>\n<p dir=\"ltr\">Align with the CFO beforehand on the value assumption for delayed deliveries. This is the most questionable item in the calculation; arriving at the board with numbers already validated by finance reduces the risk of the discussion getting lost in details.<\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">How do you pay down technical debt without stopping delivery?<\/h2>\n<p dir=\"ltr\">The most sustainable way to pay down technical debt is to reserve a fixed, recurring share of the team\u2019s capacity instead of planning a general stop. With a target, prioritization by return and a periodic report, the debt falls continuously without interrupting the product roadmap.<\/p>\n<p dir=\"ltr\">There are three practical mechanisms:<\/p>\n<ul dir=\"ltr\">\n<li><strong>Reserved capacity:<\/strong> allocate a fixed slice of each cycle\u2019s hours to the prioritized debt, treated as a plan item and not as \u201cif there is time\u201d.<\/li>\n<li><strong>Refactoring alongside delivery:<\/strong> when changing an indebted module, improve it in the same cycle, taking advantage of the fact that the context is already open.<\/li>\n<li><strong>Incremental modernization:<\/strong> replace parts of the system in planned stages, without rewriting everything at once. The article on <a href=\"https:\/\/nextage.com.br\/blog\/en\/legacy-system-modernization-choose-between-rehost-refactor-rearchitect-and-rewrite\/\" target=\"_blank\" rel=\"noopener\">legacy system modernization<\/a> helps you choose between rehost, refactor, rearchitect and rewrite.<\/li>\n<\/ul>\n<p dir=\"ltr\">This model fits well with a support contract. In NextAge\u2019s <a href=\"https:\/\/nextage.com.br\/en\/services\/application-managed-services\/\" target=\"_blank\" rel=\"noopener\">Application Managed Services<\/a>, the service is organized into four fronts (corrective, adaptive, evolutionary and governance), contracted as a monthly package of hours, with clear scope and an SLA defined from the start. This structure is a good starting point for the payment plan: reserve a fixed slice of the evolutionary hours for the prioritized debt and include, in the monthly follow-up, the evolution of principal and interest. When the cost and risk of maintaining exceed those of evolving, modernization can be incremental, in planned stages.<\/p>\n<p dir=\"ltr\">When the debt is concentrated in a module that requires a rewrite, or when a new feature depends on a redesign, a <a href=\"https:\/\/nextage.com.br\/en\/services\/software-factory\/\" target=\"_blank\" rel=\"noopener\">software factory<\/a> can take on that delivery with responsibility for the result, while support keeps the rest running. For a closer look at the model, see <a href=\"https:\/\/nextage.com.br\/blog\/en\/software-factory-what-it-is-and-why-your-company-should-hire-one\/\" target=\"_blank\" rel=\"noopener\">what a software factory is and why your company should hire one<\/a>.<\/p>\n<p dir=\"ltr\">A warning about AI-generated code: it speeds up delivery but, without review and tests, can create debt faster than it is paid. The article on <a href=\"https:\/\/nextage.com.br\/blog\/en\/what-will-change-with-generative-ai-by-2027-a-guide-for-it\/\" target=\"_blank\" rel=\"noopener\">what will change with generative AI by 2027<\/a> discusses how IT teams can prepare.<\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">What are the common mistakes when quantifying and presenting technical debt?<\/h2>\n<p dir=\"ltr\">The most common mistakes are treating the estimate as an exact number, presenting only technical metrics, adding up costs without aligning assumptions with the business, and promising a 100% return. Avoiding them increases the credibility of the numbers in front of the CFO and the board.<\/p>\n<ol dir=\"ltr\">\n<li><strong>A single number, with no range.<\/strong> Present a conservative and a likely scenario; boards distrust excessive precision.<\/li>\n<li><strong>Technical metrics instead of results.<\/strong> Cyclomatic complexity and test coverage matter to the team; the board wants deadlines, cost and risk.<\/li>\n<li><strong>Unvalidated value assumptions.<\/strong> The cost of delay depends on how much the delivery is worth to the business; without finance\u2019s validation, it is the first item to be challenged.<\/li>\n<li><strong>Using study data in place of internal data.<\/strong> The McKinsey, Stripe and CISQ numbers give context but do not replace your company\u2019s hours and incidents.<\/li>\n<li><strong>Paying everything, or nothing.<\/strong> The answer is almost always to prioritize what has the highest return and leave the rest for later.<\/li>\n<li><strong>Asking for resources without asking for a target.<\/strong> Without a tracking indicator, the investment loses support in the next quarter.<\/li>\n<\/ol>\n<h2 dir=\"ltr\" aria-level=\"5\">Frequently asked questions about technical debt<\/h2>\n<h3 dir=\"ltr\" aria-level=\"6\">What is technical debt?<\/h3>\n<p dir=\"ltr\">Technical debt is the future cost of rework taken on by choosing a faster or simpler solution now instead of a more durable one. Like a financial debt, it has a principal (the cost of fixing it) and interest (the extra effort paid on every change while it exists). It is also called tech debt.<\/p>\n<h3 dir=\"ltr\" aria-level=\"6\">How do you calculate technical debt in financial terms?<\/h3>\n<p dir=\"ltr\">Add up the cost of living with the debt (interest: extra maintenance hours, incidents and delayed deliveries) and compare it with the cost of eliminating it (principal: hours \u00d7 fully loaded hourly cost). Payback is the principal divided by the monthly interest avoided. Use internal data and present a range of scenarios, not a single number.<\/p>\n<h3 dir=\"ltr\" aria-level=\"6\">What is the difference between technical debt and a legacy system?<\/h3>\n<p dir=\"ltr\">A legacy system describes the age and technology of a system; technical debt describes the accumulated cost of changing it. An old system can be well maintained, with little debt, and a recent system can carry a lot of debt because of haste or lack of care. The two often appear together, but they are not synonyms.<\/p>\n<h3 dir=\"ltr\" aria-level=\"6\">How do you present technical debt to the board?<\/h3>\n<p dir=\"ltr\">Start with the business impact, show the annual cost in money with clear assumptions, present three options (do not pay, pay part, pay all) with their consequences, and ask for a specific decision, such as reserving a fixed share of the team\u2019s capacity each quarter. Validate the value assumptions with the CFO beforehand.<\/p>\n<h3 dir=\"ltr\" aria-level=\"6\">How much of the IT budget should go to paying down technical debt?<\/h3>\n<p dir=\"ltr\">There is no universal percentage. McKinsey reports that, in a 2020 survey of CIOs, 10% to 20% of the budget for new products was diverted to debt problems, which shows the order of magnitude of the cost. The ideal percentage depends on the calculated interest and on the payback of each module; start with what returns fastest.<\/p>\n<h3 dir=\"ltr\" aria-level=\"6\">Does all technical debt need to be paid?<\/h3>\n<p dir=\"ltr\">No. By Martin Fowler\u2019s distinction, prudent debt, taken on consciously to meet a market deadline, can be acceptable if there is a plan to fix it. Debt in rarely changed code can also wait, because the interest is low. Prioritize reckless debt in frequently changed areas.<\/p>\n<h3 dir=\"ltr\" aria-level=\"6\">How does system support help reduce technical debt?<\/h3>\n<p dir=\"ltr\">A support contract with evolutionary hours and indicator tracking lets you reserve a fixed share of capacity for the prioritized debt and report progress every month. This turns debt reduction into a routine, without stopping the roadmap. The result depends on prioritization and on the contracted scope.<\/p>\n<h2 dir=\"ltr\" aria-level=\"5\">Conclusion: three next steps for the quarter<\/h2>\n<p dir=\"ltr\">Technical debt stops being an abstract problem when it gets numbers: principal, interest and payback. The method in this article is simple and uses data that most companies already have; what changes is how it is organized and taken to the board.<\/p>\n<p dir=\"ltr\">For the next quarter, three steps:<\/p>\n<ol dir=\"ltr\">\n<li><strong>Gather the data:<\/strong> tag rework in time tracking, classify incidents by root cause and list the delayed deliveries.<\/li>\n<li><strong>Calculate as a range:<\/strong> use the formulas with a conservative scenario and a likely one, and validate the value assumption with finance.<\/li>\n<li><strong>Take a decision to the board:<\/strong> present three options and ask for reserved capacity to pay the prioritized debt, with a target and a quarterly report.<\/li>\n<\/ol>\n<p dir=\"ltr\">If your company needs capacity to pay down technical debt without compromising the roadmap, NextAge offers an initial diagnostic at no cost and with no commitment. Learn about <a href=\"https:\/\/nextage.com.br\/en\/services\/application-managed-services\/\" target=\"_blank\" rel=\"noopener\">Application Managed Services<\/a> or talk to a NextAge specialist.<\/p>\n<p><script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is technical debt?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Technical debt is the future cost of rework taken on by choosing a faster or simpler solution now instead of a more durable one. Like a financial debt, it has a principal (the cost of fixing it) and interest (the extra effort paid on every change while it exists). It is also called tech debt.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do you calculate technical debt in financial terms?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Add up the cost of living with the debt (interest: extra maintenance hours, incidents and delayed deliveries) and compare it with the cost of eliminating it (principal: hours \u00d7 fully loaded hourly cost). Payback is the principal divided by the monthly interest avoided. Use internal data and present a range of scenarios, not a single number.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is the difference between technical debt and a legacy system?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"A legacy system describes the age and technology of a system; technical debt describes the accumulated cost of changing it. An old system can be well maintained, with little debt, and a recent system can carry a lot of debt because of haste or lack of care. The two often appear together, but they are not synonyms.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do you present technical debt to the board?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Start with the business impact, show the annual cost in money with clear assumptions, present three options (do not pay, pay part, pay all) with their consequences, and ask for a specific decision, such as reserving a fixed share of the team's capacity each quarter. Validate the value assumptions with the CFO beforehand.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How much of the IT budget should go to paying down technical debt?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"There is no universal percentage. McKinsey reports that, in a 2020 survey of CIOs, 10% to 20% of the budget for new products was diverted to debt problems, which shows the order of magnitude of the cost. The ideal percentage depends on the calculated interest and on the payback of each module; start with what returns fastest.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does all technical debt need to be paid?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"No. By Martin Fowler's distinction, prudent debt, taken on consciously to meet a market deadline, can be acceptable if there is a plan to fix it. Debt in rarely changed code can also wait, because the interest is low. Prioritize reckless debt in frequently changed areas.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How does system support help reduce technical debt?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"A support contract with evolutionary hours and indicator tracking lets you reserve a fixed share of capacity for the prioritized debt and report progress every month. This turns debt reduction into a routine, without stopping the roadmap. The result depends on prioritization and on the contracted scope.\"\n      }\n    }\n  ]\n}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Technical debt is the future cost of rework that a company takes on when it chooses a faster or simpler solution today instead of a more durable one. For the CTO who needs budget, explaining the concept is rarely the hard part. The hard part is translating it into the language of the people who<\/p>\n","protected":false},"author":5,"featured_media":5843,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[265],"tags":[],"class_list":["post-5845","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-planning"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Technical Debt: How to Calculate Its Cost for the Board - NextAge Blog<\/title>\n<meta name=\"description\" content=\"Learn how to quantify technical debt in financial terms (principal, interest, payback) and present it to the board. Includes a worked example.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/\" \/>\n<meta property=\"og:locale\" content=\"pt_BR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Technical Debt: How to Calculate Its Cost for the Board - NextAge Blog\" \/>\n<meta property=\"og:description\" content=\"Learn how to quantify technical debt in financial terms (principal, interest, payback) and present it to the board. Includes a worked example.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/\" \/>\n<meta property=\"og:site_name\" content=\"NextAge Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-19T16:46:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-scaled.avif\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"1709\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Laura Marques\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Laura Marques\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"18 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/\"},\"author\":{\"name\":\"Laura Marques\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/2fdd81129ea968e45b68b610bd9629c0\"},\"headline\":\"Technical Debt: How to Quantify It in Financial Terms and Present It to the Board\",\"datePublished\":\"2026-11-19T16:46:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/\"},\"wordCount\":2997,\"publisher\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/focused-man-with-document-using-computer-scaled.avif\",\"articleSection\":[\"Planning\"],\"inLanguage\":\"pt-BR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/\",\"url\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/\",\"name\":\"Technical Debt: How to Calculate Its Cost for the Board - NextAge Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/focused-man-with-document-using-computer-scaled.avif\",\"datePublished\":\"2026-11-19T16:46:00+00:00\",\"description\":\"Learn how to quantify technical debt in financial terms (principal, interest, payback) and present it to the board. Includes a worked example.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/#breadcrumb\"},\"inLanguage\":\"pt-BR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/#primaryimage\",\"url\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/focused-man-with-document-using-computer-scaled.avif\",\"contentUrl\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/focused-man-with-document-using-computer-scaled.avif\",\"width\":2560,\"height\":1709,\"caption\":\"D\u00edvida t\u00e9cnica: homem de camisa branca, em ambiente escuro \u00e0 noite, segura folhas impressas e olha atento para um gr\u00e1fico de barras azuis em crescimento no monitor.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/en\\\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Technical Debt: How to Quantify It in Financial Terms and Present It to the Board\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/\",\"name\":\"NextAge Blog\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-BR\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/#organization\",\"name\":\"NextAge Blog\",\"url\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/01\\\/cropped-logo-nextage-completo-scaled-1.webp\",\"contentUrl\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/01\\\/cropped-logo-nextage-completo-scaled-1.webp\",\"width\":2558,\"height\":556,\"caption\":\"NextAge Blog\"},\"image\":{\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/2fdd81129ea968e45b68b610bd9629c0\",\"name\":\"Laura Marques\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/cropped-foto-perfil-avatar-96x96.webp\",\"url\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/cropped-foto-perfil-avatar-96x96.webp\",\"contentUrl\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/cropped-foto-perfil-avatar-96x96.webp\",\"caption\":\"Laura Marques\"},\"description\":\"Graduada em Letras - Portugu\u00eas pela Universidade Tecnol\u00f3gica Federal do Paran\u00e1 (UTFPR), especialista em conte\u00fado para o setor de tecnologia. Escrevo para transformar inova\u00e7\u00e3o em boas hist\u00f3rias e ajudar empresas a alcan\u00e7ar o pr\u00f3ximo n\u00edvel de transforma\u00e7\u00e3o digital.\",\"url\":\"https:\\\/\\\/nextage.com.br\\\/blog\\\/author\\\/laura\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Technical Debt: How to Calculate Its Cost for the Board - NextAge Blog","description":"Learn how to quantify technical debt in financial terms (principal, interest, payback) and present it to the board. Includes a worked example.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/","og_locale":"pt_BR","og_type":"article","og_title":"Technical Debt: How to Calculate Its Cost for the Board - NextAge Blog","og_description":"Learn how to quantify technical debt in financial terms (principal, interest, payback) and present it to the board. Includes a worked example.","og_url":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/","og_site_name":"NextAge Blog","article_published_time":"2026-11-19T16:46:00+00:00","og_image":[{"width":2560,"height":1709,"url":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-scaled.avif","type":"image\/jpeg"}],"author":"Laura Marques","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Laura Marques","Est. reading time":"18 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/#article","isPartOf":{"@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/"},"author":{"name":"Laura Marques","@id":"https:\/\/nextage.com.br\/blog\/#\/schema\/person\/2fdd81129ea968e45b68b610bd9629c0"},"headline":"Technical Debt: How to Quantify It in Financial Terms and Present It to the Board","datePublished":"2026-11-19T16:46:00+00:00","mainEntityOfPage":{"@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/"},"wordCount":2997,"publisher":{"@id":"https:\/\/nextage.com.br\/blog\/#organization"},"image":{"@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/#primaryimage"},"thumbnailUrl":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-scaled.avif","articleSection":["Planning"],"inLanguage":"pt-BR"},{"@type":"WebPage","@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/","url":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/","name":"Technical Debt: How to Calculate Its Cost for the Board - NextAge Blog","isPartOf":{"@id":"https:\/\/nextage.com.br\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/#primaryimage"},"image":{"@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/#primaryimage"},"thumbnailUrl":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-scaled.avif","datePublished":"2026-11-19T16:46:00+00:00","description":"Learn how to quantify technical debt in financial terms (principal, interest, payback) and present it to the board. Includes a worked example.","breadcrumb":{"@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/#breadcrumb"},"inLanguage":"pt-BR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/"]}]},{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/#primaryimage","url":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-scaled.avif","contentUrl":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/11\/focused-man-with-document-using-computer-scaled.avif","width":2560,"height":1709,"caption":"D\u00edvida t\u00e9cnica: homem de camisa branca, em ambiente escuro \u00e0 noite, segura folhas impressas e olha atento para um gr\u00e1fico de barras azuis em crescimento no monitor."},{"@type":"BreadcrumbList","@id":"https:\/\/nextage.com.br\/blog\/en\/technical-debt-how-to-quantify-it-in-financial-terms-and-present-it-to-the-board\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/nextage.com.br\/blog\/"},{"@type":"ListItem","position":2,"name":"Technical Debt: How to Quantify It in Financial Terms and Present It to the Board"}]},{"@type":"WebSite","@id":"https:\/\/nextage.com.br\/blog\/#website","url":"https:\/\/nextage.com.br\/blog\/","name":"NextAge Blog","description":"","publisher":{"@id":"https:\/\/nextage.com.br\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/nextage.com.br\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-BR"},{"@type":"Organization","@id":"https:\/\/nextage.com.br\/blog\/#organization","name":"NextAge Blog","url":"https:\/\/nextage.com.br\/blog\/","logo":{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/nextage.com.br\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2025\/01\/cropped-logo-nextage-completo-scaled-1.webp","contentUrl":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2025\/01\/cropped-logo-nextage-completo-scaled-1.webp","width":2558,"height":556,"caption":"NextAge Blog"},"image":{"@id":"https:\/\/nextage.com.br\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/nextage.com.br\/blog\/#\/schema\/person\/2fdd81129ea968e45b68b610bd9629c0","name":"Laura Marques","image":{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/01\/cropped-foto-perfil-avatar-96x96.webp","url":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/01\/cropped-foto-perfil-avatar-96x96.webp","contentUrl":"https:\/\/nextage.com.br\/blog\/wp-content\/uploads\/2026\/01\/cropped-foto-perfil-avatar-96x96.webp","caption":"Laura Marques"},"description":"Graduada em Letras - Portugu\u00eas pela Universidade Tecnol\u00f3gica Federal do Paran\u00e1 (UTFPR), especialista em conte\u00fado para o setor de tecnologia. Escrevo para transformar inova\u00e7\u00e3o em boas hist\u00f3rias e ajudar empresas a alcan\u00e7ar o pr\u00f3ximo n\u00edvel de transforma\u00e7\u00e3o digital.","url":"https:\/\/nextage.com.br\/blog\/author\/laura\/"}]}},"_links":{"self":[{"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/posts\/5845","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/comments?post=5845"}],"version-history":[{"count":2,"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/posts\/5845\/revisions"}],"predecessor-version":[{"id":5848,"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/posts\/5845\/revisions\/5848"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/media\/5843"}],"wp:attachment":[{"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/media?parent=5845"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/categories?post=5845"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nextage.com.br\/blog\/wp-json\/wp\/v2\/tags?post=5845"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}