
I’m Yash
Gudimalla.
During my internship with NA Application Sales Business Operations, I used AI and workflow design to improve data integrity, organizational planning, and customer relationship visibility.
Rutgers–New BrunswickFinance + Computer Science · May 2027
I expected assigned analysis. I found opportunities to redesign the work itself.
The organization was changing, managers had limited time, and several processes still required repetitive manual effort. That created room to take ownership and build practical AI workflows around real team needs.
Reduce repetitive work so teams can spend more time on decisions that require human judgment.
Choose where we start, or explore all three.
Each project begins with a real operational problem, shows what I built, and ends with the value or next opportunity.
Turn relationship gaps into clear account actions.
I connected executive relationships, engagement history, account ownership, and follow-up in one usable tracker.
The data existed, but the next move was difficult to see.
Leaders needed a simple path from portfolio health to a specific customer, the right Territory Owner or FLM, and a concrete follow-up action.
I designed the tracker around decisions, not just reporting.
The experience moves from relationship health to account context, then ends with an owner, action, and status.
Relationship coverage became easier to understand and act on.
The pattern below is descriptive, not causal. It gives leadership a useful reason to prioritize relationship-building.
581 reporting customers
This is a descriptive portfolio association. It does not establish causation.
Find timely executive-engagement opportunities.
AI could search approved public events, identify relevant executives, match an attending sales representative, and recommend an action for human review.
Make 61,198 hotel records useful for account planning.
I built an AI-assisted validation workflow to identify hotel owners and operators at a scale that manual research could not support.
Critical owner and operator information was mostly missing.
Brands, management companies, and owners are often different organizations. Searching tens of thousands of records manually would have taken an unreasonable amount of time.
I combined AI research with controlled validation rules.
Confidence rules, source checks, review checkpoints, and workbook protections kept the process inside an approved framework. Weak evidence stayed unresolved instead of being guessed.
The same records became far more usable.
The final release made owner and operator information available for account planning without requiring someone to research roughly 45,000 incomplete rows by hand.
had at least an owner or operator identified
54,827 of 61,198 scoped hotelsapproved cell updates
AI was most useful when it accelerated repetitive work while preserving uncertainty whenever the evidence was weak.
Run the same validation before new hotel records enter the TDR, so owner and operator fields are handled during normal intake.
Turn an approved hierarchy into an editable PowerPoint.
I transformed a repetitive quarterly process into an on-demand workflow built around real hierarchy, layout, and validation requirements.
Every quarterly refresh repeated the same manual effort.
Stakeholders had to interpret hierarchy data, rebuild PowerPoint layouts, reconcile counts, and correct formatting details. Small inconsistencies could send the work back for additional review.
refresh
The workflow applies reusable hierarchy and presentation rules.
It handles manager order, continuation pages, photos, counts, slide fit, and final validation, while keeping the PowerPoint fully editable.
+ validateHierarchy rulesLayout rulesCount checks
Fictional names shown. The real output remains editable for stakeholder review.
hours per quarterly cycle
Time that can be redirected toward planning, decision-making, and higher-value work.Sonia connected the workflow to recurring Connections product demand.
Sonia, a Senior Director of Product Management for Connections, highlighted that users repeatedly ask to export org charts directly from the platform for presentations and offline work.
A practical next step would be evaluating the workflow with Sonia and other Connections product and development stakeholders. This is a proposed product opportunity, not a committed roadmap item.
The tools improved as I learned to work between technical systems and business teams.
Clarify earlier
Ask more stakeholder questions before building deeply, especially around definitions and exceptions.
Build with guardrails
Use AI for speed while keeping source rules, validation, review, and human approval visible.
Translate the value
Explain technical workflows through the time, clarity, or decision they improve for a nontechnical user.
I want to keep building useful tools at the intersection of AI, business, and operations.
What would you like to explore next?
linkedin.com/in/yg13 ↗