Bloomberg Terminal Pricing for Small Investment Teams

01 / RESEARCH GUIDEThe short answer

A small team's terminal budget involves people, roles and permissions as well as software. Multiplying a headline price by the number of employees can miss the real access requirement. Map who needs to do what, when they need to do it and how the research output moves between colleagues.

02 / RESEARCH GUIDEBuild a role and task matrix

List researchers, portfolio reviewers, operations staff and anyone else who depends on the output. For each role, record the recurring tasks and the information required. Distinguish using a platform from receiving an authorized research summary produced by someone else. Ask the supplier how the proposed licensing arrangement covers those activities. Do not design a budget around shared credentials or assume that one seat can serve every employee. A role matrix is especially valuable when a team mixes part-time research with other responsibilities: headcount alone does not explain either access needs or permitted use.

03 / RESEARCH GUIDEDescribe the handoff

Follow a typical assignment from the initial question through data gathering, analysis, review and storage. Note where colleagues need direct access, where spreadsheet work occurs and where information leaves the platform. Ask about the permissions relevant to those handoffs, including internal distribution and exports. A demonstration that works for one analyst may leave a reviewer unable to check the underlying evidence. Conversely, buying identical access for everyone without examining the process can waste budget. The objective is a workable, authorized team process with clear responsibility for the evidence, not simply a screen on every desk.

04 / RESEARCH GUIDESeparate the quote from operating effort

Keep supplier charges distinct from internal onboarding, administration, documentation and support time. Identify who will manage access changes and vendor questions. If a team needs several data packages, specify which role needs each package and why, then obtain confirmation rather than guessing a bundle discount. Use a common service period when comparing quotes. A lower subscription total may require more manual consolidation or checking. Estimate that work using a pilot and disclose the assumptions. Small teams often have little spare capacity, so a fragile handoff can matter as much as the direct recurring charge.

05 / RESEARCH GUIDETest staffing changes before approval

Ask how new hires, departing employees, temporary absence and role changes are handled. Keep the supplier's written explanation with the quote. Plan a trial in which one person gathers information and another reconstructs the result from the saved output. Record unresolved access or data-rights questions. At renewal, compare actual usage by role with the matrix created at the start. This gives the team a basis for discussing changes without assuming either that every seat is indispensable or that unused credentials may be informally passed around. Administrative continuity should be part of the purchasing requirement.

06 / RESEARCH GUIDEA practical example

Illustrative team pilot: an analyst prepares a company review, a colleague checks the financial definitions and a manager reads the decision memo. Give each participant a task and record every place the process needs direct platform access. Ask the supplier to explain the appropriate arrangement for those roles and for the intended internal output. Then repeat the handoff with a second company, so the result does not depend on one analyst's memory. Add the confirmed charges and measured administration effort to the budget. This is an evaluation design, not a claim that a particular Bloomberg team package or discount is available.

07 / RESEARCH GUIDEA working record to keep

Keep a team access worksheet with a row for each role and columns for task, frequency, required information, direct access and permitted output. Add the supplier confirmation reference rather than treating your initial access design as approved. A separate handoff log records who produced the research, who reviewed it and which sources were available to each person. During a pilot, ask the reviewer to identify one value, one definition and one unresolved question without assistance from the original analyst. If that cannot be done, investigate the saved output or access arrangement before adding more users. At renewal, compare the original matrix with observed work and remove assumptions that no longer describe the team. This document should remain useful when staff change, because it records responsibilities and requirements rather than a temporary arrangement dependent on one person's memory or a set of informally shared login details.

08 / RESEARCH GUIDEKeep the commercial evidence separate

A useful purchasing record distinguishes three kinds of information. The first is the supplier's current written proposal. The second is your own requirement and the reason it matters. The third is an internal estimate, such as staff time or the expected frequency of a task. Keep these categories visible instead of blending them into a single authoritative-looking total. A quote can confirm a charge without proving a productivity benefit, while a successful research exercise can show practical fit without establishing the contract terms.

Give unresolved questions an owner and a next action. An unknown amount or permission should remain unknown until an appropriate answer is obtained. If the question changes, update the requirements version and ask whether the offer still applies. This is particularly useful for new users, additional markets and different downstream uses of data. Keep the original wording linked so a short summary does not accidentally broaden what was confirmed.

Before approval, ask a reader who did not attend the demonstration to explain the intended work, full commitment, remaining external tools and unresolved conditions from the record alone. If they cannot, improve the document. Repeat this review after a representative research cycle using actual use and effort. The goal is a clear purchasing decision that can be revisited when circumstances change, rather than a universal claim that one terminal price or subscription arrangement fits every researcher.

09 / RESEARCH GUIDEYour review checklist

• Map named roles to recurring tasks and ask the supplier how the proposed access arrangement covers each activity.
• Test the analyst-to-reviewer handoff so the saved output can be checked by the people responsible for it.
• Separate confirmed vendor charges from estimated training, administration and manual consolidation effort.
• Clarify user changes and absence procedures in writing before relying on them in the team's operating plan.

10 / RESEARCH GUIDEFrequently asked questions.