Skip to content

Edward
Batt

I connect operational understanding, technology strategy and hands-on delivery to build systems that work.

AI transformation.
Intelligent systems.

Technology strategy
Systems & product architecture
Enterprise operations

See the workContact Edward

From operating reality to working systems.

Operating realityPeople, workflows, constraints and commercial context.

30+ years of international business, technology and operational experience

Jakarta Region, Indonesia

Selected work / Operational transformation

Maestro

Making agency operations
visible and manageable.

From fragmented work to a shared operational platform for a branding and marketing agency across Iraq and Egypt.

Operational pilot achieved in approximately six weeks.

Illustrative operating model

A shared operating model across teamsIntake and planning begin in Client Services. Resource-aware scheduling connects to creative production. A human decision controls approval and delivery, with a path back for review. AI assistance supports the workflow. Exceptions can be brought to human attention.Client servicesResourcesCreative workIntakePlanningSchedulingProductionApprovalDeliveryAI assistanceResource awarenessHuman decisionReview and revision remain connected
  1. Intake & planning

    Client services define the request, scope and responsibility.

  2. Scheduling

    Resource awareness informs allocation.

  3. Production

    Creative work and activity stay traceable.

  4. Human approval

    An explicit decision, with a route back for revision.

  5. Delivery

    Completed work retains its decision history.

Work moves across teams while its context stays connected. Resource awareness and human approval are part of the operating model.

Shared visibility

Intake, scheduling and production in one operational picture.

Traceable decisions

Activity, alerts and human decisions connected to the work.

Assistance with control

AI support and non-blocking controls, with clear accountability.

Edward’s contribution

Operational discovery, workflow redesign and translation of the future operating model into a working platform. Lead architect and developer.

Pilot evidence

Client Services and Creative teams could create and schedule projects through the new workflow.

Technical foundation

React / Supabase / PostgreSQL / Vercel

The operating problem and response

The problem

Operational workflows lacked consistency and visibility. The real operating model needed to be understood and remapped before meaningful digital transformation could occur.

The response

Reviewed operating flows, identified process and visibility gaps, remapped workflows against international agency practices, and translated the future-state model into a working platform.

System capabilities

  • Project intake, scheduling and approvals
  • Production workflow and resource tracking
  • Role-based, multi-tenant operations
  • LLM-assisted workflows and exception reporting
  • Alerts, traceability and activity logging

Commissioned commercial platform

Sidegig

The business model
is part of the architecture.

A platform connecting brands with influencers and creators. I designed the commercial model and the technical solution as one connected system.

Lead solution / technical architect

Primary business-model architect

LLM-assisted ingestion, algorithmic matching and workflow automation support recommendations while keeping human decisions explicit.

Commissioned architecture engagement. No commercial outcomes are claimed.

Illustrative matching architecture

Brands

Requirements & opportunities

Creators

Profiles & content

Interpretation + matching

Commercial logic.
Technical architecture.

Recommended connections

Human choice

Algorithmic matching connects interpreted requirements with creator information to support recommendations.

Product architecture & delivery / ESTAZ

GGI

The competition runs
on the system.

An esports tournament platform for gamers in Iraq, replacing manually coordinated competition operations with an automated operating model.

CTO at ESTAZ

Lead developer / solution architect

Tournament formats, fixtures, Discord channels and leaderboards connect the organising work to the participant experience.

Delivery evidence

MVP in approximately three months; full functionality in approximately six months.

More than 5,000 users registered during the first three months.

Illustrative competition structure

RegistrationFixturesProgression
Participant
Participant
Participant
Participant
Competitionprogress
Select a fixture or trace a result
  1. Registration
  2. Tournament structure
  3. Fixtures
  4. Discord operations
  5. Results
  6. Leaderboards

Tournament structure, fixtures, Discord integration and leaderboards connect the competition’s operating work.

The complete problem.
Not just one part of it.

Executive operating experience, architectural thinking and hands-on development belong in the same conversation.

  1. Understand

    Operating reality

    Map the operating problem before choosing the technology.

  2. Redesign

    A better operating model

    Make responsibilities and decision flows explicit.

  3. Architect

    A coherent architecture

    Connect business logic, information and system behaviour.

  4. Build

    A working system

    Turn the architecture into a product people can use.

  5. Adopt

    Adoption in practice

    Bring the system into the work and learn from its use.

Capabilities behind the work

Transformation & Advisory

Determine what needs to change, where technology adds value and how adoption can work in practice.

  • Digital transformation
  • AI adoption
  • Operating-model design
  • Process redesign
  • Enterprise discovery
  • Use-case prioritisation
  • Executive advisory
  • Change and adoption

Solutions & Product

Turn operating requirements into a coherent product, system and delivery plan.

  • Product strategy
  • Solution architecture
  • Requirements analysis
  • Workflow design
  • MVP definition
  • Implementation roadmaps
  • Systems integration
  • Human-in-the-loop design

AI & Automation

