Skip to content
Srpski Describe your process Menu

One person answers for the project. Specialists join when the work calls for them.

Amar Jusufspahić leads every project, from the first conversation to the monthly report. Every job follows the same order and the same written rules.

Amar Jusufspahić

[POTREBNO POJAŠNJENJE: stvarna fotografija AJ-a, 4:5, ako AJ odluči]

[POTREBNO POJAŠNJENJE: two sentences on experience, concrete and verifiable, no employer, no family or institutional references]

We handle automation, the database, the web application and document reading in one project, under one lead. No handoffs between firms and no waiting on another team. That's why the timeline is in weeks.

Four steps, the same for every system

  1. Process Snapshot, 5 to 7 working days.

    Two conversations, with you and with the person who runs the process today. You get a process map, a list of risks and silent failures, a phased plan with prices and a baseline: how many hours and errors the process costs you today.

  2. Build in phases, 3 to 6 weeks.

    Each phase is handed over as a working part before the next one starts.

  3. Handover.

    Old data moved, people trained, documentation and access handed over in your company's name.

  4. Monitoring.

    We track failures, make small changes and send a monthly report on the state of the system. The first 30 days are included in the system price. After 30 days we measure the baseline again.

Nothing fails silently

A silent failure is a system that looks like it works and doesn't. An empty list instead of an error. A report that's right until someone checks it. It's a cost most companies never see, because nobody reports it.

Before production, every system passes four checks.

Pre-production checklist

Nothing fails silently

applies to

every system

  1. Where: every flow When something breaks, the system returns an error Must be: an error, never an empty list or "success"
  2. Where: every message Every outgoing message has a visible status Must be: sent, failed or skipped
  3. Where: startup A key or setting is missing Must be: refuses to start and says why
  4. Where: form and inputs Tested with a real message before launch Must be: real message received

Proof: in the ZippyShell flow, every text that couldn't be sent, for example because of an invalid number, triggered an error alert.

Every failure sends a message. Every change leaves a trace.

The code, the database and the documentation are yours

  • Code, flows and database, in your company's accounts.
  • Documentation in plain language: what the system does, where it runs, how to fix it.
  • Access to every account and tool the system uses.

No lock-in. If you end the engagement, you can continue with anyone, and the proposal says so.

Systems we use every day

[POTREBNO POJAŠNJENJE: snimak internog CRM-a bez ličnih podataka]

our own tool, in personal use

Internal CRM. It reads mail every 15 minutes, logs inquiries and has its own MCP server, so it can be used through an AI assistant.

[POTREBNO POJAŠNJENJE: snimak Marrow-a bez ličnih podataka; da li se marrow.intelgrator.com javno pokazuje]

our own tool, in personal use

Marrow. A personal notes system Amar built for himself: it captures articles and recordings, summarizes them, writes briefs with cited sources and a morning digest.

They're not for sale. They show how we build when nobody is watching.

Technologies we work with

Questions about who does the work

Who are the specialists who join?

People we work with when a project needs a skill outside the core, for example telephony for a voice receptionist or legal interpretation for compliance. Whoever joins, the same person answers for your project.

What if the project lead is unavailable?

Code, database, documentation and access are with you from handover, so the system doesn't depend on one person. [POTREBNO POJAŠNJENJE: who takes over monitoring and when]

How many projects do you run at once?

[POTREBNO POJAŠNJENJE: limit on concurrent projects]. When there's no free slot, our reply says so, with the date we can start.

Who maintains the system after handover?

We do, through monitoring, for at least six months. After that, monitoring can continue, or someone else takes over using the documentation.

Who owns the system?

Code, flows, database and documentation sit in your company's accounts. [POTREBNO POJAŠNJENJE: confirm ownership passes to the client after payment, and from when]

Start with one process

Describe it in the form. The description commits you to nothing. A written reply with a price range arrives within 48 hours.