IONOS Pairs 450 Planned Job Cuts With AI Reinvestment

At 7:21 p.m. in Germany on September 10, IONOS put a workforce target, a restructuring charge, and an artificial intelligence investment claim into the same stock-market disclosure.

IONOS said it planned to reduce full-time employment from about 3,800 to roughly 3,350. The difference is 450 positions, close to 12% of the starting figure. About half of the adjustment would fall in Germany and half outside it. The company expects to book approximately €35 million of restructuring expense, mostly in the fourth quarter of 2026.

Then came the reinvestment promise. The company expects annual cost savings of up to €30 million from 2027. It said the funds would go back into the business, including AI product development and further cloud expansion.

Timing changes the story. Five weeks earlier, IONOS had reported higher revenue, more customers, higher adjusted earnings and a raised growth forecast.

Five days after the announcement, IONOS was still advertising 56 job offers. Several named AI products were already on sale. The careers board included an AI developer, AI product and sales roles, a conversational-experience designer, cloud operations jobs and working-student positions.

Growth and job cuts can coexist. So can job cuts and hiring. The hard part is finding out what changed between them.

Missing from the public record are a function-by-function list of the 450 positions, a schedule of accepted voluntary exits and an allocation of the future €30 million. IONOS has also withheld product-level AI revenue. Its announcement names AI use in internal workflows as part of the transformation, without connecting a particular tool to a particular departing employee.

The numbers stop short of a causal chain. Calling all 450 positions “replaced by AI” would turn a strategy sentence into a finding about specific jobs. The voluntary program remains a target rather than 450 completed departures. Management described the future €30 million as savings for reinvestment that includes AI and cloud, not as a dedicated AI budget.

Public records support a narrower investigation. IONOS is trying to reduce one labor denominator while expanding a product and infrastructure agenda. Employees decide whether to accept an exit offer, while managers must preserve customer service and operational knowledge. Investors need to see whether a one-time cash charge creates recurring savings. Product teams still have to convert AI releases into revenue that the company has not broken out.

Each conversion needs its own date and owner. Until those records appear, the September 10 plan remains a financed hypothesis about how a growing cloud company should divide work between people, software and new products.

September 10 put 450 roles into the investment plan

IONOS chose an ad hoc announcement under Article 17 of the European Union’s Market Abuse Regulation. That format is meant for inside information that could matter to investors. The language was brief, which makes both the disclosed facts and the omissions easier to see.

In its announcement, IONOS paired technical-platform consolidation with consistent AI use in internal workflows and a changed workforce structure. It then supplied the 3,800 and 3,350 full-time employee figures.

Read together, the sentences place consolidation, internal AI and workforce change inside one program. Role-level causality remains absent. Platform consolidation can remove duplicated engineering, support or administrative work without an AI system performing it. Process harmonization can centralize jobs across countries. A voluntary departure can eliminate a position that managers later redesign, outsource or refill. AI can reduce handling time while leaving the final decision and exception work with an employee.

Management expressed the target in full-time employees, a different measure from named people, payroll records or dismissal notices. Part-time positions can translate into fractions of an FTE. Employees can move between active and inactive classifications. Acquisitions, disposals, leave and internal transfers can change published totals without representing a completed job cut.

IONOS’s own historical figures show why the denominator needs care. Its 2025 annual report reported 4,115 active employees at year end, up 43 from the restated 2024 figure. The company had changed its calculation method in the third quarter of 2025, classifying people on leave and in the inactive phase of partial retirement as inactive. It had also classified Sedo as a discontinued operation.

Subtracting September’s approximate 3,800 FTE baseline from the 4,115 year-end active-employee figure produces 315. That arithmetic does not prove 315 people left. The dates, worker definitions and corporate perimeter differ. A responsible workforce bridge would reconcile the two measures before using either as an attrition rate.

