Arjun Kannan systems / workflows / signal

Co-founder at ResiDesk

[SURFACE 01]

Signal into action

Arjun Kannan

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

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

Before that I worked on outcome-based lending at Climb Credit and advisor-facing analytics at BlackRock. 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

[START 02]

A good place to start Current snapshot

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 real operators, missing context, edge cases, and the urgency of work already in motion.

Scroll for the long version

About

[MODULE 03]

Where the pattern started

I grew up around research, so the default future looked 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 does not just save time, it changes the shape of the job.

The industries have changed since then, but the shape of the work 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 became the leverage.

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

Real stakes sharpen the interface.

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

Outcomes changed the product.

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 in the conversation.

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

Work

[MODULE 04]

Where I built the loop

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 context 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.

Advisor workflow

$40M ARR

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

ResiDesk

Co-founder / product

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: ownership, urgency, and the context needed 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.

BlackRock

Product / 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 signal and outside proof

Conversations

[MODULE 06]

Talks and conversations

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 full 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 interface chrome.

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 mid-work, mid-mess, with no audience and no one grading the demo.

FAQ

[MODULE 08]

Questions that come up a lot

What AI systems do I actually build?

I build AI that fits into how people already work. At ResiDesk, that means turning resident conversations into operational context, copilots, and agent systems that help teams decide earlier and follow through with more precision.

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. Recent talks have used resident conversations as the starting point for what better operating systems should do next.

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, mentoring, and operator advice

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.