> ## 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.

# Three ways to create an internal app
- URL: https://blog.jestor.com/three-ways-to-create-an-internal-app/
- Published: 2026-09-16T18:49:49.000Z
- Updated: 2026-09-16T18:49:49.000Z
- Author: Bruno Bannach

There are three **ways to create an internal app**, and the right one depends on what you already have. In **Jestor**, you can build from scratch, start from an existing table or app, or let **AI** build it while you guide what goes in. The same three paths apply to tables, **Kanban** boards and forms.

## Why one creation path is not enough

Building from zero is fastest when the process is simple and you know exactly what you want. It becomes tedious when the app has dozens of fields.

Letting AI build the whole thing is fast for complex structures, but you often end up deleting things you did not ask for. Guiding the AI is the middle path that most people actually want.

Where each path fits:

- A short process with a handful of fields
- A new process that resembles one you already run
- A complex structure you would rather describe than assemble
- A one off tool that only needs to work, not to be elegant

## Comparing the three paths

| Path                    | How it works                              | Best when                               |
| ----------------------- | ----------------------------------------- | --------------------------------------- |
| From scratch            | You add fields one by one                 | The structure is small and clear        |
| From something existing | An existing table or app becomes the base | The new process resembles a current one |
| Guided by AI            | You describe what it should contain       | The structure is complex or unfamiliar  |

## Step by step using the guided path

1. **Open the creation tab** and choose what you are building: app, table, form or board.
2. **Select the guided option**, rather than starting empty or copying.
3. **Describe what it should contain**, listing the fields, stages and views you expect.
4. **Review what was generated** before anyone else touches it.
5. **Edit in build mode**, adjusting fields, colors and conditionals inline.
6. **Add automations and permissions** once the structure is settled.

## Why guiding beats full autonomy

The difference between describing an app and guiding one is control. Guiding means the structure reflects what you asked for, so the review step is a check rather than a cleanup.

- **A dedicated path per entity:** apps, tables, forms and boards each have their own flow
- **Existing work as a starting point:** no need to rebuild what already exists
- **Review before release:** nothing goes to the team unseen
- **Editable afterwards:** the generated structure is a draft, not a final state

## Frequently Asked Questions

### Is building from scratch still available?

Yes. It remains the fastest option when the structure is small. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can I base a new app on one I already have?

Yes. An existing table, process or app can be used as the base and edited on top.

### Do the three paths apply to boards and forms too?

Yes. Each main entity has its own creation flow.

## Video Tutorial: Step by Step

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://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.