Pennylane, invoicing and reconciliation
Customer creation, invoice generation, payment tracking, reminders, internal notifications and pre-send checks.
n8n consultant for SMBs
Reliable n8n workflows connected to your real tools.
I design, deploy and document n8n automations that connect CRM, invoicing, messaging, reporting and business APIs. The goal: less manual re-entry, more control, and a team that can operate the system after delivery.
When n8n is useful
Not a no-code toy. An operational backbone.
n8n is useful when your processes are clear enough, but your tools still do not talk to each other properly. I use it as an orchestrator: trigger, business rules, API calls, human validation and alerts.
01
You have data moving between CRM, invoicing, spreadsheets, email or Slack.
02
A sync error can block an invoice, a follow-up or a reporting workflow.
03
You want to own your workflows, API keys and hosting.
04
You need a supervisable system, not a magical automation no one can maintain.
Use cases
The n8n projects where I am most useful
CRM, leads and sales pipeline
Inbound lead routing, enrichment, scoring, sales alerts, follow-ups and synchronization between CRM and field tools.
Self-hosted n8n on Hetzner and Coolify
Deployment on a European VPS, environment variables, backups, monitoring, updates and operations documentation.
Two n8n projects are documented in detail on the blog: Automating Pennylane invoicing · A sales-call analysis pipeline
Method
A useful workflow should still be readable six months later.
I favor short, named, documented and testable workflows. Critical steps keep human validation when business risk justifies it.
Process map
Triggers, incoming data, business rules, expected outputs and validation points.
Documented n8n workflow
Clear naming, internal notes, clean variables, error paths and operational alerts.
Deployment and supervision
Production release, hosting if needed, monitoring, backups and recovery procedure.
Team handover
Hands-on session, documentation and 30 days of follow-up on the delivered scope.
Frequently asked questions
n8n for your SMB, the questions that come up
When is n8n useful for an SMB?+
n8n becomes useful when your processes are clear but your tools don't talk to each other yet: data is retyped from one app to another, follow-ups depend on someone remembering, reporting is done by copy-paste. If the process itself is still fuzzy, we clarify it before automating anything.
Can we keep a human approval step?+
Yes. Sensitive steps, such as sending a quote, replying to a customer or writing to your invoicing system, can be prepared by the workflow and submitted to a person before execution, for example through a Slack or Telegram message with an approval button.
Which tools can be connected?+
CRM, invoicing (including Pennylane), email, forms, Slack, Telegram, Google Drive, spreadsheets and your business APIs, depending on available access. n8n ships hundreds of connectors, and any service exposing a REST API or a webhook can be integrated.
Should n8n be self-hosted?+
Both options are valid. n8n Cloud makes getting started simple. Self-hosting on your own server gives you data control and a fixed cost, independent of execution volume. I set up and document the chosen option, and you keep ownership of it.
When is n8n not the right choice?+
When the process still changes every week, when an existing tool already does the job, or when the need calls for real software development rather than orchestration between tools. In those cases I say so during scoping and we look at the simplest alternative: sometimes a script, sometimes configuring the tool you already have, sometimes nothing at all.
Path
Want the broader automation offer first?
This page focuses on n8n. The automation page covers overall scoping, hosting models and delivery commitments.