Founder file3 YC companies◆Socialcam to Autodesk◆90+ angel investments◆Building Yuma AI in Boston◆Founder file3 YC companies◆Socialcam to Autodesk◆90+ angel investments◆Building Yuma AI in Boston◆

People / Founders / The working prototype

Guillaume Luccisano Has Built Three YC Startups. The Third Began by Accident.

From Justin.tv to Socialcam, Triplebyte and now Yuma AI, Guillaume Luccisano has spent two decades following one instinct: build the working thing early, then let real demand make the argument.

Guillaume Luccisano’s third company announced itself in the least ceremonious way possible: strangers wanted demos. In late 2022, he had been experimenting with OpenAI’s Davinci model, months before “AI agent” became a phrase that could fill a conference hall. The model hallucinated. Instructions went missing. Still, enough of the future flickered through the errors to make a prototype worth releasing. Luccisano put Yuma into the world for fun in December. Shopify merchants filled his inbox. A side project acquired a calendar, then customers, then a cap table.

He calls Yuma an accidental startup, which is charming but only partly lets him off the hook. Accidents may deliver an idea; they rarely produce a working prototype. Luccisano had spent nearly twenty years becoming the sort of engineer who could move quickly when an unruly technology started behaving just well enough. By the time demand arrived, he had already learned how to notice it.

3Y Combinator companies
$60MSocialcam acquisition price
90+Angel investments

Paris to the live internet

The story begins in France. Luccisano started at a coding school in Paris in 2003 and later earned a computer science master’s degree from EPITECH. His early public code carries the marks of that era: practical Ruby projects, including a Rails plugin for translating routes. The software is old enough to feel archaeological now, but it offers a useful clue. Before the chief-executive title and investment portfolio, he was solving the small irritations that programmers understand immediately.

In his early twenties, he moved from France to San Francisco and joined Justin.tv as a software engineer. The company was a live-video laboratory that would eventually become Twitch. More important for Luccisano’s next chapter, it was also a concentrated network of builders. He met Michael Seibel, Justin Kan and Ammon Bartram there. Shared code became shared history.

With Seibel and Bartram, he co-founded Socialcam in 2011. The app let people record, edit and share mobile video at a moment when phone cameras were improving faster than social habits could settle. Socialcam joined Y Combinator’s Winter 2012 batch. That July, Autodesk agreed to acquire it for approximately $60 million. Luccisano was 25.

There is a temptation to read an early exit as a tidy ending. His was closer to an apprenticeship with unusually public results. Socialcam taught speed, consumer distribution and the instability of being early. Short video would later dominate the internet, but technical timing is not a prize awarded for predicting the broad shape of culture. The product still has to meet the particular phone, network, algorithm and appetite of its moment.

Guillaume Luccisano speaking with Jake Aaron Villarreal during a video interview about AI agents for customer support
Third-company questions, first-company energy: Luccisano talks AI agents with Jake Aaron Villarreal on Born in Silicon Valley.

The second pass

In 2015, Luccisano and Bartram teamed up again, this time with former Y Combinator partner Harj Taggar. Triplebyte attacked a different kind of friction: technical hiring. Instead of trusting pedigree and résumé signals, the company built assessments intended to measure engineering ability more directly. Triplebyte entered YC’s Summer 2015 batch and eventually raised close to $50 million.

The industries had changed completely. The operating instinct had not. Socialcam reduced the distance between recording a video and sharing it. Triplebyte tried to reduce the distance between being able to code and being recognized for it. Both companies were arguments for replacing inherited signals with observed behavior.

Luccisano ran the technical side of Triplebyte for years and left during the pandemic. He spent time in France, then Singapore, where he served as a visiting partner at the Southeast Asia-focused accelerator Iterative. By then, he had also become an active angel investor. His personal tally has passed 90 companies across the United States and France, including Algolia, Airbyte, Gorgias and Yubo. His stated style is compact: “I’m hands-off by default and helpful when asked.” It is the rare investment philosophy that understands silence can be a service.

“I released Yuma as a prototype for fun in mid-December 2022 and was overwhelmed with demo requests.”Guillaume Luccisano, on Yuma’s beginning

The useful mess

