Time for a new approach
to agency management systems?
Agency management systems appeared when computers became affordable for agencies
and the delays of old-fashion service bureaus became unacceptable. Now, the
responsiveness of online systems is being combined with the convenience and
economies of scale of Internet hosting yielding the modern service bureau
or ASP for agencies.
But does perpetuation of the traditional management system, even in ASP form
make sense? Maybe not. After all, management systems force the duplication
of data — data carriers already have and thus all the needs for and
problems connected with Interface. Maybe it makes more sense to think about
creating hybrid management systems — ASPs that save only the data that
carriers don't, mostly high-level customer and some accounting data, transparently
linking into and using carrier and other sources of data when needed.
- Does the idea of a hybrid management system ASP make any sense? Is it
technically feasible?
- If agents don't store policy detail, how can they move individual policies
or books to other carriers without doing significant re-entry?
- Does it make sense to rely on carrier systems — technically or commercially?
- Would a hybrid management system really obviate the need for agency/company
interface or would it just switch the problem from databases and interface
to constantly re-mapping to changing carrier sites?
- Are current management systems too narrowly focused and fail to handle
the broadening inventory of products and services independent agents are
embracing — like life, health, benefits, and consulting services?
- Should management systems morph into integration platforms that allow
agents to pick and choose among a wide variety of services assembled by
but not necessarily created or owned by the vendor?
We welcome your participation in this forum. Please
us with your comments, questions, and your own point-of-view!
