Selected implementation work
These projects show how Meru studies an operation, connects the right systems, preserves human review, and measures what changed.
Sales operations
At one law firm, the strongest reps knew which questions helped them decide whether to sign a caller. We studied their call histories and brought those questions and the caller’s previous answers into the intake record.
IT account management
Before a renewal, an IT account manager needed to know what the team had promised and what support had delivered. BloomChat brings the proposal, service tickets and client correspondence into one account brief.
Legal operations
A call could disappear before it reached the law firm’s intake queue. We traced the route from the first ring to intake and connected the call records to the firm’s case and campaign systems.
Independent public data product
Meru built and operates Evidence for Zero, a public map of California collisions. When a source revises a crash report, the map can reflect the correction while keeping the history of the original record.
Choose a problem you recognize. Step into the employee’s place and see what changes when the right record is already at hand.
Use an earlier call to resolve a conflicting answer, then prepare the next rep’s brief.
Legal operationsCheck what is already in the matter file and prepare a request for just the missing records.
Distribution operationsCompare the order with the receiving record. Catch the two extra cases before the invoice reaches finance.
Fictional data and prebuilt outputs. No login, uploads, or live client connections.
Explore selected workServices, clearly defined.
For operating partners and portfolio-company leaders: AI implementation across the portfolio
The opportunity is visible, but the right starting point is not.
A prioritized implementation plan grounded in value, readiness, and risk.
A prospect has already answered a question. The next person still has to ask.
We carry those answers into the intake record so the rep can focus on what still needs a decision.
The system needs ownership, review, training, and measurement after launch.
Clear operating procedures, human review, monitoring, and continued refinement.
How Meru works
In our own delivery workspace, each commitment has an owner. After a meeting, we can trace a promised deliverable back to the agreement and see who needs to act next.
Inside our client delivery workspaceWe study the people, workflows, systems, information, and decisions involved before recommending technology.
We identify the opportunity with the clearest business value, practical data access, and responsible path to adoption.
We establish the implementation plan, technical design, human review, ownership, and measures of success.
We build, integrate, test, and prepare the solution for use inside the systems your team already relies on.
We train the team, monitor performance, resolve exceptions, and refine the system as the business changes.
Implementation notes
A practical guide to moving from a promising pilot to a dependable production system.
02How lead context, call review, follow-up, and revenue feedback can work together.
03What it takes to connect AI to CRM records, conversations, documents, and review paths.
Jose Okabe has led implementation across attribution, telecom, intake, reporting, automation, and AI-supported workflows in a 350+ employee environment. That operating experience shapes how Meru evaluates risk, adoption, ownership, and measurable change.
About Jose and Meru AIBegin with a conversation.
Share the workflow, system, or decision you want to improve. You do not need a finished AI roadmap or a polished technical brief.