Product knowledge
Research, expert input, architecture and source material
I’m building practical AI and automation for business owners who want less admin and fewer missed enquiries.
Through ARKOZ, I’m starting with voice systems. Behind that: years of research, technical communication and community building.
Curiosity → useful workA call you can’t take. Details to write up. Another round of chasing. Small tasks take a large bite out of the day.
With ARKOZ, I’m working on systems that reduce that friction: capture the enquiry, organise the information and make the next step easier. Less manual work, fewer interruptions and more time for the job itself.
Our current focus is voice and enquiry handling for UK plumbing and heating businesses. It’s a concrete starting point for a broader direction: useful automation across everyday business workflows.
Explore ARKOZFor current pricing and fit, talk to ARKOZ about your workflow.
The caller needs help. You need to keep working.
Name, contact details and the reason for the call.
The aim: less information lost between the call and the callback.
Illustrative workflow. Hear the fictional Northline Heating call on the ARKOZ site.
Listen to the voice demoUnderstand the complicated thing.
Make it useful to others.
What started with people and content now extends to systems and automation.
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.
Strategic framingQuantum DebtCompanies already carry technical debt. Most are now accumulating quantum debt.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 articleI 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.
That work taught me to find the gap between what technology can do and what someone can actually use. I still own technical communication at QuStream. With ARKOZ, I’m applying that same curiosity to business workflows: where time disappears, where an enquiry gets lost, and where a better system could help.
Interested in the person behind the projects? Find me on YouTube, X and LinkedIn. This site brings the work together; those are the places to follow along.
For AI, voice and business automation, start with ARKOZ. For technical communication, editorial work or a collaboration, contact me directly. My QuStream work above shows the depth of the research and communication side.
Voice and enquiry handling is our starting point, currently focused on UK plumbing and heating businesses. The wider goal is to reduce repetitive admin and connect the steps in everyday work. If you have another workflow in mind, bring a concrete example and we can discuss what might help.
For current ARKOZ pricing, head to the business site. For editorial work or another collaboration, tell me what you need and we can discuss scope and cost. There isn’t one fixed price for every project.
Some work is better handled by a person. The starting point is to understand the task, agree what must stay human and decide how to test whether a change helps. If it doesn’t, revisit the approach before expanding it.
The QuStream examples above link to published pieces. The Pi chapter covers my earlier community work, and the Tilly chapter includes original feedback on my writing. You can also hear an illustrative voice demo on ARKOZ; its Northline Heating business is fictional.