Evgeniia Gushchina Governance & Implementation

Kazakhstan · Technology governance advisory

Build the governance system the next consequential decision will test.

I help technology companies in Kazakhstan turn AI, IP and data requirements into clear ownership, controls, working evidence and routines. The work starts with the real decision in front of the business and moves into implementation.

Discuss a live decision See the Diagnostic

When governance becomes commercial

The work begins when the question has a business consequence.

Governance is useful when it helps a company answer a real external demand, make a decision or keep growth from exposing an avoidable weakness.

01

A customer or public-sector buyer is asking for evidence.

A questionnaire, RFP, renewal, procurement or delivery review needs one coherent view of ownership, controls and accountability.

02

The product is moving into another market.

IP, data, AI and vendor arrangements must remain defensible as customers, contracts and operating dependencies change.

03

AI use has outgrown informal responsibility.

Use cases, data boundaries, oversight, vendor responsibility and incident routes exist in fragments rather than as one operating system.

04

An investor or board is testing the operating model.

The company needs to show not only what its policies say, but who owns the decisions and what evidence exists in practice.

The starting engagement

Technology Governance Readiness Diagnostic

A focused 2 to 3 week engagement. It tests the governance system against the decision in front of the company, then shows what should be fixed in the next 90 days.

01 / FRAME

Decision context

Define the external trigger, consequence, owners and the evidence the company will need to produce.

  • decision and deadline
  • stakeholder map
  • targeted evidence request
  • scope and exclusions
Start with the Diagnostic

02 / TEST

AI, IP and data baseline

Review the three connected modules and take one priority module into a deeper operating test.

  • ownership and decision rights
  • controls and records
  • vendor and contractor dependencies
  • implementation gaps
Discuss the baseline

03 / DECIDE

Readiness Pack

Give leadership a clear view of what matters now, who should own it and what the next build must contain.

  • executive decision brief
  • governance workbook
  • evidence checklist
  • 90-day roadmap
Ask for the Readiness Pack

Commercial scope. Scope, access, timeline and fee are agreed around the decision the company needs to make and confirmed in a written proposal before work begins.

Across Kazakhstan

Technology governance for growth across Kazakhstan.

My advisory scope covers technology companies across Kazakhstan. Fit is defined by the business model, operating context and live decision in front of the company.

The strongest fit includes software and platforms, consumer and citizen-facing products, AI products, industrial technology and public-sector technology where evidence and accountability directly affect growth or delivery.

  1. 01Digital productsconsumer · citizen · enterprise
  2. 02AI productsdata · oversight · user evidence
  3. 03Industrial techdelivery · suppliers · acceptance
  4. 04Public-sector techprocurement · delivery · accountability

Responsibility boundary

Senior governance work, with local authority kept local.

What I own

  • governance diagnosis and decision framing
  • roles, controls, records and evidence architecture
  • AI, IP and data operating modules
  • implementation workshops, sign-offs and routines

Where specialists enter

  • Kazakhstan-law opinions and regulated representation
  • certification and formal assurance
  • technical cybersecurity or model validation
  • clinical, tax, licensing and other regulated advice

One practice · Clear market roles

Saudi Arabia is my long-term professional anchor. The Kazakhstan advisory offer stands on its own.

Kazakhstan engagements begin with the company's own customer, user, public-sector, investor, regulatory or growth decision. If Saudi Arabia is relevant, its jurisdiction-specific questions become a separate workstream with the right local specialists.

See the Saudi context

Confidentiality & information handling

The first conversation stays high-level.

An initial enquiry only needs public or sanitised context: the decision, timing and what is at stake. If non-public information becomes necessary, I first confirm fit and conflicts, agree confidentiality terms and an appropriate exchange route, then request only what the defined engagement requires.

  • 01Minimum necessaryOnly information required for the defined work.
  • 02AI boundaryNo client-confidential material in consumer AI tools.
  • 03Separate permissionNo substantive disclosure or public case use without prior written agreement.

Kazakhstan advisory enquiry

Start with the decision that has become real.

At this stage, the decision, external deadline, owner and high-level context are enough.

Initial enquiry. Public or sanitised context is enough. No documents or confidential material are needed at this stage. If there is a fit, I will agree the next step and an appropriate exchange route before sensitive information is shared.