Kevin Chan: The One-Person Engineering Department

Impact at a Glance

• One builder is replacing 20+ SaaS tools for a 50-person business, with Salesforce next on the list
• Agent Accounts lets Kevin provision a working email identity for a new project without a Google Workspace tenant or restricted scope review
• A single Nylas integration covers email, calendar, contacts, scheduling, and meeting intelligence — collapsing what would otherwise be five separate vendor relationships

Meet Kevin

Kevin Chan isn’t a developer by trade. He’s the guy that small businesses call when they have an idea and no patience for a 24-month digital transformation project. He builds internal tools — the deeply useful kind that quietly replace a Trello board, a Salesforce instance, an offboarding checklist, and a tangle of subscriptions nobody can remember signing up for.

He’s been doing the low-code, no-code thing for years. Then Claude Code showed up and, in his words, “accelerated everything. You just do it, you do it all.”

What Kevin Builds

At one client, a small business he’s worked with for over a decade, Kevin is methodically rebuilding the entire SaaS stack from the inside out. The list keeps growing:

• A project management tool to replace Trello
• Email archives to save inboxes when employees leave (instead of paying $20/month per mailbox indefinitely)
• Asset and phone tracking wired into Google Workspace
• A resourcing tool for the team
• A security layer sitting between staff and tools like Gmail, Drive, and Calendar, so the team can use AI without handing over full inbox access
• A custom personal dashboard that pulls his calendar, email, and the rest of his daily feeds into one place

All of this. From one person.

Two days after Kevin learned about Nylas Notetaker on a call, he had it implemented and live with his client’s users, replacing a stack of meeting tools they’d been paying for separately.

Why Agent Accounts clicked

Kevin had used Nylas years ago for the email and calendar APIs, and came back when a few new projects landed on his desk. What caught his eye this time was Agent Accounts, Nylas’s purpose-built email and calendar identity for agents and apps.

The pitch made immediate sense to him: he didn’t always want to stand up a full Google Workspace tenant just to give a project an inbox. Sometimes he just needs an email address that can receive a message, run an LLM over it, and route the result somewhere useful.

“All I really care about is having it come in, have some sort of LLM in it, and then redirect it somewhere else. That was the core idea.”

With Agent Accounts, that’s the whole thing: a shell with a real email address and a real calendar, send and receive, RSVPs, hosting events, the works. Drop an agent behind it, and it has an identity in the world.

A few use cases were already lining up in Kevin’s head:

The insurance client. Every year, dozens of carriers send renewal documents into a central inbox. Right now it’s a manual triage problem. An Agent Account that receives those emails, parses them, and pushes structured data into the right system would collapse a week of work into an afternoon.

The manufacturing client. They get a flood of EDI data flowing between systems and their ERP. A dedicated agent inbox is the kind of thing that turns “we need to integrate two enterprise systems” into “forward it here, we’ll handle it.”

The security layer. Kevin’s already building a control plane between his client’s team and Google. Agent Accounts give him a way to add scoped, auditable email identities without provisioning a real human seat for every workflow.

That’s the whole game. Solve the hard infrastructure once so builders like Kevin can solve the business problems everywhere.

The CLI unlock

Kevin’s been pushing himself toward CLI-driven workflows — partly because Claude Code orchestrates so much of his work now. 

For a builder whose default mode is “scope it, hand it to AI, and ship it by tonight,” an agent-friendly CLI isn’t a nice-to-have. It’s the integration point. Agent Accounts plus the Nylas-provided CLI means Kevin can provision identities, send mail, monitor inboxes, and wire it all into whatever internal tool he’s building — without leaving his terminal. 

The bigger picture

Kevin’s story is about what a single capable builder can do when the infrastructure problems are handled by someone else.

He’s eyeing his first hire. He’s thinking about sales and outreach. He’s got more clients than he can comfortably handle. And the reason he can love the work is that the boring, hard parts aren’t his problem anymore: OAuth, calendar sync, deliverability, meeting bots, programmable email identities.

“I’m probably going to build something this week with it.”