IT project management
Your IT projects delivered on time and on budget — without the corporate jargon.
IT projects rarely fail for technical reasons. They fail from scope creep, poor management communication, lack of stakeholder buy-in and unrealistic estimates. If you've been there even once, you know exactly what we mean.
Updated
If at least three of these sound familiar, it's time to talk.
Projects running over budget until they can no longer be justified
Scope changes every week, with no approval process
External suppliers delivering poor work because nobody checks technically what you receive
Management learning about problems only at go-live
Internal teams stuck on unclear priorities
Every project starts with a structured kickoff: business case, measurable success criteria, RACI, communication plan, initial risk identification. If we can't clearly articulate why we're doing the project, we stop before spending money.
We use hybrid methodologies (waterfall for fixed-scope projects, agile for exploratory ones) — the choice depends on the project nature, not fashion. Tracking in Jira, Azure DevOps or Monday — your choice.
Structured weekly reporting: RAG status, active risks, decisions needed, scope changes. Stakeholders no longer have surprises, and you can escalate when needed — not post-mortem.
The first document is the scope: what is in the project, what is out, the criteria for accepting deliverables and who approves a change. Every new request goes through the same three questions: what it costs, how much it delays the project and who signs off.
The plan has stages with deliverables you can check, not progress percentages. Every production change gets an agreed window and a rollback plan. Risks sit in a register with likelihood, impact, owner and a prepared response, reviewed weekly together with the status report: green, amber or red, which decisions we need from you and what has changed.
Dragoș Nimu has run IT in large companies in Timișoara, as IT Manager and IT Director at TRW Automotive, Takata, Profi, AEM and Rus Savitar. At Profi he led the virtualisation of 80% of a 200+ server farm and the migration of the LAN to Cisco. He holds a project manager certificate (COR 242101, 2025) and ITIL v3 Foundation.
Many supplier problems start with vague requirements written before the contract. We write the specification so offers can be compared on the same scope, set the evaluation criteria before we see the prices, and negotiate a contract with measurable deliverables, deadlines and service levels.
During the project we check technically what the supplier delivers before you sign the acceptance: we test, ask for the promised documentation and record deviations. When a delay appears, escalation follows a path agreed at the start.
A funded project is also checked on its documents. Regulation (EU) 2021/1060 requires the managing authority to ensure that the supporting documents of an operation are kept for five years from 31 December of the year in which it makes the last payment to the beneficiary (Article 82). Article 50 requires you to make the Union's support visible on your website, on documents and on a poster or plaque; if you fail to do so and do not remedy it, the authority can cancel up to 3% of the support.
We prepare the technical part of the application under NACE code 62.20: an IT audit of the infrastructure with a signed report at €900 excluding VAT, or the complete file, with feasibility study and specifications for the tender documents, at €3,300 excluding VAT. During implementation we keep the records that matter at inspection: versions of the specification, acceptance reports, supplier correspondence and proof of visibility.
Business case, success criteria, RACI, risk register, communication plan.
RFP, bid evaluation, SLA negotiation, deliverable monitoring, escalations.
ERP, CRM, infrastructure, cloud — end-to-end coordination with cutover plan and tested rollback.
For organisations building internal capability: templates, governance, metrics.
For already-failing projects: diagnosis, recovery plan, leadership through stabilisation.
1-1 mentoring for junior or mid-level PMs in your team, with concrete objectives.
Understanding context, stakeholders, real constraints (time, budget, people).
Charter document signed by sponsor + executive plan (milestones, budget, risks).
Sprints or phases (per methodology). Daily/weekly check-ins. Weekly RAG reporting.
Cutover plan, 2-4 week hypercare, knowledge transfer to operations.
Lessons learned, realised vs estimated benefits, formal handover to business owner.
Weekly RAG reporting. You know at any time where you stand on timeline and budget.
Vendors deliver what they promise because they have a counterparty who understands what to verify.
Proactive identification, structured escalation, data-driven decisions — not gut feel.
Structured knowledge transfer, on-the-job mentoring for your PMs.
The technical documentation for your application, delivered under CAEN 6220
from €900 excl. VAT
Audit + plan + migration roadmap
from €1,000 excl. VAT
Strategy + board reporting + DNSC interface
from €1,400 excl. VAT
The price is set per project, because the effort depends on duration, the number of suppliers and how many hours a week you need a project manager. We do not give you a figure before we understand the project. We start with a free 30-minute call, then send you an offer with estimated hours and deliverables. Some parts have a fixed price: the technical file for EU funding starts at €900 excluding VAT, and running security projects through our vCISO service starts at €1,400 per month excluding VAT, for 8 hours.
We start with a diagnosis, before any promise. We read the contracts, the plan and the correspondence, talk to the team and the suppliers, and separate what was actually delivered from what was reported. Then we put the options in front of you, with the cost and timeline of each: continue with reduced scope, continue with a new budget and deadline, or stop the project and keep what can be used. You make the decision, on numbers. If you choose to continue, we lead the project until it is stable and then hand it back to your team.
Yes, and we do not ask you to replace them. Our role is to be the party that understands technically what is being delivered: we read the offer and the contract, set the acceptance criteria, track deadlines and check deliverables before you sign. If a supplier cannot deliver what was promised, we tell you early and prepare the fallback with you: renegotiation, another supplier or a smaller scope. For each supplier we keep a short list of commitments: what was promised, by when and how we check it.
The one that fits the project: waterfall planning when the scope is fixed and known, such as a server migration, and short iterations when requirements become clear along the way, such as a new application. We track tasks in Jira, Azure DevOps or Monday, whichever your team already uses. Whatever the method, the weekly report has the same shape: green, amber or red status, active risks, decisions needed and scope changes.
Everything that proves the money went where the funding application says. That means the application and the grant agreement, every version of the specification, the offers received and their evaluation, supplier contracts, invoices, acceptance reports and proof of visibility: the web page, the poster or the plaque. Article 82 of Regulation (EU) 2021/1060 provides for keeping supporting documents for five years from 31 December of the year of the last payment to the beneficiary. Check the exact period that applies to you in your grant agreement, because State aid rules can require longer.
30 minutes — we explore what you have, what's missing and what concrete next steps look like.