Bahulam
AI work platformConnected intelligence for real work.
Bring conversations, coding, tools, and domain workspaces around the task a team needs to complete.
BUILT FOREngineering leaders, builders, and teams adopting AI workflows
AXPLUSB TECH / PRODUCTS & ENGINEERINGWe build AI products.
We build AI products.
You put them
to work.
Bahulam, CoDash, and OneAdmin. Three products for the way enterprises build, modernise, and operate.
One engineering platform. And the team that brings it into your estate to build what comes next.
Applied researchDomain expertiseHuman review
IN FOCUS / 01Explore Bahulam
AI work platformConnected intelligence for real work.
Work you can inspect
For each product: the workflow it runs, what that workflow supports, and what it does not. Where a dated recording is still owed, the page says so rather than implying one exists.
Source-backedBahulam Code CLI — binary `bahulam`, package `@bahulam/code` · inspected 2026-09-26
A scoped repository change, reviewed by a person
- Input
- Action
- Artifact
- Human review
- Outcome
- Input: A scoped task against a repository the team already owns.
- Action: The agent plans the change, edits files, and runs the repository's own checks.
- Artifact: A diff and the output of the checks that actually ran.
- Human review: An engineer reads the diff and the check output and decides whether to accept it.
- Outcome: An accepted change, or a rejected one with the failure visible.
A dated recording of this workflow is owed before it is described as demonstrated.
How to read the status labels
- Source-backed
- The implementation exists in the inspected product source. It has not been demonstrated end to end here.
- Demonstrated
- A dated end-to-end run supports this capability, with environment, inputs and outputs recorded.
- Available
- A product owner has approved this capability for a stated customer scope and operating model.
- Interactive preview — simulated execution
- An illustrative interface or synthetic simulation. No live backend behaviour is implied.
- Planned
- Roadmap work. A component, route or partial API may already exist; the capability does not.
03 / THE ENGINEERING PLATFORMBuilt on the same
Built on the same
engineering foundation.
Bahulam, CoDash, and OneAdmin are not three unrelated bets. They are three things the same platform produced — the same agent engineering, the same domain modelling, the same evaluation discipline, the same insistence that a person reviews the result. That platform is also the thing we bring to an enterprise that wants an internal product of its own.
Bring it into your enterprise01Agent engineering
Orchestration, context handling, tool use, and recovery — the machinery that turns a request into an attempted piece of work rather than a paragraph of text.
In your estate: The agent layer of your internal product, built against your workflow instead of a generic template.
02Domain modelling
Real parsers and semantic models for the systems enterprises actually run — BI platform dialects, semantic layers, application snapshots, administrative object graphs. Not generic text extraction.
In your estate: The domain logic your workflow depends on and that nobody ever wrote down, modelled explicitly.
03Evaluation and validation
Evaluation sets, parity checks, negative cases, and run manifests. Knowing whether a change helped is a capability, not an afterthought, and it is what makes an AI system safe to extend.
In your estate: Acceptance criteria agreed before we build, and an evaluation set that tells you whether they were met.
04Review and authority
Every product puts a person at the decision point: an engineer accepting a diff, a reviewer repairing a conversion exception, an administrator approving a proposal. The artifact, the checks, and the decision are all inspectable.
In your estate: A system your people stay accountable for, with the failure paths exercised rather than hidden.
05Delivery and operation
Packaging, deployment, telemetry, and handover — including hosted and customer-operated configurations, agreed per deployment rather than promised across the portfolio.
In your estate: Deployment automation, telemetry, runbooks, and a handover your operators accept.
Platform here means shared engineering capability, patterns, and know-how — evidenced by three products built with them. It is not a claim that Bahulam, CoDash, and OneAdmin share authentication, a common runtime, or interoperable product state. Each is deployed and operated on its own terms, and any integration between them is scoped in an engagement rather than assumed.
04 / AI CONSULTINGYour next product.
Your next product.
Our engineers,
alongside yours.
AI consulting brings an engineering team into your workflow — with your product owner, users, systems, and constraints — from the first process map to a maintained internal product your team operates.
- 01
Opportunity and feasibility
1–2 weeks- Opportunity brief and process map
- Baseline measures and a data and access assessment
- Architecture options with their tradeoffs
- A prioritised scope
The decision at this stage
Is there a valuable, feasible internal product here?
- 02
Validated pilot
3–6 weeks- A working vertical slice
- An evaluation set and the results against it
- Quality, cost, and latency reported together
- Integration evidence and the explicit failure paths
The decision at this stage
Does the slice meet the acceptance criteria we agreed before building it?
- 03
Production delivery
Estimated after the pilot, not before- The integrated product and its deployment automation
- Telemetry and permissions
- An acceptance report, runbooks, and training
The decision at this stage
Can the customer operate this within the boundaries we agreed?
- 04
Operate and expand
Recurring scope- Monitoring reviews and evaluation regression checks
- Improvements against the agreed priorities
- Knowledge transfer
The decision at this stage
Maintain, extend, or transition ownership.
Durations are planning ranges for a bounded engagement, conditional on access, data, dependencies, and agreed scope.
05 / APPLIED RESEARCHBetter questions.
Better questions.
Better products.
Applied research is a discipline across the three products. We investigate the engineering questions that make AI work more reliable, more useful, and easier to review.
Explore our research approachResearch themes · publications will follow technical review.
01
Bahulam
Reliable agent execution
Which orchestration, context, and recovery choices actually improve the rate of accepted outcomes?
02
CoDash
Semantic modernisation
Where do translated BI calculations preserve meaning, and where do they diverge?
03
OneAdmin
Authority and operational evidence
Can an exact proposal, the policy that governs it, and the resulting state change be validated before the action is taken?
04
Bahulam
Interactive work artifacts
How do persistent workspaces and plugin views change review and handoff between people?
06 / ENTERPRISE READINESSBuilt around
Built around
your enterprise.
Start with your workflow, your systems, and the people responsible for the result. Together, we define the scope and the evidence you need to move forward.
Deployment, data boundaries, and human responsibilities are agreed for your product and configuration.
A CLEAR PATH FORWARDFrom the first question
From the first question
to an informed decision.
- 01
Say what you are trying to change
The workflow, who does it today, and what a better outcome would look like in measurable terms.
- 02
We scope what is evaluable
Which product or delivery model applies, what it covers for your platforms, and what it does not.
- 03
Agree the acceptance criteria before building
An evaluation set, the measures, and who accepts the result. Criteria agreed afterwards are not criteria.
- 04
Run a bounded evaluation
Representative data in an approved environment, with the failure paths exercised, not avoided.
- 05
Decide on the evidence
Accept, adjust the scope, or stop. The evaluation report says which, and why.
What we’ll work through together
- Which environment will this run in, and who owns it?
- Which identity and network approvals are needed, and who grants them?
- Which model providers are acceptable for this data, and which are not?
- What happens when the system is wrong — who sees it, and what do they do?
- Who operates it after handover, and what support scope applies?
Certifications, residency, and data-handling commitments are reviewed for the specific product and deployment.
The company behind the products
AxplusB Tech owns Bahulam, CoDash, and OneAdmin, and runs the delivery business that builds internal products with customers. The thesis is that engineering and domain knowledge earned in delivery becomes reusable product capability.
How the company is put together
One engineering platform underneath. Three products and one delivery business built on it. Applied research feeds the platform, and permitted, general learning from delivery feeds back.
Bahulam
AI work platform
CoDash
BI analysis, migration, and reporting
OneAdmin
Enterprise administration
Your internal product
Built with our engineers
The AxplusB engineering platform
- Agent engineering
- Domain modelling
- Evaluation and validation
- Review and authority
- Delivery and operation
Applied research and evaluation
Feeds the platform. Receives permitted, general learning back from delivery.
- Shared: the engineering platform — agent engineering, domain modelling, evaluation, and review patterns — plus the team that applies it.
- Independent: each product is bought, deployed, and operated on its own terms.
- Not claimed: Platform here means shared engineering capability, patterns, and know-how — evidenced by three products built with them. It is not a claim that Bahulam, CoDash, and OneAdmin share authentication, a common runtime, or interoperable product state. Each is deployed and operated on its own terms, and any integration between them is scoped in an engagement rather than assumed.
For investors
The hypothesis is that reusable engineering and domain knowledge improves delivery speed and product economics. That is a claim to be tested, and this site publishes the evidence that exists rather than the evidence we would like to have.
Traction figures, revenue composition, and market sizing are not published here — none is established by a source we can cite publicly. Company materials are shared with the company owner through a controlled process.
Where would you like to start?
Pick the closest one. It prefills the intake so your inquiry reaches the owner responsible for it.
Evaluate a product
Bahulam, CoDash, or OneAdmin — what it covers for your platforms, and what it does not.
Start hereBuild an internal product
Bring a workflow. We come back with a scope, an architecture option, and an acceptance plan.
Start hereTalk to the company
Investor materials, partnership, or a question this site did not answer.
Start here