FAQ: the questions asked before choosing an IT consultancy.
This page brings together the questions that come up when an IT department is looking for a partner to support a transformation: advisory stance, method, commitments, independence, skills transfer, pricing and the ability to work in complex environments. Technical questions specific to ITSM, FinOps, Atlassian, AI or portfolio management are dealt with directly in the corresponding offer pages.
Atlassian Platinum Solution Partner · Alongside IT departments since 2008 · Paris and Lyon
Where to find the technical answers.
Detailed questions by area are dealt with directly in the offer pages:
| Your question is about | The page that answers |
|---|---|
| The scope, duration and price of an audit | The Assessment |
| ITSM, ITIL, the CMDB, SLAs, choosing a tool | IT service management |
| IT costs, FinOps, ITFM, IBM Apptio | IT cost control |
| Adoption, change management, methods | Change management |
| The project portfolio, PPM, OpenProject | Project & portfolio management |
| Support, application maintenance, run SLAs, reversibility | Application maintenance and managed services |
| Jira, Confluence, Jira Service Management | Atlassian |
| Atlassian licensing and pricing | Atlassian licensing |
| A migration to Atlassian Cloud | Cloud migration |
| Archiving Jira projects before migration | Jira archiving and Aquarius |
| MCP, Rovo, agents, AI governance | Artificial intelligence |
| Results achieved, figures, references | Case studies |
| Training courses and their funding | Training |
| The constraints of your market | Industries |
Who are we?
Who is BleuLemon and what experience do you have with IT departments?
BleuLemon has supported IT departments in their transformation projects since 2008.
We work on management and governance, Atlassian platforms, service management, IT costs, change management, the integration of artificial intelligence, and project and portfolio management.
We have more than 30 staff in Paris and Lyon, with complementary experience and backgrounds, and we work across France as well as in multi-site and multi-country environments. About.
What is the difference between BleuLemon and a technical staffing arrangement?
Technical staffing mainly makes skills available under your direction.
Our role goes further: we scope, we challenge the request when that is useful, we propose choices, we implement, we support adoption and we prepare for continuity over time.
We can also reinforce your teams where that is the right model, but without losing our advisory, co-construction stance. IT Management & Governance.
What certifications and partnerships do you hold?
BleuLemon is, among other things, an Atlassian Platinum Solution Partner Enterprise with the ITSM Specialized specialisation, an IBM Silver partner, an OpenProject and XWiki partner, and has certified Matrix42 experts.
Our teams also include consultants certified in various methods and solutions, notably ITIL, SAFe and La Fresque du Changement.
These certifications attest to a level of mastery. They do not, however, replace field experience or the ability to adapt methods to the client's context. The Atlassian pillar.
Our stance and our method.
How do you make sure you are addressing the right problem?
We always start by understanding the why behind the request.
The stated need is our starting point, not necessarily our conclusion. We seek to understand the objectives, the ways of working, the irritants, the constraints and the expected results.
This lets us answer the request precisely, but also challenge it when another scope, another priority or another trajectory looks more relevant. The Assessment.
How does a BleuLemon engagement unfold?
Our approach follows five stages: understand, scope, deploy, drive adoption, keep it alive.
Understanding means starting from reality. Scoping sets the objectives, the scope and the success criteria. Deploying implements the solution. Driving adoption works on ways of working, training and practices. Keeping it alive covers support, changes and continuous improvement.
This framework stays the same across our engagements, even if its operational form varies with the subject. The five-stage framework.
How do you stop a transformation project coming down to deploying a tool?
We start by understanding the why: the objectives, the ways of working, the processes, the irritants and the expected results. The tool comes afterwards.
Our approach connects scoping, implementation, change management and long-term operation. A tool can be perfectly installed and produce no value if it does not find its place in the organisation. Change management.
What do you call a successful project?
A successful project is one that lastingly produces the expected value, not just a project that has been delivered.
Success is measured in use: real adoption, process efficiency, service quality, the ability to make better decisions, and the solution's capacity to evolve with the organisation.
A project that lives on is also a project that keeps improving after its release. Change management.
Do you work with our teams, or instead of them?
With them. We prefer to see ourselves as a partner in your success rather than simply a supplier of solutions.
We favour co-construction and skills transfer. Your teams remain the owners of the decisions, the ways of working and how things run over time.
Our consultants can scope, deploy, train, document and support your teams so that the knowledge and the ability to develop the solutions stay with you at the end of the engagement. Change management.
How do you avoid making your clients dependent on BleuLemon?
By preparing, from the outset, your teams' ability to take back control.
We document, we train, we transfer knowledge and we make sure the solutions put in place stay understandable and workable without excessive dependence on us.
Reversibility is part of how we design an engagement, whether it concerns a tool, a support arrangement or an organisation. Training.
How do you bring in AI without creating a new supplier dependency?
We seek to keep control of the models, the access rights, the data, the rules and the costs. Where relevant, a cross-cutting governance layer makes it possible to use several models or providers and to let the AI already present in your information system work side by side.
The aim is not to multiply agents, but to define what they can do, with what rights, under what control and for what value. AI governance and agents.
Are your recommendations independent of your vendor partnerships?
Yes.
Our Atlassian expertise is strong, but it does not determine the solution we recommend. We start by understanding the need and the constraints, then we choose the appropriate technology. We also work with Matrix42, IBM Apptio, OpenProject, XWiki or other solutions when their context of use makes them more relevant.
The right solution is not the one we would rather implement, but the one that lastingly finds its place in your organisation. The Atlassian pillar.
Can you work in regulated or sensitive environments?
Yes.
We work with organisations facing strong constraints of security, sovereignty, compliance or business continuity.
Depending on the sector, this can involve DORA, NIS2, operational sovereignty, access control, reversibility or the specific constraints of sensitive environments. These subjects are built in from the scoping stage and handled with the security, compliance and business teams concerned. Our industries.
Our commitments.
What do you commit to in writing?
It depends on the type of engagement.
On an assessment, we commit to the scope, the duration and the deliverable. On a project, we scope the objectives, the responsibilities and the expected results. On support and application maintenance services, the service commitments and the terms of coverage are formalised.
We favour simple, explicit and measurable commitments rather than contractual wording that is hard to use. Application maintenance and managed services.
How do you handle a project that goes off track?
We say so early.
A project can run into gaps in effort, schedule, scope or dependencies. What matters is making them visible quickly, understanding the cause and proposing a decision.
We prefer to share a difficulty when it appears rather than discover it at acceptance testing. Transparency is one of our commitments. Our case studies.
What happens after the release?
The release is not the end of the project. We can continue the support through application maintenance, user support or additional consultants, depending on your organisation and your needs.
We also monitor adoption, use and the changes needed. A successful solution has to keep working and producing value once the project is over. Application maintenance and managed services.
Getting started and contracting.
How do you price an engagement?
The model depends on the nature of the engagement.
Assessments are generally delivered on a fixed-price basis, over a defined scope and duration. Projects are priced from the agreed objectives and scope. Application maintenance works on an envelope of effort, with each request estimated before it is carried out. Support corresponds to service availability rather than time consumed.
In every case, we aim to make the scope, the commitments and the billing model understandable before we begin. The Assessment.
How soon can an engagement start?
The lead time depends on the type of engagement, the availability of the expertise needed and the complexity of the subject.
A first conversation quickly qualifies the scope, the constraints and the deadlines. We then propose a realistic setup and start date. Contact us.
Do you respond to tenders?
Yes.
We work on private and public tenders, in France and in multi-site and multi-country contexts.
We can provide the items usually requested: references, certifications, CSR commitments, administrative documents, an introduction to the teams, methodology and engagement governance. Our CSR commitments.
Do you have another question?
Some questions are not well handled in a FAQ.
A short conversation often makes it possible to understand your context, your constraints and the level of answer expected more effectively than a generic reply.
Going further: The Assessment, our way in·Our twelve services·Our case studies, with figures·Zest of Mind, the blog·Our white papers·Contact us