Skip to content

Desktop Research

Most questions a team wants to field-test already have partial answers in print. Desktop research finds them first, mapping the market, the competitors and the prior evidence, so primary research is spent only on what nobody yet knows.

What is desktop research?

Desktop research is secondary research: market analysis, competitor benchmarking, trend scanning and literature review conducted from existing sources rather than new fieldwork. It maps what is already known about a market, its players and its rules, so primary research spends its budget on the questions nobody has answered yet.

Why start with desktop research?

Because it is the cheapest evidence available. How big is this market, who else is in it, what users complain about, what the regulator requires. Most of those questions already have partial answers in industry reports, competitor sites, app-store reviews, support forums, academic work, and the analytics an organisation already owns. Desktop research collects and reads all of it before anyone pays field-study prices for an answer sitting in a report.

The deeper value is framing. A desk phase ends with a map of what is known, what is contested and what is genuinely open. That map is the brief for everything that follows. Primary research aimed at open questions is sharp and affordable; primary research launched without the map spends its first weeks rediscovering the public record.

What desktop research covers
Question
How big is the opportunity?
Source
Market reports, industry data, public filings
Output
Market sizing and growth summary
Question
What are competitors doing?
Source
Rival products, pricing pages, reviews, changelogs
Output
Competitor teardown and feature map
Question
Where is the category heading?
Source
Trend reports, funding news, adjacent markets
Output
Trend scan with design implications
Question
What must the product comply with?
Source
Standards, regulation, platform guidelines
Output
Constraints and compliance checklist
Four desk questions, and the shape their answers arrive in.

What does competitor benchmarking involve?

Working through rival products the way a user would. We sign up, onboard, buy and cancel, walking the flows that matter. We record where each competitor is strong, where it is weak, and what it charges. Around the products themselves sit the positioning signals: how each rival describes itself, who its marketing speaks to, and what its pricing page says about the customer it actually wants.

The output is not a feature checklist to copy. Chasing parity is how categories converge into sameness. A good benchmark separates table stakes from differentiators: the things users now expect from any product in the category, and the gaps no competitor has filled. The first list keeps a roadmap honest; the second is where the opportunity lives.

Where we stand on Desktop Research

  • 01Desktop research is secondary research. It reads what exists before paying to create new evidence.
  • 02It is the cheapest evidence a project can buy: days at a desk against weeks in the field.
  • 03A good desk phase ends with a map: what is known, what is contested, what only primary research can settle.
  • 04Competitor benchmarking separates table stakes from genuine gaps; it is not a feature list to copy.
  • 05Every claim is triangulated; a figure that appears in one report is a lead, not a fact.

Work featuring Desktop Research

See all work →

The London Practice

Psychotherapy Practice Website

A website for a London psychotherapy practice, built around finding the right practitioner.

Web DesignContent Management SystemBrand AuditDesktop ResearchPrototyping

RT7 Digital

Amazon Specialist Website

Branding and a website for the agency that runs everything around a brand's Amazon listings.

Web DesignBrand IdentityStyle GuideDesktop ResearchBrand Audit

BillyGoat

Bill Consolidation and Splitting Tool

A marketing site and brand for a bill consolidation and splitting product.

Web DesignBrand IdentityContent DesignContextual ResearchDesktop Research

What’s included in Desktop Research?

Competitor benchmarking
Rival products worked through as a user would: flows, features, pricing and positioning.
Market analysis
The opportunity and its segments sized from industry reports, public data and filings.
Trend analysis
Where the category is moving, read across products, funding and adjacent markets.
Standards & regulation
Standards, regulation and platform guidelines read for what the product must comply with, delivered as a constraints checklist.
Literature & data review
Published studies, prior research and the data an organisation already holds, collected.
Heuristic review
An expert pass over a product, yours or a rival's, against established usability principles.
Final questions
  • What is the difference between desktop and primary research?

    Desktop research reads evidence that already exists: reports, competitor products, reviews, published studies. Primary research creates new evidence by going to users directly, through interviews, field studies and testing. Desk work is faster and cheaper, so it comes first: it establishes what is known and hands primary research a shortlist of questions worth the spend.
  • What sources does desktop research use?

    Industry and market reports, public filings, competitor products and their pricing pages, app-store reviews, support forums and communities, academic literature, standards and regulation, and the analytics an organisation already holds. That last one is often the most valuable and the least read.
  • How long does desktop research take?

    Focused desktop research typically runs one to two weeks: long enough to map a market, tear down the main competitors and read the prior evidence. Broad multi-market scans run longer. It is measured in days where field work is measured in weeks, and that is why it comes first.
  • Is desktop research enough on its own?

    Sometimes, for early strategic calls: whether a market is worth entering, where competitors cluster, what regulation demands. But it can only report what others have recorded, and nobody has published how your users behave with your product. Questions of behaviour and usability need primary research; desk work makes that research sharper, not unnecessary.

Start with a conversation.