IN FOCUS
MARK CHOUDHARI / MACHINTEL TO JYNAI / THE FOUNDER’S WORKING WEEK

People / Founders & operators

Mark Choudhari wants his time back

The Machintel founder spent years applying AI to business, then found himself serving the software. His next venture, JynAI, takes aim at the work that keeps founders from running their companies.

Advertisement

Mark Choudhari spent about two years deciding which AI to use. This is a splendid way to become knowledgeable about software and a rather expensive way to spend a working week. By his own account, he kept treating the research as diligence until he recognized how much of the company’s attention it consumed. The founder had acquired a second occupation. The occupation was choosing.

His response now is surprisingly restrained for someone building an AI company: stop adding candidates to the list. Freeze the tools for a month. Put the careful thinking into the work the business needs completed. There is a pleasing indignity in this advice. A person can spend years acquiring technical expertise only to discover that the next useful move is to close a tab.

An early arrival at a late party

Choudhari’s acquaintance with AI predates its current social popularity. He says he began studying it in 1992 and completed a master’s at MIT in 1996. The employment prospects he remembers were discouraging. His subsequent account follows the practical uses he found anyway: software development, cellular technology and data processing.

Machintel’s name, he explains, comes from Machine Intelligence. The software work developed into Nathan Ark Software; a data team became International Data Machines. His description of those years contains a welcome domestic correction to entrepreneurial grandeur. “Some might call it stubbornness (my wife does).” A spouse can compress a corporate retrospective with admirable economy.

The line has another advantage: it admits persistence can look different from the other side of the dinner table. In his telling, the work continued through periods when AI attracted less attention. Customers still had problems to solve. The fashionable status of the technique was a separate matter.

1992Begins studying AI, by his account
1996Completes his MIT AI master’s, by his account
2024Named Machintel CEO in January announcement
2026Writes about the cost of operating AI

The business behind the campaigns

Machintel gives that interest a commercial setting. Its work brings together audience data, content, media distribution and campaign execution for business marketers. The company describes a substantial history of operating behind other businesses’ brands. Agencies and platforms could sell the service while Machintel did the work out of sight. Recognition, in that arrangement, was someone else’s department.

The company now describes opening more direct access to brands while retaining those partner relationships. Its own account emphasizes control over the ingredients of a campaign, from targeting to distribution. That is useful context for Choudhari’s later preoccupation with who owns the whole job. A campaign has to survive the journey between its constituent parts.

In January 2024, with Choudhari identified as CEO, Machintel announced an expansion of Nathan Ark’s web and app development services under Rob Kristie, its director of web development and strategy. The initiative used Jamstack technology and included a revised corporate website bringing several sub-brands into one digital presence.

The announcement linked development work with the company’s marketing, data and AI activities. For a reader following Choudhari’s career, the significant detail is the breadth of the operation: building the digital experience sat alongside reaching the audience. The business had several kinds of work to coordinate, each with its own expertise and its own opportunities for a handoff to become a delay.

The people around the operation mattered too. In 2023, Machintel welcomed Aditya Pittie to its honorary board of advisors. Choudhari spoke about the value of industry guidance and recognizing emerging opportunities. The appointment illustrates a practical side of leadership: finding people whose experience can inform decisions before the decisions become expensive. An advisory relationship gives the founder another perspective to consult, alongside the internal team doing the work.

His comments about external engineering partners are similarly concrete. In a testimonial for Videal, he described working with its team on two products involving data processing and analytics. He praised the partner’s ability to build scalable software and connected that work to revenue for his company. The emphasis is on something built and used, with another team contributing the engineering. It is a useful companion to his later writing about delegation: business capability has always involved relationships as well as tools, and knowing whom to depend on remains part of the founder’s job.

A promotion nobody applied for

In July 2026, Choudhari described another job he had accumulated: systems integrator. A new tool needed to connect with the customer database, email, finance systems and existing data flows. He did the connecting. When something changed upstream, the repair returned to the person who understood the arrangement. Familiarity had quietly become a maintenance contract.

His account is specific about the nuisance. Models updated. Interfaces changed. Connections that had worked stopped carrying information. Better documentation helped only around the edges. Someone else controlled the schedule of the changes; he inherited the consequences. It is an awkward form of responsibility, with the hours attached and the authority elsewhere.

