Skip to content

Work

Work inside real organisations.

We do not begin with demonstrations. We begin with operational problems.

Each deployment starts by understanding the business. Each one ends with a system designed for real use.

500+Certificates processed daily

Vessel certificate information handled through NavCert in production.

5+Engineers trained in the method

Forward Deployed Engineers trained to study an operation before choosing a technology.

3+Years building operational systems

Building products and systems for real organisations, not demonstrations.

~6Weeks of research before deployment

Time spent inside one organisation studying its industry, systems, and options before building.

The deployments

Three deployments, one page each.

Turn the page to move between them. Each page opens onto the full case study, where the reasoning is written out in order.

Deployment 01 of 03

Deployment 01

Building an AI workforce inside Microsoft Teams

An organisation wanted AI to become part of its daily operation—not a small experiment or another isolated application, but a working capability inside the company.

Research period
Approximately six weeks
Working environment
Microsoft Teams, email, internal systems
Ahum Labs’ role
Research, system design, agents, integration, permissions, deployment
Outcome
Outcome pending client approval

Read the case study

System diagram — governed AI workerDeployed
Operations lead · Microsoft Teams

“Prepare the weekly compliance report and send it for approval.”

Handled by
AI worker · Compliance operations

Works with an organisational identity, approved tools, and controlled access to internal systems.

  • Defined responsibility
  • Approved tools
  • Controlled access
  • Operating limits
  • Escalation rules
Escalates to
Named approver · Human decision

The action is not completed until a person with authority confirms it.

The AI workforce sits inside Microsoft Teams, where delegation and coordination already happened. No new interface was introduced.

Maritime

Deep work in maritime technology.

Maritime organisations operate across vessels, regulations, documents, people, approvals, and software developed over many years. The work cannot stop while new technology is introduced. That changes how systems must be built.

Our experience includes

  • Vessel documentation
  • Certificate management
  • Compliance workflows
  • Recruitment and crewing
  • Operational communication
  • Internal information retrieval
  • Natural-language systems
  • Legacy software modernisation
On the outcomes shown here

Where a deployment shows Outcome pending client approval, the measured result exists but has not yet been approved for publication by the organisation involved. We do not publish a figure before that approval, and we do not name a confidential client.

Do not begin with a software requirement.Begin with the work that is not working.

Tell us where people lose time, information becomes difficult to find, decisions slow down, employees repeat the same work, or an existing system holds the organisation back.

We will study the operation before deciding what should be built.

No technical specification required