HOME/ABOUT

Not a timeline. A strategy map of how I learned to build commercial systems.

The useful question is not where I worked. It is what each chapter proves: founder judgment, software delivery, e-commerce operations, CRM automation, acquisition systems, reporting and SaaS growth.

Founder to operatorBuilder + growthSoftware + systems arc
Arokofounder · 2011-2019PlunetBerlin SaaS · 2022-2025NinoxPLG SaaS · 2025-now
Download résumé (PDF)Start a conversation
the operator's arc
signal · l1

The offer, buyer journey and system map are set before anything gets built.

The career is this system, learned one layer at a time — from building to operating.

How to read this page

The career makes sense when you follow the operating pattern.

The pattern is not “marketing career.” It is: build the system, connect the handoffs, launch the demand, prove the numbers, then operate the improvement loop.

01

Build

Software, websites, e-commerce, CRM and internal tools.

02

Connect

CRM, ERP, lifecycle, operations, ownership and source handoffs.

03

Launch

Paid, SEO, content, landing pages, product or commerce flows.

04

Operate

Dashboards, BI, attribution, experiments and monthly decisions.

Journey strategy

Four acts. One through-line.

Choose an act to see what changed, what it proves, and why it matters to a business owner, operator or C-level buyer.

Act I · 2011–2019

Builder and founder

The foundation was not marketing. It was building and operating software teams, contracts, client delivery, web systems and a proprietary CRM/email platform.

Buyer meaning

For a buyer, this means I understand the pressure of owning the system, not only advising from the outside.

Aroko Tech PioneersCustom CRM + email systemWeb/mobile/desktop teamsClient delivery and support
Operating proof anchors

The journey is not one vertical. It crosses software, commerce, standards, CRM, tracking and BI.

These anchors are deliberately concrete: names, timeframes and operating context. They help the reader understand why the positioning is broader than ads or dashboards.

Commerce + ERP

Tavazo Europe

full system launch

Software/e-commerce architecture, design and development, launch advertising, ERP installation and warehouse process automation.

Inspect proof →Standards + data

GS1

2018-2019

National standards context: barcode-related platforms, catalog discipline, web infrastructure, campaign planning and data quality.

Inspect proof →Founder + software

Aroko Tech Pioneers

2011-2019

Software delivery teams, contracts, support, custom CRM and email-marketing product thinking from the operator side.

Inspect proof →CRM + reporting

Plunet

2022-2025

HubSpot, lifecycle automation, data pipelines, GA4/GTM, Looker Studio and reporting governance in a Berlin B2B software context.

Inspect proof →PLG growth system

Ninox Software

2025-now

Paid growth architecture, tracking foundations, product signals, CRM quality and BI reporting connected past signup.

Inspect proof →
What the journey produced

The through-line is visible in the artifacts: software thinking, GTM structure, tracking, reporting and operating loops.

A resume lists roles. This layer shows the kind of system material those roles created, with sensitive details removed: command centers, launch files, wireframes and optimization tools.

Scrubbed system pattern

Campaign logic, ownership and source rules inside one editable operating file.

Based on a dense GTM working document: audience tracks, landing-page logic, lifecycle steps, tracking rules and owner notes are kept together so launch execution does not fragment.

Audience tracksSource rulesLifecycle ownersLaunch governance
Open live reference
Company proof chapters

Each chapter answers a different buyer question.

Click a chapter. The inspector shows the strategic meaning, then links to the full system page where the details live.

Selected chapter

Ninox Software

Director of Performance Marketing · Aug 2025 — Present

This is the full Revenue OS in production: campaign architecture across ICPs and funnel stages, a rebuilt tracking foundation, product signals wired into the CRM, and a measurement model that connects ad spend to revenue-quality outcomes — not just clicks.

LinkedIn Ads · Google Search & Demand Gen · Reddit Ads · Capterra · G2 · GTM
Open full system page
Buyer translation

What the journey means when a company is deciding whether to trust the work.

The page should not ask a reader to admire a career. It should help them decide whether the same operating pattern fits their system.

If you want breadth

Open the work map

See the bodies of work grouped by operating problem: launch, tracking, dashboards, standards, commerce and founder delivery.

Open work If numbers are broken

Inspect tracking logic

Use the attribution page to understand where measurement fails between ads, product, CRM and revenue.

Open tracking If leadership needs truth

Inspect dashboard logic

See how reporting becomes useful only after metric definitions, ownership and source joins are designed.

Open dashboards If you are still learning

Read field notes

Start with the writing before choosing a service path. Some buyers need education before a project.

Open blog
Systems I have worked across

A small cross-section of the stack behind the journey, shown as experience rather than endorsement.

Education
  • MBA, Digital Marketing — Bahar Educational Institute (2017)
  • BSc, Computer Software Engineering — Shahid Rajaee University (2010–2014)
Languages
  • German & Persian — native / bilingual
  • English & Turkish — full professional
  • Arabic — limited working
Download résumé (PDF) See the case studies

A résumé asks to be believed. This page shows the operating pattern behind it.

Start a project conversation
Free Growth Audit → x