Skip to main content
Who actually delivers, and how

Senior-only delivery.
Capacity-limited by design.

Every practitioner on your engagement is a senior — 8+ years minimum, mostly certified, all with shipped-to-production track records. We have no analyst tier, no offshore back-bench, and no surprise junior staffing changes. We turn engagements down rather than break this rule.

Microsoft Certified Trainers across the senior team·Weekly demo rhythm, no engagement silent for >5 working days

01 · The Model

Why senior-only, and why capped.

The Big-4 pyramid

Partner sells the engagement. Manager runs the team. Senior analysts and analysts do 80–90% of the actual work. The bill rate is senior; the delivery is not.

This model works for large undifferentiated projects. It does not work for AI — where the wrong prompt, the wrong evaluation, or the wrong governance gap costs more to fix than to do right the first time.

The Gennoor model

Every line of code, every workshop slide, every architecture decision, every evaluation report touched by a practitioner with 8+ years of senior experience. No analyst tier. No offshore back-bench. No surprise junior staffing.

The trade-off: we cap active engagements per quarter. That is the cost of this model — and the reason it works.

The hard floor

Minimum 8 years of professional experience. Microsoft Certified Trainer or equivalent vendor certifications. Verified production track record in the role being staffed. We have turned away engagements rather than break this. We will continue to.

02 · The Seven Roles

Who shows up on your engagement.

Engagements are delivered through a defined role mix. Not every role appears on every engagement — a 4-week SMB pilot looks different from a 16-week enterprise build. The mix is scoped to the engagement at kickoff and disclosed in the SOW.

Engagement Lead

Senior · 12+ years

What they do

Owns the relationship end-to-end. Accountable for scope, timeline, quality, and the steering committee. The single name on every status email.

Present in

Every engagement, every phase

Typical profile

Microsoft Certified Trainer with multi-program delivery experience across regulated industries. Comfortable in CIO/CDO rooms and on engineering Slack channels alike.

Solutions Architect

Senior · 10+ years

What they do

Designs the technical approach. Signs off on the Stack Fit Assessment. Owns architecture decisions and the trade-off log. Reviews every architectural change.

Present in

Phase 1 (Diagnose) · Phase 3 (Innovate) · Phase 4 (Build)

Typical profile

Azure AI Engineer or equivalent certifications, plus deep AI/ML and integration experience. Has shipped at least three production AI systems through full lifecycle.

Senior Trainer / Coach

Senior · 10+ years

What they do

Delivers training content (executive, functional, technical). Runs adoption sessions. Coaches receiving teams through Sustain.

Present in

Phase 2 (Train) · Phase 5 (Sustain)

Typical profile

Microsoft Certified Trainer (MCT). Has trained C-suite cohorts at Fortune 500 scale. Skilled at translating between executive and technical audiences.

PoC Engineer

Senior · 8+ years

What they do

Builds the pilot. Pairs with the Solutions Architect on architecture, owns the delivery of the working PoC. Demos every Friday.

Present in

Phase 3 (Innovate)

Typical profile

Strong full-stack engineer with AI specialization (RAG, agents, evaluation). Ships fast, demos confidently, documents as they go.

Production Engineer

Senior · 8+ years

What they do

Scales the pilot. Sets up CI/CD, observability, MLOps. Co-builds with your engineering team to ensure knowledge transfer is real.

Present in

Phase 4 (Build)

Typical profile

Production-grade DevOps and MLOps experience. Comfortable in your cloud environment (Azure / AWS / GCP) and on-prem patterns alike.

Adoption Lead

Senior · 8+ years

What they do

Drives change management. Measures adoption. Designs the rollout pattern from pilot to organization-wide. The bridge between technology and people.

Present in

Phase 4 (Build) · Phase 5 (Sustain)

Typical profile

Background in L&D or change management, layered with AI/Copilot product expertise. Has run org-wide rollouts at 500+ user scale.

Governance Analyst

Senior · 8+ years

What they do

Risk, compliance, and evaluation. Owns the governance charter, the evaluation harness, and the audit-readiness pack.

Present in

Phase 1 (Diagnose) · Phase 5 (Sustain) · cross-cutting through Phase 3 & 4

Typical profile

AI risk and compliance specialization. Familiar with NIST AI RMF, EU AI Act, OWASP for LLMs, and regional rules (PDPL / DPDP / GDPR).

03 · Operating Cadence

The rhythm every engagement runs on.

Every engagement, regardless of phase or scope, follows the same operating rhythm. This is what kills the "60-day silence then a bad surprise" pattern that plagues most consulting engagements.

Daily

Async Slack channel · response within 24 hours, usually faster.

Weekly · Monday

Written status update to sponsors — what shipped last week, what ships this week, what is at risk.

Weekly · Friday