Geography introduces another denominator. IONOS said the planned adjustment would be divided roughly equally between domestic and international operations. A simple reading suggests about 225 FTE on each side. The 2025 report counted 2,008 active employees in Germany and 2,107 abroad, but IONOS has not published the September 2026 distribution on the new FTE basis. Applying 225 to the older counts would create false precision.

Still, the plan is material. A 450-position reduction against 3,800 is about 11.8%. It is larger than routine attrition and small vacancy management. The target asks the company to remove almost one position in eight while maintaining customer, infrastructure and product work.

Cash leaves earlier than the saving arrives. IONOS expects about €35 million of one-time restructuring expense, mostly in the fourth quarter. It expects up to €30 million in annual savings starting in 2027, with the amount and timing dependent on participation in voluntary programs. At the maximum run rate, the simple payback on the accounting figures is about 14 months. A slower take-up rate extends it.

Dividing €35 million by 450 gives roughly €77,800 of one-time charge per targeted FTE. Dividing €30 million by 450 gives about €66,700 of annual saving. Neither result is an individual severance offer or an average salary. The charge can include advice, program administration and other restructuring costs. Recurring savings can include property, software, vendors, management overhead and unfilled vacancies. Some spending returns through new roles or suppliers.

Reinvestment bends the calculation again. Cost removed from one team is not automatically profit retained for shareholders. It can finance a developer, a cloud facility, a model contract, marketing, customer support or another expense that restores part of the cost base. Investors need both sides of the entry.

For now, the filing ends at a target and an upper bound. Actual cash, accepted exits, transferred work and funded projects will decide whether the program changes productivity or merely moves cost between lines.

Growth came before the restructuring charge

On August 6, CEO Achim Weiß described a company gaining customers and scaling new products. IONOS’s first-half release reported 6.91 million customers, an increase of about 280,000 during the first half. Revenue rose 6.9% to €701.1 million. Excluding currency effects, the increase was 8.2%.

Adjusted EBITDA rose 3.5% to €245.2 million. The adjusted margin fell from 36.1% to 35.0%, which the company attributed partly to marketing expenses being concentrated earlier in the year. Earnings grew, but more slowly than revenue.

IONOS raised its currency-adjusted revenue growth expectation for 2026 from 7% to about 8%. It kept adjusted EBITDA guidance at roughly €530 million and projected a 37% to 38% adjusted margin for the full year. Management said growth would come from new customers, sales to the existing base and AI products.

August makes the September job plan a choice about operating design and capital allocation under growth. The 450 planned cuts followed an increased revenue forecast, not a sales collapse or withdrawn guidance.

Growth can still contain duplicated platforms, excessive customer handoffs or a skill mix built for older products. Companies regularly reduce one function while hiring in another. Later reporting needs to show whether the new mix delivers the same service, stronger products and better financial results without hiding work in overtime or vendors.

The strongest case for management is operational rather than rhetorical. If several inherited tools perform the same function, one shared platform can retire duplicate release pipelines, administration and escalation queues. A smaller team could spend less time reconciling systems and more time resolving customer problems. For a provider serving nearly 7 million customers, consistency has real value.

That case is also testable. Name the systems retired, complete the migration milestones, remove the associated vendor and maintenance cost, and compare incidents, backlog and resolution time before and after the move. If those measures improve while gross savings survive the cost of replacement hiring and suppliers, consolidation has done more than shrink the denominator.

One prior-year number offers a useful scale check. IONOS reported €274.043 million of personnel expense for 2025 and an average of 4,101 employees under the German Commercial Code calculation. That works out to about €66,800 per average employee, close to the €66,700 maximum annual saving per targeted FTE implied by the new program.

That near match is not a disclosed wage model. One calculation uses a prior-year average employee count and a broad personnel-expense line. The other divides a management savings ceiling by a future target. Country pay, benefits, seniority, part-time status, open vacancies, replacement hiring and nonlabor savings can move the result substantially.

IONOS’s personnel expense had fallen 3.5% in 2025 even though year-end active headcount rose 1.1%. The annual report attributed the lower expense mainly to the absence of prior-year one-time optimization costs. That history shows how easily charges and headcount can travel in different directions.

