--- title: "Integrations and automation · Polargate" description: "We connect your PMS, CRM, ERP, booking engine, email and payment systems, then remove the manual work around them with scheduled jobs…" url: https://polargate.ai/services/build/integrations-and-automation locale: en publisher: POLARGATE S.L. --- Build // The systems you already pay for, working as one # Integrations and automation We connect your PMS, CRM, ERP, booking engine, email and payment systems, then remove the manual work around them with scheduled jobs, webhooks and data pipelines that run server side and log every call. In short Polargate connects the systems a mid-market company already runs, PMS, CRM, ERP, booking engines, email and payment providers, and automates the manual work around them with scheduled jobs, webhooks and data pipelines. Every integration runs server side, is idempotent, logs each call and keeps credentials out of the browser. Work starts with a fixed-price Discovery Sprint from 4,900 EUR, and integration builds start from 4,900 EUR. ## What it is Integrations and automation is the work that makes the systems you already run behave like one system. Most mid-market companies do not need another tool. They need the PMS, the CRM, the ERP, the booking engine, the email platform and the payment provider to share the same data, so nobody retypes a reservation into a spreadsheet or copies a guest list by hand. Polargate builds those connections, then removes the manual steps around them: scheduled jobs, webhooks, data pipelines and internal automations that quietly do what a person was doing every morning. ## How we do it We start with the data, not with the tool. In the Discovery Sprint we map what each system holds, who owns it, which field wins when two disagree, and where the process breaks today. Then we build server side, in code, against the real APIs. Every integration follows the same rules. Credentials live in a vault, never in the browser. Jobs are idempotent, so a retry cannot duplicate an order or a guest. Calls are logged, so you can see what ran, what changed and what failed. A sync fails closed rather than writing bad data, and we put guardrails on the dangerous cases: a mass checkout, a duplicate charge, a supplier feed that returns an empty page. Where possible the integration copies what it needs into your own database, so your site or app keeps working when the other system is down. This is production experience, not theory. Polargate runs a five minute Oracle Opera Cloud guest sync across hotels, a resumable Microsoft Graph directory sync over roughly 45,600 employee records, a WordPress content pipeline that refreshes a festival app every 30 minutes with no runtime dependency on WordPress, booking engine integrations on hotel websites, GA4 and Search Console pulled into a client portal by OAuth, and email that turns into tickets and goes back out as email. ## What you get A working integration in production, the code and the provider accounts in your name, a short runbook your team can actually read, visibility of status and errors, and alerts when something stops. And the manual step gone for good, which was the point. ## What it costs Work starts with a paid Discovery Sprint from 4,900 EUR, fixed price, two weeks, with half of it credited against the build if you start within 60 days. Integration and automation builds start from 4,900 EUR, fixed price and fixed scope. Keeping them running, monitored and evolving sits in a CARE retainer from 850 EUR per month. No hourly billing. What you get - An integration map of your current systems: what data each one holds, who owns it, which one wins in a conflict and where the process breaks today - Connectors to your PMS, CRM, ERP, booking engine, email platform and payment provider, written in code against their real APIs - Scheduled jobs and webhooks with idempotency keys, retries and replay protection, so a repeated call never duplicates data - An auditable log of every sync: what ran, what changed, what failed, readable by your team and not only by us - Alerts when an integration goes quiet, a credential expires or a provider changes an endpoint, before your staff notices - Internal automations that remove recurring manual work: business-day report emails, document and photo handling, status alerts per department - Credentials kept in a secrets vault with least-privilege access per system, never in the front end or in a spreadsheet - A short runbook plus full ownership: repository, database and provider accounts in your company's name from day one Engagement Timeline Discovery Sprint of two weeks, then the first integration in production usually 2 to 6 weeks later. The variable is rarely our side, it is how fast the other vendor supplies credentials and a test environment. Team Two people, and neither of them sells. Pedro Ciordia, founder and CTO of Polargate, does the architecture and writes the integration code, with specialists from our network when a system or a language needs them. You talk to the person building it. Price From 4,900 EUR for an integration and automation build, fixed price, after a Discovery Sprint from 4,900 EUR (half credited against the build if it starts within 60 days). Running and evolving it under CARE from 850 EUR per month. Stack - TypeScript - Supabase - PostgreSQL - Deno - Vercel - GitHub Actions - Resend - Stripe - Microsoft 365 - Microsoft Entra ID - GA4 - Search Console - Firebase - Python - WordPress - MCP ## Proof Elite Smart Build ### A custom operating system for Elite Smart Build Elite Smart Build, a Spanish hotel refurbishment contractor working in more than twenty countries, ran every site on spreadsheets and email. Polargate replaced that with eleven modules on Supabase and React: daily Gantt, role-masked margins, per-department alerts and material reception with automatic incidents. 2026 Read the case [A custom operating system for Elite Smart Build](https://polargate.ai/work/hotel-refurbishment-operating-system) Concert Music Festival ### From a frozen line-up to an app that updates itself A Spanish summer music festival had its line-up compiled into the app binary and its backend locked inside a no-code platform. Polargate rebuilt the foundation in four days, ten days before the season started. 2026 Read the case [From a frozen line-up to an app that updates itself](https://polargate.ai/work/concert-music-festival) FAQ ## Questions, answered How much does it cost to connect our PMS to our website? An integration build starts from 4,900 EUR at a fixed price, once the scope is clear. What moves the number is the other system: a documented REST API with a sandbox is a small job, a legacy PMS with a nightly file export is a bigger one. Polargate quotes it after the Discovery Sprint (from 4,900 EUR, half credited against the build if it starts within 60 days), so you see a closed figure before committing. How long does an integration project take? Two to six weeks for the first integration in production, counted from the end of the Discovery Sprint. The bottleneck is rarely our side: it is how long the other vendor takes to give you credentials, a test environment and answers about their API. We request that access on day one and build against a sandbox or a recorded sample while it arrives, so the wait does not stack onto the build. What if our system does not have an API? Then we look for the next honest door: a read-only database replica, a scheduled file export, a webhook the vendor can send, or a small plugin on their side. For a festival client Polargate wrote a WordPress plugin because the standard API did not expose the event dates the app needed. If no reliable route exists, we say so instead of building something fragile that breaks in six months. Do you use Zapier or Make, or do you write the code? We write the code. No-code platforms are fine for a two step notification, but they charge per run, keep the logic out of version control, hold your credentials and are hard to debug at three in the morning. Polargate builds integrations as server-side functions inside your own Supabase project and repository, so they are testable, auditable, portable and cost nothing per execution. Who owns the integration code and the accounts? You do. The repository, the database, the provider accounts and the API credentials are in your company's name from day one, and we work inside them. If you stop working with Polargate, nothing has to be rebuilt or migrated: you change the access and everything keeps running. We have moved several clients off platforms that did not allow that, and it is slow and expensive work. INITIATE ## Start the engine Tell us what you are building in a few short questions. A senior engineer answers in writing within 48 business hours, with a first take on scope, timeline and price. [Start your project](https://polargate.ai/start) · [Talk to us](https://polargate.ai/start#static-brief-heading)