Most automation requests I get aren’t really “build me a workflow.” They’re “someone on my team spends two hours a day moving data between two tools, and I want that to stop.”
That’s what I build in n8n.
What I actually ship
- Lead intake & qualification — form / Telegram / email → validation → CRM or Sheets → a notification to the right person. With an AI step that reads and tags the message when it earns its place.
-
- Scheduled reporting — pull an API on a schedule, diff against the last snapshot, summarise with an LLM, deliver to chat or email. (Recent build: SEO rank tracking → position diff → GPT summary → Telegram, with a per-client schedule.)
-
- Data sync between tools — two systems that don’t talk to each other, kept in sync with conflict handling, not a one-way dump.
-
- AI agents that hold state — booking and consultation bots that keep the conversation in a Data Table, not in the prompt.
How I work
- AI agents that hold state — booking and consultation bots that keep the conversation in a Data Table, not in the prompt.
Fixed price by default, 50% to start and 50% on acceptance. Everything runs on your n8n — self-hosted or your cloud — so you keep the workflows if we stop working together. Every build ships with a handover doc that says what each node does and how to add a new client or data source. 14–30 days of fixes included, depending on the package.
Rates
| Scope | Price |
|---|---|
| One production workflow — error handling, walkthrough, 14 days of fixes | $350 |
| 3–5 connected workflows — shared error handling, handover doc, 30 days of fixes | $900 |
| 6–15 workflows or an AI agent with memory — architecture doc, staging + prod, monitoring | from $2,200 |
| Care plan — monitoring, fixes, small changes, cancel anytime | $400/mo |
If the scope isn’t clear yet: $45/h with a capped 2-hour discovery block, then we fix the price before anyone commits. Discovery happens in writing — you send me the current process, I send back a flow sketch and the questions that matter.
How I communicate
I work in writing, not on calls — I use a translator, so text is where I’m precise. You get recorded walkthroughs instead of meetings. In practice that works in your favour: decisions, scope and handover all end up written down and searchable, instead of said once on a call and remembered differently by two people.
Proof, since I’m new to this board
A booking agent I built recently: Telegram → n8n → Data Table, state moving waiting_date → waiting_phone → completed, card to the team at the end. No Google Sheets, no external database — the state lives in n8n. I have a 20-second recording of it running end to end; this account is too new to attach files, so DM me and I’ll send it over.
Two things I’ve learned the hard way and will happily walk you through before you hire anyone: a per-client schedule belongs in a next_report_date field plus a Filter, not in one trigger per client; and a retry without an idempotency key will quietly duplicate rows in your CRM.
Invoicing and contract go through an EU entity, so a normal bank transfer works — no crypto, no odd payment rails.
Happy to sketch the flow for your case before any money changes hands. Reply here or DM me.