# How should a company start with Queli Makra?

A company should start with one recurring process that has a clear source, owner, review boundary, and measurable result. Makra begins inside the company’s own operation, then connects more work when the first process is working well.

## Choose work that repeats and leaves evidence

Good starting points include invoices arriving by email or PDF, open-item follow-ups, orders arriving through messages and files, recurring compliance reports, or approval packets that currently move through chat and spreadsheets. These processes have a recognizable input, a repeated preparation step, and a person who can say whether the result is correct.

The first question is not which model to buy. It is what arrives, where it lives, what the team currently re-enters or chases, and what a useful prepared result looks like. An invoice workflow may start with a PDF and prepare a reviewed ERP draft. A receivables workflow may start with open items and email history and prepare a prioritized queue. A message-order workflow may prepare one structured order and expose missing details.

## Define the boundary before connecting systems

For the first process, name the authorized sources, fields, rules, owner, exception conditions, and final approver. Decide which actions Makra may prepare and which actions must wait for the person. Agree the data location, processor terms, retention, access controls, model provider or customer-hosted option, and connection method before production.

Makra prepares; the responsible person decides. Preparation, review, approval, and the completed external action remain separate states. That makes the first process measurable and safe to extend.

## Measure the real workflow

Record a baseline that belongs to the chosen process: preparation time, number of handoffs, correction rate, missing fields, exception volume, or review time. Compare the new route with that baseline and keep the source attached to the result. One automotive invoice workflow reduced processing time by 98%, another shortened Intrastat preparation from five days to five minutes, and an import/export workflow handles more than 60 daily follow-ups without spreadsheets.

Those figures are case-specific, not promises for a new customer. Once the first process has a stable owner, evidence trail, and review state, the same operational context can support a second connected workflow. Expansion should follow the work and permissions the company has agreed, not a checklist of integrations.

## Sources

- https://www.queli.ai/
- https://www.queli.ai/llms.txt

## Other languages

- [English](https://www.queli.ai/ai-agents/answers/start-with-one-process)
- [Hrvatski](https://www.queli.ai/hr/ai-agenti/answers/kako-poceti-s-jednim-procesom)
- [Deutsch](https://www.queli.ai/de/ki-agenten/answers/mit-einem-prozess-starten)