I make sure your IT project succeeds, stays on budget, and actually serves your business. The IT industry needs more straight talk and less dancing around issues.
I'm on your side of the table.
Tell us about your project →The most common reason IT projects fail isn't technology — it's that nobody dares say the hard things out loud. I ask the questions others avoid.
I stop the train if reality and the original plan don't match. In integration projects, I demand time for groundwork before execution.
In one project, the vendor offered two options. My assessment revealed Option B would take 15 hours — while Option A would have required 150 hours.
I don't represent any vendor. If a cheaper option would be enough, I'll tell you. My only interest is your benefit.
Scope, schedule, budget, architecture, and risks. Know where you're starting from.
Architecture and design mistakes are expensive to fix later. I spot them early.
Leadership understands where things stand. No cryptic reports — clear facts.
What was built temporarily and stayed that way. It's expensive for the future.
Does the billing match the work done? Is the hour usage sensible?
Companies with an IT project underway or coming up with an external vendor — who want an independent expert on their side.
Nobody can say why. Timelines stretch, budgets grow. Need an outside view.
Is the hour usage sensible? Does the billing match the actual work?
You want a second opinion before committing to millions.
But you need that perspective on whether the project will succeed.
I jumped into an integration project where Confluence was a dumping ground — all the real knowledge lived in people's heads. Jira didn't reflect reality. Documentation was missing or scattered.
I built a new documentation model with clear structure, cleaned up Jira, and made sure all customer communication was saved in one place. At the same time, I audited the technical architecture and raised risks to management before they became problems.
I also found a missing scope gap: my partner's client's RFQ was missing key information, and the integration platform's underlying data was a mess (IDoc, XML, HR format, SFTP routing). I made the case to my partner's client that you don't build automation on top of an archaeological dig. The client paid for the platform cleanup separately.
Always starts with a conversation. Tell me about your situation and project, and I'll assess how I can help best. The Guardian's role can be a one-time assessment, ongoing monitoring during the project, or a second opinion before a big decision. Always case-by-case — no blind monthly contracts.
Tell me about your situation — I usually respond the same day.