Cognoscent
Client collaboration

[ Client Experiences ]

What clients say about working with us

Honest accounts from organisations that have commissioned AI knowledge extraction, RL environment design, and technical due diligence engagements.

Back to Home

80+

Engagements completed

94%

Clients commissioning further work

4.8

Average satisfaction rating

6+

Years operating in Singapore

§ Client accounts

From the organisations we've worked with

TL

Tan Li Shan

Head of Operations · Logistics firm, Singapore

"We commissioned the RL environment design service for a vehicle routing problem we'd been stuck on for two years. The simulation they built actually reflected how our depot works — constraints, shift patterns, vehicle mix. That sounds obvious but previous attempts hadn't managed it."

The engagement ran to eleven weeks. The documentation they delivered was clear enough that our internal team could continue experimenting after handover.

January 2025 · RL Environment Design

PK

Priya Krishnan

Partner · Private equity firm, Singapore

"The due diligence report was unusually candid. Most reviews we receive either validate everything or flag trivial issues. This one identified a real reproducibility problem with the target company's main model that would have been costly post-acquisition."

The risk ratings were clearly reasoned — not just a traffic light system without explanation. We've since used Cognoscent on two further reviews.

February 2025 · AI Technical Due Diligence

MW

Marcus Wong

Chief Knowledge Officer · Professional services, Singapore

"We had fifteen years of project documentation sitting in a file server that no one could find anything in. The knowledge extraction engagement turned it into something usable. It took four weeks and the quality metrics showed us clearly what had been extracted well and what hadn't."

One limitation: extraction quality varied across older document formats. They flagged this upfront and it was in the report, which I appreciated.

December 2024 · AI Knowledge Extraction

SA

Siti Aminah

VP Technology · Regional bank, Singapore

"We needed an independent view of an AI vendor's claims before a significant contract commitment. The technical due diligence gave us exactly that — a structured assessment of what the system actually does versus what the sales materials say."

Completed in three weeks, which fit our decision timeline. The scoping conversation before we engaged was direct — they were clear about what the review would and wouldn't cover.

January 2025 · AI Technical Due Diligence

RN

Rajesh Nair

Director of AI Research · Manufacturing, Singapore

"The reinforcement learning environment they designed for our scheduling problem has been running in production for five months. The reward function design took more iteration than the stated timeline suggested it would — they extended the engagement without additional charge to get it right."

That kind of straightforwardness about the work taking the time it takes is not common in my experience.

November 2024 · RL Environment Design

JL

Jonathan Lim

CTO · Technology startup, Singapore

"I initially contacted them about a project that turned out not to fit their service lines. They were clear about that within a day rather than trying to make it work. We came back six months later with the knowledge extraction project and the engagement went smoothly."

The honesty at the initial stage built a lot of trust. Not common in a services context.

January 2025 · AI Knowledge Extraction

§ Case studies

Engagement accounts in detail

[ Case Study 01 · RL Environment Design ]

Logistics optimisation for a regional freight company

Challenge

A freight company had attempted to apply a standard RL formulation to their vehicle routing problem but found that training agents on a simplified simulation produced policies that failed in production. The simulation didn't reflect real operational constraints — time windows, vehicle heterogeneity, driver shift limits.

Approach

Cognoscent rebuilt the simulation from the ground up, beginning with a constraint mapping exercise involving operations staff. The reward function was redesigned to balance three competing objectives rather than a single metric. Validation involved running historical routes through the trained policy and comparing against human dispatcher decisions.

Outcomes

The resulting environment supported agent training to a policy that performed comparably to senior dispatcher decisions on historical data. The client team continued using the environment for internal experimentation for at least four months post-engagement. Engagement ran 11 weeks against an 8–12 week scope.

[ Case Study 02 · AI Technical Due Diligence ]

Pre-acquisition review of an AI-driven pricing platform

Challenge

An investment team was evaluating an acquisition of a Singapore-based company whose primary asset was an AI-driven dynamic pricing engine. The company's technical documentation was substantial but the investment team lacked the internal capability to assess whether the claims about model performance were defensible.

Approach

The assessment covered model architecture, the data pipeline feeding the pricing engine, evaluation methodology (the company's own performance claims were based on backtesting that had several methodological issues), the engineering team's structure, and IP ownership. A three-week engagement with access to technical documentation and two structured interviews with the target company's engineering team.

Outcomes

The report identified that performance claims were based on a backtesting methodology that overstated out-of-sample performance. The data pipeline had two points of fragility that would require remediation before scaling. These findings were presented with severity ratings and mitigation options. The investment team used the report to negotiate price and agree remediation milestones in the acquisition agreement.

[ Case Study 03 · AI Knowledge Extraction ]

Institutional knowledge capture for a professional services firm

Challenge

A mid-sized professional services firm was losing senior practitioners to retirement, and with them a significant body of client engagement knowledge that existed only in personal drives, email archives, and project folders dating back twelve years.

Approach

The engagement began with a source inventory across approximately 40,000 documents across three storage systems. Extraction model design identified six primary entity types relevant to the firm's work. The extraction pipeline processed documents in batches with human review of sampled outputs at each stage. Quality metrics tracked entity completeness and relationship accuracy.

Outcomes

The structured output covered approximately 82% of accessible documents, with quality metrics showing high entity accuracy on modern documents and reduced accuracy on documents from before 2015. The pipeline documentation enabled the firm's IT team to run incremental extractions on new documents without further engagement. Delivered in five weeks.

§ Contact

Discuss your situation with us

We respond to all initial enquiries within one working day with an honest view of whether an engagement is a reasonable fit.

Mon–Fri, 9am–6pm SGT
Send a Message

Ready to talk about your situation?

We'll read what you send carefully and respond with a direct view of how we might help.

Get in Touch