00 / Intake - EU-based · GDPR-first automation engineering

Your systems, finally talking to each other.

Your CRM, enrollment, and email tools were never designed to work together. We build the systems that make them - engineered in the EU, GDPR-first, built to last.

12+

Years in IT, helpdesk to CTO

EU

Based in the EU, GDPR-first

1:1

You talk straight to the engineer

01 / The systems

Systems that stay connected after launch.

Five ways an engagement usually starts.

Port 01

M365 Administration & Support

Your Microsoft 365, looked after day to day. Accounts, mailboxes, and security policies handled - so nobody on your team has to live in the admin center.

  • Microsoft 365
  • Entra ID
  • PowerShell

Engagement - ongoing retainer

Port 02

Custom Automation & Integration

When you outgrow Zapier, we replace the fragile no-code flows with a proper application - built for GDPR compliance and for volumes no-code can't handle.

  • Node.js
  • Express
  • REST/Webhooks

Engagement - fixed-scope build

Port 03

Salesforce / CRM Integration

Contacts and opportunities land in Salesforce correctly the first time, created through the official API. No duplicates, no manual cleanup.

  • Salesforce API
  • Composite API
  • OAuth

Engagement - fixed-scope build

Port 04

Freelance PM + AI Automation

We find the automation opportunities across your business, rank them by payoff, and deliver them one scoped project at a time - every hour tracked and visible to you.

  • AI Automation
  • Project Mgmt
  • Consulting

Engagement - ongoing retainer

Port 05

Fractional IT Leadership

CTO-level guidance without the full-time hire. Budgets, vendor choices, and IT strategy from someone who has actually run this function - not just advised on it.

  • Budgeting
  • Vendor Mgmt
  • IT Strategy

Engagement - advisory retainer

Step 01

Scope

We start with a call to map what's not talking to what - and whether automation actually pays off here. If it doesn't, you'll hear that too.

Step 02

Build

A fixed scope, delivered in working pieces you can try as we go. You talk directly with the engineer building it.

Step 03

Ship

It goes live in your environment, with documentation written for whoever maintains it next - including future you.

Step 04

Run

The system runs on its own. Support stays available - but the goal is that you stop thinking about this workflow entirely.

02 / In production

What this looks like when it ships.

A language education provider

Enrollment automation system

Problem

Enrollment ran on a patchwork of Zapier steps. It broke easily, needed constant manual attention, and couldn't meet GDPR requirements as volume grew.

Approach

We replaced it with a custom Node.js application. Salesforce contacts and opportunities are now created in one atomic call, and confirmation emails go out directly from the client's own domain.

Outcome

Enrollment now runs unattended, at higher volume, with GDPR-compliant data handling. Nobody spends their morning fixing failed steps anymore.

  • Node.js
  • Express
  • Salesforce Composite API
  • M365 SMTP

A multi-sector Latvian company

M365 user provisioning automation

Problem

Every new hire meant a manual, multi-step setup job for the admin team - repetitive, easy to get wrong, and a poor use of anyone's time.

Approach

We built a workflow that reads each incoming request, creates the Microsoft 365 account, and sends the new person a welcome email - start to finish, without a single manual step.

Outcome

New accounts now appear on their own. A chore that ate real hours every week is simply gone.

  • M365 Admin Center
  • IMAP/SMTP
  • Scripted Workflow

A multi-sector Latvian company

Freelance PM + AI automation engagement

Problem

The business had plenty of automation potential, but nobody was mapping or prioritizing it - and past contractors left no visibility into where the hours went.

Approach

An ongoing engagement: we identify opportunities across departments, rank them by payoff, and deliver them as scoped projects - with every hour logged and shared with the client.

Outcome

A steady pipeline of automation projects, and a client who can see exactly what they're paying for at any moment.

  • Project Management
  • AI Automation
  • Hour Tracking

03 / The operator

One engineer. Direct access. No account managers.

  • 12+ years in IT, every level
  • IT Business Partner & CTO-level ownership
  • 10+ years running an IT business

ITSW is run by Gatis, based in Latvia. There are no account managers between you and the person writing the integration. When something breaks or a requirement changes, you talk directly to the engineer who built it.

Behind that is 12+ years in IT at every level - from hands-on helpdesk work to IT Business Partner roles with full CTO-scope responsibility: budgets, vendors, provisioning, infrastructure. Add 10+ years of running an IT business, and this isn't a developer's side project. It's built by someone who has owned the budget, the vendor contract, and the 2am outage call - not just the code.

Being small and EU-based isn't a limitation. It's why clients choose ITSW over a larger agency: decisions happen fast, GDPR compliance is the starting point rather than an afterthought, and every system is built to be understood by whoever maintains it next - including future you.

The work spans backend integration, day-to-day IT support, and fractional IT leadership: connecting Salesforce, Microsoft 365, and internal tools so they behave reliably - built by someone who can also sit on your side of the table and plan the budget for it. If that sounds like your problem, it's a conversation worth having.

Have a system that should talk to another system?

Start a conversation

04 / Open a channel

Let's get your systems talking.

Fill in the form, or email directly - whichever's faster for you.

Your details go only to ITSW, to answer your message - handled as described in the Privacy Policy.