Skip to content
Srpski Describe your process Menu

Your most important process leaves Excel and starts running on its own.

In three to six weeks, at a published price. We take one process in your company (inquiries, work orders or the weekly report) and build a system that runs it without retyping.

Describe your process

A written reply with a price range within 48 hours.

See the prices and what moves them

Execution trace

Lead Intake · ZippyShell Louisiana (US)

live since

25 Mar 2026

  1. Runs on: Gmail An inquiry arrives by email name · phone · email · type · date Outcome: received
    An inquiry arrives by email
    FieldType
    nametext
    phonephone number
    emailemail address
    typemoving or storage
    datedate

    Field names come from the flow description. Exact schema: [POTREBNO POJAŠNJENJE: tačna imena polja u ZippyShell toku]

  2. Runs on: n8n Reading the text into fields Outcome: fields filled
    Reading the text into fields
    FieldType
    nametext
    phonephone number
    emailemail address
    typemoving or storage
    datedate

    Field names come from the flow description. Exact schema: [POTREBNO POJAŠNJENJE: tačna imena polja u ZippyShell toku]

  3. Runs on: n8n Duplicate check by phone and email already exists: skipped and logged Outcome: 2 of 41 inquiries, 25 Jul to 2 Sep 2026 Outcome: new, continues
    Duplicate check by phone and email
    FieldType
    phonematch key
    emailmatch key

    Field names come from the flow description. Exact schema: [POTREBNO POJAŠNJENJE: tačna imena polja u ZippyShell toku]

  4. Runs on: Google Sheets Row written to this month's sheet Outcome: row written
    Row written to this month's sheet
    FieldType
    sheetmonth received
    rowone inquiry

    Field names come from the flow description. Exact schema: [POTREBNO POJAŠNJENJE: tačna imena polja u ZippyShell toku]

  5. Runs on: Dialpad Text to the customer, by inquiry type Outcome: sent
    Text to the customer, by inquiry type
    FieldType
    phonephone number
    messageby type: moving or storage

    Field names come from the flow description. Exact schema: [POTREBNO POJAŠNJENJE: tačna imena polja u ZippyShell toku]

  6. Runs on: Gmail Email to the customer, for moving or storage Outcome: sent
    Email to the customer, for moving or storage
    FieldType
    emailemail address
    templatemoving or storage

    Field names come from the flow description. Exact schema: [POTREBNO POJAŠNJENJE: tačna imena polja u ZippyShell toku]

  7. Runs on: n8n If sending fails Outcome: error alert sent
    If sending fails
    FieldType
    step[POTREBNO POJAŠNJENJE: koji korak je pao, sadržaj obaveštenja]

    Field names come from the flow description. Exact schema: [POTREBNO POJAŠNJENJE: tačna imena polja u ZippyShell toku]

5 of 5 runs successful, 27 Aug to 1 Sep 2026. More than 200 emails sent by 2 Sep 2026.

Source: run logs and the system's sent mail, checked 2 September 2026.

Where work stalls today

  • An inquiry waits hours for a reply.
  • Work orders get retyped from one sheet into another.
  • The report gets built at night, before the meeting.
  • A system fails quietly and nobody knows.

The real cost doesn't show up in the spreadsheet. You look at numbers you don't fully trust. On holiday you keep your phone in hand, because only one person knows where everything is.

A company that does good work shouldn't depend on whether someone remembered to log the order.

The tool is the easy part

The hard part is everything around it. Old data that has to move without loss. People who use it from day one. And the day something breaks. So every system we build follows three rules.

  1. One process, finished

    One named process gets a database, data entry, reminders and a report. Old data moves over, people get trained, the documentation stays with you.

    Proof: Suzuki Servis Musa Racing, 1,865 rows moved from Excel into a database, 69 duplicate vehicles merged.

  2. The price before the first call

    The range is on this site, with what pushes it up and down. Few firms in this market publish prices like these.

    Proof: the Pricing page.

  3. Nothing fails silently

    When something breaks, an error message goes out. You don't find out by accident two months later.

    Proof: ZippyShell Louisiana, 5 of 5 runs successful from 27 August to 1 September 2026, with error alerts built into the flow.

Three steps to a system that runs

  1. You describe the process.

    In the form, in two or three sentences. Within 48 hours you get a written reply with a price range.

  2. Process Snapshot, 5 to 7 working days.

    A process map, the risks and a phased plan with prices. The full amount is credited against the system price.

  3. The system in 3 to 6 weeks.

    Built in phases, with your data and training. After handover, monitoring and a monthly report.

