> For the complete documentation index, see [llms.txt](https://avatar-social.gitbook.io/bkindness/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avatar-social.gitbook.io/bkindness/readme/why-now.md).

# Why now?

• 📉 Small businesses are struggling to retain customers in an attention-fragmented world.

 • 📱 Gen Z and Millennials are bored of traditional loyalty systems — they want experiences.

 • 🎮 The gamification industry is booming. People crave dopamine, not punch cards.

 • 🌐 Emerging economies (SEA, LATAM, Africa) are ripe for low-cost, high-impact digital transformation tools.

 • 🚀 BKINDNESS taps into this momentum by mixing hyperlocal rewards, discovery, and purpose into a platform that feels fun and frictionless — but delivers real business results.

<br>

The future belongs to platforms that make people feel something. BKINDNESS makes them feel rewarded, seen, and part of something bigger.


---

# 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://avatar-social.gitbook.io/bkindness/readme/why-now.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.