n8n builds that
keep running.
I build and look after n8n and AI automations for agencies and businesses. Every job starts with a ₹5,000 / $75 feasibility test: a written verdict within 48 hours, Monday to Friday, credited against the build.
Built by Yug Chandak, who ships the n8n tools on this site. Not affiliated with n8n GmbH.
Three steps. Stop at any of them.
The test tells you whether to build. The build ships one workflow. The retainer keeps it running. Each step is priced on its own.
Step 1 · Feasibility test
₹5,000 / $75
one-time, credited against the build
Tell me what you want automated. The 48 hours run Monday to Friday and start when both the payment and a complete brief have arrived (plus the export, if one exists). You get a written verdict and a fixed-price quote.
- Verdict: build, don't build, or build differently
- The failure modes to design around
- A fixed-price quote with a delivery date
- Fee credited in full if you go ahead
Step 2 · Fixed-price build
₹20,000–45,000 / $300–900
per workflow
One workflow, scoped in writing before you pay for the build. You get a delivery date, not an estimate.
- Written scope and delivery date
- 14-day fix window after delivery
- Handover with a runbook (one page on how to run and fix it)
- Built in your n8n instance, not mine
Step 3 · Monitoring retainer
₹8,000–15,000
per month, cancel any time
For workflows that must keep running after handover. Optional and month-to-month.
- Missed-run and silent-failure watch (runs that finish green but did nothing)
- Credential-expiry warnings before a token dies
- Monthly report
- Priority fixes
Enough to give a real answer
- One paragraph on what should happen, start to end: the trigger, the apps involved, the result.
- If a workflow already exists, one sanitized JSON export. Remove credentials and personal data first.
- Where it runs: n8n Cloud, self-hosted, or Make. The version if you know it.
- What “working” means: runs per day, how fast it must finish, what must never happen.
- Someone who can answer a question within a day.
Something you can act on
- A written verdict within 48 hours: build, don’t build, or build differently.
- The failure modes to design around: rate limits, token expiry, duplicate runs, empty responses that look like success.
- A fixed-price quote with a delivery date. The fee is credited if you go ahead.
- On a build: written scope, a date, a 14-day fix window, and a runbook at handover.
- On a retainer: a monthly report, priority fixes, and a warning before a credential expires.
The n8n tools on this site
Yug Chandak builds and ships the n8n tooling on Papercuts Tools. These are live and free. Open one and judge the work before you pay for any.
Credential Radar
FreeKnow the exact date every OAuth token, key and cert will die — before your client does.
n8n Credential Sync
FreeFor teams running dev and prod n8n instances who are tired of re-entering credentials.
n8n Git Sync
FreeFor teams who can't afford to lose a workflow
OAuth Token Refresh
FreeGet a fresh Google access token from your refresh token — no re-auth dance.
who this is for
- Agencies running n8n or Make for clients, with workflows that have to keep working.
- Businesses with one automation that matters: invoicing, lead routing, reporting, a sync between two systems.
- Anyone who wants a written verdict before spending on a build.
not for
- Hobby projects and experiments. The free tools on this site are for those.
- “Make me an app.” I build automations, not products.
- Anything that needs production credentials shared in chat. Access gets set up properly in your instance or not at all.
Before you start
Do I need to send you credentials?
No. An n8n export does not contain secret values, but it does carry credential names and often sample or pinned (saved test) data. Remove both before you send it. If a build needs access, I set up a separate login in your n8n with only the access the build needs. Nothing is shared in chat.
What happens after I send the brief?
I reply within one working day confirming what I have, asking anything that is unclear, and sending a Razorpay link (INR) or a PayPal or Wise invoice (USD). The 48 hours run Monday to Friday and start when both the payment and a complete brief have arrived (plus the export, if one exists). The verdict arrives by email as a document you can forward.
How long does each step take?
Feasibility: 48 hours once the payment and brief are in, counted Monday to Friday. Build: most single workflows take one to two weeks, and the quote states the exact date. Retainer: starts the month after handover, or any time for a workflow that already exists.
What if the verdict is “don’t build”?
You keep the write-up: why it will not hold, and what to do instead. That might be a different tool, a manual step, or a smaller version that will work. The fee pays for the analysis, not for a yes.
What is the refund policy?
The 48 hours run Monday to Friday and start when both the payment and a complete brief have arrived (plus the export, if one exists). If no written verdict has arrived by then, the feasibility fee is refunded in full. Builds are covered by their written scope. The retainer is month-to-month. See the Services section of the refund policy.
Can you work on Make or Zapier too?
Feasibility tests and builds: yes for Make, and Zapier case by case. The monitoring retainer is n8n only for now, because the missed-run and credential-expiry checks read n8n execution history.
Start with the 48-hour verdict.
₹5,000 / $75. Written verdict, failure modes, fixed quote. Credited if you build.
papercutstools@gmail.com