> For the complete documentation index, see [llms.txt](https://pingbusiness.gitbook.io/pingbusiness/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pingbusiness.gitbook.io/pingbusiness/use-case/by-use-case/launching-an-mvp-and-getting-your-first-sale-in-a-weekend.md).

# Launching an MVP and Getting Your First Sale in a Weekend

**How fast can I actually get a paid product live?**

Fast enough that payments shouldn't be the reason you delay shipping. Copy a prompt from the PingBusiness template library into Claude or Cursor, and the checkout, API calls, and webhook handling are wired up in one pass - no payments experience required.

**A realistic weekend timeline:**

* **Friday night:** build the core product
* **Saturday:** create your PingBusiness account, submit the merchant application, and start identity verification
* **Sunday:** copy a checkout prompt into your AI assistant, connect it to your app, and go live in test mode
* **Monday:** flip to real mode once your application is approved, and take your first real payment

The point isn't skipping the merchant review - it's not losing days to hand-building a payments integration while your application is being reviewed in parallel.


---

# 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://pingbusiness.gitbook.io/pingbusiness/use-case/by-use-case/launching-an-mvp-and-getting-your-first-sale-in-a-weekend.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.
