Arjun Kannan product / systems / signal

Co-founder at ResiDesk

Control Surface 01

Signal to action

Arjun Kannan

I turn messy signal into systems people trust enough to use.

I co-founded ResiDesk to help multifamily operators translate resident conversations into earlier decisions about retention, rent, maintenance, and staffing.

Before that I worked on outcome-based lending at Climb Credit and advisor-facing analytics at BlackRock. Before that I studied applied physics at Cornell and learned that code is useful when it removes real friction.

The thread across all of it is the same: important information trapped in the wrong system, reaching the wrong person, after the decision window has closed.

Arjun Kannan
Resident signal AI harnesses Operator workflows Decision loops

Quick Start 02

A good place to start Spring 2026

If you are new here

Now

Building product and engineering at ResiDesk around resident signal, operator workflows, and AI-assisted decision loops.

Before

Product and engineering work at Climb Credit and BlackRock, where better context changed lending decisions, advisor workflows, and growth.

Start here

Read Work for the arc, Recent for outside proof, and Writing for the operating philosophy.

What I care about

Systems that survive contact with real operators, missing context, edge cases, and Wednesday-afternoon urgency.

Scroll for the long version

About

Module 03

Where this started

I grew up around research, so the assumed path was academic. I studied applied physics at Cornell because it sat between the things I liked most: fundamental science, real systems, and problems where small details changed the outcome.

Software came in through the side door. I was in an electron microscopy lab and wrote code to make a magnetic-noise setup faster. It saved hours of manual work immediately, which made the lesson hard to ignore: the right tool changes the shape of the job.

The industries have changed since then, but the pattern has not. At BlackRock it meant making institutional tools usable for advisors. At Climb Credit it meant underwriting against outcomes. At ResiDesk it means turning resident conversations into operating signal before small problems become expensive.

Software was an accident.

I wrote a tool in an electron microscopy lab to speed up magnetic-noise setup. It saved enough time, immediately enough, that software stopped feeling abstract.

I need the problem to be real.

I came back six months later, re-interviewed, and moved to New York. It was the first place I learned how much interface quality matters when the user is making decisions with real money behind them.

We asked a better question.

Instead of asking who looked safest on paper, we asked what happened to earnings after the program. That reframed underwriting, product, and data, and took annual loan volume from $1 million to $300 million.

The signal is already there.

Residents tell operators what matters every day. The work is translating those conversations into priority, timing, and ownership before the issue shows up in churn.

Work

Module 04

What I have built

The work has mostly been the same job in different settings: find the useful signal hiding inside a messy process, then build the shortest reliable path from signal to action.

Renewal signal

7%

Reported renewal and rent lift from turning resident feedback into earlier, more specific operating action.

Climb Credit

$1M → $300M

Annual loan volume growth after treating student outcomes as product data, not marketing decoration.

BlackRock

$40M ARR

Advisor-facing analytics product taken from zero to $40 million in recurring revenue in year one.

ResiDesk

Co-founder

We help multifamily operators understand what residents are telling them across renewals, rent, maintenance, and staffing. The product works when it changes what a team does next: who owns the issue, how urgent it is, and what context they need before responding.

Climb Credit

CTO and CPO

We underwrote against a different question: not who looks safest on paper, but what happens to a graduate's earnings. That forced the product to treat outcomes as infrastructure, not a story layered on top.

BlackRock

Product and engineering

The job was turning institutional infrastructure into something advisors could actually use with clients. Same information underneath, but packaged for the moment where a person had to explain, compare, and decide.

Recent

Module 05

Recent writing and outside proof

Conversations

Module 06

Interviews and talks

These are the best way to hear the operating system directly: what I pay attention to, what I ignore, and where I think AI starts becoming useful.

I write when the consensus feels too smooth. Most of it circles back to AI, product adoption, and the widening gap between a model that can answer and a system that can be trusted inside real work.

Read the archive

Usefulness is the only test.

If a tool does not help someone reach a better decision sooner, with less context loss, it is furniture.

Understand the job first.

Without knowing what someone is actually trying to do, you are just rearranging pixels.

Build the harness, not just the model.

The model is one part. Context, tools, guardrails, evaluation, and the handoff into someone's day are the rest.

Demos lie by omission.

What matters is whether people still reach for it on a Wednesday afternoon, mid-mess, with no audience.

FAQ

Module 08

Questions I get asked a lot

What kind of AI work do I do?

I build AI that fits into how people already work. At ResiDesk, that means analyzing resident sentiment, building copilots for property teams, and designing agent systems that surface the right context before small problems become big ones.

What have I built before ResiDesk?

I worked at Climb Credit and BlackRock. At Climb, I helped grow annual loan volume from $1 million to $300 million. At BlackRock, I built a retail analytics product that reached $40 million ARR in its first year.

What do I usually write and speak about?

How AI products actually hold up in practice: agent workflows, LLM evaluation, product loops, and what separates a compelling demo from something that works on a Tuesday afternoon. My recent 20for20 talk started with resident conversations across 30,000+ units in 11 states.

What is my view on AI?

I care less about whether something looks impressive and more about whether it helps someone make a better call. That usually means getting context right, measuring what matters, and keeping a human in the loop before automating anything.

Investing

Module 09

Investing and mentoring

I have invested in more than 100 startups and mentored through Techstars. I tend to back founders who are close to the problem, close to the customer, and clear-eyed about what they do not know yet.

That honesty matters more now than ever. Generic advice is everywhere. What still counts is specific context, good judgment, and helping someone get to the next real decision faster.