Skip to main content
IT Advisory · KSA & GCC

IT Consultation

Senior IT advisory for boards, executive teams, and CIOs across KSA and the GCC — strategy, architecture, compliance, cost, and vendor decisions. Board-ready recommendations in four to six weeks, signed by the partner who wrote them.

0+ advisory engagements
4–6 wks typical assessment
Partner-led no junior hand-offs
// 01 · Advisory disciplines

Six places the conversation starts.

Boards engage NAS on one of six axes — strategy, architecture, compliance, cost, vendor, or organisation. Most engagements end up touching two or three.

CON.01

IT strategy

3-year IT strategy aligned to business objectives, Vision 2030 anchors, and a portfolio of investments costed against a budget that actually exists.

CON.02

Enterprise architecture

Current-state mapping, target-state design, transition plan. Application, data, integration, and infrastructure architectures coherent against each other.

CON.03

NCA ECC & PDPL compliance

Gap assessment, control mapping, remediation roadmap. Sector-specific overlays for SAMA, NHA, and CITC where they apply.

CON.04

Cost & FinOps advisory

Cloud spend baseline, rightsizing, reserved-instance strategy, and a 12-month savings forecast with owners on every line.

CON.05

Vendor selection & RFP

Requirements scoping, vendor long-list, scored evaluation, contract negotiation support. We name a winner — we don't write "it depends".

CON.06

Organisation & operating model

Target operating model, RACI redesign, skills-gap analysis, and a hiring plan that ties to the new architecture — not a parallel exercise.

// 02 · How we engage

Four shapes the engagement can take.

Discovery sprint, advisory retainer, interim leadership, or a single board read-out. The format follows the decision the board is trying to make — not a packaged offer.

01

Discovery sprint

4-week intensive assessment. Interviews, document review, current-state mapping, and a written recommendation. The shape when the board has named the question.

  • Best for · focused decision
02

Advisory retainer most chosen

Quarter-by-quarter advisory access. Monthly check-ins, ad-hoc strategic calls, and a senior partner on text for the calls that can't wait for Monday.

  • Best for · ongoing decisions
03

Interim leadership

A senior partner steps in as interim CIO or CTO. Typically 3–9 months while a permanent hire is sourced, with a documented hand-off plan from week one.

  • Best for · leadership gap
04

Board read-out

A single, surgical board presentation. Typically the deliverable arc of a discovery sprint, but sometimes commissioned on its own when the question is sharp and the timeline is short.

  • Best for · one big decision
// 03 · Formats & commitments

Four formats. Pick one, pick two.

Length, output, and partner involvement vary. Pricing is fixed by format, not by hour — so the conversation is about the decision, not the timesheet.

01

Discovery sprint

4–6 week assessment ending in a written recommendation, presented to leadership.

  • Duration · 4–6 weeks
  • Output · Written report
  • Partner · Lead author
  • Best for · Named question
03

Interim leadership

Senior partner steps in as fractional CIO or CTO. Documented hand-off plan from week one.

  • Duration · 3–9 months
  • Output · Hand-off pack
  • Partner · On-site, 2 d/wk
  • Best for · Leadership gap
04

Board read-out

Single surgical board or steering-committee session. Deck, talking points, Q&A rehearsal, in the room delivery.

  • Duration · 2 weeks
  • Output · Board deck
  • Partner · Presents
  • Best for · One sharp call
// 04 · What lands on your desk

A written recommendation. Signed by the writer.

Every assessment ends in a single document. Stakeholders named, costs numbered, trade-offs declared. Designed to be read by a busy board chair on the drive in — not by a slide-shop preparing a re-shoot.

Designed to be presented as-is.

Every recommendation we ship is signed by the partner who wrote it. The board reads names, not initials. The costs are signed-off by the partner who wrote them, not by a junior who modelled them.

And when the recommendation is wrong — sometimes it is — we'll be the ones in the room when that gets discovered.

28Avg pages
14Avg slides
1Signature
// 05 · Methodology

Four phases. Same loop, every engagement.

Frame the question, gather the evidence, write the recommendation, present and stand behind it. Sequence and depth vary by format — the loop does not.

  1. 01

    Frame

    One-week scoping. Who's asking, why now, what decision are we trying to inform, what counts as "done". The frame is the most important week of the engagement.

  2. 02

    Gather

    Interviews, document reviews, technical assessments, vendor briefings. Hypothesis-led — we ask the questions that move the recommendation, not the ones that fill the report.

  3. 03

    Write

    The recommendation in plain language with named owners, costed options, and stated trade-offs. Drafted by the partner, not delegated.

  4. 04

    Stand behind it

    Board presentation, Q&A, follow-up calls — the partner who wrote the recommendation is the partner who defends it. No hand-offs at the door.

// 06 · Advisor expertise

Partner-led. Not pyramid-staffed.

Every engagement is led by a senior partner with 15+ years of regional delivery. The partner you meet in the pitch is the partner who writes the deck, presents it, and answers the messages that come after.

Strategy & architecture

Multi-year IT strategy, enterprise architecture, target operating models — anchored against Vision 2030 themes and the business strategy that funds them.

TOGAF Vision 2030 Board-grade

Compliance & risk

NCA ECC, PDPL, SAMA CSF, NHA, and sector-specific overlays. Gap assessment to remediation roadmap, with controls mapped to owners and dates.

NCA ECC PDPL SAMA CSF ISO 27001

Cost & FinOps

Cloud-spend baselining, rightsizing, reserved-instance and savings-plan strategy. Average client savings · 28% in the first 90 days, with documented owners.

FinOps Certified AWS Billing Azure Cost Mgmt
// 07 · Frameworks & partners

Framework-neutral. Credentialed across the field.

// 09 · FAQ

Common questions.

Q.01How long is a typical consulting engagement?

Targeted assessments run 4–6 weeks. Advisory retainers run quarter-by-quarter with monthly check-ins. Interim CIO / CTO mandates are typically 3–9 months with a documented hand-off plan from day one.

Q.02Do you write the recommendations, or just facilitate?

We write them — clearly, with stakeholder names, costs, and trade-offs. Our deliverables are designed to be presented as-is to a board or steering committee, not as starting points for a slide-shop rewrite.

Q.03Can you help with NCA ECC and PDPL compliance?

Yes. Compliance-by-design is the most common reason boards engage us. We map controls to NCA-ECC, PDPL, SAMA CSF, and sector regulators, then deliver a remediation roadmap with owners and dates.

Q.04Are your consultants vendor-neutral?

Vendor-neutral by policy. We hold partner credentials with AWS, Azure, Microsoft, Cisco, Fortinet, and others — and we recommend against any of them on the days the data says we should.

Q.05Do you do board-level presentations?

Routinely. About 40% of engagements end in a board or steering-committee read-out. Senior partners attend the read-out personally — not just the writer of the deck.