At 11:30 at night, Nicolas Walker had finished talking to ten investors and still had something to say. In a video recorded ahead of Y Combinator’s Demo Day, he sounds pleased by this discovery. Customers, fundraising, product development: the list is long, and he is ready to talk through it. Somewhere in that crowded evening, he offers a qualification for the founder’s job that rarely appears in a university prospectus.
“You gotta really like yapping to be a founder.”
Nick Walker, ahead of Demo Day
Walker, who goes by Nick, is the co-founder and CEO of MochaCare. The company handles hiring, scheduling and client intake with AI agents and human operators. He built it with Pranav Uppiliappan, a computer science graduate whose experience includes building agentic systems at GoDaddy. They entered Y Combinator’s Winter 2026 batch, taking on the work that arrives between a business owner’s plans for the day and the day itself.
The late-night video is a useful introduction. Walker does not deliver a hushed monologue about destiny. He talks about work and enthusiasm, with the conversational speed of someone whose evening has acquired a second evening. His advice is to choose a subject you can discuss for hours and still find interesting. A founder, in this telling, should test the endurance of his curiosity before testing anyone else’s patience.
01A haircut can wait
Before the investors came the questions. After finishing his degrees, Walker described a period of talking to grandparents, business operators, employees and families. He wanted to understand their problems before deciding what to build. The conversations included an older gentleman in a church parking lot who recommended that he shave his mustache and cut his hair. Market research had briefly become a grooming consultation.
Walker conceded that the gentleman might have a point. He also said the haircut could wait: there were more conversations to have. His grandmother was asking why he did not have a job. A Stanford education may earn a person an impressive credential; it offers limited protection from a grandmother’s perfectly reasonable questions.
His grandparents helped raise him. The family history matters here without requiring a grand theory of entrepreneurship. He describes their importance directly, and MochaCare’s founding account places both founders’ grandparents near the beginning of the story. His choice of work follows a personal connection as well as a technical interest.
The church parking lot anecdote also gives the research phase a pleasingly untidy shape. Walker was willing to ask questions beyond the usual professional circuit, and willing to report an answer that had little to do with his proposed product. Listening to people includes hearing what they think you ought to have asked. Sometimes their priority is your mustache.
02The music app before the midnight shift
At Stanford, Walker earned bachelor’s and master’s degrees in computer science, with a focus on AI and human-computer interaction. Those interests bring together the machinery inside a system and the experience of the person trying to use it. His student work gives a concrete example of that combination.
In the winter 2022 CS147 course, he was a developer on Entourage, a project about music NFTs and fan communities. His teammates were Alahji Barry, Emilio Rivas and Ruslan AlJabari. The proposed app let fans purchase digital music collectibles, connect with other listeners and participate in artist-led events. Its ambitions belonged to a particular moment in internet culture. Its development process remains more interesting than the fashion of its subject.
The team interviewed people, tested early ideas, built a Figma interface and developed a React Native prototype. Peer evaluations informed revisions. This was coursework, with a project site, reports and a concept video. It is a small, inspectable piece of Walker’s education: the work involved asking people what they needed, making something they could try and changing it after they did.
His professional experience crossed several kinds of technology. At Microsoft Azure, his work included software engineering and the Internet of Things. At Amazon Web Services, it involved software and data. Spotify brought personalization and product work. Linktree brought product engineering and growth experimentation. Across those roles, the recurring ingredients were code, users and decisions about what deserved to be built.
He also led a community service organization with more than 300 volunteers. Coordinating people belongs on this résumé alongside programming. A volunteer organization has participants, commitments and practical arrangements; software experience alone does not describe that work. By the time Walker became a founder, his background included both technical systems and groups of people who had to act together.
03The founders put themselves on the schedule
MochaCare’s launch offered an unusually specific detail about its own staffing. Walker went to bed at 3:30 a.m. Uppiliappan woke at 3:30 a.m. The pair described this arrangement as their way of guaranteeing continuous coverage while their AI agents handled much of the hiring and scheduling work.
There is a modest comedy in a company promising automation and then explaining precisely which founder is awake. There is also an operational commitment. Customers hand over a function of their business. The founders monitor the activity and intervene when an exception requires them. Their own time becomes part of the service they sell.
For Walker, the shift from engineer to operator is visible in that handoff. A product can be demonstrated during office hours. A managed service has to keep working after the demonstration ends. The schedule places him close to the exceptions, where a general rule encounters a particular person, a changed plan or an unanswered message.
The launch account presents this as the founders’ arrangement at that stage of the company. Its lasting interest is the choice it reveals: they personally took responsibility for monitoring the work. Building the software and running the operation occupied the same working day, even when that day ran well into the next one.
04Seven weeks, with the arithmetic intact
At Demo Day, Walker presented a more compact version of the story. He introduced himself as CEO, outlined his background and described Uppiliappan’s experience. Then he gave a number: $80,400 in contracted annual recurring revenue closed in seven weeks. He said the company was working within two franchise systems whose combined networks contained more than 600 locations.
The wording matters. Contracted annual recurring revenue is a statement about annualized contracted business. The 600-plus figure describes the size of the franchise networks. Neither figure means that MochaCare had 600 customers, or that it had collected a year’s revenue in seven weeks. The actual account is specific enough to be interesting without adding customers it never claimed.
In the lead-up to the presentation, Walker was onboarding customers, talking to investors and building the product. Those activities compete for a founder’s attention. The video at 11:30 p.m. catches him in the middle of that competition, still eager to talk. On stage, the same work has to fit inside a short introduction and a few numbers.
After Demo Day, he praised what his batchmates had built and said he was excited to see what came next for them. The public voice is social as well as ambitious. Uppiliappan’s comment on the post was affectionately direct: he liked Mocha, Care and Nick Walker. A pitch stage can make a young company look formal. The comment thread restores the two people who have been doing the work.
Contracted annual recurring revenue closed in seven weeks.
The 600+ locations he mentioned belonged to two franchise networks, not a claimed customer count.05An engineer wanted, conversation required
A later hiring post said demand exceeded what the team could service. Walker was recruiting a founding engineer in San Francisco and offered a $10,000 referral bonus if an introduced candidate joined and stayed for more than three months. It was a practical request, addressed to people who might know someone who could help.
His description emphasized full-stack development, AI and machine learning, product judgment and taking responsibility from identifying a problem through delivering a solution. The published role adds direct conversations with users and, where appropriate, meeting local customers in person. The work is meant to reach real users immediately. That expectation fits the founder who postponed his haircut to keep asking questions.
The recruitment page also makes room for silliness, basketball, yoga, freestyle rap and an interest in matcha and lattes. These are invitations in a company’s hiring copy, rather than a catalogue of Walker’s private hobbies. They do tell a prospective colleague something about the atmosphere the founders want: serious responsibility with enough room left for people to enjoy one another’s company.
The demands are substantial. The role is in person, with long hours and a schedule described as six to seven days a week. That detail belongs beside the cheerful language. Walker is looking for a person willing to work through an early company’s unsettled systems, talk with customers and build while the service is already operating. The jokes do not shorten the job description.
06Back to asking people
In October 2026, the Talk to Users Hackathon at San Francisco Tech Week listed Walker among its founder mentors. The event advertised office hours with founders and a building process that included feedback from intended users while teams still had time to revise their work. His listed role was CEO of MochaCare.
There is a clear continuity between that programme, the Stanford project and his own early research. Each puts a conversation inside the making of a product. A user gets to answer back before a builder has become too attached to the first version. For Walker, that approach has appeared in coursework, customer discovery and the team he is trying to recruit.
His story is still being written through everyday commitments: an investor conversation, a customer’s request, a piece of code, a handoff to his co-founder. The public details give him more texture than a row of employer logos. He can be enthusiastic in a late-night video, gently self-mocking about his hair and precise when presenting the company’s progress.
At 11:30 p.m., after ten investor conversations, he still wanted to talk. The interesting question in his new working life is what those conversations help him finish.