01 A marketplace that worked, but only barely
Three years of trying
Parkurda is Tezmaksan's venture to digitize the machining industry: by its own definition, Türkiye's first digital platform where the CNC sector can meet all of its needs. Tezmaksan is one of the giants of that sector, so the ambition was real and the budget was real. The problem was execution.
When ETREXIO arrived, the platform had already existed for three years. It technically worked. Orders trickled in. But the site was painfully slow, and the codebase was tangled enough that the system could only run at its bare minimum. The company had no realistic path to growth on top of it. The smallest change requests took the in-house team months, partly because of the code, and partly because the people managing the team had no real product experience. Every decision meant the CEO and managers thinking out loud through endless meetings, then explaining conclusions to developers who needed every business rule spelled out. Three years in, the marketplace was alive but stuck, and everyone involved knew it.
02 We told them on day one: nothing from the old codebase survives
Starting from zero, on purpose
Our first statement was blunt: we would reuse nothing from the old codebase. We studied the existing platform only to understand the flows the team had imagined, took our notes, and rebuilt everything from scratch, design included.
Scope was not cut to hit a deadline. The only thing removed was a contract-manufacturing module the client no longer wanted in the new platform, and by their own account, keeping it would not have changed the timeline. What made the speed possible was product experience. A marketplace needs invoicing, withholding tax handling, cancellation and return flows, and a typical developer needs all of that explained line by line. We proposed those flows before the client asked, because we have shipped marketplaces before and we run companies ourselves, so the procedural and accounting side of commerce is not foreign territory. Meetings that used to sprawl across an org chart became short working sessions that we drove with concrete proposals. The client's estimate is that the whole project ran on roughly ten times less talking.
The other half of the answer is our own tooling. DigiSapiens let two people scale like a full team; without it, even we would not finish a marketplace in under eight to ten months. And StackWatch sat inside the development process from day one, surfacing bugs while we built instead of after launch. By the time the platform went live it was already hardened. There was no month of post-launch firefighting, because the firefighting had happened continuously, quietly, during the build.
03 A complete industrial marketplace, not a slimmed-down one
What shipped in two months
In roughly two months, Parkurda got a full rebuild of a working industrial marketplace, and nothing on this list was descoped. After launch, ETREXIO also took over the entire cloud operation.
- Full marketplace rebuild: storefront, seller stores, catalog, ordering, and checkout
- New design system built from scratch alongside the platform
- Migration of three years of production data from the old system
- Payment integration with automated error monitoring on every transaction
- Cloud infrastructure taken over and managed end to end by ETREXIO
- StackWatch monitoring and DigiSapiens AI engineers wired in from day one
04 Fixed before the customer could try again
The checkout save
Shortly after launch, a customer's payment failed. A bug in the payment provider integration threw an error and bounced them back a step. In the normal version of this story, the customer retries, fails again, retries, fails, and leaves for good, because no amount of retrying fixes an integration bug.
Here is what actually happened. Before the customer even attempted a second payment, StackWatch had detected the error, identified the probable cause, and handed it to DigiSapiens. The fix was written, reviewed, and deployed within moments. The customer's second attempt went through cleanly. They never learned that the failure came from the system at all.
One saved sale is a small thing. A checkout that repairs itself faster than a customer can retry is not.
05 A system-down alert, an AI diagnosis, and an approval from a phone
The night the data fought back
The old platform's three years of data had to come along, and that data was not clean. One night, a duplication conflict deep in the migrated records stopped the system from serving at all.
StackWatch immediately sent the system-down alert to two places: the founders' phones and the manager agent inside DigiSapiens. The agent traced the root cause, prepared a fix, and, because this was live production data, requested human approval instead of acting alone. The founders read the proposal in the notification, judged it sound, and approved it from right there. The change deployed to production and the system came back.
A marketplace that would have stayed dark until morning was fixed in the fastest way the situation allowed, and not a single customer was lost to the outage.
06 Two months to live, and no reason left to build in-house
The outcome
The Parkurda and Tezmaksan teams did not believe a platform like this could ship in two to three months, and they certainly did not believe it would ship smoothly. It did both. No critical problem surfaced after launch, and from day one the new platform matched the old one's revenue and began passing it.
In the first three weeks, the marketplace processed more than 140 orders, welcomed more than 90 new customers, and onboarded more than 14 new stores. The commercial side improved too. Parkurda had been paying its previous infrastructure vendor close to $4,000 a month for cloud and management. That cost disappeared entirely when ETREXIO took over operations, and through our perks pool we secured $10,000 in AWS credits on top of it.
Parkurda reached us the way most of our clients do: a long-time client who was advising Tezmaksan recommended us. Asked about the future, the team's position is simple. As long as the reaction speed and quality stay at this level, building an in-house team makes no sense to them. Three years of trying inside. Two months to live with ETREXIO. The math speaks for itself.