Book a call
Case study MOBILE APP

Five more hires, or one outside team. The founder did the math.

Moseiki is a Turkish Web3 social media app: very much like Instagram, but with NFT buying and selling and wallet operations built into the product. ETREXIO joined their in-house team around August 2024 and provided external development on the mobile app and website until early 2025, replacing at least five hires by the client's own math.

5+ hires
What bringing our service in-house would have cost, by the client's math
Web3 social
Instagram-class app with NFT trading and wallets built in
2 fronts
Mobile app and website, developed in parallel
2024-2025
On the team from August 2024 to early 2025

Project facts

Client
Moseiki
Sector
Web3 social media
Country
Türkiye
Timeline
August 2024 to early 2025
Scope
External development on the mobile app and website
Engagement
Team augmentation alongside the in-house team
Status
Engagement completed early 2025; the platform was later temporarily suspended for financial reasons

01 Comprehensive scope, in-house pace

A team that existed, and a roadmap that did not care

Moseiki was not a small idea. A Web3 social media app, very much like Instagram in its social core, but with NFT buying and selling and wallet operations built directly into the product: feed plus marketplace plus financial plumbing, all in one comprehensive app, with a website alongside it.

Erkan Gül's problem was not the absence of a team. The in-house team existed; it was simply slow for what the product demanded, and a roadmap that spans social features and on-chain operations does not wait politely for a team to catch up. The classic answer is a hiring round: recruit, interview, onboard, and hope the new people mesh, while the roadmap ages another quarter. Moseiki chose the other answer and brought ETREXIO onto the team around August 2024 as external development capacity.

02 External development that plugs into an existing team

Extra muscle, not a replacement

The engagement was team augmentation in its honest form. We did not take the product over and we did not work around the in-house team; we supplied development capacity on top of it, on the two fronts where Moseiki needed throughput: the mobile app and the website.

Working as an extension of someone else's organization is its own discipline. The work has to land inside their codebase and their product direction, at a pace that pulls the whole effort forward. That is the difference between augmentation and outsourcing: the client keeps ownership and direction, and the outside team's job is to make the internal roadmap move visibly faster than it did before.

It also spares the founder the quietest cost of hiring, which is time. A recruitment round for five developers is months of interviews and onboarding before the first useful commit. External capacity that arrives already senior skips that entire runway, which for a product racing a market window is often the whole argument.

  • External development on the mobile app
  • External development on the website
  • Capacity added alongside the existing in-house team
  • Client retains product ownership and direction throughout

03 Social feed and on-chain operations in one product

Instagram-class, with a wallet inside

What made Moseiki demanding was the combination. An Instagram-like social app is already a serious build: feeds, profiles, media, the interaction surface users compare to the best-polished apps on their phone. Moseiki layered Web3 on top of that, with NFT buying and selling and wallet operations living inside the same product rather than linking out to external tools.

That combination is exactly where a slow team gets hurt most, because the social side and the chain side each demand different expertise and neither can be neglected. Supplying external development across that full, comprehensive scope, on both the app and the web front, is what made the arithmetic of the engagement so lopsided in the client's favor.

04 The client's arithmetic, in his own words

The outcome

The clearest summary of this engagement came from the client. His math: bringing the service ETREXIO provided in-house would have required hiring at least five more people. Five recruitments, five salaries, five onboardings, for capacity his roadmap needed immediately rather than after a hiring season.

He put the rest of it more personally. "I wish I had met you when I first started," Erkan told us. "I spent a fortune and still did not have anything solid to show. The good parts we have were built during the period we worked together." We carry that quote with some humility: it says as much about how expensive the wrong build can be as it does about us.

We joined Moseiki's team around August 2024 and left early 2025 with the engagement complete, the in-house team alongside us throughout. Later in 2025 the platform was temporarily suspended for financial reasons, which we state plainly. For founders in the same position, the shape of the lesson matters more than the specifics: a slow in-house team is not a verdict on your product, and the choice is not replace or endure. External capacity that plugs into your team, respects your ownership, and moves your own roadmap faster can beat a hiring round on both speed and cost.

Questions

About this project

Our in-house team is too slow. Can you add capacity without replacing them?

That is exactly what we did for Moseiki. Their in-house team stayed, and ETREXIO supplied external development on the mobile app and website on top of it. The client kept ownership and direction; our job was to make his own roadmap move faster. His math: the alternative was at least five more hires.

How does team augmentation compare to just hiring more developers?

Moseiki's founder ran that comparison himself and concluded that replacing our service in-house would have taken at least five additional people. Hiring means recruiting, salaries and onboarding before the first line of useful code; augmentation means experienced capacity landing inside your codebase immediately, and it can end when the need ends.

Can an external team really work inside our codebase and our product direction?

It has to, or it is not augmentation. On Moseiki the work landed inside the client's product direction across two fronts, mobile and web, alongside their own developers. The discipline is fitting the client's organization rather than making the client fit ours.

Can you handle Web3 features like NFT trading and wallet operations?

Yes. Moseiki was an Instagram-class social app with NFT buying and selling and wallet operations built into the product itself, not linked out. The combination of a polished social surface and on-chain plumbing is demanding, and it is precisely the kind of scope where external expert capacity pays for itself.

Do we lose control of our product with external development?

No. Augmentation done honestly leaves ownership where it belongs. Moseiki's team and founder kept the product throughout; we added throughput, not a dependency. The measure of success was their roadmap moving faster, which is also the measure we suggest you hold any external team to.

Next case study

Three years stuck in-house. Live in two months.