About

Two founders. We build every system ourselves.

Heaq Digital is a small business process automation studio. This page is about who we are, and how we decide what a system should do before we build it.

Why Heaq exists
Connecting two tools is rarely the hard part. Deciding what should happen between them is.

We kept seeing the same thing: the integration worked, the process around it didn't. A follow-up went to a customer who asked to wait. A failed payment sat in an inbox for a week. So we start with the process, and pick the tools after.

Before Heaq, Miloš built GoHighLevel, HubSpot and n8n automation at a marketing automation agency, for businesses in real estate lending, roofing, career coaching, e-commerce and marketing.

Miloš Mršović, co-founder of Heaq Digital
Miloš MršovićCo-Founder. Designs and builds the systems. Builds sales, CRM and payment workflows in n8n, GoHighLevel and Python.n8n creatorLinkedIn
Živojin Perović, co-founder of Heaq Digital
Živojin PerovićCo-Founder. Runs your project from the first call to handover. Enterprise RPA background in retail: Automation Anywhere, document automation, SAP scripting, Python and SQL. AWS Certified Cloud Practitioner.n8n creatorLinkedIn

A workflow does the same thing every time. A business shouldn't.

Take one situation: a deal has gone quiet for three weeks.

A basic automation
Deal inactiveSend follow-up

Every quiet deal gets the same email. Including the customer who asked you to wait until November.

What we build
  • How long has it been quiet?
  • Is a proposal waiting on the customer?
  • What did the last email say?
  • Is it clear enough to act on?
Rules

If a rule can decide it, a rule decides it.

AI

Reads the email thread when context changes the answer.

Person

Decides when the system isn't sure.

What has to be true before anything ships.

Five rules we hold every build to, whatever the tool.

The process makes sense first.

We map how the work moves before we automate it. Sometimes the fix is in the process, not the tools.

Every decision has a reason.

The system can tell you why it took a path, and it writes that down.

The messy cases are part of the job.

Missing fields, failed API calls, customers who never reply. The happy path is not the whole system.

It knows when to stop.

Where judgment matters, a person decides, with the context in front of them.

Your tools stay.

We build inside what already runs your business. No new platform to learn.

Trained in the tools we build with.

Formal training behind the work, plus a published template on n8n.io.

n8n

Workflow Automation

Logic, branching and error handling, so a workflow keeps working when something fails.

n8n

AI Agents & API Integrations

Connecting AI steps and outside APIs securely, inside the same workflow.

Amazon Web Services · Živojin

AWS Certified Cloud Practitioner

How cloud infrastructure, security and costs work, for systems that run reliably.

Small on purpose

The person you talk to is the person who builds it.

No salesperson, no project manager, no handoff to a developer you never meet. Nothing gets lost between the call and the build.

  • You talk to the people building it, every time
  • Fixed price per project, no retainer
  • Documented, so it's yours to run

Things we don't believe

More automation is always better.
Sometimes the right answer is to leave a step manual.
AI belongs everywhere.
A simple rule is better when a rule is enough.
You need a new stack.
What you run today is usually fine. The gap is between the tools.
It works because it ran once.
Failures and edge cases are the actual job.

Want to meet us? Book 30 minutes.

Bring one process that eats your team's time. You'll talk to one of us, and leave with a clear answer on whether it's worth automating.

Not ready for a call? Describe one process in writing and we'll reply with what we'd build.