Nizar Abi Zaher and the value of starting over

A thousand dollars is an unremarkable sum in a startup story, which is precisely what makes Nizar Abi Zaher’s account of spending it interesting. In July 2025, he said his team had put $1,000 into user feedback for Mail0, the email company also known as Zero. The return he described was understanding: why people kept using it, what they wanted, and who might want it next.

He sounded delighted. The post had capital letters, a list of discoveries, and the excitement of someone who had finally been given directions after driving around the block. For a founder building software to organize other people’s work, there was something pleasingly practical about the purchase. Ask the people doing the work. Pay attention to what they say.

That small episode offers a way into a career whose public labels have already changed several times. Abi Zaher is known online as Nizzy. He worked at Cal.com, published coding projects, co-founded Zero with Adam Wazzan, and helped turn the company into Orchid. More recently, he has been introducing Keiki, a platform built from the systems behind Orchid. The products moved. His interest in reducing the steps between asking and doing remained visible.

Before the inbox, a public workshop

Abi Zaher’s route into this work included business law studies at Carleton University in Ottawa. His education belongs to the story because it widens the picture of a software founder beyond the usual tidy progression through a computer science department. The public record also includes a programming course platform and a collection of repositories designed to help other developers get applications working.

The course platform, Nizzyabi.com, describes its audience as self-taught developers improving their web development skills. Its repository is public. That is a concrete form of teaching: learners can inspect an application as well as hear someone explain one. A finished screen can be attractive; the folders and files behind it are where a curious developer starts asking more useful questions.

Another project, Nizzy Starter, packages the repetitive groundwork of a software business. Authentication, database connections, payments, email integration, and an analytics page are already included. These are the chores that arrive before the supposedly interesting part. Abi Zaher was making a shortcut through them. The project’s instructions link to a YouTube walkthrough, bringing the code and the explanation back together.

His teaching site puts the invitation bluntly: “Build cool sh*t”. The tone is casual, the work fairly specific. It is an invitation to make something, with enough material supplied to begin. That combination helps explain the public Nizzy persona: code, demonstrations, and a willingness to have the workshop door open.

A familiar annoyance, rebuilt in public

Before Zero, Abi Zaher worked as an engineer at Cal.com. A scheduling product sits close to the small negotiations that fill a working day: finding a time, confirming it, remembering what happens next. Email supplied another part of that territory. With Wazzan, he took on the inbox, a place where requests accumulate faster than anyone’s enthusiasm for sorting them.

Zero entered Y Combinator’s Spring 2025 batch. Its public launch presented an AI email client that could prioritize messages, summarize threads, draft replies, and let people ask questions about their inbox. The pitch began with a recognizable problem: the user was still responsible for turning incoming correspondence into an organized day. Zero proposed having the software take on more of that coordination.

The code was open. Developers could examine the application, modify it, or undertake the work of running it themselves. The repository documented connections to existing email services and a self-hosting route. Those choices gave technically inclined users something more substantial to evaluate than a polished landing page. They could look at how the thing had been assembled.

There is a useful distinction between making code available and making a product effortless. Self-hosting still requires setup. Connecting to outside services still introduces dependencies. Zero’s documentation makes those pieces visible. For Abi Zaher, whose earlier projects also included instructions and working code, a public repository was a familiar way to put the product in front of other builders.

The audience and the people using it

In July 2025, Abi Zaher appeared on The Lobster Talks Podcast to discuss Zero. The conversation’s published chapters move from open-source development to social presence, authenticity, onboarding, and launching quickly. It is an instructive list of concerns. Building the software occupied one part of his attention. Helping people encounter it, understand it, and begin using it occupied several more.

His public presence also connected him with other people building audiences. Startup creator Bryce Johnson later thanked Abi Zaher for appearing on his stream in its early days. That is a modest connection, but a revealing one. A founder’s distribution can develop through other people’s experiments as well as his own. Showing up for a conversation is one way to become part of somebody else’s working network.

The $1,000 feedback exercise belongs alongside those activities. Attention can bring a person to a product. The person still has to decide whether to keep it. Abi Zaher’s list of discoveries was about that second decision. He wanted to understand the users who stayed and the work they expected the application to do. The answers gave him something to build against.

Zero changes its address

The company eventually changed direction. Zero became Orchid, an assistant delivered through messages. In June 2026, Abi Zaher looked back on the decision, describing it as difficult and, in his judgment, worthwhile. The striking part of his account concerned what survived: conversations, distribution lessons, relationships, and the instincts developed along the way.

“almost nothing was wasted.”Nizar Abi Zaher, reflecting on the Zero-to-Orchid pivot

His account gives the pivot a less theatrical meaning than the word sometimes acquires. The earlier work had produced knowledge as well as an application. Changing the application did not require discarding every relationship or repeating every lesson. There was experience available for the next attempt, even when the company’s public description needed rewriting.

Orchid moved the interaction into a messaging thread. Its proposition was an assistant that could brief the user, prepare replies, and arrange meetings, with approval built into the process. The change made the interface more familiar. Rather than learning another set of screens, a person could begin by explaining what needed to happen. The work behind that apparent simplicity remained the company’s responsibility.

An assistant with a trash-day reminder

Abi Zaher’s own automation demonstration brings the idea down to earth. He shows a recurring search for workspace properties in Dallas, asking for details such as the address and square footage. He then demonstrates a weekly digest of meetings through Granola and a reminder to take out the trash. Ambitious software, it turns out, must still accommodate Tuesday.

Those examples reveal the scale at which he wants the assistant to be useful. A property search involves gathering information over time. A meeting digest involves returning to material that might otherwise be forgotten. A household reminder involves remembering something unglamorous at the right moment. Each example gives the promise of automation a task small enough to recognize.

The appeal depends on the handoff actually working. A reminder that needs reminding has become another chore. Abi Zaher’s later writing returns to this requirement: an assistant needs dependable memory, clear permissions, and an account of what happened. His aspiration is to give people room to decide while software handles more of the coordination around the decision.

The second product inside the first

Keiki grew out of the infrastructure required to make Orchid function. Abi Zaher has explained that a useful model response arrived relatively early; turning the response into dependable software took much longer. The team had to solve delivery, ongoing conversations, memory, tool use, and work continuing in the background. Those systems became something it could offer other builders.

In his September 2026 introduction, he described a platform for deploying an agent across the messaging channels customers already use. The business supplies its knowledge and the work the agent may perform. Keiki supplies the surrounding systems. There is a family resemblance to the starter kit: package the necessary groundwork so someone else can begin closer to the thing they want to make.

For Abi Zaher, the longer-term interest is how a person’s intentions can travel across services. A customer wants an item, an appointment, or an answer. Each business has information about what it can provide. His writing imagines personal agents and business systems coordinating more of the exchange, while people retain control over important choices. It remains an ambition whose value will be decided in use.

The sequence is more interesting than a polished origin myth. A coding creator supplied working examples. An engineer helped build an inbox. A founder paid to hear what users wanted, then helped change the company’s direction. Now he is offering other teams some of the infrastructure the work required. A thousand dollars bought a clearer set of questions. He has kept building around them.