Revenue per employee reached about €321,000 in 2025, according to the report. A smaller denominator would mechanically raise that figure if revenue held steady. Such a ratio cannot prove productivity on its own. Outsourcing work removes people from the employee count while preserving the cost elsewhere. Price increases lift revenue without changing task output. A discontinued operation can change the perimeter. Employee effort can intensify until service deteriorates later.

Management’s adjusted EBITDA presentation creates another boundary. The €35 million restructuring cost will be treated as a special item and will not affect the company’s adjusted guidance. The cash and employee consequence still exist. An investor comparing reported and adjusted performance should retain the charge rather than let the chosen metric make the transition appear free.

At the maximum €30 million annual run rate, the expected saving equals about 5.7% of IONOS’s €530 million adjusted EBITDA guidance. That is large enough to matter, but not large enough to explain the whole business. Future margin movement will also include pricing, customer mix, infrastructure depreciation, energy, marketing, partner costs and product investment.

Parent-company context adds scale without resolving IONOS’s case. Handelsblatt reported that United Internet’s programs at IONOS and sibling 1&1 Versatel together cover about 800 positions. It put the combined one-time cost at €95 million and annual savings at €55 million. The 1&1 plan separately targets management layers and its business-customer organization. Combining the totals does not make the causes or affected roles identical.

What the record can show is narrower. IONOS has enough growth and profitability to choose where to spend. It chose a workforce reduction and promised that some of the released cost will support AI and cloud expansion. Later reports need to bridge exited work and funded work before that promise can be tested.

Voluntary exits create a participation problem

A voluntary target still depends on hundreds of individual decisions. IONOS said it would shape the programs for each country with employee representatives and use voluntary redundancy as the main route.

An employee must receive an offer, assess it and decide. The company may be able to reject applications from people whose knowledge it needs. If too few employees participate, the savings arrive late or management considers other measures. If too many people from a critical team apply, the company must protect operations, negotiate exceptions or rebuild the team later.

Participation therefore sits inside the financial forecast. Management expressly said the amount and timing of savings would depend on take-up. The target organization exists on paper before the company knows which people will choose it.

For an employee, the decision extends beyond the headline payment. A voluntary agreement can change the employment end date, notice period, bonus, equity treatment, pension position, unemployment eligibility, reference, noncompete terms and access to internal openings. These details vary by country and contract. IONOS has not published its offer terms.

For the company, each accepted exit removes more than a cost. It can remove knowledge of a customer, a billing exception, a legacy platform, a security response, a language market or a fragile operational dependency. A platform-consolidation plan often needs the people who understand both systems until the migration is finished. Letting them leave too early can convert payroll savings into contractor cost or outage risk.

An internal labor market offers a harder alternative to choosing between retention and departure. IONOS could publish which new job families are reachable, reserve some openings for affected employees, fund the relevant training and report applications, offers and starts. Not every old role will map to a new one, and retraining can delay the savings. The exercise would still reveal whether the needed expertise already sits inside the company before managers buy it again outside.

Country borders split one target into several programs. IONOS reported employees across Germany, the Philippines, Spain, Poland, Romania, the United Kingdom, the United States and smaller locations at the end of 2025. Labor rules, consultation duties, notice, benefits and market alternatives differ.

German procedure offers one public reference point, though it cannot be applied to every IONOS employee. The Federal Employment Agency says employers must notify it before dismissals cross specified establishment-level thresholds within the relevant period. For a workplace with at least 500 employees, the listed threshold is 30 dismissals. Evidence that a works council was involved must accompany a required notification.

Public data stops before the establishment-level test. IONOS has not disclosed whether a German workplace will cross a threshold within 30 days. Some employer-initiated voluntary agreements can enter the calculation, depending on the actual process. Half the program sits outside Germany, and the general rule proves neither a filing nor a failure to file.

