IN FOCUS
TYLER KOBLASA / FROM CLOUDAPP TO ORCARUVISUAL COMMUNICATION / CUSTOMER DEVELOPMENTBELOW THE SURFACE / SHARKS4KIDS ADVISOR

People / The working life / No. 01

Tyler Koblasa and the trouble with explaining things

He helped turn CloudApp into a business built around showing people what you mean. Now the founder and former CEO of the company known as Zight is applying his attention to AI content, wildlife encounters, and the misunderstood shark.

Advertisement

A screenshot is an admission that language has become hard work. Somewhere between “click the thing on the left” and the fourth explanatory email, a person gives up, captures the screen, and sends a link. Tyler Koblasa built a substantial part of his career around that moment. There is something appealingly modest about the proposition: a little less explaining, a little more understanding, and perhaps everyone gets to lunch.

As founder and former CEO of CloudApp, the visual communication business later renamed Zight, Koblasa worked on turning that everyday shortcut into something teams would buy. His subsequent interests include AI-assisted content and ocean conservation. They make an unusual business card. Yet each involves a familiar difficulty: getting another person to pay attention long enough to see what is actually there.

A builder, before the business cards

Koblasa grew up in Los Angeles, with a father who worked in entertainment. He took another route, writing code in high school and launching a hosting business while still a student. Around 2000, he moved to San Francisco, witnessed the dot-com collapse, and returned to Los Angeles. The timing supplied an education that no software tutorial could offer.

His working history includes engineering at Advertising.com/AOL, StoreAndServe, and Xenon Ventures. At HiroLabs, his interests extended into product and customer development; he worked on rebuilding StartupDigest for UP Global. Code was a way into business, but the questions became broader: who needs this, how will they find it, and will they pay?

The early years also taught him the cost of scattering attention across too many lines of business. He has described wishing he had spoken to more customers and developed sales and marketing sooner. There is a useful lack of romance in that admission. A finished product can still be a beautifully furnished room to which nobody has been given directions.

A weekend with a deadline

Mingly began with the problem of keeping professional relationships from slipping away. Koblasa and a friend brought the idea to Startup Weekend in Los Angeles. His LinkedIn honors place the win in November 2009. A short event helped turn a proposal into a company, and the company went on to receive backing from Bill Gross and Idealab.

The assembled talent was part of the story. The book Startup Weekend describes a Mingly team that included Google engineers, a former Hulu vice president, a Georgetown MBA, and a lawyer who also designed. What mattered to Koblasa was the circumstance: “they wouldn’t have been in a room ready to work.” A contact list is useful. A contact list facing Sunday evening is a different instrument.

He later helped organize events at CoLoft in Santa Monica. Those gatherings became part of a growing Los Angeles startup community, with founders and people from business, marketing, and engineering working together. Entrepreneur Espree Devora remembers him helping organize CoLoft’s educational and connective events. Community building was practical work: convene people, give them somewhere to meet, and let useful introductions happen.

Mingly appeared in Entrepreneur’s 2012 list of 100 Brilliant Companies. It was eventually wound down, and Koblasa’s attention moved toward business software. The distinction matters. Recognition supplied a moment in the spotlight; customers and distribution would have to supply the rest.

The little link becomes a business

CloudApp had a life before Koblasa became its CEO. Max Schoening launched the original project in 2010, and Larry Marburger helped develop its backend. Following its acquisition by Aluminum.io in 2014, Koblasa took the leadership role. His founder designation belongs to the business’s later development, rather than authorship of that first application.

By July 2016, CloudApp was announcing a $2 million seed round and revenue that had quadrupled over 18 months. The release paired financing with a concrete product expansion: visual search. A screenshot could carry information that users wanted to retrieve later, rather than disappearing into a digital drawer with the other things everyone meant to organize.

A dated snapshot / July 2016
18 months earlier
1×
At announcement
4×
Relative revenue, indexed to the earlier period. CloudApp’s July 2016 announcement reported fourfold growth; these bars do not represent dollar revenue.

In March 2017, the business reported 65,000 monthly active users and 500 paying customers. Those are different measures, and the difference is the business. An individual can enjoy a shortcut for free. A company needs a reason to put it on the budget.

