Request a demo · agentization-core

Received. We write back with the demo's shape.

Not sent. Try again in a moment.

Or write to [email protected].

Website

You and the firm

name · required work email · required role firm · required country industry firm size

languages the demo must speak

English Arabic Other

The demo

what you want to see · required

A business application run by agentscustomers, operations or a custom application, on web and mobile Agents that build and operatedevelopment, infrastructure, engineering, data, research

The application

the agents

Customers agentserves your customers on web and in the app stores Operations agentserves your teams on the company network Custom application agent

surfaces

Web Mobile, app stores Employee app on a private network

knowledge the agent must read

Policies and procedures Product and price catalogues Contracts and agreements Regulations and compliance manuals Reports and statements Forms and templates Tickets and correspondence Technical manuals Other

where it lives

Shared drives A document system A wiki or intranet Email Paper and scans

how much

data to mock for the demo

Customers and accounts Policies, contracts or subscriptions Orders, sales or point of sale Inventory and stock Claims, cases or tickets Invoices, payments and ledger Staff, roles and rota Assets and equipment Logs, events or sensor readings Other

systems in use

ERP CRM A core system of the industry Point of sale Ticketing HR system Spreadsheets Built in house

tools that must run locally

OCR of scanned documents Reading and extraction from PDFs and spreadsheets Handwriting Barcode and QR reading Photo classification (damage, products, documents) Speech to text (calls, voice notes) Translation Reconciliation (documents against ledgers) Drafting email and tickets Scheduling and calendars Maps and routing Questions over your databases Reports with charts and statements Automation on a screen with no API Payments and receipts (sandbox) Other

What a sharp manager catches by eye today

patterns and drift the agent should notice

Unusual volumes per entity or period Units that do not add up (packs against pieces, boxes against items) Duplicates and near duplicates Price or cost drift Who approves whom, and how often Stock that moves without a sale Activity at odd hours The same parties recurring together Items ageing unresolved or unpaid Missing documents or steps Other

Describe two situations your best manager would catch today, in your words The numbers that matter and how you compute them

approvals and roles

Operator Supervisor Auditor Customer

integrations the demo must touch

Email Messaging Ticketing Calendar Payments E-signature Maps SMS and notifications Single sign-on

brand

We have a mark and colours to use Use a neutral brand

right to left

The application must read right to left

The work and the stack

the work

Development (features, fixes, tests) Infrastructure (provisioning, clusters, deployments) Operations (on-call, runbooks) Data engineering (pipelines) Data analytics (notebooks, reports) Research (experiments, reproducibility) Other

the stack, by layer

front end

Component framework in JavaScript or TypeScript Server-rendered templates Native mobile Cross-platform mobile None

back end

TypeScript or JavaScript Python Java, Kotlin or another JVM language C# and .NET Go Rust PHP Ruby Other

APIs and messaging

REST GraphQL gRPC Events and queues

databases

Relational Document Key-value Graph Search Time series Warehouse Lake or lakehouse

data engineering

Batch pipelines Streaming An orchestrator or scheduler Transformation in SQL Notebooks in production

data analytics

Notebooks Dashboards Spreadsheets A statistical language

infrastructure

On-premise servers Private cloud Public cloud Hybrid

Virtual machines Containers Container orchestration Serverless

Infrastructure as code Configuration management Neither yet

version control and delivery

A hosted service Self-hosted

Pipelines on every change Manual releases

Reviews required Reviews optional

observability and security

Logs Metrics Traces A secrets manager Single sign-on Code scanners

the environment

Development Staging Production

repositories engineers

what must wait for a person

Deploy Provision Delete or destroy Schema changes Secrets Merges

reference the agent should read first

Architecture notes Runbooks Coding standards Decision records

The harness

one agent or a team · required

One agent for alla single instance does the work under the harness A team of agents, by tierinstances tiered from the first: more control over actions, knowledge, logic and audit; protocols for tracking (the ATO), communication (A2A) and sandboxing

models · required

Frontier models, hosted where your policy allows Fine-tuned open-weight models, on your own machines

where the demo runs

On our machines On yours Both

what the demo must show

Approvals by a named person The audit channel A guardrail blocking an action A pattern or drift finding Right to left Mobile The terminal reached from a browser or a phone

format

In person, Amman Remote Recorded walk

when attendees anything else