Employment lawyer Jens Usebach drew a useful factual boundary in a September 13 explanation of the IONOS and 1&1 announcements. A public target is not a record that 800 individual dismissals have already occurred. The group total is not a German-only total. His page is general legal commentary and promotes his practice. Individual rights still require local advice and the actual documents.

Departure terms are only one item for employee representatives. Section 96 of Germany’s Works Constitution Act says employers and works councils should promote vocational training. It also calls for discussion of identified training needs. That statute guarantees no particular IONOS program, but it places capability planning beside headcount planning.

A credible transition plan would identify the task before it identifies the person. Management would map which work disappears, which work moves to a shared platform, which work an AI system assists, which work stays with a human and which work is being created. The map would show the knowledge handoff, training hours, service owner and escalation path.

Without that map, voluntary take-up can select the future organization by accident. The people most confident of finding another job may accept first. Employees with portable AI, cloud or customer skills may have the strongest alternatives. A program designed to make the company more capable could lose precisely the experience needed for the change.

Managers face the opposite risk when too many people from a scarce team apply. They might block those exits while expecting participation elsewhere, leaving employees with unequal choices. IONOS may fill new AI vacancies while colleagues in older roles receive departure offers. A fair process needs transparent job families, internal-mobility routes and selection logic, subject to privacy and local law.

No public IONOS document yet names affected functions, acceptance rules, redeployment commitments, training budgets or employee-representative agreements. Describing the program as socially responsible states an intention. The signed terms and outcomes will determine what it means.

Fifty-six vacancies point to the work that remains

Five days after announcing the target, IONOS was still recruiting. Its English careers board returned 56 job offers on September 15. The page grouped openings across data centers, system and network administration, software development, product management, marketing, sales, customer service, finance, legal and human resources.

Treat 56 as a snapshot of advertisements, not a net hiring plan. Some listings repeat one reference number across locations. A requisition can replace someone who left, support several hires, move internally or close without an offer. A public board omits confidential searches, vendors and roles reserved for internal candidates.

Even with those limits, the titles show what IONOS still needs while it reduces the overall denominator.

An AI Developer with Python posting placed the role in a customer-care AI platform team. The description includes multimodal systems, retrieval, model orchestration, voice interaction and real-time performance. An AI Sales Strategy Manager appears in three German locations under one reference number. A working-student role covers automation and AI. A senior user-experience role focuses on an AI agent’s conversational experience.

Cloud and infrastructure work remains visible too. The board included site reliability, network reliability, customer operations, data-center management and a data-center technician role open to graduates or career starters. Product, finance, accounts receivable, sales, marketing, customer support and human-resources positions remained on the list.

Advertising continues even as the total workforce target falls. IONOS could remove a customer-support layer, hire an AI platform engineer and still need more people to handle exceptions. It could consolidate two systems and add a site reliability engineer because the combined platform carries more operational consequence. The postings reveal simultaneous labor flows without connecting an AI vacancy to an eliminated job.

Scale matters too. Fifty-six advertisements equal about one-eighth of the planned 450-position reduction, even before duplicate locations and unfilled requisitions are removed. Filling every listing would not reverse the target. The board is better evidence of reallocation than of overall expansion.

Even the careers site exposes a denominator conflict. A general page says the group has more than 4,000 employees, while the September 10 announcement uses a current level of about 3,800 full-time employees. The annual report counted 4,115 active employees at the end of 2025. Rounding, timing or scope may explain the difference, but no public reconciliation is available.

Vacancy-level evidence can improve that bridge. Record each reference number, first-seen date, location, level, department and status. Separate a duplicated location from a distinct role. When a page disappears, do not mark it filled without a disposition. Join later starts to payroll headcount and classify them as growth, replacement, internal transfer or conversion from a contractor.

Internal mobility deserves its own field. An employee whose platform is being consolidated may be able to move into cloud operations, product support or an AI workflow team. An internal fill preserves employment and knowledge but does not increase net headcount. It may leave another vacancy behind. The current public board does not say which roles are open internally, externally or both.

