> For the complete documentation index, see [llms.txt](https://docs.salesmonk.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.salesmonk.ai/readme.md).

# Welcome to SalesMonk

<figure><img src="/files/uUAapNQUANxAnyRdWLtR" alt=""><figcaption></figcaption></figure>

### What SalesMonk Is

SalesMonk is an AI-powered Go-To-Market (GTM) platform built to help B2B companies consistently generate qualified sales meetings by unifying inbound intent, outbound execution, and automation into a single system.

Most GTM stacks today are fragmented:

* One tool tracks website visitors
* Another runs outbound campaigns
* Another logs CRM data
* Another handles analytics

SalesMonk replaces this fragmentation with a connected GTM layer that sits across inbound and outbound, allowing teams to:

* Identify buying intent early
* Act on it automatically
* Measure outcomes, not activity

***

### Who It Is Built For

SalesMonk is designed primarily for:

* B2B SaaS companies
* Growth-stage and mid-market teams
* Revenue, sales, and demand generation leaders

It is especially valuable for teams that:

* Have meaningful inbound traffic but low conversion rates
* Run outbound campaigns without real-time intent context
* Want inbound and outbound to reinforce each other
* Care more about meetings and pipeline than vanity metrics

SalesMonk is not built as a generic CRM or email tool.\
It is built as a GTM execution and intelligence layer.<br>

### Core Problem It Solves

Most companies struggle with the same GTM problems:

1. Inbound intent is underutilized\
   Visitors browse pricing pages, product pages, or docs — but sales never acts in time.
2. Outbound is disconnected from intent\
   Outreach is cold, generic, and poorly timed.
3. Signals are scattered\
   Website behavior, CRM data, and outbound engagement live in silos.
4. Teams optimize the wrong metrics\
   Emails sent, visitors tracked, or clicks — instead of meetings booked.

SalesMonk solves this by:

* Making intent visible
* Making action automatic
* Making meetings the primary KPI

***

### Inbound + Outbound GTM Philosophy

SalesMonk is built on a simple philosophy:

Inbound captures intent.\
Outbound amplifies intent.\
Automation connects the two.

Instead of treating inbound and outbound as separate motions, SalesMonk treats them as one continuous GTM system.

For example:

* A pricing page visitor is not just an inbound lead
* They are an outbound opportunity — immediately

This philosophy drives the entire product architecture.

***

### What “Qualified Meetings” Mean in SalesMonk

A qualified meeting in SalesMonk is not just a calendar event.

It is a meeting that:

* Is associated with a known account
* Is backed by behavioral or intent signals

  * Is logged through inbound or outbound flows
  * Can be tied to pipeline and revenue

  SalesMonk is optimized around meeting quality, not meeting volume.

  <br>

***

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.salesmonk.ai/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
