Skip to content

Pricing

What this costs, before you ask.

Fixed scope, fixed price, written down before we start. Most first projects land between $8,000 and $18,000.

01 · 2 weeks

Automation Map

$2,500

flat

We map one workflow end to end and hand you the diagrams and a build plan. The fee is credited if you go ahead with the build.

  • Interviews with the people doing the work today
  • A diagram of the current process and where it leaks time
  • A costed build plan with a recommended sequence
  • An honest call on whether it is worth automating yet
Start with a Map

02 · 3–5 weeks

First System

$8,000 – $18,000

fixed scope

One workflow, built, documented and handed over. Fixed scope and fixed price, so the number does not move while we build.

  • The system built in visible weekly increments
  • Monitoring, retries and alerting from day one
  • Runbooks and diagrams written as we ship
  • Code and accounts in your name, not ours
Talk it through

03 · Ongoing

Operations Partner

From $6,000

per month

A standing engagement for teams automating more than one thing. We keep building, keep it running, and stay accountable for uptime.

  • A rolling backlog of systems, prioritized with you
  • Maintenance and monitoring of everything we have built
  • A named engineer who knows your operation
  • Cancel with 30 days notice — no lock-in
Talk it through

How we keep it fair

The number doesn’t move.

Scope is fixed in writing

Agreed after the Map, before any building. Overruns are ours to absorb.

The Map is credited

If you go ahead with the build, the $2,500 comes off the project fee.

You own everything

Code, accounts and documentation in your name from day one. No lock-in.

We’ll talk you out of it

If a workflow isn’t worth automating yet, we say so before you spend.

Worth it, per the people who paid

Signed, and checkable.

Every quote below is a public LinkedIn recommendation. Click any name to read it on their profile.

Over 10 workflows working in sync.

I worked with Niraj on an n8n project that comprised of over 10 workflows working in sync. He improved the efficiency, added new features with ease and deployed custom code where necessary — showing that he’s more than just a no/low-code developer which is very valuable in this day and age. I would not hesitate to recommend him if you’re looking for professional execution and strong communication!
Stephen Anindo

AI Engineer / Founder · Granite Marketing

  • A solid foundation for my automation agency.

    Hired Niraj to build out a website for me at automatedbureaucracy.com and he delivered a great full stack application that provides a solid foundation for my automation agency.
    Blake DeHaas

    Graduate Operations Software Engineer · Laboratory for Atmospheric and Space Physics

  • One of the most versatile professionals I have come across.

    One of the most versatile professionals I have come across. His eagerness to learn new things is truly inspiring — whether it’s picking up a new skill, exploring a different approach, or taking on a challenge outside his comfort zone. His incredible ability to take even the harshest criticism in stride sets him apart even more.

FAQ

Questions about cost

Why do you publish your prices?

Because hiding them wastes everyone’s time. Published ranges let you decide whether we’re worth a conversation before you sit through one, and they hold us to a number rather than pricing off how badly you appear to need help.

What happens if the project takes longer than expected?

The price does not move. Scope is fixed in writing after the Automation Map, so overruns are our problem to absorb, not yours to pay for. If you want to add scope mid-build, we quote it separately rather than quietly extending the invoice.

Do you charge for the first conversation?

No. The first call is free and ends with an honest answer about whether the workflow is worth automating yet. Only the Automation Map, which produces documented deliverables, is paid.

What if you decide our workflow is not worth automating?

We tell you, and we say why. Talking a company out of a build we could have sold is cheaper for us than delivering something that quietly fails to earn its cost.

Who owns the code and the accounts?

You do, from the first day. Credentials, repositories and infrastructure are in your name, and handover includes runbooks and diagrams so another engineer could pick the system up without us.

Start with one workflow.

The first conversation is free and ends with an honest answer.

Map my workflow