Live demo of work-in-progress. Mandatory. No engagement goes more than 5 working days without a demo — this is the rule.

Fortnightly

Steering committee for enterprise engagements (E3 onward). Executive-level review of progress, risks, decisions needed.

Phase gate

Written sign-off before moving from one Gennoor Way phase to the next. No phase starts without explicit approval of the prior phase's deliverables.

Quarterly (Sustain)

Full health check across all deployed systems. Written report with prioritized action list.

Annually (Sustain)

Strategy day for the next 12 months — portfolio expansion, retirement decisions, budget alignment, capability gaps.

04 · Demo Culture

The five-day rule.

No engagement goes more than five working days without a demo of something.

Even at week one. Even if it's a clickable mockup. Even if it's a 5-minute walkthrough of an architecture decision and what we're trying with it.

The rule is not "demo when there is something to demo." It is "demo every week, regardless." If a week passes without anything worth showing, the engagement has already gone wrong and we surface that — instead of running silent for another three weeks until the bad news lands at once.

This is the single most important operational rule at Gennoor.

05 · Knowledge Transfer

Co-build, not handover.

The classic "we built it, here are the keys, good luck" model fails for AI engagements. Our approach: your team is in the build from week one, and Knowledge Transfer is contractual — not a final-week milestone.

Pair from day one

Your engineers shadow ours from the first commit. We pair on architectural decisions, code reviews, and incident response. They learn the system by building it with us, not by reading about it after.

Three measurable checkpoints

By Go-Live, your team has: (1) merged code into production, (2) executed a deployment, (3) resolved an incident — without us in the room. These are checkpoints in the contract, not aspirations.

Runbook + on-call rotation

The operations runbook is owned by your team. By the end of hypercare, your on-call rotation includes the system, your engineers have practiced on-call scenarios with us, and you can resolve a Sev-2 without escalating.

Training built into the schedule

Phase 2 (Train) runs in parallel with Phase 3 and Phase 4 for the receiving team. Your engineers, your operations folks, your business sponsors all get role-specific training timed to where they enter the system.

06 · Engagement Capacity

What we will (and will not) take on.

Active engagement cap

We typically run 3–5 active engagements at once, scaled by phase mix. SMB packages (S1–S5) and Strategic Diagnostics (E1) run shorter; E3 Pilots and E4 Transformation Programs are longer and tie up more senior capacity.

At scoping, we tell you our next available start date — honestly, including when we are queued out.

When we say no

We turn engagements down when: (a) the senior bench is full and an urgent start date cannot be met; (b) the scope is unrealistic for the budget; (c) the engagement is a poor fit for our model (e.g., pure staff augmentation, or fixed-bid managed services).

When we turn an engagement down, we recommend partner firms where possible.

07 · Continuity & Resilience

The protections built in by design.

The procurement question, often unasked but always present: what happens if Gennoor disappears tomorrow? Six structural protections.

Your code lives in your repositories

Every commit goes to your GitHub / Azure DevOps / GitLab from day one. We do not maintain "client-X-private" repositories. If we vanished tomorrow, your code is still there, still operable, still yours.

Your cloud accounts are yours

We build in your Azure subscription, AWS account, GCP project, or on-prem infra. Credentials are your IAM's problem, not ours. Off-boarding is a credential revocation, not a data migration.

Documentation handed over at every phase gate

You hold the design documents, decision logs, evaluation reports, operations runbooks, and training materials at each phase gate — not in a deliverables-at-the-end model.

Knowledge transfer is contractual

Every Build (Phase 4) engagement carries an explicit KT clause. By Go-Live, your engineering team has merged code, run a deployment, and resolved an incident — without us in the room.

Senior partner network for surge

For larger engagements requiring additional capacity, we work with a vetted network of senior partner practitioners under back-to-back NDAs. Surge capacity does not change the seniority bar.

No proprietary lock-in

Our reusable frameworks (methodology, evaluation harnesses, course templates) are non-confidential and re-implementable. You can fork them. We don't hide value in tooling that locks you in.

Bottom line: If Gennoor Tech vanished tomorrow, your AI system keeps running, your code is still yours, your team can operate it, and you can engage another firm to extend it. The protections are not promises — they are structural defaults baked into how every engagement is set up.

08 · The Founder

Who leads delivery today.

Jalal Ahmed Khan, Founder of Gennoor Tech

Founder & Lead Practitioner

Jalal Ahmed Khan

Microsoft Certified Trainer with 16 active certifications. 14+ years of enterprise AI experience across Fortune 500 clients including Microsoft, IBM, EY, Boeing, Saudi Aramco, HDFC Bank, Siemens, and Bank of Tanzania. 50+ C-suite leaders trained across 6+ countries.

On SMB engagements and Phase 1 Strategic Diagnostics, Jalal is typically the Engagement Lead. On multi-quarter enterprise programs, he may be the executive sponsor with another senior practitioner as Engagement Lead. Reachable for any client at any time.

