Retainer hour tracking for UX researchers and user research consultants.
UX research retainers give product teams a fixed monthly capacity for studies, interviews, synthesis, and advisory — but product teams routinely underestimate how many hours a single well-run study requires. A five-session usability study isn’t five hours: it’s study design, screener development, recruitment coordination, five sessions, affinity mapping, synthesis, and a shareable insight report. HourTab gives the product team a live balance URL so they can see exactly how much research capacity remains before requesting the next sprint’s study.
Free forever for your first retainer · no credit card.
Why UX research retainer hours disappear faster than expected
-
Product teams measure research in sessions — researchers measure it in full cycles.
A product manager who books “5 user interviews” is thinking of 5 hours. The researcher knows that 5 interviews require 2 hours of protocol development, 3 hours of recruitment and scheduling coordination, 5 hours of sessions, 6 hours of synthesis and affinity mapping, and 3 hours of insight writing — a total of 19 hours. When the PM submits another study request halfway through the month, they’re surprised to learn that the first study already consumed the entire retainer. The live balance surfaces that reality before the second request, not after.
-
Research advisory hours are real but invisible to product teams.
A UX research retainer isn’t just studies — it’s also the 1-hour conversation about what to study next, the 30-minute review of a PM’s survey instrument, the 2-hour research ops support for setting up Dovetail, and the ongoing advisory on how to apply past findings to new feature decisions. These advisory interactions are valuable, but they don’t produce a report. Without a work log, they disappear — and clients who only see the formal study deliverables underestimate the advisory layer they’re actually receiving.
-
Cross-team research requests fragment the retainer without a single owner tracking the balance.
When multiple product teams (growth, core product, platform) share a research retainer, each team submits requests without visibility into what the others have consumed. The researcher becomes the gatekeeper for a budget that no one else can see. A live balance URL, shared with all stakeholders, creates distributed visibility: each team checks the balance before submitting their request, and the scope conversations happen between teams, not just between each team and the researcher.
How it works for UX researchers
-
1
Create the retainer. Enter the client name, monthly hour cap, and billing cycle. For retainers split across multiple product teams, set the total pooled hours and share the balance URL with all stakeholders — everyone sees the same remaining capacity, preventing cross-team overbooking.
-
2
Log hours by research phase. Export from Toggl, Harvest, or your time tracker. Use phase-level descriptions in each entry: “usability study — protocol development, 2h”; “recruitment coordination, 3h”; “sessions x5, 5h”; “synthesis + affinity mapping, 6h”; “insight report, 3h.” That granularity is the product team’s education about what a study actually costs.
-
3
Share the URL in the research Slack channel or sprint planning doc. Product managers check the balance before adding a research request to the next sprint. The prioritization conversation happens in the team, not between the PM and the researcher. At quarter end, the full work log is the research portfolio — every study, advisory session, and support task documented in one place.
Product teams that see the full research cycle cost plan more realistic research programs — and get better outcomes.
“The biggest challenge in research retainers is that product teams think in sessions and researchers think in full cycles. A shared balance URL bridges that gap.”
— User research consulting practice guide
HourTab makes the full research cycle cost visible to the team that’s requesting the work.
Frequently asked questions
What does a UX research retainer typically include?
UX research retainers cover ongoing research capacity for a product team: study design, participant recruitment, moderated and unmoderated testing, user interview sessions, synthesis, insight reporting, and research advisory. A typical monthly retainer might cover 1–2 moderated studies with full synthesis, plus ad hoc expert advisory. Clients who only think in terms of ‘interviews’ underestimate the full research cycle.
How do UX researchers show clients the full cost of a research study?
Breaking a study into phases in the work log makes the true cost visible: ‘research plan + screener design: 2h’, ‘participant recruitment: 3h’, ‘5 moderated sessions: 5h’, ‘affinity mapping + synthesis: 6h’, ‘insight report: 3h’ = 19h for one study. Product managers who think of a usability study as ‘5 interviews’ are often surprised — and that surprise is best surfaced before the study kicks off.
How do UX researchers handle product teams that want multiple studies per month?
A live balance creates the prioritization conversation. When a product team wants a usability study, 3 stakeholder interviews, and a competitive review in the same month, the researcher can show the math and ask: ‘Your retainer is 20 hours. The usability study takes 18 hours. What are the two priorities?’ That data-driven scope conversation is only possible when both parties can see the balance in the same view.
Can UX researchers track research prep separately from session time?
Yes — and it builds accurate expectations. When clients can see that a 5-session study requires 3 hours of prep and 6 hours of synthesis in addition to the 5 hours of sessions, they stop thinking of research as a ‘quick interview’ and start thinking of it as a full research cycle. That shift is the foundation of a research retainer relationship where the team respects both the time and the process.