Relationships bring the work.Structure keeps it moving.

The agency model

A roster is not a renamed contacts table.

Separate the person, the representation relationship and the commercial work. A talent record may have multiple representatives or territories. A brand can work through different agencies and contacts. A brief may involve several people, while a confirmed booking carries its own dates, deliverables and terms.

We map those relationships before designing the interface. The team should be able to move from a client to past briefs, from a talent record to relevant opportunities and from a booking to the information needed for delivery. A generic deal with every detail buried in notes is difficult to run.

The scope also defines who can view sensitive commercial or personal information, what can be shared externally and which records remain useful when a representative changes role. Access is part of the agency model, not a last-minute preference.

Commercial workflow

Connect the brief to the booking and the handover.

Start with enquiry intake, qualification, shortlist preparation and commercial discussion. Decide what makes an opportunity ready to advance: a usable brief, confirmed dates, an owner and a clear next step. Required information should be visible instead of scattered across a chain of messages.

Bookings and delivery need their own lifecycle. The CRM can track agreed deliverables, internal responsibilities and invoice status through a supported accounting connection. Commission, rights, exclusivity and territorial rules require specific scoping; they are not assumed to be universal talent features.

We design the report around the management decision: open opportunities by owner, confirmed work awaiting a handover or bookings with missing information. Revenue, commission and cash collected should remain distinct measures with clear source data.

The agency agent

Prepare the work without inventing the agreement.

An agent can summarise an incoming brief, identify missing information and prepare a follow-up from permitted records. It can assemble meeting context or propose handover tasks. The representative reviews the sources and edits the output before consequential actions.

An agent must not infer that talent is available, a fee is agreed or usage rights have been approved merely because a discussion mentions them. Those facts need explicit records and the appropriate person’s decision. Connections to mailboxes, calendar or external roster tools are scoped and verified separately.

Start with the operation

Build the first complete agency journey.

For discovery, bring a representative brief, an opportunity that became a booking and one that stalled. Show how the team currently tracks talent, commercial information and delivery. We use those examples to define the first release and acceptance scenarios.

Meibo is our own CRM product in development and includes agency-oriented records and reviewed workflow tools. It gives us direct experience of the daily product decisions involved: record editing, pipeline views, follow-up context and handover. We assess the reusable components against the requirements of your agency.

The proposal identifies the build investment from £50,000, the agreed ownership model, migration coverage and running costs. Specialist modules are priced as requirements rather than hidden behind a broad promise to handle everything a talent agency does.