Skip to content

Cloud transition, security and performance audits

IT & Architecture Consultancy

Independent technical assessment: architecture review, cloud transition planning, performance and security audits, delivered as a written report with prioritised, costed recommendations.

2–6 weeksFixed-fee audit or advisory retainer

The problem this solves

Consultancy that ends in a slide deck is worth very little. Ours ends in a document an engineering team can act on: what is wrong, what it costs to leave it alone, what to change first, and how to tell whether the change worked.

What the work includes

  • Architecture and code review against stated quality attributes
  • Cloud transition assessment — what to move, what to rebuild, what to retire
  • Performance profiling with reproducible benchmarks, not impressions
  • Security review modelled on the OWASP ASVS and CIS benchmarks
  • Build, release and environment-management assessment
  • Technology selection with the trade-offs written down

How the engagement runs

  1. 01

    Technical discovery1–2 weeks

    A paid, time-boxed discovery: we read the existing code and data model, interview the people who run the process today, and write down the constraints. It ends with a specification, not a proposal deck.

  2. 02

    Architecture and scope1–2 weeks

    Architecture decisions are recorded with the alternatives we rejected and why. Scope is split into milestones that each end in something demonstrable, so progress is observable rather than reported.

  3. 03

    Iterative deliveryBulk of the engagement

    Two-week iterations against your repository and your board. Every iteration ends with a deployable build, automated tests, and a written summary of what changed and what is still open.

  4. 04

    Handover and support1–2 weeks, then optional retainer

    You receive the source code, the infrastructure definitions, the runbook and a recorded walkthrough. Continued support is a separate, optional agreement — never a dependency we engineer in.

A note on the duration stated above

2–6 weeks is a typical range for this shape of work, not a commitment. Real scope, existing data quality and the availability of the people who know the current process all move it. The date we commit to appears in the written quote.