That experience explains the target of his current venture more clearly than a catalogue of features could. He wants the maintenance and coordination to live somewhere other than the founder’s week. His proposed solution is an operating layer that carries those obligations. The attraction, as he describes it, is getting back to deciding what the company should do.

Mark Choudhari’s stylized LinkedIn portrait, facing to the right
A different angle: the stylized portrait Choudhari uses on LinkedIn. The question in his recent writing is what deserves a founder’s attention.

He has also developed a three-layer picture of the problem. Tools do individual jobs. Workflows connect steps. Above them sits the responsibility for running the operation. In his telling, Machintel kept buying within the first two layers while expecting the third to appear. The collection grew. The missing responsibility remained missing.

Choudhari’s three-layer model
03 / Business operationOwn the job and its completion
02 / WorkflowsConnect the steps
01 / ToolsPerform individual tasks
A conceptual diagram of his argument, rather than a performance chart. More pieces do not automatically supply ownership of the whole.

The family resemblance

There is a quieter strand to Choudhari’s public life. In a 2017 statement seeking to contribute to Canyon Crest Academy’s site council, he wrote that both his parents had been teachers for more than 35 years. He described a lifelong interest in education, co-founding an elementary school in another country and helping establish a nonprofit for children’s education.

The statement placed those experiences alongside corporate board work as reasons he might be useful to the school. It offers a different scale of ambition from the technology-company biography: a willingness to bring experience into a school community. Education was something to help organize as well as something to list after his name.

In March 2025, marking International Women’s Day, he credited his mother with teaching him hard work, resilience and kindness. His wife, he wrote, had taught him about patience and partnership; his daughters had prompted him to question assumptions and see with fresh eyes. The account gives his independence some company. He describes people who have changed how he thinks.

Colleagues supply their own perspective. A public farewell from Saurabh Khadilkar thanked Choudhari for the opportunity to join Machintel and for mentorship along the way. A LinkedIn recommendation from Neil D’Mello describes a focused, witty person, outwardly calm while working hard underneath. Such recollections are personal assessments, and they make the picture more human than a list of appointments.

The useful art of stopping

One of Choudhari’s more interesting recent anecdotes concerns a campaign that ended. In a July 2026 essay, he described Machintel using Works across six teams. An outbound sequence had run across 31 publications, he wrote, with activity continuing while the replies failed to develop into useful conversations.

The team had invested in the sequence and defended it. Reviewing its record made it easier to stop and return attention to accounts that were responding. His lesson concerns judgment: a system’s value includes the work it helps people abandon. He draws attention to the less visible value of deciding what deserves to continue.

“Producing is easy to point at and judgment is quiet.”

Mark Choudhari, July 2026

This is Choudhari’s account of the experience, and its interest lies in the decision he chooses to celebrate. New software ordinarily arrives accompanied by examples of things made faster. Here, the useful exhibit is something removed from the schedule. Even a very capable machine ought occasionally to save everyone the trouble.

A company that can carry the work

JynAI, where Choudhari is founder and CEO, positions Works as an AI business operating system for founders and their teams. The company describes its intended work in practical terms: operations, follow-ups and decisions that otherwise keep returning to the person in charge. Its public company profile lists a 2024 founding and a San Diego base.

His ambition is directed toward smaller businesses. The challenge he describes is giving them an operation they can use without obliging the founder to assemble and supervise every component. That remains a product proposition to be earned in practice. It also follows directly from the frustrations he has chosen to recount.

His writing on delegation adds an organizational condition: the team needs access to the context and standards behind decisions. An owner who merely steps away leaves a gap. Choudhari argues for putting the rules, objectives and escalation points where other people can use them. The founder’s knowledge has to become available beyond a conversation with the founder.

Elsewhere, he describes the opportunity cost of tending the tools: attention unavailable for a customer, a hire or a consequential business decision. His proposed measure of progress is the return of that attention. The purchase can be completed in an afternoon. Creating room in the working week is the more demanding test.

That is where the story leaves him: still building, still arguing for AI, and more interested in the burden it removes. A founder can acquire an impressive collection of tools and remain the only person who knows how the place works. Choudhari’s current ambition is to give the company more of that knowledge, and give its founder a little less to do.