Aaryush Gupta

Aaryush Gupta

I build the systems behind how anyone solves problems.

Interesting people are the best part of this. Say hi.

Save contact
Dwg. no.
AG-001
Sheet
01 / 05
Region
us-central
Last deploy
2026.10 · 035b43f
Scale
NTS
§ 02How AI fitsSheet 02 / 05

Four levels where AI changes an organization.

Most problems show up at one level but are caused at another. I start by finding which level a problem actually lives at, then build there. Each level links to the work below that sits at it.

  1. How the organization runs

    Operating models and decision rights: who decides what, and which decisions a system can carry so people don’t have to.

    Seen in CylerityOperating modelGupta AdvisoryAdvisory

  2. How work moves

    The handoffs between people and AI: where judgment is needed, and where volume can be absorbed without anyone touching it.

    Seen in EarlierSmartBenAICylerityEngineering intake

  3. How things get built

    Engineering and product processes rebuilt around AI, so more people can build and fewer steps wait on a specialist.

    Seen in Ready ReboundEngineering loopCylerityEngineering intake

  4. What gets built

    Products that only exist because AI does.

    Seen in EarlierUniviseSkale.winCareer platformCylerityClaims underwritingEarlierUMN Discovery Launchpad
§ 03WorkFig. 3.1 — Timeline, newest first

Companies, and the systems inside them.

Next — contextOS. Coming soon.

Gupta Advisory Founder I work with organizations on how they should operate with AI. Inside Gupta Advisory

Jan 2024 – PresentAI Lead

Cylerity

A fintech-healthcare company that underwrites insurance claims and advances cash to healthcare providers, so they aren't waiting weeks to get paid.

Inside Cylerity
SYS.01 L.04

Claims underwriting

Turns a weeks-long claims cycle into same-day funding decisions. Risk and compliance run in parallel, and providers see what was approved and why.

Backs an eight-figure lending facility
SYS.02 L.02L.03

Engineering intake

Anyone in the company drops an idea into a shared Claude project. A conversation draws out what's needed and classifies it as an idea, tracked, or a scope, ready to build.

Retired a sprawling spreadsheet
2023 – 2024Earlier work

Earlier

The first products I built with AI, from the release of GPT-4 onward.

SYS.05 L.04

Univise

Built a university advising system that spread across campus through word of mouth. No marketing, no push, just a product that solved a daily problem.

Best pitch at Transcend
SYS.06 L.02

SmartBenAI

Automated claims data extraction for healthcare TPAs while keeping humans in the loop where compliance demands it.

Compliance-first automation
SYS.07 L.04

UMN Discovery Launchpad

Replaced ad-hoc startup mentorship with a system that structures what each founder has already done, so the right people can help without relearning it.
§ 04WritingSheet 04 / 05

Notes on where this is going.

Once, for Good

Solving the same problem twice never sat right with me. Here’s what AI changed about that.

This Is Bigger Than Electricity

My attempt, after years of failing to find the right words, to finally explain what AI means for everyone — not the technology, but what's already changing in the world around you, right now, while most people are going about their lives.

The Quiet Singularity

An observational analysis of three concurrent developments in artificial intelligence — recursive model self-improvement, the commoditization of frontier-class inference, and the compounding automation of cognitive labor — and their implications for institutions designed around assumptions of scarcity.
All writing
Cylerity
Esc

Cylerity · AI Lead · SYS.02

  • L.02 — How work moves
  • L.03 — How things get built
Engineering intake system diagram Anyone in the company starts a conversation in a shared Claude project. The conversation is classified as an idea, which is tracked and revisited as it sharpens, or a scope, which is ready to build and goes to an engineer. Shipped work feeds back to the people who asked. OPS FIN SALES VAGUEDEFINEDSHIPPED WORK FEEDS BACKREVISITED ASIT SHARPENS Anyone IN THE COMPANYN.01 Conversation SHARED CLAUDE PROJECTN.02 Classify N.03 Idea TRACKEDN.04 Scope READY TO BUILDN.05 Engineer builds SHIPS ITN.06
Fig. 02 — Every request enters the same conversation; classification decides where it waits. FlowRevisitedFeedback loop

Engineering requests used to live in a sprawling spreadsheet. Half-formed ideas sat next to work that was ready to build, and scoping an idea depended on someone already knowing what it needed.

Now anyone in the company drops an idea into a shared Claude project. A proactive conversation draws out what’s actually needed, then classifies it: an idea, vague but tracked, or a scope, defined enough for an engineer to build. People focus on the ideas; the system handles the definition, and what ships feeds the next conversation.

Input
Anyone in the company
Interface
A shared Claude project
Output
Idea (tracked) · Scope (ready to build)
Replaced
A sprawling spreadsheet

Keyboard map

?
This map
g h
Go to the hero
g l
Go to how AI fits
g w
Go to work
g r
Go to writing
g c
Go to contact