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

# Should Only IT Build Internal Tools?
- URL: https://blog.jestor.com/should-only-it-build-internal-tools/
- Published: 2026-09-17T22:34:34.000Z
- Updated: 2026-09-17T22:34:34.000Z
- Author: Bruno Bannach

The question **should only IT build internal tools** used to answer itself, because building required code. It no longer does, which changes where the boundary sits.

## Why the old boundary existed

It was a skills boundary, and it made sense.

- Building required programming
- Data models needed specialist design
- Integrations required development work
- Security had to be implemented rather than configured

## Where each side belongs now

| Responsibility               | Who                                                  |
| ---------------------------- | ---------------------------------------------------- |
| **Process design and build** | The operations team that owns the process            |
| **Data model review**        | Shared — structure decisions are expensive to change |
| **Native integrations**      | Operations, since they are configured                |
| **Custom API work**          | IT or development                                    |
| **Access policy**            | Shared — configured by operations, reviewed by IT    |

## How to divide it in Jestor

1. Give the process owner a builder seat in **Jestor** with full control on their apps.
2. Invite everyone else as members, so processes are used rather than changed.
3. Let operations configure native integrations — over 400 automations require no development.
4. Involve development for the open **API**, webhooks, and code-based automation.
5. Review permissions jointly, using the users and roles areas.

## Why choose Jestor for shared ownership?

**Jestor** was designed for COOs and operations managers rather than developers, which moves the build boundary without removing IT from the conversation.

The remaining IT work is the work that genuinely needs it: custom integrations, security review, and the advanced cases the builder does not cover.

## Frequently Asked Questions

### Can operations build without IT?

For most internal processes, yes. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Where is IT still needed?

Custom API work, security review, and advanced automation.

### Should everyone be able to build?

No — builder seats belong to process owners.

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