> For the complete documentation index, see [llms.txt](https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/selling-kurv/ideal-customers.md).

# Ideal Customers

Who to target — the merchants where Kurv is an easy yes.

Kurv can serve almost any merchant, but some are a faster, happier yes than others. Spend your time where the fit is strongest.

## Strongest-fit profiles

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Small &#x26; mid-sized retailers</strong></td><td>Want fast checkout, tap-to-pay, and real inventory — without enterprise cost.</td><td></td></tr><tr><td><strong>Restaurants &#x26; bars</strong></td><td>Need tips, splits, and pay-at-the-table that speed up turnover.</td><td></td></tr><tr><td><strong>Field &#x26; home services</strong></td><td>Bill on-site by invoice or Tap to Pay; value getting paid before they leave.</td><td></td></tr><tr><td><strong>Growing multi-channel sellers</strong></td><td>Take payments in person, online, and by phone — want it all in one place.</td><td></td></tr></tbody></table>

## Buying signals to listen for

* "My statements are confusing and full of fees I don't understand."
* "Approvals take forever with my current processor."
* "I can never reach a real person for support."
* "I run one system in-store and a totally different one online."
* "I want to start taking cards but don't want to buy a bunch of hardware."

{% hint style="success" %}
Any one of those lines is an open door — map it straight to a [differentiator](/1roOeoqsO7DNkeNJG2xS/selling-kurv/why-kurv.md) and a [product](/1roOeoqsO7DNkeNJG2xS/products-and-services/products-kurvmerchant.md).
{% endhint %}

## When to qualify carefully

{% hint style="warning" %}
Very high-risk categories, extremely high ticket sizes, or businesses needing deep custom POS integrations may need a tailored conversation. Loop in your Kurv contact early rather than over-promising.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/selling-kurv/ideal-customers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
