Scaling a foodtech DTC brand from MVP to profitability
What started as a three-person bet on fresh juice became the category leader in European direct-to-consumer wellness.
The challenge
Kencko's founders believed cold-pressed juice could reach customers on subscription the way coffee-of-the-month clubs had, but without the logistics overhead. The category didn't exist. The first hurdle wasn't supply chain or product — it was a platform that could handle the subscription economics: recurring payments, personalized ordering, customer retention, inventory forecasting across a growing number of SKUs, and the operational workflows to actually ship fresh juice weekly.
Building in-house would have meant hiring a small engineering team. Time to market mattered more than perfect infrastructure. They came to Twistag with a three-person founding team and a clear ask: build the platform fast enough that we can prove product-market fit before capital runs out.
What we learned
| DTC punishes rigid platforms | When the platform can't adapt as customer needs shift, you pay by rebuilding instead of pivoting. |
| Operations need their own surface | If operational decisions need engineering support every time, the team running the business can't run it. |
| First model is usually wrong | Subscription DTC pivots — the architecture has to survive multiple business model iterations, not just the launch one. |
The solution
Twistag built Kencko's DTC platform on Node.js and React, with AWS for infrastructure and Stripe for payments. The architecture prioritized two things: first, a subscription engine that could adapt as the product changed — customer cohorts, flavor rotations, gifting, corporate accounts. Second, an operational dashboard that the team could use to manage inventory, orders, and customer retention without calling the engineering team for every decision.
The platform launched with the core subscription flow: customers select flavors, Stripe manages the recurring charge, and AWS handles fulfillment orchestration to the regional fulfillment partners. We built the admin layer so Kencko's operations team could manage customer cohorts, pause/resume subscriptions, and run retention campaigns without Twistag in the loop. That separation of concerns — product-facing subscription platform and internal operations layer — is what allowed the team to scale from three people to fifty without the platform becoming a bottleneck.
Over six years, the platform evolved through three major phases: MVP (subscription + recurring billing), scale (cohort management, gifting, corporate accounts, B2B logistics), and profitability (margins optimization through delivery route planning and inventory forecasting). We shipped each phase as the business demanded, not as the original roadmap predicted.
What this shaped
| Build for adaptation | Design platforms to survive feature changes without rewrites — assume needs will shift. |
| Customer surface separate from ops | The interface customers see should be independent from the dashboard the team uses to manage supply and orders. |
| Infrastructure outlives product fit | The platform that finds product-market fit isn't the one you launched — flexibility lets you iterate without rebuilds. |
The impact
Kencko shipped its first order four months after Twistag started, proved subscription retention in the cold-pressed juice category, and raised Series A within eighteen months. By the time Series B closed at an $85M valuation, the platform had delivered twelve million smoothies across six countries — with no rebuild.
The platform survives because it was built to adapt, not to solve the problem once. When fulfillment partners changed, the orchestration layer scaled. When corporate gifting became a revenue line, the subscription engine handled it. When unit economics demanded route optimization, the platform supported the analytics layer without needing a rewrite.
What this proved
| Adaptation outlasts perfection | A system that survived six years of product changes outperforms competitors who rebuilt at every pivot. |
| Funding rounds fund growth, not debt | When the platform survives product evolution, capital goes to expansion rather than paying down architectural debt. |
| Volume amplifies operational design | As the business scales, the same team can orchestrate more complexity because the system routes work intelligently. |
Technologies used
- Node.js
- React
- AWS
- Stripe
