Sorin Alupoaie built Swifteq around a narrow, unglamorous wedge: support teams already using Zendesk. Instead of inventing a broad customer-service platform, he focused on repeated workflow friction: duplicate tickets, help-center maintenance, translations, search, exports, and other jobs that were painful enough for support teams to buy specific tools. The first apps were intentionally small. They solved one job at a time, then improved from real customer feedback.

Small apps, real buyer intent

Swifteq's advantage was distribution with intent. Zendesk users visit the marketplace and related communities because they already have a support-workflow problem. Sorin leaned into that by shipping focused tools, charging from the start, and using customer feedback to decide which products deserved more work. That portfolio approach let Swifteq capture several small operational pains inside the same ecosystem instead of depending on one big feature bet.

From builder mode to business mode

By June 2024, Swifteq had passed €20K MRR and 300+ customers, growing more than 120% year over year. The numbers were not magic from one viral launch. They came from compounding small products, documentation, customer support, expert content for support teams, marketplace demand, and finally taking pricing and marketing more seriously.

The lesson for founders

Swifteq is a reminder that a durable SaaS does not have to begin with a new category. It can begin with a platform ecosystem, a repeated operational annoyance, and a founder willing to keep the first version almost embarrassingly small. The risk is platform dependence, but the upside is clarity: a narrow audience, obvious jobs to be done, and buyers who already know the workflow hurts.