> 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/start-here/the-pitch.md).

# The 60-Second Pitch

The fast, repeatable way to explain Kurv in about a minute.

When a merchant asks "so what's Kurv?", here's the version you can deliver in a minute — and the structure behind it.

{% hint style="success" %}
"Kurv is modern payment processing built to be simple. You take payments however you want — countertop, handheld, phone, online — all on one dashboard, one deposit, and one U.S. support team that actually answers, 24/7. Pricing is transparent, with a model to fit your business, and there are free terminal options to get started. Most merchants are **approved in about a day**. It's payments without the headaches — and it already powers **30,000+ businesses**."
{% endhint %}

## Run it as a three-step conversation

{% stepper %}
{% step %}

### Anchor on simplicity

Open with the promise: *Modern payments, made simple.* Most merchants have a story about a clunky terminal, a surprise fee, or a support line that never picked up. You're the opposite of that.
{% endstep %}

{% step %}

### Match to how they get paid

Ask one question: *"How do your customers pay you today?"* Their answer points you straight to the right [product](/1roOeoqsO7DNkeNJG2xS/products-and-services/products-kurvmerchant.md) or [solution](/1roOeoqsO7DNkeNJG2xS/sales-tools/solutions.md).
{% endstep %}

{% step %}

### Land the proof points

Close the loop with what sets Kurv apart: **transparent pricing with free terminal options**, **\~1-day approval**, and **24/7/365 U.S. support** — trusted by 30,000+ businesses. Then set the next step.
{% endstep %}
{% endstepper %}

## The proof points to remember

| Say this                                   | Because                                                                                                        |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------- |
| **Transparent pricing, your way**          | Three clear models — Flat Rate, Zero Cost, or Interchange Plus — plus free terminal options for new customers. |
| **\~1-day approval**                       | Proprietary underwriting means most merchants are up and running fast.                                         |
| **24/7/365 U.S. support**                  | 350+ real people, any hour — a genuine differentiator against big processors.                                  |
| **30,000+ businesses · 1M+ payments/week** | Proven scale and reliability.                                                                                  |


---

# 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/start-here/the-pitch.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.
