Leadership built for
telecom complexity.
ZoikoNex is led with a clear operating mandate: build a governed, scalable, AI-powered telecom OSS/BSS platform that helps MVNOs, MNOs, digital connectivity brands, and telecom groups launch, monetize, manage, and grow with confidence.
Built for buyers who need executive accountability across platform architecture, monetization, compliance, security, delivery, and long-term roadmap governance.
Executive Direction
operating mandate · capital discipline
Leadership mapped to operating
responsibility — not vanity titles.
In enterprise telecom, buyers don't just buy features. They buy confidence that someone is accountable for every part of the platform. Here is who owns what, and the procurement question each answers.
Executive Direction
Corporate strategy, platform doctrine, market positioning, capital discipline, and partnership posture.
Product & Platform
Domain architecture, roadmap, product governance, release discipline, usability, and customer value.
Technology & Architecture
Cloud architecture, API-first design, event architecture, resilience, data model, and scalability.
Security & Governance
Security posture, access control, audit readiness, AI governance, risk controls, and evidence discipline.
Commercial & Partnerships
MVNO/MNO partnerships, pricing strategy, channel development, procurement support, and deal quality.
Implementation & Customer Success
Onboarding, migration, support escalation, customer education, adoption, and retention.
Run by operators
accountable for the
outcome.
ZoikoNex is designed to run operators, not merely support them with another application layer. Leadership is structured around the four ideas that separate critical monetization infrastructure from conventional BSS.
At runtime
Markets are activated from runtime
packs, not deployed.
Not logs
Financial and compliance events are
immutable and provable.
With control
Intelligence bounded by policy,
evidence, and approval.
Not software
Built to run serious operators at scale.
Senior leadership, with relevance over
biography.
Filter by responsibility area. Concise at the surface; deeper context one tap away. Each profile
connects to what it means for an MVNO, MNO, enterprise, or partner buyer.
Adaeze Okonkwo
Chief Executive Officer
Owns corporate strategy, platform doctrine, and capital discipline, keeping direction accountable to operator outcomes.
Marcus Boateng
Chief Operating Officer
Owns operating cadence, delivery governance, and cross-functional execution across the platform organization.
Mathias Vogel
Chief Technology Officer
Owns cloud architecture, event-driven design, resilience, and scalability across the eighteen platform domains.
Lena Sorensen
VP, Platform Architecture
Owns API-first design, the data model, and integration patterns connecting ZoikoNex to carrier and partner ecosystems.
Priya Raghunathan
Chief Product Officer
Owns domain architecture, roadmap, and release discipline so capabilities ship governed, usable, and commercially aligned.
Daniel Asare
Chief Information Security Officer
Owns security posture, access control, AI governance, and evidence discipline for enterprise review.
Sofia Marchetti
Chief Commercial Officer
Owns MVNO/MNO partnerships, pricing strategy, channel development, and procurement support.
Yara Haddad
Chief Customer Officer
Owns onboarding, adoption, support escalation, and renewal so customers reach value and stay there.
Profiles shown are representative of the approved CMS structure, with portrait placeholders ready to receive approved photography. Only verified names, titles, and credentials are published — no degrees, awards, prior employers, or certifications appear unless legally approved.
The team functions behind the leaders.
For enterprise BSS buyers, implementation, governance, security, and customer success determine
long-term value. These functions have named ownership.
Platform Architecture
Senior product architects, API leads, and data-
architecture owners responsible for domain design
and implementation depth.
Security & Compliance
Security owner, compliance lead,
privacy/governance contact, and evidence lead
supporting enterprise due diligence.
Implementation & Delivery
Program delivery, onboarding, partner integration,
migration, and QA/release ownership across live
environments.
Customer Success
Support escalation, account success, adoption
education, and renewal support after go-live.
Commercial & Partnerships
MVNA/MNO partner owners, ecosystem partners,
and channel leads who open market access and
deal maturity.
How leadership shows up across the customer
lifecycle.
Leadership involvement does not end at signing. Each moment below has a leadership-backed
support model and a retention impact.
“We move fast where speed creates customer
advantage — and we slow down where security,
compliance, billing accuracy, or customer trust
require control.”
The leadership philosophy behind the
platform.
Governed speed
We move fast where speed creates customer advantage, and we slow down where security, compliance, billing accuracy, or customer trust require control.
Evidence over assertion
Important platform events, decisions, approvals, releases, and policy actions should be traceable through evidence-aware systems.
Modularity over sprawl
Each ZoikoNex domain must have clear ownership, clean interfaces, and measurable operational responsibility.
AI under control
AI should accelerate telecom operations, but material decisions must remain bounded by permissions, policy, evidence, and human oversight where required.
Commercial discipline
The platform must support real telecom monetization: charging, billing, taxation, payments, reconciliation, partner settlement, and revenue protection.
Customer continuity
The relationship must not end at implementation. Documentation, support, roadmap governance, and adoption design must protect long-term value.
Credibility protected by claim discipline.
We publish what is verified, and we are explicit about what we will not claim without proof. That
restraint is itself a trust signal for procurement and security reviewers.
Leadership credentials
Verified degrees, roles, licenses, board positions, and company associations.
Unverified academic claims, inflated titles, or former-employer references.
Team size
Current approved numbers — or no specific count at all.
“Largest”, “global team”, or “hundreds of engineers” without evidence.
Security maturity
Security-by-design, access controls, review pathways, and Trust Pack availability.
SOC 2, ISO 27001, PCI, GSMA, or TM Forum certification claims unless formally achieved.
Customer proof
Approved customers, anonymized scenarios, or “representative use case” labels.
Named customers, logos, revenue figures, or outcomes without written approval.
AI leadership
Governance, control levels, human review, and auditability.
Claims that AI is fully autonomous, error-free, compliant, or regulator-approved.