Automation Specialist

    Automation Specialist for Swedish Businesses

    Independent automation specialist on n8n, Make.com, and Power Automate. I build workflows that connect your tools, move data automatically, and run in production without breaking. No prototype demos that die after two weeks.

    See my services

    What an automation specialist actually delivers

    An automation specialist is not an RPA salesperson, a consultant who installs Zapier for you, or someone who builds brittle Excel macros. It's an engineer who maps your processes, finds where manual work is destroying your margin, and builds orchestration flows that run themselves — with clear logic, monitoring, and evals. Default stack: n8n self-hosted (you own the runtime, no new license fees), Make.com when the customer already runs it, Power Automate for Microsoft 365-heavy orgs. Python and dbt where the data flow needs more than a no-code tool can deliver.

    Common automation jobs I solve

    CRM ↔ accounting ↔ customer support

    Sales closes a deal in HubSpot or Pipedrive. Today, someone manually pushes it into Fortnox/QuickBooks, creates a task in Asana, emails the delivery team. With n8n: the whole chain runs in 30 seconds with zero human touch.

    Inbound email and forms routed correctly

    You receive 200 inbound emails per day. 80% are routine, 20% need a senior. An LLM classifies and routes without hallucinating — because we set an escalation rule: when uncertain, flag a human.

    Data sync between SaaS tools without real integrations

    Notion ↔ Linear ↔ Slack ↔ Google Sheets ↔ customer database. n8n abstracts away differences in the APIs, handles rate limits and retries, logs every run so you can see what happened.

    Recurring reports and broadcasts

    Weekly report that pulls data from four systems, formats into a template, and emails or posts to Slack. Build once, run forever, adjust when the report needs to change.

    How I work

    1. 01 · Week 1

      Process mapping

      We map the flow you want to automate. What triggers what? Which systems are involved? Where are the bottlenecks today? Output: a clear document showing current state, target state, and risks. Fixed price when scope is clear.

    2. 02 · Week 2–3

      Build and dry-run

      I build the flow in n8n or Make. We run it in parallel with your current process for 1–2 weeks to catch edge cases. No production damage while you test.

    3. 03 · Week 3–4

      Cutover and documentation

      Cutover in a controlled moment. Documentation, runbook, and monitoring in place. You own the flow — runtime is self-hosted, not on my account.

    Tools I use

    n8n self-hosted (default — open source, you own data and flows) on Coolify or Docker. Make.com when you already have a license or need Make-specific modules. Power Automate and Logic Apps for Microsoft 365-based orgs. Prefect and dbt when the data flow requires scheduling, idempotency, and versioned transformation. Python for what no-code tools can't handle. LLM calls via OpenAI or Claude when rules aren't enough — always with escalation paths.

    Frequently asked questions

    What's the difference between n8n, Make, and Zapier?+

    n8n is open source and can be self-hosted — you own the data, runtime, and flows. Make has more pre-built modules but is hosted (data goes through their infra) and priced per operation. Zapier is the easiest to start with but limits branching logic and gets expensive at scale. Default in Sweden: n8n self-hosted for GDPR and cost, Make when it's already in the company.

    Can you work with Power Automate and Microsoft Copilot Studio?+

    Yes. For organizations already on Microsoft 365, Power Automate and Logic Apps are usually the right choice — you get SSO, security, and governance that integrate with existing IT. Copilot Studio fits chat/agent flows against internal data via Graph.

    How do you handle errors and monitoring?+

    Every flow has retries, a dead-letter queue for what permanently fails, and alerts to Slack/Teams when something breaks. Logs are kept at least 30 days. For critical flows: Sentry/Grafana hookup and on-call rotation if you want it.

    What does an automation project cost?+

    A single workflow: 50,000–150,000 SEK fixed price depending on number of systems, edge cases, and evals. Pre-build assessment (1–2 weeks): 25,000–60,000 SEK. Larger programs (5–10 workflows + platform setup): 200,000–500,000 SEK. No open accounts — always price-capped.

    How long does a typical automation take?+

    A simple automation (CRM → email → Slack message) goes from idea to production in 1–2 weeks. Complex flows with multiple data transformations and LLM steps: 3–6 weeks. Larger programs with evals and monitoring: 2–3 months.

    Who owns the flow when the project is done?+

    You. Runtime runs on your server (self-hosted n8n) or your account (Make/Power Automate). I document every flow, your own developers can modify it, and any retainer is voluntary — not a lock-in.

    Which workflow takes the most time at your company right now?

    Book a free 30-minute call. We walk through your current processes and identify where automation has the highest ROI. You get a concrete assessment, not a sales script.

    Cookies & analytics

    We use cookies for essential functionality and, with your consent, analytics to improve the site. Read the Privacy Policy.