Start with the inbox
Buyers, sellers and advisors create a steady stream of requests, follow-ups and documents. The useful first step was to organize that traffic and prepare work for the team, rather than start with a new screen.
The scope included email triage and staged replies, an operations interface and buy-side origination work. A support runbook gave the team a way to handle uncertainty and exceptions.
Those activities belong to the same working day but need different handling. An incoming request needs context; a document needs to be associated with the work it supports; a draft reply needs a person to decide whether it is appropriate. Organizing the traffic gives the team a more useful starting point for the next conversation.
The engine before the application
Intake, research, document ingestion and prospect refresh are operating workflows. The deal-origination engine is running; the application rollout around it remains in development.
AcquireDesk was the earlier application direction. AME is its successor. Keeping that distinction visible avoids treating an evolving application as a finished product.
The buy-side work looks for possible acquisition targets, including businesses that are not already on the market. Intake, research and prospect refresh support that ongoing origination process. Document ingestion brings received material into the work rather than leaving it as another disconnected item in an inbox.
Keep the broker in the decision
Drafting, organizing and finding possible next steps support the broker’s work. The broker remains responsible for the client relationship and the decisions made in it.
A workflow needs a clear boundary between preparing a response and sending it. Our account here describes the work and its status without promising a universal control across every connected system.
Let actual work shape the interface
Starting with a working process gives the application a concrete job. The team can identify which information belongs together and which handoffs need attention before those choices become permanent screens.
An operations interface and a support runbook accompany the workflows. The interface gives the team a place to work with the system; the runbook records how to respond to uncertainty. Together they connect the agent work to the people who know the transaction and the client relationship.
Questions & answers
A few useful distinctions
What is already operating?
Intake, research, document ingestion and prospect refresh are operating, alongside the deal-origination engine. The application rollout is a separate workstream.
What is AME?
AME is the successor application to AcquireDesk. Its rollout is developing around the brokerage’s operating workflows.
What does the inbox work include?
Email triage and staged draft replies, with the brokerage’s people responsible for the client relationship and the decision about a response.
What is buy-side origination doing here?
It supports the search for potential acquisition targets, including businesses that are not already listed for sale, through research and ongoing prospect work.
Why build the engine before the application?
Running the workflow first helps reveal which information and handoffs the team actually needs. Those needs can then shape the application.
How are exceptions handled?
The engagement includes a first-line support runbook and an operations interface, giving the team a documented route for uncertainty and follow-up.
Public sources
These links provide the public material and background identified below. Client engagements are described by type.
- How we work
Background on the Zen Aegis method; not an independent audit of a private engagement.