Apply intelligent systems where they improve work, knowledge, decisions or control.

  • Generative AI and LLM workflows
  • Agentic-system concepts
  • Workflow automation
  • Intelligent decision support
  • Knowledge and context systems
  • AI-enabled operational tooling

Business & Operations

Ground transformation in commercial reality and the way organisations actually operate.

  • Executive operations
  • Supply chain
  • Procurement
  • Contracts
  • Project operations
  • Commercial analysis
  • Cross-functional transformation

Designing the systems
around intelligence.

Independent R&D into digital workforces and reliable context for AI-assisted development.

Independent R&D / Operating-system concept

SolomonOS

A workforce needs
an operating model.

SolomonOS is a Digital Workforce Operating System for creating and operating AI-powered digital employees. Each digital employee has a defined organisational role, persistent knowledge, specialised skills, behavioural rules and controlled access to the capabilities required to perform its work.

Its proprietary engines coordinate cognition, knowledge, skills, authority and collaboration while preserving organisational context and human oversight. The architecture is LLM-independent, separating the digital employee and its operating environment from the underlying language model.

Work in progress.

Concept architecture

Human oversight

Objectives, decisions & accountability

Role-based AI workers

Defined responsibility
Role
Skills
Rules

Organisational knowledge

Durable context & multi-agent collaboration

LLM-independent design

Independent R&D / Knowledge & context

Keystone

Context is an
architecture problem.

Target

−80% context tokens

Live-project validation pending

Built with Keystone

Early Keystone context structures were used in the development of Keystone itself.

AI-assisted development loses coherence when decisions, constraints and working knowledge are scattered, repeatedly reconstructed, or pushed back through the model as expensive context.

Keystone is a work-in-progress repo-native context system designed to make project knowledge structured, persistent and inspectable through deterministic artifacts, indexing, validation and relationships.

The target is an 80% reduction in context-token usage while preserving the information needed for effective AI-assisted development. This target will be measured and validated against a live software project rather than treated as an assumed benefit.

Keystone is already helping build Keystone. Early versions of its own context architecture were used during Keystone's development, allowing the project to progressively manage specifications, decisions, tasks and implementation context using the system it was creating.

Independent R&D. Once the architecture and token-reduction target have been validated in real project use, the intention is to release Keystone under an appropriate licence.

Illustrative artifact relationships

Repository-native context

Tasks

Keep implementation grounded.

Tasks relate to features and the decisions and rules that constrain the work.

Related contextFeaturesADRsRules

Index relationships. Validate context.

Explicit artifacts and deterministic relationships make development context inspectable.

Earlier explorations

Reaptor chatbot platform

Earlier independent product R&D / Parked

Knowledge ingestion, configurable LLM assistants, knowledge bases and embeddable deployment. This earlier no-code product is separate from Reaptor’s current identity as my professional practice.

Valsyg

Supporting infrastructure exploration

Independent R&D into Solana validator infrastructure and blockchain operations.

Experience

Depth behind
the work.

Decades of responsibility for organisations, operations and technology across international environments.

2026–Present

EGI

Traffic Manager & Digital Transformation Lead

Iraq / Egypt / Dubai — Remote

2023–2026

ESTAZ

Chief Technology Officer

2021–2022

Business & Technology

Independent Consultant

2016–2020

Köenigsys MSS

Principal / Owner

Indonesia

Earlier leadership spans COO and operations roles, contracts, procurement, supply chain, energy, infrastructure and Defence.

Earlier international experience

2015–2016

COO

Ichor Holdings LLC / Dubai / Mozambique

2013–2016

COO

3Lysium Holdings LLC / Dubai / Mozambique

2011–2013

Senior Contracts & Procurement Manager

Unaoil Group / Dubai / Monaco / Iraq

2008–2010

Senior Contracts & Procurement Manager

Woodside Energy — Browse LNG / Australia

2009–2011

Director Operations

PT Cipta Trikreasi Indonesia / Indonesia

2010–2011

Operations Manager

Joint Oilfield Service Solutions / Brazil

2009–2011

Director Operations

PT Niaga Gema Teknologi / Indonesia

1997–2000

Project Support Manager

Santa Fe / Devon / Indonesia

1994–1996

Chief Logistics & Operations Officer

Indochina Goldfields / Indonesia

1986–1994

Australian Defence Force

Army / Australia

About Edward

A consistent thread.
An expanding toolkit.

Complex organisationsOperational problemsTechnology & systemsIntelligent transformation

My career has centred on making complex organisations work better.

Across executive operations, CTO and COO roles, consulting, contracts, procurement and technology ventures, the recurring question has been how people, processes and technology can work together more effectively.

AI extends that thread. I bring the operating context, shape the system and work through the practical details of building it and bringing it into use.

International experience across APAC, the Middle East, Africa, Australia and Latin America.

Let’s talk about
what comes next.

Senior permanent leadership opportunities and selective transformation / technology advisory engagements.

edward@reaptor.io

Edward Batt

Jakarta Region, Indonesia

+62 812 9435 2999
REAPTOR

AI transformation / Intelligent systems / Technology strategy

© 2026 Edward Batt