HKGpipi

METHOD

From opportunity to verified saving.

HKGpipi owns the path from identifying economically meaningful AWS waste to measuring the result of an approved production change.

Operating principle

Recommendations are inputs.Verified reductions are outcomes.

01 · Operating method

Six stages. One accountable path.

Each stage has a purpose, an evidence requirement and a clear output. Production authority remains with the customer.

  1. 01

    FIND

    Purpose

    Identify economically meaningful AWS cost opportunities.

    Evidence / action

    Billing and cost data, waste, commitment exposure and architecture patterns.

    Output

    Candidate opportunity

  2. 02

    VALIDATE

    Purpose

    Test whether the opportunity remains worth acting on after usage, commitment and engineering-risk context.

    Evidence / action

    Usage evidence, relevant commitments and engineering-risk context.

    Output

    Validated opportunity

  3. 03

    ASSIGN

    Purpose

    Connect the opportunity to the responsible workload, owner and implementation location where identifiable.

    Evidence / action

    Workload, team and infrastructure context.

    Output

    Accountable owner / implementation context

  4. 04

    CHANGE

    Purpose

    Define the engineering remediation required.

    Evidence / action

    PR, ticket, configuration change or specific implementation instruction, as appropriate.

    Output

    Change-ready work

  5. 05

    APPROVE

    Purpose

    Move the work through the customer's existing engineering and change-control process.

    Evidence / action

    Customer review, checks and approval authority.

    Output

    Customer-approved work

  6. 06

    VERIFY

    Purpose

    Measure the post-deployment economic result against the agreed baseline.

    Evidence / action

    Baseline and post-change billing evidence under the agreed verification basis.

    Output

    Verified saving

02 · Decision gates

An opportunity earns its way forward.

A recommendation advances only when the evidence supports the next decision.

  1. IDENTIFIED
  2. Technically valid?
  3. Economically meaningful?
  4. Acceptable engineering risk?
  5. Owner / context known?
  6. Customer approved?
  7. Deployed?
  8. Measured?

03 · Responsibility split

Engineering delivery without taking away customer control.

Primary rolesNot a contractual RACI
Primary roles from opportunity identification through verification
DecisionHKGpipi primary roleCustomer primary role
Opportunity identificationDrives analysisProvides bounded access and context
Engineering risk validationDocuments evidence and riskSupplies workload and architecture context where required
Change preparationPrepares remediation workReviews through existing process
Production approvalDoes not own approval authorityRetains approval authority
DeploymentWorks with engineeringRetains deployment control
VerificationMeasures against agreed basisReviews agreed result and basis

04 · Traceability

Keep the saving connected to the change.

Decision evidence stays attached from the identified opportunity through approved remediation and measurement.

Illustrative

Opportunity
RDS rightsizing
Expected
£4,820 / mo
Owner
Platform
IaC
infra/prod/rds.tf:118
State
Approved / illustrative
Change
db.r6g.4xlarge → db.r6g.2xlarge
Measurement
Post-change verification pending
Synthetic example

This trace is illustrative. It is not customer activity, a live account or a measured customer result.

05 · Next action

Start with bounded discovery.

The Savings Sprint identifies, validates and ranks the work before implementation begins.