Snapbytes, an Atlassian-plugin specialist, sold to ecosystem leader Appfire: the strategy of growing in "someone else's yard"

Snapbytes’s sale wasn’t accompanied by any headline-grabbing numbers. The sale price went undisclosed, and the business itself operates in the unglamorous territory of Jira plugins. What still makes it worth recording is that you can trace the entire arc (from the starting point (“a plugin for internal use, around 2005”) to the exit (a sale to a roll-up in 2021)) in one continuous line, and that the trigger for the sale was a textbook case of ecosystem risk: a platform-level policy shift by the platform owner itself.

From an internal fix to a sale — 16 years on a timeline

Getting off the ground via “internal problem → free → paid”

Senturk’s starting point, around 2005, was a Jira plugin he wrote in his spare time to solve a nuisance at the IT company where he worked. He published it for free first, and only switched to paid once usage had grown. He recalls that “going paid is where a profitable business actually began.” He formalized the business as Snapbytes in 2016, selling on the Atlassian Marketplace with the Enhancer Plugin, which extends Jira’s workflows, and Time to SLA, an SLA (service-level agreement) management tool, as its two pillars.

By the time of the sale, the team was 8 employees plus 4 contractors (with an additional roughly dozen people at the separate Turkish subsidiary, Snapbytes Turkey), and customers had grown to 90+ countries and 4,000+ companies. The reason he could reach that kind of distribution with no sales team at all lies in the structure of the marketplace itself.

A big platform’s “yard” is a three-in-one bundle: acquisition, billing, and exit

A major platform’s marketplace bundles three things together: customer acquisition, billing, and exit. Customers arrive from marketplace search, billing is handled by the platform, and even the exit, a sale to a roll-up like Appfire, is a well-worn, established path. It’s the same pattern seen in Shopify app sales and Flusk, in the Bubble ecosystem (the finished form of the strategy of “opening a shop in someone else’s yard.” The buyer, Appfire, is a “plugin roll-up”) a company that acquires and consolidates a large number of plugins within the Atlassian ecosystem. By the time of this acquisition it already operated at a scale of 26 countries and 750+ employees.

The trade-off is dependence on the platform’s rules, fees, and spec changes. This is the flip side of the lesson from Black Magic, and it means an in-ecosystem business pairs well with an “exit early” mindset. In Snapbytes’s case, that textbook risk actually materialized.

From Turkey to the world — what location meant here

Senturk kept development based in Istanbul while obtaining a UK “Exceptional Talent” visa in 2018 and setting up headquarters in Cambridge. Most of the customer base was in Western companies, but because the Atlassian Marketplace handles acquisition, payment, and billing as a store, the developer’s own location never became a constraint on the business. Where Prowly (Poland) and AXDRAFT (Ukraine) had to build sales teams to cross borders, a marketplace-based business is global from birth, with zero sales staff.

The existence of roll-ups like Appfire further reinforces this location-independence. Because buyers evaluate plugins worldwide against the same criteria (revenue, reviews, churn) even an unknown individual can land at the negotiating table as long as the numbers hold up.

The trigger for the sale was Atlassian’s own policy shift

The three big risks of running an in-ecosystem business (the platform absorbing your feature natively, fee changes, and changes to the underlying platform’s spec) are all, without exception, outside a seller’s control. For Snapbytes, it was the third one that became real. In October 2020, Atlassian announced it would wind down support for its Server-edition product over three years and move everything to the Cloud. A plugin asset built around the Server edition would need to be rebuilt for Cloud. Senturk says he wasn’t confident in his read on Cloud technology, and that this became the direct trigger for considering a sale.

At the same time, the business was growing on the back of pandemic-driven remote work demand, and Appfire was in the middle of buying up plugins across the ecosystem. A seller’s negotiating leverage peaks during an ecosystem’s growth phase and only declines from there. It’s not “why sell while it’s still growing” — it’s “you can sell precisely because it’s still growing.” Snapbytes’s sale demonstrates, alongside an actual platform risk event, that this principle is more than theory.

Not selling everything — the structure of the deal

What Appfire acquired was the UK entity and the IP (intellectual property), plus the 8-person team in Istanbul. The Turkish entity, Snapbytes Turkey, survived as a separate company. Senturk himself joined Appfire’s project engineering division and left after two years. He still serves as a director of Snapbytes Turkey today, saying “I can’t just retire and do nothing, I need to be building something.” Rather than selling the entire business as a single block, carving out just the IP and the core team is a useful reference for the exit design of a business run across multiple locations.

What to discount when reading this

There are limits worth stating plainly. Because the sale price is undisclosed, the one number that matters most, what a 16-year business actually sold for, can’t be verified. Appfire’s acquisition was one of many deals, and individual terms should be read as a function of negotiating leverage. And while Atlassian’s Cloud migration turned out to be good timing for a sale, flip it around and it was also a decision to give up the option of pushing through the Cloud transition and continuing to grow. Whether “policy shift equals immediate sale” was always the right call isn’t something this record can settle. What’s certain is only that Senturk chose to hand the business to a buyer with conviction about Cloud, rather than keep running it himself without that conviction.

Conditions for replication

Three pieces of this travel well. The startup sequence of releasing a small tool that solves your own day-job problem for free, then charging once usage takes hold. The structure of riding a marketplace’s acquisition-and-billing infrastructure to reach customers worldwide with zero sales effort and no constraint from your own location. And an exit instinct that reads a platform’s rule changes as a signal for “time to sell.” This same pattern extends beyond Atlassian to any platform with demand for smaller, nimbler peripheral features than the core product offers, Shopify, browser extensions, and so on.

Even so, ecosystems where a roll-up buyer like Appfire has matured are limited in number. How developed the exit path is varies enormously by platform, and in an ecosystem with no such buyer, the only option besides “keep running the business while carrying regulatory risk” is thin at best. Checking, before you enter, whether any company is actually out there buying plugins in that particular yard, is the first step in exit design.

Related cases

• Order Tagger — the same pattern of an exit via a Shopify app
• Flusk — a variant where the platform itself was the buyer