The platform
Maybank Service Intelligence
Service intelligence for professional services firms.
Maybank Service Intelligence applies the operating model first developed inside Pyxl to other professional services firms. It connects recurring work, institutional knowledge, operating standards and management signals that normally live across project systems, documents, inboxes and individual memory.
What it is
An operating layer around the systems a firm already runs.
Rather than adding another system for teams to maintain, MSI works across the ones where client work already lives. It reads what is changing, assembles the context a person would otherwise rebuild by hand, and carries that context into the workflows the firm actually runs.
Agents run inside that layer. They are one component of MSI, configured last, once the context and the review standards are in place.
Maybank platform · the order the layer is built in
What it does
Client and delivery signals
Reads across the systems where client work already lives, rather than asking teams to maintain another one.
Client-health concerns
Surfaces accounts that need attention before a status meeting establishes it.
Portfolio-level context
Assembles the view across accounts that normally takes someone senior an afternoon.
Account information on demand
Provides account context without a project manager reconstructing it by hand.
Client context in workflows
Carries approved client information into the work instead of re-establishing it each time.
Reporting, research, content and QA
Supports the delivery workflows where they fit the firm’s model, each with its own review gate.
Reduced coordination work
Removes manual project-management and account-coordination steps, which is where the operating leverage came from.
Configured agent workflows
Agents run inside the layer, scoped per client, under the firm’s own review standards.
What it is not
What MSI does not do
A firm carrying professional liability needs to know where a platform stops. These are the limits, and they are set deliberately.
Not a replacement for your systems
Asana, Slack, Drive and email stay where they are. MSI reads across them.
Not a CRM or PSA
It reads CRM context. It does not become the system of record.
Not a chatbot
Configured workflows against your delivery model, not a general-purpose assistant.
Not an autonomous workforce
Every workflow has a named owner and a review gate. Writes are proposed and confirmed.
Not a tool you switch on
Each implementation is configured around one firm’s delivery model, systems, methods and governance requirements.
Two layers
The work, and the operating system around the work.
The objective is not simply to make individual tasks faster. It is to reduce the friction required to produce, coordinate, review and manage the work the firm sells. Those are two different problems and they show up in two different places on the P&L.
Layer one
The work
- Research and synthesis
- Recurring drafting
- Knowledge retrieval
- Reusable firm methods
- Recurring deliverables
- Review preparation
Layer two
The operating system around the work
- Briefing
- Handoffs
- Status reporting
- Information retrieval
- Recurring reporting
- Version awareness
- Management visibility
- Institutional knowledge
The first layer can improve delivery economics. The second can create additional operating leverage.
Pyxl Intelligence was the first operating implementation of this model, built by Maybank inside Pyxl. From August 2025 through Q2 2026, Pyxl expanded gross margin by +1,300 bps and EBITDA margin +1,800 bps while the company changed its delivery and operating model alongside the technology.
Pyxl is one internal operating example. Results will vary by work mix, cost structure, adoption and commercial decisions.
Before the platform, the operating model
See why a tool alone does not produce firm economics.
The 18-minute briefing shows what changed inside Pyxl before Maybank Service Intelligence became the client-facing operating model—and where the evidence stops.
Four chapters · Every figure cited · Not a software demo
The surfaces
Six screens from a configured implementation.
What each agent can do, what it is allowed to read, what runs without being asked, how it is gated, what it recorded, and what it cost to run.
Client names are illustrative and people are shown by role. These are representative MSI configurations: the operating model and controls Maybank configures for a client environment. Where a behavior is verified as running inside Pyxl today it is labeled as such below.
The same operating pattern runs inside Pyxl as Pyxl Intelligence, which is the proof case rather than the product. See it in the Pyxl case study.
How it arrives
MSI was not built to be sold. It was built because Pyxl needed it, over 18 months of investment in the system, the processes and the prompt library, and it has been running there since. A client configures a system that already works rather than funding its invention, which is the difference between a project measured in months and one measured in years.
Configured during the engagement rather than licensed
MSI is scoped in the readiness assessment and configured during the build phase, against the firm's own delivery model, systems, methods and governance requirements. There is no seat count to buy and nothing to switch on.
The operating pattern was proved before it was offered. It runs inside Pyxl as Pyxl Intelligence, which is the proof case rather than the product.
“As Pyxl’s long-time Controller, I see the impact of AI through Pyxl Intelligence in the financial results, not just in anecdotal productivity gains. Over the past nine months, Pyxl has expanded gross margin by 13 percentage points and EBITDA margin by 18 percentage points. The gross-margin improvement reflects stronger delivery economics, and that gain flowed through to EBITDA. EBITDA expanded further as the company also generated additional operating leverage below gross profit. From a finance perspective, this is a meaningful improvement in the operating model, not simply a technology-efficiency story.”
Where it is scoped
In the readiness assessment. $4,500, two weeks, credited in full against a build engagement.
Where it is built
In the build phase. Configuration rather than construction where the delivery model fits, which shortens it considerably.
Who holds it afterwards
The firm. Prompt libraries, review standards and documentation sit in your own systems.