# Overview

Account Research harnesses AI to empower RevOps teams to address critical data gaps that complicate strategic decisions, such as segmentation, territory design, and ABM prioritization. 

These gaps often arise from the limitations of bulk data enrichment and the subjective nature of human-level research conducted by sales reps. By providing comprehensive account information, Account Research merges the adaptability of human insights with the scalability of software solutions.

<figure><img src="https://2378295204-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUYXbv7c6RsZzQ00WCDTM%2Fuploads%2FVcxHyotX5aLpmnsvztCj%2Fapp.gradient.works_tasks_taskType%3DMARKET_MAP(desktop).png?alt=media&#x26;token=b5378584-1688-4628-977e-6f7b202d3cb4" alt=""><figcaption></figcaption></figure>

### Introduction

While bulk data enrichment delivers essential data points, organizations often struggle to transform these attributes into actionable insights for company-wide decisions. On the other hand, rep prospecting tools assist sales teams with targeted outreach but fall short in facilitating systematic prioritization.

This disconnect results in less accurate and efficient segmentation, territory planning, and account prioritization. Many teams attempt to bridge this gap through outsourcing, which can be both challenging and costly.

**Account Research** automates tasks traditionally handled by human teams, offering a cost-effective and scalable alternative.&#x20;

### Video Introduction to Account Research

{% embed url="<https://8216850.fs1.hubspotusercontent-na1.net/hubfs/8216850/Account%20Research%20Launch%20Video.mp4>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gradient.works/kb/account-research/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.