Monday, nine in the morning. The IT Asset Manager of a manufacturing group with plants in Germany, Poland and the Czech Republic has just come out of a meeting with the CFO. The Flexera One contract is signed, the first subscription invoice is paid, and the board expects a compliance report for Microsoft and Oracle within a quarter. The CFO asked one question: “When will we know how many licences we actually have?”
The IT Asset Manager knows the answer does not depend on the tool alone. The Microsoft agreements sit in three places because each country bought separately. The security team has not yet approved inventory agents on production servers. Nobody knows who has access to the Oracle support portal. And the Configuration Manager administrator, the one person who knows the whole estate, goes on leave in two weeks.
That is how a typical Flexera One implementation begins. This article is for the person responsible for it. We set out a realistic timeline, what makes up the cost, what you must prepare on your side, which decisions to take before the first day and how to tell early that the implementation is heading the wrong way.
What is Flexera One and what are you actually implementing?
Flexera One is an IT asset management platform that combines visibility of hardware and software, software licence management, SaaS management and cloud cost management across AWS, Azure and Google Cloud. In February 2024 Flexera completed its acquisition of Snow Software, so many organisations that used either tool are now considering consolidating on one platform.
From a project point of view, implementation is not “installing a program”. The platform runs as a cloud service. You are implementing four things:
- Data collection. Inventory agents on workstations and servers, connections to existing sources (Active Directory or Entra ID, Intune, Configuration Manager, vCenter, cloud accounts, SaaS systems) and the components that pass data from the corporate network to the platform.
- Normalisation. Raw installation data is mapped to specific publishers, products and versions from Flexera’s library, so that “MS Office Pro Plus 2019 x64 EN” and thirty other name variants end up as one product.
- Entitlements. Importing contracts, orders and invoices, plus the licensing rules, so the tool knows what you own and on what terms.
- Process and reporting. Roles, responsibilities, the reconciliation cycle, reports for the board and procurement, rules for exceptions.
The first two are largely technical and predictable. The third and fourth depend on your organisation. That is why two implementations of the same tool in companies of similar size can take six weeks or sixteen.
If you are still comparing tools or building the business case, our article on Flexera One in practice walks through inventory, licence optimisation and compliance on the platform, and how ARDURA Consulting and Flexera One turn software chaos into savings covers the financial angle. This article assumes the decision for Flexera One has been made.
Why implement a SAM tool now rather than next year?
Because pressure from both sides, cost and audit, is growing while visibility shrinks. The Flexera 2026 State of ITAM Report, based on a survey of 512 professionals worldwide, contains several numbers that work well in a board discussion.
Audits are the norm, not the exception. 48% of organisations were audited by a software publisher in the past year. 44% spent more than USD 1 million on vendor audits over three years. Among those audited, 64% reported a Microsoft audit.
Complete visibility is falling. The share of organisations with complete visibility of their IT estate dropped from 43% in 2025 to 36% in 2026. Only 31% report visibility into AI software.
Waste is growing in new categories. 59% of organisations report increased wasted spend on AI software, 44% on public cloud software and 43% on SaaS.
Inventory is the priority. 78% of ITAM teams name maintaining an accurate inventory as their top priority.
A caveat: this is a report by a tool vendor with an interest in showing the size of the problem, so treat it as a signal of direction rather than a precise measurement for your company. The direction is consistent with what any organisation sees after rolling out Microsoft 365, dozens of SaaS applications and its first AI tools in two years. Without a tool, nobody can answer the CFO’s question, and without a software licence inventory every audit starts with panic.
What does the Flexera One implementation timeline look like week by week?
A typical Flexera One implementation at ARDURA Consulting takes 4 to 12 weeks depending on scope. We split it into four phases. Below is each phase, together with what happens on your side.
Weeks 1–2: assessment. Workshops with IT, procurement and security. We agree the scope: which countries, domains, data centres, clouds and publishers the first phase covers. We review existing hardware and software data sources and assess their quality. We record where the licence agreements live. The output is an implementation plan with a list of sources, the order of publishers and a dated list of client-side tasks. On your side: key people in the workshops and quick scope decisions.
Weeks 3–6: deployment. Configuring the platform tenant and connections to Active Directory or Entra ID, endpoint management tools, vCenter and cloud accounts. Rolling out inventory agents where needed and the data collection components inside the corporate network. The first data reaches the platform and goes through normalisation. On your side: service accounts, firewall rules, maintenance windows for agent installation, security approvals. This is the phase where delays most often arise.
Weeks 7–10: configuration. Importing entitlements: contracts, orders, invoices, data from publisher portals. Configuring licensing rules for priority publishers, for example core-based server licensing, virtualisation rights, per-user and per-device licences. Reconciliation, meaning explaining the differences between what is installed and what was bought. Preparing the first compliance and optimisation reports. On your side: access to purchasing documents and decisions on how to treat exceptions such as test environments or licences in transfer.
Weeks 11–12: training and handover. Training the ITAM team, administrators and report consumers. Handing over configuration documentation, entitlement update procedures and the review cycle. Agreeing who on your side owns the data in the tool. On your side: the people who will take over the tool, and time for them to learn.
The shorter, four-week variant is realistic for an organisation with one country, one domain, a well-maintained Configuration Manager and one priority publisher. Closer to twelve weeks is more likely for a company with several countries, a mixed physical and virtual estate and three or four large publishers. Very large organisations split the work into waves, and the order that works best is by risk rather than geography: the first wave covers the publisher whose audit you expect first, or the one you spend most on, together with all the data sources needed to reconcile it. Later waves add publishers, countries and categories such as SaaS and cloud. That way the first reliable report arrives after a few weeks, not after the whole organisation is covered, and the sponsor gets an argument for funding the next stages.
What makes up the cost of a Flexera One implementation?
The project cost has three parts, and it is worth separating them before you take the budget to the board.
The platform subscription. A fee paid to Flexera or its reseller, usually annual. We have not found a public price list for Flexera One. Pricing depends on the modules and the size of the estate, for example the number of devices, users or the cloud spend under management. This part cannot be estimated reliably without a quote, so we do not give figures.
Implementation services. Consultant time: assessment, deployment, configuration, training. It is billed in person-days or quoted as a fixed fee for an agreed scope. The number of person-days depends on the factors in the table in the next section.
Your own team’s time. Infrastructure administrators, procurement, security, a lawyer reading licence agreements, the SAM process owner. This part never appears on an invoice, but it is a real cost, and its absence is the most common reason for overruns.
Then there is the run cost after implementation: someone must update entitlements with each purchase, investigate new discrepancies and prepare reports. That can be a person in your team or a managed SAM service. If you want to weigh the cost of a whole SAM programme against the savings it can bring, our article on SAM implementation cost and ROI sets out a detailed model.
How do you estimate implementation services before talking to a vendor? Add up the estimated person-days per phase and multiply by the consultant’s day rate. As an illustration of the method only: if assessment takes 5 person-days, deployment 15, configuration 15 and training and handover 5, that is 40 person-days. At an example rate of EUR 500 per day, services would come to EUR 20,000. Your number of person-days may be half that or double, as the table below shows, and day rates for SAM consultants in Germany or the UK are typically higher than in Central Europe. This is not an ARDURA quote, only a way for you to check whether a vendor’s estimate makes sense.
The second budget question is the billing model. There are two basic options, and each shifts risk in a different direction.
Fixed fee for an agreed scope. The vendor prices the whole implementation up front. For the buyer that means budget certainty, but only if the scope is precisely described: which countries, which sources, which publishers, what the end deliverable is. A vendor that takes the risk will include a contingency in the price and bill any deviation as a change. A fixed fee works well after a thorough assessment phase, when both sides know what is in the estate.
Time and materials. You pay for the person-days actually worked. It is a fair model when the estate is poorly known and scope may change, but it requires you to control progress: a weekly report of days used, tasks completed and blockers on your side. Without that control, the project grows with every week spent waiting for approvals and access.
A sensible compromise, often used in SAM projects, is to bill the assessment phase on time and materials or as a small separate fixed fee, and only then quote the remaining phases as a fixed price. You pay for discovering the estate once, and the implementation quote rests on facts rather than on assumptions from a sales deck. Also ask who pays for idle time: if consultants wait a week for a service account, the contract should say how that week is billed.
What drives the timeline and cost the most?
The table below lists the factors that in practice decide whether a project lands at the lower or upper end of the range. Use it as a checklist before your vendor conversation.
| Area | Simple case (shorter implementation) | Complex case (longer implementation) | What to prepare on your side |
|---|---|---|---|
| Geography | One country, one legal entity | Several countries and entities, separate purchasing | List of entities and countries in phase one |
| Identity and domains | One AD domain or one Entra ID tenant | Several domains, mergers, acquisitions | Map of domains and tenants, service accounts |
| Inventory sources | Well-maintained Intune or Configuration Manager | No central tool, many islands | List of sources with a completeness rating |
| Data centre | A few physical servers | Heavy virtualisation, clusters, many hosts | Access to vCenter or Hyper-V, cluster description |
| Priority publishers | One, for example Microsoft | Microsoft, Oracle, IBM and SAP at once | Ranked publisher list with rationale |
| Entitlements | One master agreement, portal access | Scattered agreements, no purchase history | Complete contracts, invoices and portal access |
| SaaS and cloud | Out of scope for phase one | In scope from the start | List of SaaS apps and cloud accounts |
| Security | Fast approval path | Long change procedures, segmented networks | A named security contact for the project |
| Process owner | Named before kick-off | None, or “the team” | The name of the accountable person |
Look at the last column. Almost every factor that lengthens the project originates on the client side, not with the tool or the vendor. That is good news, because it means you can shorten the project before the consultants start the clock.
What changes when you move to Flexera One from another tool?
Many implementations do not start from zero. The company already has Snow License Manager, ServiceNow SAM, its own entitlement spreadsheet or reports from Configuration Manager, and the move to Flexera One comes from tool consolidation, an acquisition, or the old solution no longer keeping up with cloud and SaaS. That situation has advantages and traps.
Advantage: entitlements already exist somewhere. If the old tool held imported contracts and purchases, they can be migrated rather than collected again, which can shorten the configuration phase by several weeks. The condition is that the data is current. Entitlements nobody has updated for two years, moved into a new tool, give you a wrong answer faster, not a better one.
Advantage: the team knows the process. People who ran reconciliation in the old tool understand the concepts, exceptions and contract specifics. Training is then about the new platform, not SAM basics.
Trap: two tools running in parallel. For several weeks both tools collect data and show different numbers. Decide up front which one is the source of truth during the transition and when the old one will be switched off. Otherwise procurement and finance receive two conflicting reports.
Trap: duplicate agents. Two sets of agents on the same servers mean extra load and extra work for security. Plan the order: new sources first, then completeness checks, then removal of old agents.
Trap: publisher reporting requirements. If the old tool underpinned reporting a publisher requires, for example IBM sub-capacity licensing, which must be reported with an IBM-accepted tool, do not switch it off until the new setup covers that function in a way the publisher accepts.
The assessment plan should include migration as a separate item with a decommission date for the old tool. Without that date, the company pays for two subscriptions for a year.
Which entitlement data should you prepare before kick-off?
Entitlements are the most underestimated part of an implementation. The tool can find every installation, but it does not know what you bought until you show it. A compliance report without complete entitlements shows a licence “shortfall” that does not exist, or, the other way round, hides a real risk.
Before kick-off, collect:
Master agreements and their terms. Microsoft Enterprise Agreements, CSP and MCA agreements, Oracle agreements with support identifiers, IBM Passport Advantage agreements, SAP and Adobe agreements. Not only licence counts matter but also terms: virtualisation rights, downgrade rights, test environment rights, core counting rules.
Purchase history. Orders and invoices for at least the period a publisher audit could cover. If purchases went through a reseller, ask it for a statement.
Access to publisher portals. The Microsoft 365 admin centre and licensing portals, My Oracle Support, IBM Passport Advantage, SAP for Me. Find out who has access and grant it to the person who will import the data.
Information on licence transfers. Licences moved to the cloud under bring-your-own-licence, licences assigned to divested entities, licences in migration.
It helps to have these documents in one repository before week 7, when configuration starts. If collecting them involves several departments, start in parallel with the assessment, in week 1. Our glossary entry on licence compliance explains why contract terms matter as much as the numbers.
Which access and technical approvals must be ready?
The deployment phase is where timelines most often slip, almost always for the same reason: waiting for access or approval. Here is what to prepare.
Service accounts with read-only rights to Active Directory or Entra ID, endpoint management tools, vCenter or Hyper-V and cloud accounts. Write access is not needed for inventory.
Approval for inventory agents. Security should know what the agent does, what data it collects and where it sends it. Give them the vendor documentation and agree whether the agent can be deployed through your existing software distribution tools.
Network rules. Communication from agents to the data collection components inside your network, and from those components to the cloud platform. In companies with segmented networks, for example production networks in plants, this is often a separate request per zone.
Maintenance windows. Installing agents on production servers usually needs a maintenance window. If your company schedules windows once a month, book them for weeks 3–6 now.
Data protection review. The tool collects, among other things, user names and application usage. Under GDPR your data protection officer should review this before kick-off, not halfway through. In Germany, also check early whether the works council needs to be involved, since usage monitoring of employees can trigger co-determination rights.
Each item can take from one day to several weeks depending on the organisation’s culture. The golden rule: name one person in security who looks after the project, and invite them to the week 1 workshop.
Who from your organisation do you need, and for how long?
A Flexera One implementation is not an IT department project. It sits where IT, procurement, finance and security meet. These are the roles to staff before kick-off, with indicative involvement. The figures are an estimate you should confirm with your vendor for your scope.
SAM process owner (IT Asset Manager or similar). Decides scope, priorities and exceptions and takes over the tool afterwards. Involvement during the project: a large part of the working week.
Infrastructure administrators (AD, endpoints, virtualisation, cloud). Create service accounts, install agents, open network rules. Involvement concentrated in weeks 3–6.
Procurement. Provides contracts, invoices and reseller information. Involvement concentrated in weeks 1–2 and 7–10.
Security and data protection. Agent approvals, data processing review, network rules. Involvement concentrated at the start.
Executive sponsor (CIO or CFO). Settles disputes on priorities and budget and receives the first reports. Involvement: short meetings every two weeks.
The most common mistake is assuming “the consultants will do everything”. Consultants will configure the tool, but they will not obtain contracts from three countries or a security approval on your behalf. If you already know your team lacks the time, consider adding a SAM specialist to the team for the project or a managed SAM service after go-live.
Which warning signs appear during implementation?
A few signals let you see early that a project is heading the wrong way. They are worth knowing, because every week of delay is a week of paid subscription without value.
By the end of week 4, most sources are not sending data. That usually means blocked approvals or network rules. Escalate to the sponsor instead of waiting.
Normalisation leaves a large number of unrecognised applications. Some internal applications will always be unrecognised, but if popular commercial software is affected, the problem lies in source data quality or collection configuration.
The first compliance report shows a huge licence shortfall. That almost always means incomplete entitlements, not a real shortfall. Do not show such a report to the board before reconciliation.
Nobody on your side can demo the tool. If in week 10 only the consultants can operate the platform, handover will fail. Training should start earlier than the last two weeks.
Scope creeps during the project. “While we are at it, let us add SaaS and cloud” is a reasonable thought for phase two but a dangerous one in phase one. Record every scope extension as a change with its effect on timeline and cost.
How do you choose an implementation partner and what goes into the contract?
Before signing an implementation services contract, ask a few questions. The answers will tell you more than a presentation.
What does the plan look like for my scope? Ask for a timeline with phases, person-days per phase and a list of tasks on your side. A vendor that cannot say what it needs from you will not manage it during the project either.
Which publishers and licensing rules are in scope? Configuring rules for Microsoft, Oracle, IBM and SAP takes different expertise. Check that the vendor has experience with the publishers that matter to you.
What is the end deliverable? A configured tool is not enough. Write into the contract: working data sources at an agreed completeness level, imported entitlements for named publishers, a reconciled first compliance report, configuration documentation, training and run procedures.
What happens after handover? Does the vendor offer post-go-live support, periodic reviews or managed SAM? Settle this before signing, not after.
How are scope changes handled? The change mechanism, rates and approval process should be in the contract.
ARDURA Consulting specialises in Flexera One implementations and delivers them end to end: assessment, deployment, configuration, training and ongoing optimisation, in the four phases described above. We also work with Snow, ServiceNow SAM and Microsoft SAM tools, and as an IBM Business Partner we bring enterprise-grade discovery and optimisation tooling. Our SAM services are available as a one-off SAM assessment, managed SAM or SAM tool implementation. Details of the implementation scope are on our Flexera One page.
What should you do in the first 90 days after go-live?
The end of the implementation project is the start of the work, not the end. The first three months after handover decide whether the tool becomes the source of truth or another system nobody updates.
Set a reconciliation cycle. Every week or two, the process owner reviews new discrepancies: new installations, new purchases, devices that stopped reporting. Without this, the data goes stale quickly.
Build the tool into procurement. Every software purchase should end with the entitlement being imported into the platform. The simplest way is a step in the purchasing procedure and a named person in procurement.
Start with one quick optimisation. Reclaiming unused licences for one large product gives the board proof that the tool works. Our article on license harvesting describes a practical approach.
Prepare for the audit before it arrives. A reconciled licence position for the priority publisher is the best answer to an audit letter. If an audit has already been announced, reconciliation for that publisher should be the first task after go-live.
Measure progress with a few simple indicators. The board does not need dozens of charts. Five numbers reported monthly are enough: the share of devices that reported in the last 30 days; the share of installations recognised by normalisation; the share of software spend with imported entitlements; the licence position for priority publishers; and the value of licences reclaimed or purchases avoided. The first three tell you whether the data is reliable. The last two tell you whether the tool pays for itself.
Plan phase two. SaaS, cloud, further publishers, further countries. Phase two is usually shorter, because processes and people are already in place. Cloud cost work fits naturally here, and our glossary entry on FinOps explains how it connects to licence management.
What should you remember before starting a Flexera One implementation?
A Flexera One implementation typically takes 4 to 12 weeks and goes through four phases: assessment, deployment, configuration, and training and handover. Whether the project lands at the lower or upper end depends mainly on client-side factors: the number of countries and domains, the quality of existing inventory sources, the number of priority publishers, the completeness of contracts and the speed of security approvals.
The cost has three parts: the platform subscription, implementation services and your own team’s time. The first is priced by Flexera or its reseller, the second you can check with the person-day method, and the third is the one most often forgotten, even though it affects the timeline most.
Before kick-off, prepare contracts and purchase history, publisher portal access, read-only service accounts, agent approvals, network rules, maintenance windows and a named SAM process owner. In the contract with your implementation partner, describe the end deliverable, not just “tool configuration”. After go-live, set a reconciliation cycle and build the tool into procurement.
If you are planning a Flexera One implementation or want to check whether your organisation is ready for one, see how we implement Flexera One or book a scoping call. We start with a one-to-two-day discovery workshop and will tell you what is missing on your side before you start paying for consultant time.