Decide · the cost of a quarter

How many hours does it take to respond to an RFP? A costed quarter

No regulator or independent study publishes how many hours an asset manager spends answering an RFP or updating its consultant databases, so the only reliable number is one you build. This guide builds it in the open, field by field and wage by wage, and shows which inputs move it, using a sample firm in Consultant Database Management.

Updated · 12 min read

How many hours does it take to respond to an RFP? For an asset manager the honest answer is that it depends on four things you can count: how many fields and questions the response carries, how many seconds each takes to find and enter from an approved source, how many review loops compliance and the content owners run, and how many corrections follow. No regulator or independent study publishes a benchmark, and figures quoted in vendor surveys are not a basis for a budget. This page builds the hours and the cost for one quarter of consultant database updates, the recurring work behind every RFP, with BLS wage data and the sample firm in Botminds' Consultant Database Management, and shows how to measure your own.

The unit matters more than the total. An RFP is a one-off; the consultant database cycle comes back every quarter, carries the same figures and feeds every RFP and DDQ that follows. Pricing the field, not the document, is what lets a head of distribution compare one quarter with the next and one way of working with another.

The hours in a response cycle, term by term

+

Entry

fields × seconds per field ÷ 3,600

Finding the approved value, checking its date and typing or pasting it into each portal, template or answer.

RFP and database coordinator

+

Review

+ regulated fields × reviewer seconds ÷ 3,600

Compliance re-checking each performance and assets figure against its source and the presentation rules.

Marketing compliance

+

Chasing

+ owners × hours per owner

Commentary from portfolio managers, team changes from HR, marks from the fund administrator, translations.

Coordinator, with consultant relations

+

Corrections

+ errors × hours per correction

Re-submission, a correction note, re-approval and the call to the consultant.

Everyone above

Our formula. Multiply each term by a loaded hourly cost for the people doing it to turn hours into money.

How many hours does it take to respond to an RFP? Start from the field

A field is anything a portal or questionnaire asks for separately: one return for one period, one assets figure, one bio, one fee line. Count them before estimating anything. Take the sample firm in Consultant Database Management, the fictional Quillfield Capital: its third-quarter 2026 cycle covers 60 strategies on 12 consultant portals in 300 profiles, which comes to 9,012 fields, about 30 per profile.

Time per field is the second input. The estimate published with the solution uses about 40 seconds a field for a person working by hand: open the source, confirm the period and definition, enter the value in the portal's format. At 40 seconds, 9,012 fields take about 100 hours of entry alone. That is the floor, because it assumes every value is ready, final and unambiguous when the coordinator reaches it.

For a single RFP the same arithmetic applies, with a different mix. Most answers come from the library with a date change; some need a new figure or a redrafted paragraph; a few are new questions with no approved answer at all. Log a sample of each kind on one RFP and the totals follow; guessing them is where budgets go wrong.

Pricing one RFP, question by question

The same method prices a single RFP if the questions are sorted by how much work each needs. Most fall into four groups: answers reused from the library with only a date change, answers that need current figures filled in, answers that need a paragraph redrafted, and questions the library cannot answer at all. Time a few of each on one real RFP and the rest is multiplication. The table shows the arithmetic on an illustrative 250-question RFP; every quantity in it is an assumption to replace with your own log.

An illustrative 250-question RFP: the new questions cost the most

Kind of questionCountMinutes eachHours
Reused from the library, date updated150410.0
Figures filled from current sources601010.0
Paragraph redrafted by its owner303015.0
New question, no approved answer109015.0
Compliance review of performance and assets answers6033.0
Assembly, formatting and submission——6.0
Our illustrative arithmetic, not a benchmark: 59 hours in all, about $3,200 at the loaded rates below. Ten new questions take longer than 150 reused ones, which is why the library's coverage, not typing speed, decides the cost of an RFP.

Two numbers in that table deserve attention when budgeting. The ten new questions take half as many hours again as the 150 reused ones, 15 against 10, so a library that grows after every RFP pays for itself. And the sixty figure questions are where errors enter: filled from the right source they take minutes, copied from last year's answer they take seconds and carry last year's numbers.

Typical RFP response time vs the hours inside it

Response time and response hours are different measures. The response window is set by the issuer in the RFP document and runs in calendar days; the hours are the effort the firm spends inside it. A response due in three weeks may take forty hours or two hundred, depending on the questionnaire and on how much of the answer the firm can source quickly. Consultant database deadlines work the same way: in the sample cycle the twelve portals fall due between October 22 and November 13, while the effort is concentrated in the weeks after the quarter's returns are locked on October 9.

Measure both, because they fail differently. Long response times usually mean waiting: for locked returns, for a portfolio manager's commentary, for a private fund's marks. High hours usually mean rework: values copied, checked, corrected and checked again. A tool or a hire that fixes one may do nothing for the other.

What an hour costs: 2025 BLS wages and employer cost

