Skip to main content
Keyur PatelBook a call

CASE STUDY · REAL ESTATE · AHMEDABAD

From ten IT sessions to a group-wide AI rollout

I ran ten AI training sessions for an Ahmedabad real estate group’s IT team. The work then extended to their Sales team, and a second entity in the group is now onboarding. This is what that looked like, and why it grew.

An Ahmedabad real estate group · Real estate · Ahmedabad · Updated 2026-07-28

What happened

  • 10

    Sessions delivered

    A sustained run with the IT team, not a one-off workshop.

    Delivered

  • 2

    Departments trained

    IT first, then Sales on a separate track built for their work.

    Delivered

  • 2

    Group entities onboarding

    A second entity in the group is now starting its own AI onboarding.

    Delivered

The starting point

The group had the same problem most companies have after an AI mandate lands. People had accounts, a few were pasting prompts into chat tools, and nobody could point at what had actually changed in the work.

The IT team needed AI to show up in delivery, not in demos. Sales needed something completely different, because the work is proposals, follow-ups, research and client communication rather than code.

What I ran

  • Ten hands-on IT sessions

    A run of sessions with the IT team working on their own systems and workflows rather than a generic example project. Hands on keyboards each time, not slides.

  • A separate track for Sales

    Sales does not benefit from the engineering curriculum. That track covered research, drafting, follow-up and the judgement of when the output is good enough to send.

  • Workflows the team keeps

    Each session ended with something reusable: a prompt that works on their material, a checked workflow, a standard the team agreed on. The value has to survive the session.

  • Honest limits

    I am direct about where AI is the wrong tool. That matters more than enthusiasm, because a team that trusts the boundaries actually adopts what is inside them.

Why it grew

The part worth paying attention to is not the curriculum. It is that the engagement grew on its own.

Ten sessions with IT went well enough that the group asked for Sales next, which is a different audience with different work and no shared vocabulary with the engineering track. That expansion is the signal. Training that does not land does not get extended into a department where the buyer has to explain the value all over again.

A second entity in the group is now onboarding. At that point this stops being training and becomes an adoption rollout, which is exactly the shape my AI Engineering Operating System engagement is built around.

Want this for your team?

A free 30-minute discovery call is the fastest way to scope it. On-site in Ahmedabad and GIFT City, remote across India.