Question → evidence
Assess
Frame the real question. Understand the system, constraints, incentives, evidence and cost of staying still.
Independent engineering advisory
Technology strategy.
Architecture.
Remediation.
I assess systems, recommend architecture and technology choices, plan modernisation, and lead remediation delivery.
Services & pricing ↗Start with the problem
Nobody calls about architecture.
They call because a buyer stopped the deal, an auditor left a list nobody owns, a vulnerability went public, or a release is blocked and no one can say by what. Architecture is usually what the answer turns out to be.
Buyer requirements block the deal
A customer’s security requirements are holding up the sale.
What this involves ↗Evidence is assembled after the fact
Your buyers require security evidence your delivery process does not produce.
What this involves ↗A vulnerability was disclosed in your product
A vulnerability in your product is public, and your customers are asking.
What this involves ↗Imaging systems reachable from outside
Your imaging archive may be reachable from the internet.
What this involves ↗Findings with no owners
An audit or penetration test returned findings nobody owns.
What this involves ↗A decision with no criteria
A technology decision is being made on the strength of the word, not the problem.
What this involves ↗The system is slowing delivery
Architecture and ownership have drifted, and change has become expensive.
What this involves ↗How the work is done
What the work consists of.
01
Security engineering and compliance
Turning a customer or regulatory requirement into controls that exist, owners who hold them, and evidence that survives being questioned.
↗ 02Architecture and system assessment
Establishing how the system actually works now, why change costs what it costs, and which directions are genuinely open.
↗ 03Platform, cloud and modernisation
Deciding where the platform should go, and in what order to get there, at a scale the problem actually justifies.
↗ 04Technology strategy and decision support
Settling a decision — a vendor, a platform, build or buy, cloud, AI — with the reasoning written down so it holds up later.
↗ 05Technical due diligence
Testing what a company says about its technology before money moves, and saying what would change the price.
↗ 06Remediation and engineering leadership
Owning the work that closes a findings list: sequence, decisions, the awkward changes, and proof each item is finished.
↗Defined engagement
Technology Decision Review.
A focused review for an architecture, platform, vendor, cloud, AI or build-versus-buy decision. The review documents the decision, evaluation criteria, options, trade-offs, recommendation, approval conditions and a 90-day action plan.
See scope and deliverables ↗DecisionPlatform direction for a regulated product environment
RecommendationAdopt conditionally
Proceed only after ownership, exit path and operational controls are agreed.
ConfidenceHigh on direction.
Medium on readiness.
Medium on readiness.
01Decision framing & constraints
02Options and trade-offs
03Risk conditions
0490-day decision path
Services & starting prices
Engagements and starting prices.
Fixed scopeTechnology
10 business days · from €9,500 excl. VAT
Technology
Decision Review
Independent recommendation, options, trade-offs, economic impact, decision conditions and a 90-day action plan.
Scope and deliverables ↗ Fixed scope10 business days · from €6,500 excl. VAT
Findings Translation Sprint
Normalised findings, technical priorities, owners, dependencies, evidence needs and a 30/60/90-day plan.
Scope and deliverables ↗ Delivery6–12 weeks · from €9,500/month excl. VAT
Remediation Delivery Lead
Backlog leadership, technical reviews, team coordination, evidence collection and retest readiness.
Scope and deliverables ↗ AdvisoryScoped per engagement · from €9,500 excl. VAT
Architecture, Strategy & Engineering Advisory
Assessments, due diligence, target architecture, platform and modernisation strategy, and external technical leadership.
View all services ↗ Starting prices are indicative and exclude VAT. Final scope and commercial terms are confirmed in a written proposal.
Delivery method
Assess.
Design. Deliver.
Each phase has a documented output. The engagement can stop after a recommendation or continue through implementation.
Evidence → direction
Design
Choose the direction. Make assumptions and trade-offs explicit, then define the conditions for success.
Direction → operating change
Deliver
Review implementation decisions, resolve blockers and collect evidence until the agreed scope is complete or risk is formally accepted.
Who calls
CTOs, CIOs, security leaders, investors and specialist partners.
Usually when a technical decision crosses architecture, cost, security, ownership and delivery.
See client situations ↗No handover
The person who scopes the work forms the recommendation and stays through implementation.
No vendor quota
No commission is earned from recommending a cloud, a platform or a product.
Capacity is finite
Availability is confirmed before a proposal is issued, not after it is signed.
Regulated work
Technical change is tied to ownership, controls and the evidence someone will ask for.
Partner delivery
Technical delivery support for audit, security and GRC partners.
Findings become architecture decisions, engineering ownership, remediation work and closure evidence.
Partner services ↗Contact
Need a documented technology decision or remediation plan?
Send the decision, the affected system, the known constraints and the deadline. You get back the relevant service and the inputs it needs.
Send the context ↗