Geneva automates high-frequency trading. Not the paperwork around it.

The Canton of Geneva hosts 120 banks, the highest concentration of commodity trading firms in the world, and the European headquarters of dozens of international organizations. Trading floors operate in microseconds. But one floor down, compliance teams compile KYC reports by copying PDFs into spreadsheets. The legal department at a trading house routes contracts by email, with manual approvals at every step, across three currencies and two jurisdictions.

International organizations are a textbook case. A report that crosses five approval levels, translated into three languages, reformatted for four different audiences. The content is the same, the processes around it eat weeks. Document routing, signature chains, multilingual report generation: all of it follows clear rules. Clear rules are exactly what you automate.

On the HR side, Geneva companies face a unique complexity: teams that include French cross-border workers (frontaliers), G permits, B permits, different tax regimes. Cross-border payroll calculations, AVS/LAMal declarations, allowance management depending on canton of residence. Every month, someone spends days verifying edge cases in a spreadsheet.

The Geneva paradox: trading algorithms managing billions, and administrative processes running on shared Excel files and follow-up emails.

What I do for Geneva businesses

Process audit and lost-hours mapping

I look at how your teams actually work day to day. Not the official process signed off by compliance in 2021. The reality: copy-pasting between the CRM and regulatory reporting, trading contracts passing through seven inboxes before approval, monthly reports compiled manually from three different systems. I quantify the time lost on each task and rank them by ROI. A commodity trading firm described their multi-currency invoice reconciliation process to me. Four data sources, two currencies, a consolidation spreadsheet updated manually every week. Forty hours a month. To do a job a script handles in ten minutes.

Building automated workflows

This is where the hours come back. I connect your tools so data flows without anyone touching it. A signed contract triggers invoicing, the invoice generates in the right currency (CHF or EUR depending on the client), payment tracking updates itself, reminders go out automatically in the right language. For companies under FINMA oversight or cantonal reporting requirements, I automate data collection and regulatory report formatting. The rules are fixed, the formats are documented: ideal territory for automation. I use n8n for orchestration, Google Apps Script for the Google ecosystem, Python when data processing gets heavier or multi-currency calculations are involved.

Monitoring and maintenance

Automated workflows break. A banking API changes versions, a FINMA reporting format evolves, a supplier redesigns their portal. In a context where compliance errors are expensive, monitoring is not optional. I set up alerts so you know when something stops working before the regulator notices. And I document everything. The goal is that your team understands what runs, can fix simple issues, and doesn't depend on me for day-to-day operations.

How it works

1. Discovery call (free, 30 min)

You tell me what eats your time. Which tools you use, which processes annoy you, what you've already tried. If automation isn't the right answer, I'll say so. No one's time gets wasted.

2. Manual task audit

I map the data flows between your tools, the manual steps, the friction points. You get a clear document: what can be automated, estimated time savings, and where to start. No 50-page report.

3. Iterative implementation

We tackle the workflow with the best effort-to-impact ratio first. You see a concrete result in days. We adjust, validate, move to the next one. No three-month development tunnel before seeing anything work.

4. Documentation and autonomy

Every automation is documented: what it does, how it triggers, what to check if something breaks. Your team takes over. You don't need me for the day-to-day.

Tech stack

n8nGoogle Apps ScriptPythonREST APIsSQLBigQueryZapier

Frequently asked questions

You're based in Tbilisi. How does that work for a client in Geneva?

Video calls, shared documents, async updates. Process automation is work on your tools and data, not in your offices. I connect to your systems remotely, deliver workflows, and we validate together on calls. Tbilisi is GMT+4, which gives full overlap with Swiss business hours. For an automation project, what matters is that your processes run, not that I'm sitting in Plainpalais.

How is this different from an ERP integrator?

An ERP integrator sells you a license and configures software. I look at what happens between your software. The gap between your CRM and your compliance tool. The manual step between signing a trading contract and generating the invoice. The Excel file that bridges two systems that don't talk to each other. That's where the lost hours hide, and no standard ERP module covers them.

Do you work with Swiss clients? Can you handle multi-currency?

Yes. CHF/EUR invoicing, exchange rates, multi-currency reconciliation: these are textbook automation cases. Clear rules, reliable data sources (ECB rates, SNB rates), documented formats. I also automate cantonal tax filings and FINMA reports when the format is standardized. If the rules are written down somewhere, they can run on their own.

How long does it take?

A simple workflow (syncing two tools, automatic notifications) takes a few days. A broader project with multiple interconnected systems and regulatory constraints, a few weeks. The initial call is free and scopes the project. If it's not worth the investment, I'll tell you before we start. In Geneva, given local hourly costs, the payback period for an automation project is often measured in weeks, not months.