Early-career access is also uneven. The September snapshot included student positions and a graduate data-center technician. It did not publish a complete seniority distribution. If restructuring removes routine work and concentrates hiring in experienced AI roles, the company may narrow the path through which new workers learn its systems. If it protects apprenticeships, student jobs and reviewed production work, it can build skills rather than buy them all from outside.

Managers carry the conversion cost. They have to interview, select, onboard and supervise new hires while transferring work from departing employees. Existing staff may be asked to document systems, train replacements and keep service stable at the same time. Interview hours and handoff hours belong in the restructuring budget even if accounting does not label them as severance.

Customer experience supplies an external check. A smaller workforce can be more effective after platform consolidation. It can also produce longer response times, weaker escalation, repeated explanations and slower incident recovery. Support backlog, first-contact resolution, complaint rates, availability, security incidents and churn should be compared before and after the change.

For now, the 56 postings offer a concrete watch list. They show the categories of work IONOS is willing to advertise during a 450-position reduction, without promising 56 hires or renewed employment growth. Later starts and service records will show whether the mix works.

AI products still lack a revenue denominator

Inside IONOS, AI is supposed to save time. Outside it, AI is supposed to make money. Management named internal AI workflows as part of the transformation and AI product development as one destination for future savings. Productivity and customer revenue remain different bets.

On the product side, Weiß has presented AI as a way to expand beyond hosting and domains. The first-half release said an AI Phone Assistant was live in all markets. In July, IONOS launched an AI App & Site Builder that accepts text, voice or screenshot instructions and produces websites or applications with hosting, a database, a domain, email and security features.

The product announcement described three plans, a promotional first-month price starting at £9 in the United Kingdom, and a 30-day money-back guarantee. It also described an AI Receptionist and said more agents would arrive during 2026.

Features and prices are visible; economics are not. The release gives no active-user count, paid conversion, renewal, usage frequency, support load, gross margin or revenue. IONOS also says data is processed on European infrastructure and excluded from training public AI models. That is a vendor policy statement rather than a customer-level audit of every data route or subprocessor.

IONOS has a large distribution base. Nearly 7 million customers create many opportunities to place an assistant beside a domain, mailbox, website or cloud account. Existing billing and support relationships can lower customer-acquisition cost. European data location and independence from large US hyperscalers may appeal to small businesses and public-sector buyers.

For a small business, the bundle has a coherent appeal. One account can connect a domain, email, hosting, database, generated site, security features and a phone assistant. Fewer vendors can mean fewer credentials, bills and integration failures. IONOS can also observe whether an existing customer keeps using the new product without paying to acquire that relationship again.

Distribution does not guarantee adoption. A hosting customer may try an assistant once and never rely on it. A promotional month can raise sign-ups without durable revenue. A generated website can look complete while carrying accessibility, security, licensing or maintenance problems. A phone agent can answer routine calls and still require a person when context, emotion or money enters the conversation.

Product economics also feed back into labor. If the AI Phone Assistant reduces customer demand for a small-business receptionist, IONOS may gain subscription revenue while its customer changes staffing. If the tool produces more configuration questions, IONOS’s own support burden may rise. If App & Site Builder reduces agency work, it may increase demand for review, integration and repair.

No current disclosure joins these outcomes. An AI product contribution table would need product-level bookings, recognized revenue, trial conversion, retention, usage, inference cost, support cost, refunds, incident rate and customer-reported task completion. Management can then compare the new gross profit with the reinvested savings.

Internal productivity requires a separate table. A workflow can be faster without eliminating the role. Record the task, baseline volume, handling time, error rate, exception rate, model and tool cost, reviewer time, affected employee group and final service result. Then identify whether the saving came from fewer hours, an unfilled vacancy, redeployment, outsourcing or a completed departure.

Germany’s wider adoption data makes that discipline timely. On September 14, digital-industry association Bitkom said 57% of 603 surveyed companies with at least 20 employees reported using AI, up from 36% a year earlier.

