> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Describe an App So AI Builds It Correctly
- URL: https://blog.jestor.com/describe-an-app-so-ai-builds-it/
- Published: 2026-09-17T22:38:14.000Z
- Updated: 2026-09-17T22:38:14.000Z
- Author: Bruno Bannach

To **describe an app so AI builds it**, describe the records, the phases, and the rules. A description in terms of screens produces an interface over a structure nobody designed.

## What a vague description produces

The builder fills the gaps, and the gaps are the important part.

- Field types chosen for you, sometimes wrongly
- Relationships inferred rather than specified
- Phases invented to fit a generic pattern
- A result that looks right and calculates nothing

## What to include

| Element           | What to state                                 |
| ----------------- | --------------------------------------------- |
| **The record**    | What one row represents                       |
| **Key fields**    | Including which are money and which are dates |
| **Relationships** | What connects to what, and in which direction |
| **Phases**        | The stages records move through               |
| **Rules**         | Approval thresholds, required fields, routing |

## How to do it in Jestor

1. Write the description in plain text before opening the builder in **Jestor**.
2. Name the record, the fields with their types, and the relationships.
3. Describe the phases and any rules that govern movement between them.
4. Answer the builder's clarifying questions rather than skipping them.
5. Review field types and connected labels afterwards, before adding records.

## Why choose Jestor for AI-assisted building?

The **AI** builder in **Jestor** asks clarifying questions before building, which means an incomplete description produces a conversation rather than a wrong guess.

Because it can also edit existing apps, a first attempt does not have to be right — the structure can be refined in the same way it was created.

## Frequently Asked Questions

### Should I describe screens or data?

Data — records, fields, relationships, and phases. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Does the builder ask questions?

Yes, before building.

### Can it edit an existing app?

Yes.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.