# IBOTSystems — Full Context Bundle > An AI Practicing Engineering Company headquartered in Atlanta. AI adoption for complex enterprise line-of-business applications — the legacy systems you can't afford to rewrite. PlayerZero Implementation Partner. AI SDLC Practice. HIPAA · HITRUST · SOC 2 in the baseline. This is the long-form companion to https://ibotsystems.com/llms.txt. It includes the full text of every published blog post and expanded descriptions of every major surface, so an LLM agent can answer questions about IBOTSystems from this single file without crawling. Last generated: 2026-05-20T18:56:34.152Z Canonical short index: https://ibotsystems.com/llms.txt --- ## Who We Are IBOTSystems is an AI Practicing Engineering Company founded in 2014 and headquartered in Atlanta, Georgia. We are not a consultancy. We are a small team of practicing engineers who deploy AI into the engineering systems and operations of complex enterprise organizations — and stay to run them. Our positioning: **AI adoption for complex enterprise line-of-business applications.** The decades-old .NET monolith. The COBOL backend. The integration layer encoding twenty years of compliance and business logic. The systems where AI pilots dazzle in a controlled environment and collapse the moment they hit the real codebase. Our promise: **Stop sustaining. Start compounding.** Engineering organizations spend 60–70% of their R&D capacity on sustenance — keeping legacy systems alive — and the remaining 30–40% on new value. We bend that ratio with AI applied at the practice level, not the tool level. The benefits compound. --- ## Manifesto Most teams adopted AI on greenfield. They never solved legacy. We've watched the same pattern play out at every enterprise we've worked with. The pilots dazzled on new repos. The same tools collapsed the moment they hit a twenty-year-old codebase. Co-pilots generating C# they didn't understand. Agents stalling at undocumented business logic. RAG systems retrieving stale wiki pages while the actual rules sat in a stored procedure nobody had touched since 2014. That doesn't mean AI fails on legacy. It means AI fails on legacy by default. To make it work, the codebase has to be mapped, the business rules surfaced, the unsafe surfaces marked, and the simulation layer wired in so agents can propose changes without breaking production. PlayerZero as the spine. Claude Code and a tailored agent toolchain doing the work. Humans whose judgment is the final gate. AI on legacy isn't a smaller version of AI on greenfield. It's a different practice. We've built it. --- ## Offerings ### PlayerZero Implementation Partner We are an official PlayerZero implementation partner. Used in 100% of engagements. We map your codebase, wire CodeSim into CI, route customer tickets to the exact line of code, and train your engineers and support team to operate the platform as a daily habit — not a tool that gathers dust. PlayerZero is the control plane for software quality in the AI-code era: it learns your codebase, ties customer tickets to the exact line that broke, and simulates how a proposed change will behave before it ships. Reference: https://ibotsystems.com/playerzero-implementation-partner/ ### AI SDLC Practice A practicing engineering discipline that rewires your software development lifecycle for AI-first workflows. Delivered as fixed-bid AI Readiness Blocks scoped to your codebase. We rework each stage of the lifecycle so AI tools and agents are first-class participants — and so the quality system catches up with the speed of code production. Discovery: AI-augmented customer research, evaluatable specs. Design: design docs written so a simulator can check them. Build: Claude Code, Cursor, and custom agents handle obvious code; engineers handle judgment. Ship: CodeSim runs on every PR and gates the top regression-prone surfaces. Operate: customer reports route to the failing path; Cowork handles non-engineering grind; feedback loops back into discovery. Reference: https://ibotsystems.com/ai-sdlc-practice/ ### Managed AI Operations (in development) A build-operate-license shape for organizations with small in-house engineering teams but real operational AI needs — senior care operators, mid-market healthcare, regulated mid-market. We build the AI agents that live across your EHR, your HRIS, your billing platform, your family/customer comms; we operate them; we improve them. You pay per shift filled, per MDS coded, per denial recovered, per outcome that matters. Page not yet built on the site; in active scoping. --- ## Practitioners ### Gopal Koratana — Founder & Chief Practitioner Two decades inside the systems Fortune 500s actually run on: - Manheim's Dealer Management System (Cox Enterprises subsidiary) - GE rail electronics (GE-Harris Railway Electronics, GE Transportation) - Logistics at UPS Logistics, Eagle Logistics - Heavy equipment at John Deere Founding CTO of **Vendormate**, the healthcare GRC/credentialing platform acquired by **GHX in November 2014** ($585M acquisition). Co-Founder & CTO of **Cyrano Video**, a healthcare video subscription platform (hardware + Cyrano Studio software + services) serving 100s of healthcare organizations including HCA, CommonSpirit, Dignity Health, Trinity Health, Prime Healthcare, UHS, Medtronic, Coloplast, Emory, Piedmont, UF Health, CHI Health, OrthoCarolina, EyeCare Partners, EyeSouth, Shepherd Center. The AI SDLC Practice ships in production every day at Cyrano with measurable, compounding results — the same playbook IBOTSystems brings to clients. Education: Master's in Electronics and Power Engineering, IIT Chennai. Bachelor's in Electrical Engineering, Nagpur University. Affiliation: Charter Member, TiE Atlanta. Based in Johns Creek, Georgia. LinkedIn: https://www.linkedin.com/in/gkoratana Profile page: https://ibotsystems.com/practitioners/ ### Practitioner bench (in progress) IBOTSystems is a small team by design. Additional practitioner profiles are being published; the standard is senior engineers who use AI to compound productivity inside large enterprise systems while keeping them scalable, secure, and maintainable as they grow. --- ## Methodology The IBOTSystems engagement model has three load-bearing ideas: **AI Readiness Blocks.** Every engagement decomposes into 2–6 week units with a fixed price, a defined deliverable, and an outcome measurable from the outside. No time-and-materials drift. Blocks compound: each one permanently reduces the cost of working in the surface area it touched. A pilot has no exit criteria, which is part of why so many of them quietly become permanent. A block does. **Opinionated about the spine. Tool-agnostic about the rest.** PlayerZero is the spine of every engagement — codebase mapping plus the simulation layer that lets AI propose changes without breaking production. Claude Code is the primary delivery tool, used on most code edits. Cowork handles non-engineering operational grind (file ops, reporting, vendor follow-up, ticket triage). Cursor, Linear, and custom toolchains compose around them as the job calls for. We don't bet on a single tool; we bet on the practice that composes them. **Compounding is the real metric.** The right question isn't whether a pilot worked. It's whether each block of work makes the next block cheaper. That's the curve that matters, and it's the one we'd push leadership to track. The engagements where this has worked produce durable 30–50% productivity gains across the engineering organization — not 10× on a single task, not "transformation" — thirty to fifty percent of the engineering org's capacity, recovered and reinvested. --- ## The Approach Three steps: 1. **Assess.** Full access to your engineering system — codebase, workflows, incident history. We map exactly where maintenance spend is trapped and where AI will move the needle fastest. 2. **Define.** A prioritized AI Readiness Block roadmap, scoped and priced before any work begins. Every block has a fixed cost, a defined deliverable, and a measurable outcome. 3. **Ship.** Blocks delivered in 2–6 week sprints. Each one permanently reduces the cost of the previous surface area. The curve bends with every block — and keeps bending. --- ## Verticals ### Priority Verticals (Active Outbound) **1. Senior Care.** Healthcare lineage from Vendormate→GHX gives instant credibility. HIPAA / HITRUST / SOC 2 baseline. Two distinct buyer types: - *Senior care software vendors*: PointClickCare (top of list), MatrixCare (ResMed), WellSky, CarePort, Aline, Yardi Senior Living, Glennis Solutions, Homecare Homebase, Axxess, AlayaCare. Standard PlayerZero + AI SDLC engagement. - *Senior care operators*: Brookdale Senior Living (largest US operator), Atria, Sunrise, LCS, Watercrest, Senior Lifestyle, Discovery, Frontier Management; CCRC networks (Erickson, Acts Retirement, Asbury Communities); SNF operators (Ensign Group, NHC, PACS Group); home health (BAYADA, Amedisys, Compassus, Bristol Hospice). Managed AI Operations build-operate-license model. Use cases for operators in priority order: staffing/shift-fill agent (CNAs, DSPs, RNs); clinical documentation + MDS coding assistant; family communication automation; revenue cycle (eligibility, denial prediction, appeal automation); survey/audit prep; onboarding & training; risk prediction; cross-system integration. **2. Energy Software Vendors.** Same archetype as senior care software vendors. Engineering orgs 80–800, multi-decade legacy stacks (some still carry C++ from the '90s), NERC CIP and SOC compliance baseline, active interest in AI with no clear path to apply it. Named targets: GE Vernova (top of list), Itron, Landis+Gyr, Sensus, OATI, Tantalus, ION Energy (formerly Allegro/OpenLink), Aspect Enterprise Solutions, Energy Exemplar, Mercatus, PowerHub, kWh Analytics, Bidgely, AutoGrid, Uplight, Aurora Solar, Enact Systems, Watershed, Persefoni, Sweep. **3. Utilities.** Largest deals in energy but longest sales cycles. Pursue mid-size IOUs first: Avista, Black Hills, Hawaiian Electric (top of list — post-Maui mandate), Portland General Electric, IDACORP/Idaho Power, Pinnacle West/APS, PNM Resources, Alliant Energy, Eversource. Then public power: Salt River Project, CPS Energy, SMUD, Seattle City Light. Finally named mega-IOU subsidiaries (not corporate): Georgia Power, Alabama Power, Duke Energy Sustainable Solutions, NextEra Energy Resources, Constellation Energy, Sempra Infrastructure, AEP Energy. Wildfire-risk / vegetation management and customer operations / call deflection are the strongest entry use cases. ### Credentialed via Gopal's Career and Cyrano Video - **Hospitals & Health Systems** — HCA, CommonSpirit, Dignity Health, Trinity Health, Prime Healthcare, UF Health, Emory Healthcare, Piedmont (via Cyrano). - **Medical Device** — Medtronic, Coloplast (via Cyrano). - **Behavioral Health** — Cyrano vertical. - **Marketing / MarTech & Corporate Communications** — Cyrano operates as a healthcare-specialized MarTech + InternalComms + CustomerEngagement platform; the discipline translates to other regulated B2B verticals. - **Logistics & Supply Chain** — Gopal's direct experience at UPS Logistics, Eagle Logistics, John Deere. - **Auto / Mobility** — Gopal's direct experience at Manheim Dealer Management System. ### Verticals Under Evaluation - **FinTech / PayrollTech / HR-Tech** — Netchex-adjacent shape (payroll + HCM platforms with NMLS licensure and AI ambition). Pedigree anchor pending. --- ## Compliance HIPAA · HITRUST · SOC 2 · FedRAMP-ready as the baseline compliance posture, built in not bolted on. Every engagement begins inside the client's existing compliance perimeter; data residency and access boundaries are scoped before any work begins. Vertical-specific additions where engaged: - *Senior Care*: CMS Five-Star Quality Rating alignment, state survey readiness. - *Energy / Utilities*: NERC CIP (Critical Infrastructure Protection), NIST CSF (Cybersecurity Framework). - *Financial services* (when engaged): PCI DSS, NYDFS. --- ## Selected Work Three reference engagements named on the homepage: **Healthcare · Video Platform (multi-year partnership).** A sub-10 engineer organization running a complex, regulated healthcare-video platform — where every inbound support ticket used to pull engineers into days of triage and context-gathering before code could be touched. We wired PlayerZero into support, triage, onboarding, PR review, and CodeSim — turning every inbound ticket into a ready-to-merge proposal by the time engineering opens it. Claude Code powers day-to-day development; Cowork runs across operational work. One of the earliest AI-in-SDLC adoptions anywhere, predating ChatGPT. Result: ~50% drop in maintenance overhead. **SaaS · Growth-stage (8-week engagement).** Customer tickets bounced between support and engineering for days. Root cause hunts started from scratch every time. We connected PlayerZero to ticket intake so customer reports routed to the exact failing path in code, and trained the support team to read the trace. Result: 60%+ faster incident resolution. **Research SaaS · HIPAA · FedRAMP (multi-year partnership).** A regulated research platform serving 700+ institutions across a Java / PHP / .NET / AWS stack. Growing surface area meant every release carried system-wide risk — and customer NPS tracked it closely. PlayerZero runs as the engineering research function — identifying where major system-wide changes need to land, planning each release with full codebase context, automating PR reviews, and running code simulations before every ship. Claude handles day-to-day code edits. Result: 4× overall productivity gain in 18 months; customer NPS climbed 51 points across the engagement. --- ## Stack Tools used across most engagements: - **PlayerZero.ai** — AI engineering quality platform. The control plane for software quality in the AI-code era. Used in 100% of engagements. https://playerzero.ai - **Claude Code** — Agentic coding from the terminal. The pair-programmer that actually finishes the task. Primary delivery tool. Most of our delivery flows through it. https://claude.com/product/claude-code - **Cowork** — A desktop agent for non-developer ops. File shuffling, reporting, vendor follow-ups, and the rest of the non-engineering work that quietly eats a team's week. We deploy it for ops, BD, and founders who'd rather build. https://www.anthropic.com/news/claude-is-a-space-to-think - **Cursor** — In-IDE flow for engineers who prefer IDE-first interaction. - **Linear** — Project gravity / ticketing. - **Anthropic API** — Direct model access for custom agents. - **Amazon Bedrock** — Where deployment regulation requires it. - **Custom agents** — Built on top of the above for integrations that don't exist yet. We're opinionated about the spine. Tool-agnostic about the rest. --- ## Contact To start a project or have a discovery conversation: - **Start a project form**: https://ibotsystems.com/#contact - **Blog subscription**: https://ibotsystems.com/blog/ - **LinkedIn (founder)**: https://www.linkedin.com/in/gkoratana - **Head of Growth**: Anushka Koratana — anushka.koratana@ibotsystems.com — 678.549.5510 - **Office**: Atlanta, GA · Remote-friendly · Worldwide engagements Replies within one business day. Engagements from 4 weeks. --- ## Blog Posts The full text of every published post follows, newest first. ### Hype rides high. The thirty percent compounds. Published: 2026-05-20 Author: Gopal Koratana, Founder & Chief Practitioner URL: https://ibotsystems.com/blog/hype-and-the-thirty-percent/ Tags: AI Hype, Enterprise AI, Line of Business Apps, AI SDLC, Compounding, PlayerZero Most enterprise AI noise is incentive-driven. Underneath is the smaller, real story — the 30 to 50% of AI that compounds inside production systems. The AI economy in 2026 has many reasons to overstate its case. A platform vendor needs to justify the spend on its AI division. A model lab needs the valuation to clear an IPO or persuade its next investor that the compute bill is buying a defensible business. A board needs a clean public reason for the headcount call it already wanted to make. A consultant needs a thesis to bill against. None of these incentives are sinister. All of them push the same direction — toward an account of AI that is bigger, faster, and more universally applicable than the work currently supports. We get it. We also have to ship inside real codebases. So here's the version of the story that survives contact with production. ## The hammer, and the cost of nails When every vendor needs the same outcome, the slide decks converge. The recommendation is always: more AI. Sometimes that's correct. Often it isn't. The hammer-nail problem in enterprise AI isn't that the tools are bad. It's that *nails are expensive*. A production engineering team that spends three quarters chasing a generative use case that doesn't move a customer metric has paid a real cost — in engineering hours, in trust, in the next budget's appetite to try again. The check isn't *"is AI possible here?"* — it almost always is. The check is *"is the value to the customer durably greater than the cost of getting there, after the initial novelty wears off?"* ## Where AI is already step-function Honest accounting first. Greenfield POCs. New repos. Bounded surface area. One team, one definition of success, one data slice. In those conditions, current-generation AI tooling is not 10% better. It is *step-function* better. Discovery, prototyping, throwaway tooling, internal apps — we use AI heavily for these and so should you. This is the demo half of the story. It is also the half the vendor deck shows. ## Where the work actually is Most enterprise value is not on greenfield. It is locked inside *line-of-business applications* — the systems that run the business, encode the regulatory posture, and carry a decade of integration weight. These are the systems where AI gets hard. A short list of why: **The codebase wasn't built to be read.** Business logic lives in stored procedures, in undocumented conventions, in the names of the people who wrote it and have since left. A retrieval pipeline can't index what was never written down. **The data model carries history.** Twenty years of acquisitions, schema migrations, and field-overloading mean "customer" can mean five different things depending on which team is asking. Agents make confident wrong calls when the underlying entity is ambiguous. **Compliance won't accept "the model decided."** HIPAA, HITRUST, SOC 2, NERC CIP — these regimes require an audit trail with a human in it. AI-generated decisions are admissible only when the simulation, evaluation, and human-gate layers are built around them first. **Workflows differ across teams.** What looks like one process from outside is four locally optimized variants no one has had the authority — or the budget — to harmonize. AI inherits the divergence. It doesn't fix it. **SLAs are unforgiving.** A 0.5% regression rate on a greenfield demo is a non-event. The same regression rate on a billing or clinical workflow ends careers. **Ownership ambiguity surfaces on first failure.** Pilots can dodge it. Production cannot. This isn't a list of reasons AI fails in the enterprise. It is the list of conditions any AI initiative has to design around to survive past the pilot. ## The thirty percent So what's actually achievable inside these systems, once the hype is filtered out? Our number, from engagements we've actually run, is *30 to 50% productivity gains* across the engineering organization — durable, measurable from the outside, compounding across blocks. Not 10× on a single task. Not "transformation." Thirty to fifty percent of the engineering org's capacity, recovered and reinvested. That number shows up under three specific conditions: **The right tool, for the right surface.** A code-completion agent is not the same product as a codebase-mapping platform, which is not the same as an evaluation harness, which is not the same as a desktop ops agent. Most teams adopt one and treat it as the whole answer. The real practice composes them — PlayerZero on the spine, Claude Code in delivery, Cowork on the operational long tail, custom toolchain in the gaps. **SDLC aligned to AI.** Discovery, design, build, ship, operate — every stage has to be rebuilt to assume AI is in the room. AI editors collapsed the cost of producing code. They didn't collapse the cost of reviewing, integrating, or supporting it. So the bottleneck moved. If the SDLC doesn't move with it, the team works harder to ship the same volume of regression risk. **Mindset shifts from pilots to blocks.** A pilot has no exit. A block does. Each engagement is a 2–6 week unit with a fixed price, a defined deliverable, and an outcome measurable from the outside. Blocks *compound* — each one permanently reduces the cost of the surface area it touched. Thirty percent isn't a number you reach by buying better AI. It's the number you reach when the *practice* the AI lands in is built to absorb it. ## The take Most of what gets called enterprise AI right now is incentive-driven noise. Some of it is real. The thirty to fifty percent that is real also happens to be the half that doesn't make the press release — because it shows up as fewer incidents, faster ticket resolution, lower maintenance overhead, NPS that climbs while the rest of the industry's NPS slides. The hype rides high. The thirty percent *compounds*. **Stop sustaining. Start compounding.** *If you're counting the cost of nails, [talk to us](/#contact) — we may be able to help.* --- ### Pilots stall, or pilots compound. There isn't a third option. Published: 2026-05-19 Updated: 2026-05-20 Author: Gopal Koratana, Founder & Chief Practitioner URL: https://ibotsystems.com/blog/pilots-stall-or-compound/ Tags: AI SDLC, Pilot Trap, Enterprise AI, PlayerZero, Legacy Systems, Compounding The pilot trap Sid Mookerji named in retail AI isn't a retail problem. Any enterprise running AI on systems built before AI hits the same wall — the pilot survives the lab, meets the legacy, and stops compounding. Sid Mookerji wrote a piece last week about [the pilot trap in retail AI](https://www.linkedin.com/posts/mookerji_the-pilot-trap-in-retail-ai-share-7462842115069243392-ydTr). He named something every engineering leader I talk to has felt: the pilot dazzles in a controlled environment, then collapses the moment it touches the real system. His diagnosis pointed at the usual suspects. No structured data. Mismatched processes. Unclear ownership. He's right about all of it. But the trap he's describing isn't a retail problem. It's what happens any time AI adoption gets treated as a tool rollout instead of a change in how the work gets done. ## Greenfield was always the easy half The current generation of AI tools was tuned and demoed on greenfield code, fresh data, and one team's well-bounded workflow. Those are the conditions that make any software tooling look like magic. A new repo. A clean slice of the problem. A single owner who can say yes. Then the pilot leaves the lab. Now it's looking at a .NET monolith stitched together from three acquisitions. A billing platform whose business logic lives in a stored procedure that nobody has touched since 2014, because the person who wrote it left in 2017 and nobody else understands what it does. Four teams with four definitions of "customer." A compliance posture that will not accept *"the model decided"* as an answer to anything. The AI was good. The conditions it was good in just don't exist in production. ## What the diagnosis actually means When people say "no structured data," what they usually mean is that the codebase was never required to be queryable by anything other than the application that wrote it. The data is there. It's encoded in twenty years of business rules, edge cases, and conventions that live in people's heads. A retrieval pipeline can't extract what was never written down. "Differing processes" is the polite framing. The real version is that *the business runs on locally optimized workflows, and nobody has the authority or the budget to harmonize them*. AI doesn't fix that. It inherits it. "Unclear ownership" is what the org chart looks like the moment something breaks. A pilot can dodge that question. Production can't. ## The shape of the fix You don't escape this by buying better AI. You escape it by changing the practice the AI lands in. Three things have to be true. First, **the system has to be readable before the model touches it.** Business rules surfaced. Unsafe surfaces flagged. Dependencies traced. We use PlayerZero as the spine for this work, with its simulation layer letting agents propose changes without breaking production. Whatever stack a team uses, the principle holds: a model can only be as good as its model of your system. Second, **the work has to be decomposed into measurable blocks.** A pilot has no exit criteria, which is part of why so many of them quietly become permanent. A block does. Two to six weeks, fixed price, a defined deliverable, an outcome you can measure from the outside. Blocks compound. Each one permanently lowers the cost of working in the surface area it touched. Third, **somebody has to operate the system instead of handing it off.** Pilots fail at the handoff. Practices don't have a handoff. The agents live across CI, support, ops, and reporting, and they get tended like anything else in production. ## Compounding is the real metric The pilot trap doesn't announce itself as failure. It shows up as a slow stall. The pilot worked. The next one was harder. The third one stalled out. The fourth got deferred to next quarter, then the quarter after that. Eighteen months in, the team is back to sustenance work and there's a procurement bill stapled to it. The right question to ask isn't whether the pilot worked. It's whether each block of work makes the next block cheaper. That's the curve that matters, and it's the one I'd push leadership to track. In the engagements where this has worked for us, that curve bends. A lean healthcare engineering team cut maintenance overhead roughly *in half*. A research SaaS company in a regulated space saw productivity climb about *4×* over eighteen months while their customer NPS went up *51 points*. The curve bends because the practice got better, not because the tool got newer. ## The take Sid named the symptom accurately. The cause is bigger than retail. Any enterprise running AI on systems that were built before AI will hit the same wall, in roughly the same way: the pilot survives the lab, meets the legacy, and stops compounding. A different pilot won't fix that. A different practice might. *If you're somewhere on that curve and it's starting to flatten, [get in touch](/#contact). We've seen this one before.*