The reported customer list included Zendesk, Foursquare, Quora, Twitch, and MailChimp. Team accounts offered a useful route to growth: one person shared a visual, colleagues saw it, and more people joined. CloudApp reported that a team-account signup invited an average of 8.7 other members. In that small decimal sits a very ordinary scene: somebody asking a colleague how they made that.

The less glamorous half of “show me”

A quick video can make a complicated product easier to understand. Koblasa’s 2018 explanation of CloudApp emphasized sales demonstrations, personalized communication, and giving remote customers something they could see. He also urged marketing teams to interview their intended users before deciding what an interface ought to do. The order is refreshingly economical: ask first, design afterward.

His view of customer support extended beyond answering a ticket. He argued for helping customers reach useful answers through self-service, chat, and human assistance, without making them repeat everything when they changed channels. A recording or annotated screen could become part of that exchange. An explanation should survive the handoff.

Then there was the work that rarely gets the lively product demonstration: account access and security. Koblasa publicly discussed the risks of unauthorized users and missing two-factor authentication in collaboration tools. A screen capture can contain material a company would rather keep private. Sharing quickly still requires deciding who should be allowed to see.

The product’s move from individual users to teams and enterprise customers therefore involved more than adding seats. Permissions, administration, and control became part of its usefulness. The original pleasure was speed. The organizational requirement was being able to trust it.

The founder has to find the customer

After CloudApp, Koblasa took on growth and advisory work, including a chief revenue role at Invisible Technologies. His public profiles also connect him with High Impact Ventures and Permanent Capital. Across those roles, a recurring concern is distribution: how a useful product reaches the people who might buy it.

In his teaching on product-channel fit, he asks founders to define an ideal customer, test their assumptions, and build messaging around the customer’s concerns. Advertising and publicity need to sit within an approach to marketing and sales. They cannot be expected to do all the work by themselves.

“As builders we love to build, but you also have to figure out how you actually market this.”

Tyler Koblasa, on product-channel fit

Today he is cofounder and CEO of Orcaru, whose offering combines AI with editorial work for business content. Jason Toy, another cofounder, previously held technology and product leadership roles at CloudApp. The partnership carries an existing working connection into a new venture. The medium has changed from screen captures to content; the commercial questions about attention and usefulness remain.

The continuity is especially clear in content. A writer can produce a page, just as an engineer can produce an application. Getting the right person to recognize its value requires additional work. Koblasa’s current venture sits in that gap between making something and helping it find an audience.

His CloudApp background gives that work a specific history. He has already dealt with a communication product moving from individual enthusiasm into organizational use. Orcaru brings a different set of tools and a different buying decision. The earlier experience supplies questions to ask, rather than a guarantee that the same answers will apply.

An education below the surface

There is another education running alongside the software career. At 13, Koblasa tried scuba diving on Hawaii’s Kona Coast while traveling with his elementary-school friend and that friend’s family. Later came diving certification at Catalina Island, further training, underwater photography, and eventually qualification as a PADI instructor.

A great hammerhead shark passes close to a diver in blue water
The meeting has moved underwater. A great hammerhead photograph accompanying Koblasa’s December 2025 essay, captioned Bimini, Bahamas.

His first shark dive in Jupiter, Florida, challenged the expectations he brought into the water. Later encounters with great hammerheads in Bimini became part of the path to Sharks4Kids. Here the communications problem had teeth: an animal familiar from frightening stories could look quite different when encountered directly.

Sharks4Kids now lists him on its advisory board, where he brings experience in operations, fundraising, and growing teams to ocean education. WildVoice, his wildlife-experience and ecotourism venture, gives that interest another outlet. His work with Wild Hope Collective also connects photography, storytelling, and conservation.

A piece of family advice fits this varied career. Koblasa calls his father a hero and recalls his journey from occupied Czechoslovakia, through asylum in Greece, to America. The advice was simple: “Don’t sweat the small stuff!” It is a good sentence to carry into a business with endless details, provided someone still remembers the customer.

For Koblasa, the next explanation might concern an AI content strategy or an animal beneath a boat. Both ask something of the audience. Look closely. Ask a better question. Give the subject a chance to be more interesting than the description you arrived with.

Follow the thread

More from Tyler Koblasa and the organizations in his story.