Another 38% were planning or discussing it. Yet 59% of users said they were not exploiting the potential at all, and only 3% said they were using it rather strongly.

Bitkom’s figures come from company responses and an industry group advocating digital adoption. They measure neither IONOS productivity nor audited returns. Their useful signal is the gap between installing AI and extracting an economic result.

An ifo Institute survey adds a labor expectation. Among companies already using AI, nearly 20% said it would be easy or very easy to substitute an employee with a university or professional qualification with an AI-assisted worker lacking that qualification.

About 15% said the same about replacing experience with an inexperienced, AI-assisted worker. Researcher Anna Ruffert cautioned that experience appeared harder to compensate for than formal credentials.

Employer expectations do not document substitutions at IONOS. They still define a risk in the plan. Managers may believe a tool lets a less experienced or smaller team carry old work. Errors, customer outcomes, review time and employee learning should test that belief before the organization treats a position as permanently unnecessary.

AI reinvestment earns its name only after money reaches a project and that project produces a durable result. Until IONOS publishes a product or workflow denominator, the public can see ambition, features and a funding source. It cannot see the return.

Build a workforce-to-reinvestment file

The program needs one operating record that connects finance, people, technology and customers without merging their measures. Call it the workforce-to-reinvestment file.

The file should be maintained by workstream, not as one 450-row list of people. Individual employment data belongs behind strict access controls. Public and board reporting can use aggregated, privacy-reviewed cohorts while the accountable teams retain the evidence needed for consultation, audits and individual decisions.

Workstream record	Minimum evidence	Owner question	Failure signal
Baseline and target	Headcount date, worker definition, legal entity, establishment, FTE method, vacancies	Can finance reconcile 4,115 active employees, about 3,800 current FTE and the 3,350 target?	Headcount falls without a bridge for scope, leave, disposals, contractors or openings
Task change	Process step, volume, old owner, new owner, platform migration, AI assistance, retained human decision	Which work disappears, moves, automates or remains?	A position closes while exceptions, reviews or customer work have no named owner
Employee process	Country, program terms, consultation status, offer date, acceptance or decline, internal options	Did the employee receive a real choice and a usable route to another role?	Participation misses the plan, critical skills leave, or terms vary without an explained basis
Knowledge handoff	System, customer, runbook, access, trainer, successor, completion test	Can the continuing team perform the work before access ends?	Contractor spend, incidents, backlogs or repeated escalations rise after departures
Cash charge	Severance, benefits, advice, systems, site and other program cost, payment date	What consumed the €35 million and when was cash paid?	The special-item label hides recurring cost or the charge grows without explaining scope
Recurring saving	Payroll, vacancy, property, vendor, software and management cost removed	Which savings recur, and which are delayed or offset?	The €30 million ceiling is reported without gross-to-net reconciliation
Hiring and mobility	Requisition ID, internal or external, replacement or growth, offer, start, manager and training time	Do 56 advertised jobs change the target or the skill mix?	Postings close without starts, scarce roles stay empty, or backfills recreate removed cost
AI workflow	Tool, model, task volume, handling time, error, exception, reviewer, security and service measure	Did internal AI reduce total work while preserving accountable review?	Headcount falls but overtime, corrections, customer complaints or model cost increase
Product reinvestment	Approved budget, product, staff and supplier cost, milestone, release and customer cohort	How much saving reached AI products or cloud, and what shipped?	Reinvestment remains an undated label or spending rises without a product milestone
Product result	Paid users, conversion, retention, revenue, gross margin, inference and support cost, incidents	Did the funded product create durable customer value and economic return?	Trials rise while renewal, margin or service quality stalls

Start with the denominator. Finance should publish a bridge from the last audited employee count to the program baseline and target. Employees, FTE, contractors, inactive workers, acquisitions, disposals and vacancies require separate lines. Otherwise every later productivity ratio inherits an unexplained starting point.