Describe your process

Nine systems, one job each

The Systems page says, for each one, whether it has already run for a client.

Find your process in the catalog
SystemJob
Lead Intake No inquiry goes without a reply and a record.
Work Orders & Records A work order is entered once and never retyped.
Quote & Configurator The customer builds the request, the quote starts without retyping.
Owner Report One screen instead of a report built at night.
Company Knowledge Base Answers from your own documents, with the source.
Document Reader Data from an invoice or contract enters the system without typing.
Voice Receptionist A call gets answered even when nobody can pick up.
WhatsApp Intake A customer's message becomes an order in the system.
SEF Sync An invoice reaches SEF without manual entry.

The spreadsheet listed 1,079 vehicles. There were 1,010.

Suzuki Servis Musa Racing in Belgrade ran its work orders in an Excel file with macros. We moved 1,865 rows into a database. Of 1,079 vehicles, 69 were duplicates. Today the shop runs on AutoServis OS, with 947 customers and 1,848 work orders.

Read the full case

Case record

Suzuki Servis Musa Racing, Belgrade

1,079 to 1,010

vehicle records in the sheet, to real vehicles

1,865

rows moved from an Excel file with macros into a database

69

duplicate vehicles merged

1,848

work orders in the database, linked to vehicle and customer

947

customers in AutoServis OS

Source: migration records and the AutoServis OS database, as of [POTREBNO POJAŠNJENJE: datum preseka].

This work became AutoServis OS, software for car service shops, piloted at Suzuki Servis. See AutoServis OS: [POTREBNO POJAŠNJENJE: domen AutoServis OS sajta]

Three prices, published up front

PackagePriceTime
Process Snapshot400 to 700 EUR, credited against the system price5 to 7 working days
One Process, One System2,500 to 6,000 EUR3 to 6 weeks
Monitoring150 to 400 EUR per month6 months minimum

If you don't continue after the snapshot, the process map and the plan are yours to keep. There's a smaller first step too: Single Automation, 600 to 900 EUR. All prices exclude VAT.

All seven packages and what moves the price

What it costs to keep things as they are

An unanswered inquiry doesn't call back to complain. It goes to whoever replied first. A retyped order with a mistake shows up only on the invoice. And manual work gets paid for every month, just without a line item.

The Process Snapshot turns that cost into a number, before you sign anything bigger.

What a day looks like when the process runs itself

TodayWhen the system runs
An inquiry waits for someone to get to it.The inquiry gets a reply and a record, without duplicates.
A work order is retyped into another sheet.A work order is entered once.
The report is pieced together at night.The report is on one screen.
A failure is discovered by accident.A failure arrives as a message.
Only one person knows where everything is.The documentation belongs to the company.

When this isn't for you

If you want an hourly rate or a small 200-euro workflow. If nobody in the company owns the process, or IT will "get to it when they can".

If you want "something with AI" but no process is actually hurting, you don't need a system yet. Start with AI Adoption: a day of training and rules for the company.

If it's one process, if it lives today in a spreadsheet, an inbox or one person's head, and if you make the call, then it is.

Who answers for your system

Every project has one accountable lead, Amar Jusufspahić, from the first conversation to the monthly report. Specialists join when the work calls for them. You talk to the same person from start to finish.

How we work

Questions before the first step

You're probably thinking this is expensive.

A system for one process costs 2,500 to 6,000 EUR. The first step is a Process Snapshot, 400 to 700 EUR, and the full amount is credited against the system price. The exact price per phase is in a written proposal, before you commit to more.

Our data is a mess. Does that need fixing first?

No. Moving old data is part of the job and part of the price. At Suzuki Servis, 69 duplicates were found and merged among 1,079 vehicle records.

My people won't want a new program.

That's why the Process Snapshot includes a conversation with the person who runs the process today. The system is built around work people already do, and training is included.

What if the system breaks?

A failure arrives as a message, to us and to you. The first 30 days of monitoring are included; after that, monitoring runs monthly, with a report.

What if we don't continue after the snapshot?

The process map, the risk list and the phased plan are yours. You can take them to any builder.

Describe one process that's slowing you down

Tell us what hurts and where it lives today. The description costs nothing and commits you to nothing. Within 48 hours you get a written reply with a price range and one recommended next step.