09 · FAQ

Questions about the team and how we deliver.

How many active engagements does Gennoor run at once?

We cap active engagements per quarter to maintain the senior-only standard. Typical limit: 3–5 active engagements at any one time depending on phase mix (Diagnose engagements are shorter, Build engagements run longer). For E4 Transformation Programs in the $300k+ range, we are transparent about start-date availability at scoping; we do not over-commit.

Who specifically will be on my engagement?

The Engagement Lead is named in the SOW. The supporting roles (Solutions Architect, Senior Trainer, PoC Engineer, etc.) are named in the kickoff document within the first week. You meet every practitioner who will touch your engagement before they start work.

What if my Engagement Lead is unavailable mid-engagement?

Engagement Leads have a designated backup named at kickoff — typically the Solutions Architect or another senior practitioner who has been in the engagement from week one. The backup has working context, attends key reviews, and can step in without re-orientation. Lead transitions (planned or otherwise) are handled with written notification and a 2-week overlap where possible.

Do you subcontract any of the work?

Sometimes, but with strict boundaries. For specialized capacity (e.g., a deep MLOps engineer for one workstream, a regional language specialist), we work with a vetted senior partner network under back-to-back NDAs. Every subcontracted practitioner meets the same seniority bar as our core team. We never use junior staff augmentation. Subcontractors are disclosed to you before they join the engagement.

How do you scale for very large programs (E4 Transformation, E6 CoE)?

Larger programs are delivered with a small senior team — typically 3–6 practitioners (Lead + Architect + Trainer + Engineers + Adoption + Governance) — coordinated through the Engagement Lead. The team scales by adding seniors, never by adding analysts. For programs requiring more than 8 active practitioners, we partner with system integrators as the AI specialist arm of a broader delivery.

Is the founder always involved?

For SMB engagements (S1–S5) and Phase 1 Strategic Diagnostics, the founder is typically the Engagement Lead. For multi-quarter enterprise programs, the founder may be the executive sponsor with another senior practitioner as Engagement Lead. The founder remains accountable to every client and is reachable for any client at any time.

What are your hiring standards?

Two hard requirements: (1) Senior — minimum 8 years of professional experience, mostly in AI / ML / cloud / enterprise software delivery; (2) Certified or equivalent — Microsoft Certified Trainer status, or equivalent vendor certifications, or a verified track record of senior delivery in AI for the role we are hiring for. We hire slowly. We do not hire to grow the headcount.

How does engagement capacity affect my start date?

Honestly. At scoping, we tell you when we can start. For Strategic Diagnostics (E1) and most SMB packages, start is typically within 2–3 weeks. For E3 Pilots, 2–6 weeks. For E4 Transformation Programs, 4–10 weeks depending on the queue. If your timeline is urgent and we cannot meet it, we say so — and we recommend partner firms when relevant.

What happens to my engagement if Gennoor goes out of business?

Three protections built in by design: (1) Your code, models, prompts are in your repositories from day one — you can operate without us. (2) Your cloud accounts and credentials are yours — we have no access after off-boarding. (3) Your documentation is handed over at every phase gate — no critical knowledge lives only in our heads. Practically: if we disappeared tomorrow, your AI system would keep running, and you could engage another firm to extend it.

Can we negotiate exclusivity for our region or industry?

Not as a hard rule, but as a soft commitment. For large, multi-quarter engagements, we sometimes agree to non-compete clauses for direct competitors within a defined region or sector for the engagement duration. The clause has to be reasonable and not constrain our practice broadly — we serve multiple clients across BFSI, healthcare, public sector, and others, and that diversity is part of what makes our team good.

How do you handle handover when the engagement ends?

Per the contractual KT clause: by Go-Live (Phase 4) or scope completion (any phase), your team has the artifacts, the runbook, the credentials, and the practice to operate independently. Off-boarding includes: credential revocation within 5 working days, final documentation pack, exit retrospective with written recommendations, and (optional) a 4-week hypercare extension. After hypercare, the relationship continues through Sustain (Phase 5) if you elect it; otherwise we are out of your environment.

How do you grow without compromising the senior-only model?

Slowly, deliberately, and with a hard floor on seniority. Our growth path is: (1) Build a small core team of 4–8 seniors (not 40 mid-levels). (2) Use a partner network for surge. (3) When we grow, we add seniors only — no analyst tier ever. The reason we cap engagements per quarter today is exactly because growth at the wrong tier would dilute the model. We would rather turn engagements down than under-deliver on senior delivery.

Ready to talk about a specific engagement?

A 30-minute scoping conversation tells you whether we're the right fit, when we can start, and which roles your engagement will need. The corresponding procurement reference is on our Trust & Security page.