Next comes the work itself. A manager should be able to identify the old step, the new step and the human decision that remains. If platform consolidation removes duplicate administration, call it consolidation. If a model drafts a response while an employee checks and sends it, measure the whole combined process.

Participation can be visible without publishing personal details. Report offers, acceptances, declines, internal applications and redeployments by an appropriate cohort. Record the local representative process. Keep voluntary agreements separate from dismissals and natural attrition.

Handoff has its own deadline. A departing engineer’s account can close on one date while a platform migration completes months later. A customer-care specialist can hold exception knowledge that no model retrieved from the official documentation. Test the handoff before the last working day, rather than inferring success later from the absence of a major outage.

Finance must reconcile gross and net. Suppose payroll savings reach €20 million, property and software add €10 million, and replacement hiring costs €8 million. The net recurring effect differs from the headline ceiling. A new €5 million AI supplier contract would belong in the reinvestment record even if procurement classifies it outside personnel expense. These figures are illustrative, not IONOS guidance.

Hiring data closes a common blind spot. A company can achieve a lower year-end headcount and still spend heavily on recruiting, relocation, sign-on awards, contractors and interview time. It can also cancel necessary roles to hit a number, then pay more for emergency coverage. Requisition history and actual starts reveal the difference.

Internal productivity and product growth split at this point. A faster support workflow says nothing about whether App & Site Builder customers stay. A popular customer product does not show that an internal team can safely lose positions. Each requires its own cost, quality and cohort evidence.

Owners should sign each conversion. Human resources owns program status and internal routes. Employee-relations and legal teams own consultation and local procedure. Finance owns cash and savings. Technology leaders own migration and AI workflow evidence. Product and commercial leaders own usage, revenue and retention. Customer operations owns service measures. The board owns the decision to proceed when the measures conflict.

Publication frequency can match the risk. Monthly internal reviews can track participation, departures, vacancies and service. Quarterly investor reporting can reconcile headcount, restructuring cash, recurring savings and reinvestment. Product cohorts can mature long enough to reveal renewal and support cost. Employee representatives need timely information before choices become irreversible.

A stop condition belongs in the file. If critical incidents rise, customer backlog breaches an agreed threshold, a platform migration slips, or voluntary participation concentrates in scarce teams, management should slow the relevant exits. A target date is not more important than keeping the service operable.

No file can settle whether every decision was fair. It can make the company’s theory inspectable. IONOS says a smaller workforce, consolidated platforms, internal AI and reinvestment can produce stronger growth. Each handoff belongs in the record rather than inside one adjusted earnings number.

2027 opens with two numbers to reconcile

The first useful 2027 report will pair the 3,350 target with actual program participation, restructuring cash and recurring cost. Another product description will not do that work.

Start with people. How many voluntary offers were made? How many were accepted? How many employees moved internally? How many positions ended through attrition, agreement or dismissal? Which countries and functions changed? How many advertised roles produced starts? A net headcount total should sit at the end of that bridge, not replace it.

Then follow the money. Did the company spend about €35 million? How much of the €30 million run-rate ceiling became a realized gross saving? What new cost entered through recruitment, contractors, models, infrastructure or customer support? How much was approved for AI product development and cloud expansion?

Product reporting can close the final gap. Paid adoption, renewal, product revenue, gross margin, service incidents and support burden would show whether the reinvestment produced a business rather than a release calendar. Internal workflow data can show whether AI reduced total effort or moved correction and review work to fewer employees.

Open that report at the workforce bridge, not the AI release list. Pick one migrated service and show its old and new owner, departures and redeployments, AI tool and reviewer, incident record, backlog, gross saving and replacement cost. Then trace part of the saving into a product cohort and report whether those customers renewed at a viable margin.

One complete chain would be more useful than another stack of product announcements. Without it, two favorable numbers, 3,350 FTE and €30 million saved, would leave the central question open: did IONOS build a better operating system, or merely book a smaller payroll?