Five Kits for building enterprise AI

Ontokit connects enterprise data into knowledge, and Bespokit turns requirements into design and code.
Askit builds agents that answer from that knowledge, and Mallkit and ERPkit extend it into storefront and operations system builds.

01OntokitBuild and operate an enterprise data ontology02BespokitGenerate software from requirements03AskitBuild AI agents that show their evidence04MallkitModule based D2C storefront builds05ERPkitBuild purchasing, sales, inventory and shipping systems

Five products,
one AI pipeline

From understanding enterprise data to generating software, running agents, and building operations systems, there is a product at every stage.

Ontokit

Scattered enterprise data becomes
knowledge AI can reason over

We connect the objects and relationships across ERP, groupware, and documents, then build and operate a query environment where every answer can be traced to its source. Deployment and operating scope are set after assessing your data environment.

  • Connect enterprise data, objects and relationships across databases and documents
  • Source-backed queries, see the evidence behind an answer and its review state
  • Deployment options, dedicated cloud, your VPC, or on-premise
More on Ontokit
Example structure · sample data
Bespokit

Take requirements in any form,
return software you can review

Plans, documents, and images are organised into a standard spec, and design, code, and deployment artefacts are produced against reusable code assets. Feature scope and acceptance criteria are fixed per project.

  • Standard spec, requirements and acceptance criteria in one structure
  • Asset reuse, existing code and design documents as reference
  • Explicit handover, code, documents, and repository terms written into the contract
More on Bespokit
Example process
Askit

An AI agent that answers from your documents,
built to your operating rules

We connect documents and operational data into an agent that shows where each answer came from. Channels, answer policy, and permission scope are reviewed before it ships.

  • Configuration first, knowledge, prompts, and tools managed in one place
  • Evidence policy, define answer sources and when not to answer
  • Multichannel, web widget and messenger integration scope
More on Askit
Example screen · sample data
Mallkit

Treat your storefront
as a product, not a project

We assemble product, order, payment, settlement, and CRM modules into a D2C storefront. After confirming the integrations and brand experience you need, we separate standard modules from new development.

  • Standard modules, products, orders, payments, settlement, CRM
  • Extension scope, ERP, logistics, and marketing tool integrations
  • Handover terms, code, data, and operational responsibility written into the contract
More on Mallkit
Example module set
ERPkit

Work that breaks between spreadsheets and packages,
connected into one operational ledger

We design purchasing, sales, inventory and shipping workflows with master data and permissions, then build a custom ERP and its operating screens. What a package can handle is separated from what needs building first.

  • Master data design, items, accounts, and role based permissions
  • Operating screens, purchasing to shipping, in processing order
  • Migration and integration, terms agreed for existing data and external systems
More on ERPkit
Example screen · sample data

The products are connected

Askit answers on top of the knowledge Ontokit builds, and the Bespokit generation pipeline extends into Mallkit and ERPkit.

Enterprise dataERP · groupware · documents · sheetsRequirementsplans · documents · images · conversationOntokitontology build · knowledge layerBespokitsoftware generation pipelineknowledge ↔ generationAskitAI agentERPkitoperationsMallkitstorefront

Frequently asked questions

The conditions people check most often before adopting.

Which Kit should we look at first?

If structuring enterprise data and its usage rules comes first, start with Ontokit. If requirements need to become working software, start with Bespokit. If you need an AI agent that answers from documents, start with Askit. If the goal is a D2C storefront, start with Mallkit. If you need a system for purchasing, sales, inventory and shipping, start with ERPkit.

Can we adopt more than one Kit?

Yes. For example you can organise data and permissions with Ontokit and then connect an Askit agent, or combine the Bespokit generation scope with Mallkit commerce modules. The actual combination is decided after reviewing your data and the scope of work.

How are timeline and cost estimated?

They depend on data sources, systems to integrate, feature scope, the security environment, and acceptance criteria. After reviewing your current environment and goals in a consultation, we propose the included scope, an expected schedule, and the terms of the quote.

Who owns the code and the data, and who operates it?

Each project contract sets out the code repository, deliverables, data, external service accounts, and operational responsibility separately. Where your own infrastructure or a dedicated environment is required, the deployment method is agreed alongside.

Can we talk to you before the requirements are concrete?

Yes. We define the first review scope around the work you want to solve, the systems you use today, and the security and operational conditions you have to meet.

We will help you find
the Kit that fits

We look at your current data and operating environment and set the first review scope together.

Discuss solution scopeCompare the five KitsSee the industry Packs

Not sure where to start? Start with the AX journey