People · CiteSurge

Mark Laursen Co-Founder & Product Lead

Mark began working with computers on a TI-99 at age five, followed by the Commodore 64 and Amiga. He became a professional gaming world champion at 21, then spent more than 25 years building and shipping software, game technology, digital products, and applied R&D. As CiteSurge's Co-Founder & Product Lead, he writes research on generative engine optimization, AI visibility measurement, citability, and enterprise governance.

Meet the CiteSurge team

Profile updated

01 · Experience

What experience informs Mark's work?

Software and applied AI
  1. Game technology
    • Three production engines
  2. Studio workflows
    • MCP integrations
    • AI tooling
  3. Current work
    • Brainjuice Labs
    • Marathon Variety

Before founding and leading technology companies, Mark competed professionally in games and became a world champion at 21. His subsequent work has spanned proprietary engines, production infrastructure, technical product leadership, and company building. Across that work, he has contributed to teams that created three distinct game engines, each of which reached production.

He has built Model Context Protocol integrations and AI tooling used in production studio workflows. At a game-technology company he founded and led, the technical team developed proprietary engine technology backed by ten US provisional patent applications and an international PCT application. One related US patent has since issued.

He has also served as an independent external expert on an EU-funded game-technology R&D initiative in Portugal that included an international research, knowledge-exchange, and mobility cooperation route involving Macao. His assessment reconciled project objectives, technical evidence, research outputs, and delivery records into a formal technical-scientific opinion.

His current work continues through Brainjuice Labs and Marathon Variety, where he builds and advises on AI infrastructure, production systems, game technology, tools, and emerging distribution platforms. That combination of technical, commercial, and production experience informs his work on how AI systems discover, describe, compare, and recommend companies and products.

02 · Responsibility

What does the author role cover?

The published record
  1. Evidence
    • Sources
    • Review dates
  2. Analysis
    • Interpretation
    • Limitations
  3. Accountability
    • Correction route

As the accountable named author for this research, Mark identifies sources, records review dates, separates evidence from CiteSurge interpretation, states limitations, and maintains a correction route. CiteSurge remains the publisher, and Brainjuice Labs LDA remains the legal operator.

His role connects the source record to the published analysis, so readers can see why a conclusion appears, where its evidence came from, and how to challenge or correct it.

Read the editorial and research standards

03 · Research method

How is CiteSurge research reviewed?

  1. Public sources

  2. Visible review date

  3. Source list and limitations

His published method starts with identified public sources and a visible review date, then distinguishes what the evidence supports from CiteSurge's interpretation. Each Insight preserves its source list and limitations.

The comparison publishes its scoring rubric, evidence date, self-authorship disclosure, re-verification deadline, and correction route. CiteSurge does not manufacture statistics, authorship, reviews, or outcomes to strengthen a claim.

04 · Published research

Work attributed to Mark.

The complete public authorship set represented by this profile, not a claim about unpublished work or outside recognition.

Corrections

Question the evidence. Keep the record accurate.

Readers can question a source, scope, date, or interpretation in Mark's published CiteSurge work. A useful request identifies the page, disputed statement, and supporting source. No private customer information is required.