MARKO ARNAUTOVIC · INDEPENDENT ENGINEER

Intelligent software.Smarter business.

AI automation & custom software engineering.

Custom AI agents, intelligent automation, and web and mobile applications—engineered to reduce manual work and solve real business problems. I’m Marko, your direct engineering partner with 12+ years of professional web development experience.

12+ years in web development · Based in Serbia · Working worldwide

  • PHP
  • Node.js
  • React
  • Flutter
  • MySQL
  • WordPress
  • Joomla
  • Odoo
  • Laravel
  • WooCommerce
  • JavaScript
  • TypeScript
  • Python
  • Dart
  • HTML5
  • CSS3
  • Tailwind CSS
  • Bootstrap
  • Vue.js
  • Angular
  • Next.js
  • Express
  • PostgreSQL
  • MongoDB
  • Redis
  • Docker
  • Git
  • GitHub
  • Linux
  • Nginx
  • Android
  • iOS
  • n8n
  • Swift
  • Kotlin
  • Java

ONE ENGINEERING PARTNER. THREE WAYS FORWARD.

Intelligence meets
solid engineering.

FROM INPUT TO VERIFIED OUTCOME

Follow the data.
See what changes.

Watch a fictional record move through each workflow. These interactive illustrations run only in your browser: no AI model, CRM, email, or document service is connected.

01 / INTERACTIVE ILLUSTRATION

Lead research agent

SAMPLE DATA
  1. Authorized sources

    Select a permitted business directory or an approved CRM export. No real records are loaded here.

  2. Structured research

    Extract company facts with source references. Missing facts stay empty.

  3. Deduplicate

    Compare stable identifiers against the destination records before proposing a new lead.

  4. Draft outreach

    Prepare a message from verified context. This illustrative draft is not sent.

  5. Human approval

    A reviewer checks relevance, permission, and the draft before any external action.

  6. CRM update

    Record an approved outcome with its reference and check that the write completed.

Read the complete workflow above.

02 / INTERACTIVE ILLUSTRATION

Customer support assistant

SAMPLE DATA
  1. Customer enquiry

    A fictional customer asks how to change a delivery address.

  2. Approved knowledge

    Retrieve the relevant shipping policy and verify that it applies to the order state.

  3. Grounded draft

    Prepare an answer from that policy. Do not invent an exception or expose another customer’s data.

  4. Escalation

    If the order is already dispatched or the policy is unclear, hand the case to a person.

  5. Record outcome

    Save the summary and handoff status according to the agreed retention policy.

Read the complete workflow above.

03 / INTERACTIVE ILLUSTRATION

Document processing

SAMPLE DATA
  1. Document intake

    A fictional invoice enters a restricted queue with a stable document identifier.

  2. Field extraction

    Extract supplier, invoice number, currency, line items, and total with source references.

  3. Validation

    Check required values, line-item arithmetic, and potential duplicate invoice identifiers.

  4. Review exceptions

    An operator compares missing or conflicting fields with the source document.

  5. Approved update

    Write approved data to the destination and reconcile the saved record. No payment is initiated.

Read the complete workflow above.

WHY WORK WITH ME

Your development partner.
Personally involved.

You work directly with the developer making the technical decisions. I ask questions early, explain trade-offs clearly, and keep the scope visible throughout delivery.

Meet the developer behind ArnautCode

Clear communication

Direct conversations about requirements, priorities, and technical decisions. No ambiguity about who is responsible for implementation.

Maintainable by design

Readable code, deliberate dependencies, and a handover that helps the next change stay manageable.

Practical engineering

Security, performance, and operating costs inform the solution. Complexity has to earn its place.

THE TOOLKIT

Strong foundations.
The right tools around them.

AI integrations and automation build on solid application engineering. Models, orchestration, interfaces, databases, and infrastructure are selected around each project’s needs.

AI models & APIs

OpenAI APIs · Anthropic APIs · Google Gemini APIs

Automation & orchestration

n8n · Laravel jobs and queues · PHP automation · Webhooks · Scheduled processes · Human approval workflows

Backend & applications

PHP · Node.js · Laravel · REST APIs

Mobile applications

Flutter · iOS · Android

CMS & business platforms

WordPress · WooCommerce · Joomla · Odoo

Content & interfaces

ACF · Elementor · JavaScript · React · HTML5 · CSS3 · Tailwind CSS

Data & integration

MySQL · MariaDB · REST APIs · Redis · n8n

Delivery & infrastructure

Git · Linux · cPanel · Plesk · Cloudways

HOW WE WORK

A clear path from
problem to production.

Discovery

We define the business goal, current constraints, users, and what a successful delivery needs to include.

Technical planning

I review the existing system, identify dependencies and risks, and turn the scope into clear deliverables.

Design & architecture

We agree on the interface, content structure, data model, and integration boundaries before implementation.

Development

I build in manageable stages, with version control and regular progress reviews against the agreed scope.

Testing & optimization

I check key workflows, responsive behavior, access controls, and performance in a staging environment.

Launch & support

We plan deployment, verify the live experience, document the handover, and agree on any ongoing support.

COMMON PROBLEMS I SOLVE

Something isn’t working.
Let’s find out why.

Start with the symptom. I’ll help identify the constraints and a practical way forward.

A slow WordPress website

Approach: measure server response, page assets, interactions, and plugin overhead. Intended outcome: targeted improvements supported by comparable measurements.

A hacked or compromised installation

Approach: investigate affected files, accounts, and entry points, then plan cleanup and hardening. Intended outcome: a documented recovery with monitoring priorities.

Broken plugins or unreliable APIs

Approach: reproduce the failure, review dependencies and data contracts, and test recovery paths. Intended outcome: a maintainable fix with visible failure handling.

A legacy PHP application

Approach: map critical workflows and dependencies, then modernize in controlled stages. Intended outcome: a supported foundation without a risky all-at-once rewrite.

Complex WooCommerce requirements

Approach: define product, checkout, and operational rules, then implement focused extensions. Intended outcome: a store that supports the agreed business workflow.

Repetitive business workflows

Approach: map triggers, approvals, and exceptions before automating. Intended outcome: less manual handoff and a clear recovery process.

A website migration

Approach: inventory dependencies, rehearse the move, and agree on a cutover and rollback plan. Intended outcome: a controlled transition with key journeys verified.

Database performance problems

Approach: inspect expensive queries, data growth, and application access patterns. Intended outcome: changes targeted at the actual workload.

INSIGHTS

Practical thinking.
Useful answers.

Read all insights

AI & Automation

AI Agents vs Traditional Automation: Which Does Your Business Need?

Use a practical request-routing example to decide between rules, a bounded AI workflow, and an agent that chooses its next tool.

AI & Automation

How to Build a Reliable AI Customer Support Workflow

A practical design for approved knowledge, account access, escalation, and evaluation in a customer support assistant.

AI & Automation

AI Document Processing: From Extraction to Verified Records

Why extracting an invoice is only one step: design source references, validation, review queues, and duplicate-safe writes.

NOT SURE WHAT TO AUTOMATE?

Start with the task
slowing you down.

Describe the repetitive work. I’ll help identify where AI can make a difference—and where standard automation or conventional software is the better fit.

Let’s automate your business
Chat on WhatsApp