> ## 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 Combine Small Processes Into One System
- URL: https://blog.jestor.com/combine-small-processes-into-one-system/
- Published: 2026-09-17T22:41:31.000Z
- Updated: 2026-09-17T22:41:31.000Z
- Author: Bruno Bannach

To **combine small processes into one system**, share the records rather than merging the processes. Forcing unrelated work into one pipeline produces a process that fits none of it.

## What to share and what to keep separate

The distinction is between data and flow.

- **Share** — clients, suppliers, products, cost centres, employees
- **Share** — permissions, reporting, and the home page
- **Keep separate** — phases, forms, and automations per process
- **Keep separate** — anything with different owners and different timing

## What sharing produces

| Benefit                  | Why                                      |
| ------------------------ | ---------------------------------------- |
| **One client view**      | Everything connected appears on one card |
| **Faster builds**        | Core records already exist               |
| **Consistent reporting** | One definition per entity                |
| **Simpler access**       | Roles apply across processes             |

## How to do it in Jestor

1. Build core entity tables once in **Jestor** — clients, suppliers, products, cost centres.
2. Connect every process to those tables rather than duplicating them.
3. Keep each process's phases, forms, and automations distinct.
4. Organize each process into its own folder for navigation.
5. Build reporting across processes on the shared entities.

## Why choose Jestor for connected operations?

Because tables and apps are separate in **Jestor**, several processes can read the same records while each keeps its own interface, phases, and rules.

That is what makes a client card show deals, tickets, contracts, and payments at once — four processes, one record, no duplication.

## Frequently Asked Questions

### Should processes be merged?

Share the records, not the flows. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### What should be built once?

Core entities — clients, suppliers, products, cost centres.

### Does each process keep its own rules?

Yes, phases and automations stay separate.

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