The Bureau of Labor Statistics has no occupation for RFP writers or database coordinators, so the wage input rests on a mapping, which is ours. The closest occupation for the people doing the entry is market research analysts and marketing specialists; for the reviewers, compliance officers. Wages are not the whole cost: BLS's employer-cost survey found that wages and salaries made up 70.0% of private-industry employer compensation costs in June 2026, with benefits the rest (BLS, Employer Costs for Employee Compensation, September 9, 2026).

A loaded hour of entry and an hour of review cost about the same

RoleMedian hourly wage, May 2025Loaded hourly cost (wage ÷ 0.70)
Entry: market research analysts and marketing specialists (13-1161)$37.87$54.10
Review: compliance officers (13-1041)$38.81$55.44
Wages from the BLS Occupational Outlook Handbook, 2025 median pay (May 2025 wage data), all industries. The loaded cost applies BLS's private-industry share of wages in total compensation (70.0%, June 2026) and is our approximation; it leaves out office space and systems. Asset managers in large financial centres often pay above national medians, so use your own payroll where you can.Source: BLS OOH, Market research analysts; BLS OOH, Compliance officers; BLS ECEC

What does a quarter of consultant database updates cost?

Put the inputs together and one quarter of the sample firm's database cycle costs, by hand, somewhere around twelve thousand dollars in loaded staff time before a single correction, with entry the largest term. The build below is illustrative: the field count is the sample firm's, the 40 seconds is the solution's published estimate, and the other assumptions are ours, stated so they can be replaced with a firm's own logs.

One sample quarter by hand: entry dominates, corrections decide the tail

Entry: 9,012 fields × 40 s = 100 h
$5,417
Self-check: 9,012 fields × 10 s = 25 h
$1,354
Compliance review: about 1,300 figures × 60 s = 22 h
$1,201
Chasing owners: 30 owners × 1 h
$1,623
Submitting and screenshots: 300 profiles × 5 min = 25 h
$1,353
Corrections: 12 errors × 2 h, across three roles
$1,314
Illustrative arithmetic at the loaded rates above ($54.10 for entry, self-check, chasing and submitting; $55.44 for review; corrections at the average of the two). Field count from the fictional sample firm in Consultant Database Management; the 40-second entry time is the solution's published estimate; every other quantity is our assumption. Total about $12,260 (sum of the rounded bars, $12,262), or about $1.36 a field.

Per field, that is about $1.36, and per profile about $41. The per-field number is the one to watch, because it scales with the business: a firm that adds a strategy to eight portals adds roughly 240 fields, or about $330 a quarter, before anyone writes a sentence of commentary. It also shows why entry speed alone is the wrong target. Halving entry time saves about $2,700 a quarter; a single error that reaches a consultant and triggers a correction across three people costs more than a hundred dollars and, unlike entry, carries regulatory weight.

Which inputs move the total most

Seconds per field and the error count move the total far more than wages. The sensitivity below changes one input at a time from the base case and shows the change in the quarter's cost.

What one change does to the cost of a quarter

Entry takes 60 s a field instead of 40
+$2,708
Two more portals at the same depth (+1,502 fields)
+$1,554
30 errors reach consultants instead of 12
+$1,972
Compliance reviews each figure in 2 min instead of 1
+$1,201
Wages 25% above the national median
+$3,066
Our illustrative arithmetic on the base case above. The portal case adds entry, self-check and a proportional share of review and submission. Wages 25% higher scale every term; local pay data are worth using for that reason.

Two lessons follow. First, a quarter's cost is a function of process, not headcount: the same team spends about a fifth more when entry slows from 40 to 60 seconds a field, which is what happens when sources are scattered or definitions unclear. Second, errors are cheap to count and expensive to ignore. Each one costs a correction cycle, and the Marketing Rule's general prohibitions apply to the figure that went out in the meantime (17 CFR 275.206(4)-1(a)).

The hours nobody budgets: read-backs, corrections and examiner requests

Three costs rarely appear in a staffing plan. Read-backs: after submitting, someone should confirm the portal stored what was sent, because portals round, truncate and occasionally reject fields silently. Corrections: when a value is wrong on a live profile, the fix touches the coordinator, compliance and consultant relations. And requests from examiners: an adviser must keep every record needed to support or demonstrate the calculation of the performance in its advertisements (17 CFR 275.204-2(a)(16)), and finding them by hand for a profile submitted two years ago can take days.

SEC examiners have reported the gap directly. In their April 2024 risk alert on the Marketing Rule they listed, among books-and-records deficiencies, advisers that kept no documentation supporting the performance claims in their advertisements (SEC Division of Examinations, April 17, 2024). The hours to rebuild that support after the fact are the most expensive hours in the cycle.

Read-backs as part of the cycle, not an afterthought

