Skip to content
POLARGATE
Custom software, scoped in two weeks and in production in four to eight.

Build

BUILD is Polargate's delivery line for custom software: websites, products, internal portals, mobile apps, AI features and integrations. Scope and price are settled in a paid Discovery Sprint, the build is fixed price, and the first iteration reaches production in four to eight weeks.

Hotel lobby by day: a receptionist checks a room list and floor plan on screen while a technician wires a wall TV and a guest looks at her phone
4-8
Weeks to the first iteration in production
59/59
Audit findings confirmed and fixed before an internal platform release
100/100/100
Lighthouse accessibility, best practices and SEO on a delivered site, measured in production
0
Records lost migrating a client project to its own backend

Capabilities

How it works

  1. 01Week 1 to 2

    Discovery Sprint

    Interviews with the people who will use the thing, an audit of the systems you already run, a data model, an architecture decision and a scope written in plain language. It ends with a fixed price and a delivery plan, and the document is yours whether or not you continue.

  2. 02Week 2 to 4

    Foundations

    Design direction, database schema with row level security from the first migration, environments, continuous integration and the first screens in a place you can open. Nothing is built on a platform you cannot leave: the repository, the backend and the hosting are created in your accounts.

  3. 03Week 4 to 8

    Build to the first shipped iteration

    Weekly deployments, a short written update with each one and a running list of decisions. The goal of this stage is a version in production with real data where someone can finish an actual task, not a demo. Scope changes are priced before they are built.

  4. 04Week 8 onwards

    Audit, launch and handover

    Several review passes over correctness, architecture, accessibility, performance and security, with every finding checked by a second reviewer before it counts as real. Then the launch, the handover pack and, if you want it, a move to the CARE retainer for maintenance and evolution.

What BUILD is

BUILD is the line where Polargate writes software: public websites, customer products, internal portals, iOS and Android apps, AI features and integrations with the systems you already run. Senior engineers do the work and use AI inside it, in their own tooling, instead of selling it as a separate product. Every project ends with the code, the database and the hosting in accounts your company owns.

Who it is for

Mid-market companies, roughly 50 to 500 people, that have outgrown their current site or run part of the operation in spreadsheets and shared inboxes. Common starting points: a marketing site nobody can edit without fear, a multilingual site for several markets, an internal tool that has to replace a manual process, an app for guests or customers, or an AI assistant that answers from your own data instead of guessing. Polargate works natively in English, Spanish and Dutch, for clients in Europe and the Americas.

How it works

Every engagement starts with a paid Discovery Sprint: two weeks of interviews, an audit of what you already have, a data model, an architecture decision and a scope you can say no to. It ends with a fixed price for the build, calculated from evidence rather than from a first meeting.

The build then runs in weekly deployments to an environment you can open at any time. The first shipped iteration lands between week four and week eight. It is not a prototype, it is a version in production with real data behind it. Before a release goes live it passes an audit loop where several review passes look for bugs, architecture problems, accessibility failures, slow pages and security holes, and every finding has to survive a sceptical second reading to count. On one internal platform, that pass left 59 confirmed findings: one blocker, seven high, twenty five medium and twenty six on user experience and accessibility. All of them were fixed and deployed.

What it costs

The Discovery Sprint is fixed price, from 4,900 EUR, and you keep everything it produces even if you stop there. The build itself is quoted at a fixed price once Discovery is done. As a reference from past projects, a multilingual site with its own backend starts from 7,600 EUR, and the first phase of an internal operations platform from 12,000 EUR. Work after launch moves to a monthly CARE retainer, priced separately.

What you get

A working product in your own accounts: Supabase for the database, Vercel for hosting, GitHub for the code, your own developer accounts on the App Store and Google Play. Row level security on every table, HTTP security headers, real server-rendered HTML for every route so search engines and AI assistants can read the page, and a handover pack with environment variables, admin accounts and the audit report. If you decide to continue with another team, nothing has to be rebuilt.

Proof

FAQ

Questions, answered

How much does it cost to build a custom website or internal platform?
A Discovery Sprint with Polargate starts from 4,900 EUR at a fixed price, and it ends with a fixed price for the build itself. As a reference from past projects, a multilingual site with its own backend starts from 7,600 EUR and the first phase of an internal operations platform from 12,000 EUR. There is no hourly billing during a build: scope and price are agreed before anyone writes code.
How long until we have something live?
The first shipped iteration reaches production four to eight weeks after Discovery, and Discovery itself takes about two weeks. What lands first is a working slice with real data rather than a clickable prototype, so you can put it in front of real users while the rest is built. Larger internal platforms are delivered in phases, with a first testable version roughly a month after development starts.
How is Polargate different from a traditional digital agency?
Three things. The people who scope the project are the people who write the code, so nothing is lost between the sales meeting and a delivery team you never met. AI is used inside the work, which is why a first iteration takes weeks instead of quarters. And every release goes through an audit loop with a second reviewer before it ships, so you are not the one finding the bugs.
Do we own the code and the data?
Yes. The Git repository, the Supabase project, the Vercel project and the App Store and Google Play accounts are yours, and the handover pack includes environment variables, admin accounts and a runbook. Polargate does not build on a proprietary platform you cannot leave, and when a prototype starts on a tool like Lovable it is moved onto your own infrastructure before launch.
Can you integrate with the systems we already use?
Yes, and in practice that is most of the work. Past builds connect to hotel property management systems such as Oracle Opera Cloud, booking engines, WordPress as a content source, card payment terminals, transactional email and messaging channels including WhatsApp and SMS. If a system has an API or a documented export, it can be integrated. If it does not, Discovery says so before you commit to anything.
What happens after launch?
You can take the product in house, because everything already lives in your accounts, or move to the CARE line: a monthly retainer for maintenance, evolution and support, run through Polargate's ServiceDesk with an hour balance you can check. Many clients continue with CARE, since a live product needs security updates, content changes and small improvements every month.
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.