Operating model
Seller lifecycle, ownership and operational progression from onboarding to sustained participation.
Work
Selected work across business, operations and technology, from designing operating models and performance systems to building a business from the ground up.
The focus is not only on what was delivered, but on the systems behind the outcome: how they were designed, operated, measured and improved.
Designing the operating and decision system behind Seller Success for a new marketplace model.
Fırsat is a marketplace venture built within ikas and established through a separate company.
Fırsat required more than a set of seller-facing processes. The challenge was to connect onboarding, operational readiness, activation, campaign participation and performance within a system that could support day-to-day execution and better decisions.
My contribution focused on designing key parts of the operating model and structuring seller-side information for management decision support.
I led coordination across the product, design, commercial, finance, customer success and legal functions involved in shaping the seller and customer experience.
Seller lifecycle, ownership and operational progression from onboarding to sustained participation.
High-level performance signals structured to support operational decisions and appropriate intervention.
Seller-side operational information organized to support decisions beyond the day-to-day operation.
Seller-side requirements translated into coordinated action across the functions shaping the marketplace experience.
Leadership teams
Operational and commercial signals translated into structured management insight.
Product · Design · Business Development · FP&A · Customer Success · Legal
Connecting seller-side operational needs with the teams responsible for product, commercial, financial and contractual decisions.
I helped create a structured operating model connecting seller operations, performance signals, management decisions and cross-functional action.
The work established a clearer foundation for ownership, decision support and continuous improvement as the marketplace evolves.
Read the case →Turning sales quality into a measurable system for performance diagnosis and continuous improvement.
Sales results show what happened. They do not always explain why it happened. The challenge was to connect real sales behavior with quality assessment, performance information and targeted improvement actions.
I designed and owned the system across call review, quality evaluation, role-play, coaching, training, sales meetings and performance measurement, creating a repeatable cycle for identifying gaps, acting on them and evaluating what changed.
Standardized review of real sales interactions and observable selling behavior.
Commercial results, activity and quality signals combined to create a clearer view of performance.
Specific findings translated into feedback, practice and recurring evaluation.
Training, role-play and supporting materials built around observed performance needs.
Where is performance actually breaking down?
Results plus activity plus quality plus consistency equals performance view
Performance was treated as a combination of results, activity, quality and consistency rather than a single output metric.
A recurring individual problem can become a team-level signal.
When the same performance gap appeared repeatedly, the question shifted from individual coaching to whether training, process or enablement needed to change.
The system created a repeatable structure for connecting observed sales behavior with diagnosis, targeted development actions and measurable improvement.
It created clearer visibility into individual and team development needs while connecting quality findings with coaching, training and performance conversations.
The goal was not to score salespeople. It was to understand performance well enough to improve it.
Read the case →Building the commercial system behind a direct-to-consumer home-textile venture while experiencing the realities of entrepreneurship first-hand.
Dolce.ev started without an inherited operating model, customer base or commercial infrastructure. Product selection, pricing, logistics, payments, digital infrastructure, customer acquisition and the economics connecting them had to be built from the ground up.
As co-founder, I work across strategy, commerce, operations and growth, testing assumptions against market behavior and adapting the system as new evidence appears.
Understanding the real cost of selling by connecting product cost, tax, payment fees, shipping, acquisition and margin conceptually.
Designing channel-aware pricing and basket economics rather than treating price as a standalone number.
Building the storefront, catalog, payment, marketplace and operational foundations required to take products to market.
Testing products, offers and acquisition assumptions against market behavior and adjusting from evidence.
Product cost plus tax plus payment plus shipping plus acquisition plus channel cost equals real cost to sell
Selling price minus real cost to sell equals contribution
Shipping costs pushed the commercial model beyond individual product margin. Basket structure, multi-product orders and the free-shipping threshold became part of the pricing problem rather than separate logistics decisions.
Price changes with the economics of the channel.
Payment
Shipping
Acquisition
Commission
Shipping
Campaign pressure
Marketplace economics
Preparing for reactivation.
Dolce.ev is an established commerce venture currently dormant, with work underway to reactivate and continue building it.
We turned an initial product idea into a commerce system that could be tested against real market behavior.
The work connected product, pricing, logistics, payments, customer acquisition and unit-economics thinking while creating a practical environment for learning from commercial decisions.
Dolce.ev is both a venture and a learning environment.
Read the case →The contexts change, but the work repeatedly comes back to a small set of problems: how systems are designed, how performance is understood, and how better decisions become better execution.
How should the operation work?
Designing the processes, ownership, decision points and feedback mechanisms that allow an operation to function with greater clarity and consistency.
How do we know what is working?
Building measurement structures that connect activity, behavior and outcomes so performance can be understood rather than simply reported.
Does the economic model work?
Connecting pricing, cost, margin, channel economics and commercial decisions into a structure that can survive real operating conditions.
What should be built or changed?
Translating operational, seller and customer needs into clearer workflows, product requirements and practical system improvements.
How do different functions move together?
Creating enough shared structure for operational, commercial, product, financial and legal dependencies to move toward the same outcome.
What happens when there is no existing system?
Turning an idea into something operational by making decisions, building infrastructure, taking risk, testing assumptions and adapting through evidence.
Next
Understand the problem.Design the system.Put it into real operation.Measure what happens.Improve from there.