Submissions and receipts: 50 profiles submitted this cycle, 1,322 fields read back from the portals, 1,320 exact and 2 rounded by the portal and accepted. A banner reports an expired sign-in at Aoba Pension Research: the Submission agent paused at 6:02 a.m. and nothing was sent or lost. The Submission agent's note says the read-back also found one hand entry outside the cycle. A table lists each submission with time, portal, profiles, fields, method (data feed, web form or spreadsheet template), receipt number, read-back result and who released it.
Fictional sample data in Consultant Database Management. Every submission keeps its receipt and a field-by-field read-back, which is the evidence an examiner or a consultant asks for later.

Fields counted for you: what the agents filled and what still waits

Today screen for the RFP and database coordinator. Needs you: a conflict on one portal's strategy assets, a portal due Thursday October 22 with 24 profiles, a co-portfolio manager's departure with a notice drafted, an expired portal sign-in and 110 stale fields across 14 strategies. What the agents did since yesterday: 8,798 of 9,012 fields filled from approved sources with 214 waiting for final data, every live portal compared with three new conflicts, performance fields checked against the presentation rules, stale fields and a key-person change found, Japanese and German commentary drafted, and 40 profiles submitted with receipts and 1,058 of 1,060 fields read back exactly.
Fictional sample data in Consultant Database Management, business day 11 of the third-quarter cycle. The counts a cost model needs (fields filled, fields waiting, conflicts, read-backs) are on the coordinator's first screen.

How to measure your own RFP response time and hours in one quarter

Measure for one full cycle before changing anything. The method below takes little extra effort if it starts on the first day after quarter-end, and its output is a per-field cost the firm can defend.

Seven measurements for one quarter

  1. Count fields, not documents

    Export each portal’s field list per strategy; add the fields of every RFP and DDQ answered that quarter.

  2. Time a sample of entries

    Fifty fields across three portals, stopwatch on, from opening the source to saving the value.

  3. Log reviewer minutes

    Ask compliance to note minutes per batch and the number of figures in it.

  4. Record waiting separately

    Days between asking an owner and receiving the input are elapsed time, not effort; keep them apart.

  5. Count every correction

    Each re-submission or correction note, its cause, who touched it and for how long.

  6. Test a retrieval

    Pick one performance figure from a profile submitted a year ago and time how long it takes to produce its source.

  7. Price it

    Multiply each term by a loaded rate from payroll or the BLS medians above, and divide by fields.

Our method. The retrieval test is the one most firms skip and the one an examiner effectively runs.

Where agents change an RFP team's arithmetic, and where they do not

Agents change the entry and comparison terms most and the review and waiting terms least. In Consultant Database Management a Sourcing agent fills fields from approved sources and a Conflict agent compares every live portal value with drafts and sources, so the entry and self-check terms shrink. Compliance still approves every performance and assets figure, a portfolio manager still writes commentary, and a private fund's marks still arrive when the administrator sends them.

A quarter's business days by hand and with the agents

StepBy hand (estimate)With the agents (target)
Rebuilding the portal calendar and waiting on data20.5
Copying fields into each portal’s form or template122
Chasing portfolio managers, HR and translators42
Compliance re-checking every figure42.5
Submitting, screenshots and corrections31
Total258
Business days for a two-person team keeping 60 strategies on 12 portals. By hand is the estimate published with Consultant Database Management; with the agents is its design target, not a measured result.

Read the target with care. Eight business days is what the solution is designed to reach, measured in the live solution, and the compliance term barely falls because a person still signs every regulated figure. For the RFPs and DDQs that draw on the same figures, what an agent may draft and who signs sets out the split, and the RFP writer's seat shows what the coordinator's week becomes. To price a quarter on your own strategies, start from Consultant Database Management.

Questions people ask

How long do you have to respond to an RFP?

As long as the issuer allows. The RFP document sets the deadline, the question period and any quiet period, and public plans often publish these on their procurement pages. There is no regulatory minimum or maximum; read the instructions section first and plan backwards from the due date.

What is a typical RFP turnaround time for an asset manager?

No regulator or independent study publishes one. Turnaround depends on the issuer's window and on how much of the answer the firm can source from locked figures and an approved library. Track your own median from receipt to submission, and separately the hours spent, for a quarter before setting a target.

How many questions are in an institutional RFP?

It varies with the issuer and the mandate; there is no standard count. Count fields rather than questions, because one question can ask for returns over six periods, gross and net, against a benchmark, which is twelve or more figures to source and check.

How can an asset manager reduce RFP response time?

Fix the waiting first: lock performance on a known date, keep an approved answer library with owners and expiry dates, and know each portal's definitions in advance. Then reduce rework, by entering each figure once from its source and comparing every copy, which is where most of the hours go.

Is RFP and consultant database work a cost or an investment?

Both. The cost is measurable per field; the return is harder to attribute because consultant searches start from these profiles. Research on consultants' recommendations finds they move flows, which is why what consultant databases ask matters to the budget as much as the hours do.

Consultant Database Management.
See it on your own files.

An agentic solution from Botminds. Keeps every consultant database profile current each quarter from approved fund data Book a demo, or explore how it works.