# Mastering prompts for Kaiya Apps

### How to write an effective prompt

The quality of your prompt directly affects how close the first generated app is to what you need. A well-structured prompt usually means the blueprint is right on the first pass and only minor adjustments are needed.

A strong prompt typically includes:

1. **The primary question or goal.** One sentence is enough — *"Analyze sales performance across regions"* or *"Investigate why churn increased in Q3."*
2. **The key metrics that matter.** Naming 3–6 specific KPIs ensures they are treated as priority. Kaiya can infer metrics from the Business View, but explicit naming prevents surprises.
3. **The dimensions you want to slice by.** *"By region, by product category, by sales rep"* drives the filter options and breakdown sections.
4. **The audience.** *"For the executive team"* produces KPI-heavy, scannable layouts. *"For the operations team"* produces denser layouts with more tables and detail.
5. **Design preferences (optional).** Theme (dark or light), accent colors, spacing density. If you do not specify, Kaiya auto-designs based on the data domain.

**Weak prompts vs strong prompts**

| Weak                             | Strong                                                                                                                                       |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| "Create a dashboard for my data" | "Analyze sales performance by region and product. Show revenue, margin %, and MoM trends. For the sales leadership team."                    |
| "Show me sales"                  | "Show total orders, average order value, and top 10 SKUs by revenue. Quick overview, no deep analysis."                                      |
| "Something that shows revenue"   | "Deep dive into customer churn. Investigate why churn increased in Q3, focusing on cohort patterns, product correlations, and risk signals." |

**What to specify and what to let Kaiya decide**

| You should specify                         | Kaiya will decide                      |
| ------------------------------------------ | -------------------------------------- |
| The core metrics that matter to you        | The exact chart types for each section |
| The primary dimensions to slice by         | Tab names and section ordering         |
| The audience (executive, analyst, ops)     | Color palette unless you specify       |
| The depth you want (overview vs deep dive) | The number of tabs                     |
| Specific time periods or filter values     | Layout details                         |

### Prompt examples by use case

Use these prompts as starting points for your own Kaiya Apps. Adapt the metrics, dimensions, and depth to the specific Business View you are building from.

**Sales and revenue**

* *"Analyze Q4 sales performance across regions and product lines. Key metrics: total revenue, units sold, average deal size, quota attainment %, and win rate. Show MoM trends and top and bottom performers by rep. For the sales leadership team."*
* *"Deep dive into why revenue dropped in the enterprise segment last quarter. Investigate deal size trends, win/loss patterns, stage-level drop-off, and competitive displacement signals. Include actionable recommendations."*

**Marketing and campaigns**

* *"Campaign performance analysis. Show ROAS, CPA, click-through rate, and conversion rate by channel and campaign type. Compare this quarter to last quarter. Highlight underperforming campaigns with improvement actions."*
* *"Analyze email campaign engagement: open rate, click rate, unsubscribe rate by list segment and send time. Show trends over the past six months and surface the top five segments by engagement lift."*

**Operations and supply chain**

* *"Supply chain health check. On-time delivery rate, inventory turnover, backlog volume, and supplier lead times by region and product category. Flag any metrics below threshold with severity indicators. Operations team, compact layout."*
* *"Investigate order fulfillment delays over the past 90 days. Break down by warehouse, carrier, and SKU category. Show root cause distribution and a prioritized bottleneck list."*

**Customer and churn**

* *"Comprehensive churn analysis. Overall churn rate, churn by customer segment, product plan, and tenure cohort. Show MoM trend, top churn drivers, and a risk-ranked list of at-risk accounts with recommended retention actions."*
* *"Customer health scorecard. Show NPS, support ticket volume, product usage frequency, and renewal likelihood by account tier. Flag accounts below health threshold. For the customer success team."*

**Finance**

* *"P\&L overview. Revenue, COGS, gross margin, operating expenses, and EBITDA. Compare actuals to budget by department and month. Highlight variances above 5%. Executive audience, spacious layout."*
* *"Analyze billing and collections health. ARR, MRR, net revenue retention, invoice aging, and days sales outstanding. Show trend over 12 months and segment by customer tier."*

**Pharma commercial**

* *"Build an app for regional directors showing TRx and NBRx performance vs target, call frequency trends, and territory coverage gaps."*
* *"HCP targeting. Rank HCPs by decile and segment, flag high-potential drop-offs, and surface recent call history. Built for the weekly cycle plan."*

**Healthcare and clinical**

* *"Patient outcomes summary. Show readmission rate, average length of stay, discharge disposition breakdown, and complication rate by care unit and diagnosis group. Clinical team, light theme."*

**People and HR**

* *"Workforce analytics. Headcount by department and level, attrition rate, time-to-fill, and engagement score. Show trends over the past year and surface departments with elevated attrition risk. For HR leadership."*

### **Phrasing edit requests effectively**

Specific edits route directly. Kaiya applies the change without needing follow-up questions:

* *"Add a KPI card for gross margin % to the Overview tab."*
* *"Remove the Trends tab and replace it with a Segment Breakdown tab."*
* *"Add a filter dropdown for product category that drives both the chart and the table."*
* *"Switch the bar chart on the Sales tab to a horizontal bar sorted descending by revenue."*

Vague edits trigger clarifying questions before any change is made:

* *"Improve the charts"* — which charts, and what improvement?
* *"Add more analysis"* — what kind? Trends, comparisons, breakdowns, new metrics?
* *"Make it look better"* — colors, chart types, layout, typography?

**Batching multiple edits**

You can combine small edits into one request: *"Change the title to 'Q4 Sales Review', switch the bar chart to a line chart, and add a date range filter."* Kaiya applies them together.

{% hint style="info" %}
To refresh the visual style without changing data or structure, ask Kaiya to *"redesign the app"*. Kaiya will offer a small set of theme options. Picking one regenerates the visual layer only. All data and tabs are preserved exactly as they were.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://help.tellius.com/tellius-6.3/kaiya/kaiya-apps/mastering-prompts-for-kaiya-apps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.