Product knowledge
Research, expert input, architecture and source material
I learn complex products, find the angles worth communicating and turn technical knowledge into clear, authoritative content — then run the editorial system behind it.
QuStream metrics from a sustained period of technical communication, including extended low-news periods.
Strong technology was already there. The missing layer was a repeatable way to turn technical depth into clear public communication.
What began with individual social posts evolved into independent ownership of most of QuStream’s day-to-day X communication: product research, editorial planning, technical explainers, long-form threads, publishing and audience interaction.
I work independently from product context and expert input, using technical review where claims need verification while keeping demands on the technical team low.
Technical context moves through a repeatable editorial system.
Research, expert input, architecture and source material
Decide what matters, for whom and why
Write, structure and review sensitive claims
Maintain a deliberate, reliable cadence
Extend one strong idea across useful formats

Explained how PQC-based authentication, continuous key evolution and QuStream’s quantum-safe key distribution fit into one architecture.
View original
Turned QKD’s last-mile limitation into a clear visual explanation of QuStream’s quantum-safe key distribution approach.
View original
Connected quantum-secure communications to aerospace and server infrastructure in a focused technical narrative.
View originalLong-form work is only one layer. The ongoing editorial system turns architecture, market context, product developments and technical knowledge into useful communication between major announcements.
Editorial angle · Strategic positioning · Copy · Visual directionView work Technical explanationWhen the Link DegradesHow much useful information can still get through safely?
Technical research · Explanation · Copy · Visual directionView work Product positioningPKI vs Provisioned TrustPKI solves stranger trust. What changes when the operator already controls the endpoints?
Architecture positioning · Technical simplification · Copy · Visual directionView work Migration strategyThe Last-Mile ProblemPQC upgrades the algorithm for a quantum world. The infrastructure still has to be migrated.
Technical positioning · Migration narrative · Copy · Visual directionView work Company communicationsOperational ReadinessQuStream at NMIOTC's annual NATO conference in Greece.
Event communication · Narrative framing · Editorial copyView work Market narrativeOne Architecture, Multiple MarketsThe surface area is bigger than one market.
Market positioning · Use-case storytelling · Copy · Visual directionView work Research-led articles, explainers, threads and case studies that make difficult products easier to understand without flattening the technical truth.
Deciding what deserves communicating, planning the cadence, publishing consistently and keeping the editorial system moving between launches.
Turning technical calls, founder thinking and expert input into clear narratives, product communication and thought leadership.
Working with technical review where claims matter, then extending strong ideas across formats through structured workflows.
I start by learning the product and extracting what matters from the people who understand it and the source material around it. From there, I can research independently, identify angles, create and verify content, publish consistently and improve the system with minimal demands on the technical team.
Market, product and context
Build real technical fluency
Decide what matters, to whom and why
Write, structure and direct
Review technical or high-risk claims
Maintain a reliable cadence
Use performance and feedback to improve
Next research cycle
Before technical communications, I learned distribution by building audiences, educational content and community from zero.
Pi Network became my first serious internet project. Over four years, I learned audience building, educational writing, localisation and online distribution by doing the work every day.
I built minepi.hu, became its primary blog writer, translated technical material into Hungarian, ran livestreams and created multi-year content across X and Facebook.

I researched and wrote an independent long-form feature for a community-led Web3 project. The work led to an unsolicited offer for future paid writing.
View article
I learned this work from the outside in: audience building and distribution first, then writing, then research, and eventually the technical products where shallow communication breaks down.
Today, I work at the intersection of technical research, editorial strategy and public communication. I’m most useful when a company has a strong technical product, valuable expertise inside the team and no clear owner turning that knowledge into accurate, consistent public communication.
CYBERSECURITY · PRIVACY · CRYPTOGRAPHY / PQC · AI INFRASTRUCTURE · DEVELOPER / DATA INFRASTRUCTURE