Yuma began while large language models were still awkward houseguests. They could be startlingly capable, then confidently wrong before lunch. Luccisano’s prototype aimed at customer support for Shopify merchants, a narrow beachhead full of repetitive questions and unforgiving details. An agent might need to locate an order, interpret a policy, preserve a brand’s tone and take an action in another system. Fluency without accuracy would merely produce beautifully written trouble.

That constraint shaped the company. Yuma developed from a support copilot into agents designed to handle conversations and actions across commerce systems. It joined YC’s Winter 2023 batch, Luccisano’s third trip through the program. In 2024 the company announced $5 million in funding. Its team grew across Boston, Barcelona and remote locations, while the product expanded into sales questions, social comments, workflow controls and ticket analysis.

01 / Build before naming

A rough working object can reveal demand that a polished thesis misses.

02 / Start painfully narrow

Commerce support gave early models concrete systems, actions and failure cases.

03 / Watch behavior

Demo requests mattered because merchants volunteered their time and problems.

04 / Keep the clock visible

Luccisano tracks days since Demo Day to remember that company-building is long work.

The clock matters to him. In one investor update, Luccisano highlighted the 757 days since Yuma’s Demo Day and explained that he included the count each month, before the business metrics. It was a reminder that startups are a long-term game. The gesture is slightly comic and usefully stern. Growth percentages can turn a month into a verdict. A day count restores scale.

In 2024, he moved with his family to Boston, positioning himself between Yuma’s American and European operations. He is a father of four daughters and has lived in France, San Francisco, Singapore and now Massachusetts. The geography reads less like restless wandering than a career organized around the work and the people doing it.

When the tool changes the builder

There is an appealing symmetry in Luccisano’s current position. He sells AI agents to teams whose work will change because of them, while his own work is changing for the same reason. In 2026, he wrote that after two decades of coding, the hands-on portion of his day had become mostly a matter of talking to agents, directing them and reviewing their output. More got done. Yet the old flow state, the hours that disappeared inside a programming problem, had faded.

It is a more honest observation than a productivity chart. New tools redistribute pleasure as well as labor. The experienced engineer gains leverage but loses some intimacy with the material. The job becomes orchestration, judgment and context switching. Luccisano’s nontechnical colleagues can now ship features that once required engineers; his wife, he wrote, was building a minigame with AI. The barrier to making software is falling, while the identity of the software maker becomes less settled.

Yuma’s newer products follow that movement from doing to directing. Ask Yuma, launched in April 2026, lets commerce teams build automations, investigate issues and generate reports through conversation. A Claude integration connects support data with other tools. The interface is language, but the real product is accumulated context: the policies, tickets, workflows, metrics and brand decisions that turn a plausible answer into a useful action.

He has also begun turning that operational context into conversation of another kind. In 2026, Luccisano and customer-experience operator Anya Kelly began hosting CX After Hours, a podcast built around practitioners from commerce and retail. The guests are the people who inherit the consequences of promises made elsewhere in a company: support leaders, operations directors and founders. It is a fitting format for someone whose companies have repeatedly lived at the border between a technical system and a human judgment. A product can automate a reply. A useful company still has to understand why the question keeps arriving.

The future rarely arrives as a strategy slide. Sometimes it arrives as a faulty prototype that customers keep asking to see.

Luccisano’s career does not form a neat industry thesis. Mobile video, engineering recruitment and commerce support occupy distant aisles of the software supermarket. The through-line is closer to temperament. He builds systems that observe what people can do, then tries to remove the friction between capacity and action.

That also explains the enduring importance of his early network. Seibel and Bartram were not famous names collected at an event; they were colleagues inside a difficult live product. Bartram became a co-founder twice. Y Combinator became a repeated institution across three eras. Investing became a way to return some of that accumulated help to other founders. The graph has value because its edges contain work.

Now Luccisano is building in a market crowded with declarations about autonomous agents. His advantage is not that he found a vocabulary nobody else would use. Everyone found it. His advantage is that he began when the models were still inconvenient, pointed them at a specific operational mess and stayed long enough for the mess to become useful knowledge. For a founder on company number three, an early habit remains intact: make the thing, show it early and pay attention when the inbox answers.