Independent IT project audit for companies
Verify your IT project quote and scope before you sign the contract
I review software-house offers, estimates, scope, architecture and technical risks. You get a clear recommendation: proceed, renegotiate, simplify or stop the project.
15 years on both sides — vendor and client. No commission on delivery. No interest in growing the scope.
For companies planning or running expensive IT projects.
The most expensive mistakes start before the code
Six questions worth asking before you sign the contract.
Hasn't the scope been inflated?
Isn't the architecture too complex?
Could the same outcome be achieved more simply?
Have the risks been named?
Do you have someone on your side who can challenge it?
Audit scope
We pick the audit scope based on the stage, value and risk of your project.
IT estimate audit
Independent review of a software-house or IT vendor quote: estimates, assumptions, buffers and items to negotiate.
Project scope audit
Verification whether the scope matches the real business need — and which items can be removed or postponed without harm.
Architecture audit
Check whether the proposed solution fits the actual problem and is not over-engineered.
Vendor audit
Assessment whether the technology partner fits the project — including vendor lock-in risk and execution-side dependencies.
In-flight project audit
Independent review of a project whose budget is growing or timelines are slipping. Identification of costs you can still avoid going forward.
Fractional CTO post-audit
Continued decision support for companies that need an experienced technical person on their side without hiring a full-time CTO.
How the audit works
Five steps from first message to decision. No hidden stages.
- You send the offer, scope, estimate or a description of the problem.
- We sign an NDA if the documents are confidential.
- I analyse the scope, assumptions, estimate, architecture and risks.
- You get a document with recommendations and a list of negotiation points.
- We discuss the decision: proceed, renegotiate, simplify or stop the project.
What I need
- the offer from the software house
- an hourly or fixed-price estimate
- scope / backlog / mockups
- the contract or contract draft
- a description of the business goal
- budget and timeline information
How long it takes
- Initial assessment
- 1–2 business days
- Full audit
- usually 3–7 business days
- Urgent pre-signature review
- ask about availability
What you get
A concrete document, a list of recommendations and a decision conversation. No fluff.
- An assessment of whether the project and estimate make sense.
- A list of places where you may be overpaying.
- Items to negotiate with the vendor.
- An assessment of technical and organisational risks.
- Simplification recommendations.
- Action priorities.
- A clear recommendation: proceed, renegotiate, simplify or stop.
The audit must pay for itself
A lower estimate, a simpler scope, less risk — or stopping a project that does not make sense.
I don't build. I audit.
This is not a software-house offering. I have no interest in making the project bigger, longer or more expensive.
My job is to help you make a sound decision — even if the best decision is to simplify, renegotiate or stop the project.
When an audit makes sense
It makes sense if:
- you've received a high IT-project quote
- you're about to sign with a software house
- the project is running but the budget is growing
- you have no CTO on your side
- you want to negotiate price or scope
- the vendor pitches T&M, Scrum and a series of milestones, while you want to understand the consequences for budget, scope and deliverable
- you suspect overengineering
- you need an independent opinion before deciding
It's probably not for you if:
- you're looking for an app vendor
- you need a developer by the hour
- you only want confirmation of your decision
- you don't want to challenge scope or architecture
- you expect a report without a business-decision conversation
Experience on projects for demanding organisations
Selected organisations whose projects I worked on during the past 15 years.
Sebastian Kubiak
15 years in software houses.
I know how estimates are built and where unnecessary costs creep in — because I was on the other side of the table.
Today I work on the client's side as an independent auditor and fractional CTO.
- Experience
- 15 years
- Working for
- Client
- Conflict of interest
- None
Frequently asked questions
Short answers to the questions I get most often before we start.
Q.01 Do you sign an NDA before the audit?
Yes, if the documents contain confidential information. We sign the NDA before I start working on the scope, estimate or architecture.
Q.02 Do you talk to the software house directly?
Optionally. I can work only on documents (offer, scope, estimate, contract draft) or step into a direct technical conversation with the vendor — whatever is more convenient for you.
Q.03 Does an audit make sense if the project is already running?
Yes, especially if the budget is growing, the scope is drifting or the deliverable is not in sight. An in-flight audit focuses on what can still be avoided going forward.
Q.04 Will I only get a technical opinion?
No. You get a decision recommendation: proceed, renegotiate, simplify or stop the project. Plus a concrete list of points to negotiate with the vendor.
Q.05 Can you then run the project as a CTO?
Yes — in a fractional CTO model, if you need decision support on the client side after the audit. Without hiring a full-time CTO.
Got a quote to verify?
Send the quote, scope or project description. I will get back with a note on whether an audit makes sense.