Skip to content

01 / Services · Build

Build. Custom software live in weeks.

We build custom software for mid-market companies, and the first version reaches production in four to eight weeks at a price fixed before the build starts.

Weeks to the first iteration in production
4-8
Audit findings confirmed and fixed before an internal platform release
59/59
Lighthouse accessibility, best practices and SEO on a delivered site, measured in production
100/100/100
Records lost migrating a client project to its own backend
0

In detail

What you should know.

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

For example: 16 indexable URLs, Spanish and English. Hotel Talavera

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.

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 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.

Who it is for

We don't take every project.

We would rather tell you now than halfway through. If you recognise yourself on the left, let's talk.

It fits if

  • You need a website, a portal or an app that does not exist yet, or one that has run out of road
  • You want the code, the data and the hosting in accounts your company owns
  • You prefer a fixed price before work starts to an open hourly bill
  • Someone on your side can decide and give the project a few hours a week
  • You care that Google and AI assistants can read it from day one

It is not for you if

  • You are after a cheap template or a site put together over a weekend
  • You want it to live on a platform you cannot leave later
  • Nobody on your side can review screens or make decisions
  • You need people to bill hours without a clear goal

For example: 2 languages live on the site, Spanish and English. Global Dynamic Security Group

What you get

What you take away.

Everything is written down before we start, and everything stays in accounts your company owns.

01Deliverables

  1. 01

    A Discovery document with scope, data model, architecture decisions, risks and a fixed price for the build

  2. 02

    A working application deployed on your own Vercel project, with a staging and a production environment

  3. 03

    Your own Supabase backend: Postgres schema, row level security on every table, authentication, storage and edge functions

  4. 04

    Source code in a Git repository your company owns, with continuous integration that blocks a merge when types, lint or tests fail

  5. 05

    Multilingual structure where the project needs it: one route per language, localized slugs, bidirectional hreflang and per-language sitemaps

  6. 06

    Search and AI-search layer: server-rendered HTML per route, JSON-LD, sitemap and a robots policy that lets answer engines read the site

  7. 07

    iOS and Android builds published under your own developer accounts, with over-the-air updates, when the project includes an app

  8. 08

    Security baseline: HTTP security headers, a real 404 page, restricted CORS on server functions, secrets kept out of the repository

  9. 09

    Handover pack: environment variables, admin accounts, a runbook and the written audit report of what was found and fixed

02How it runs

  1. 01 · Week 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. 02 · Week 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. 03 · Week 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. 04 · Week 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.

For example: 38 Spanish and English routes prerendered as static HTML. Santo Domingo Bay

Timing and budget

How we quote.

No price list and no hourly billing during a build. After a short call you get a written quote for your project.

Timeline
About two weeks of Discovery, then the first iteration in production between week four and week eight. Larger platforms are delivered in phases.
Team
Our team scopes and builds it. Pedro Ciordia, founder and CTO, sets the architecture and reviews every release. You talk to the people building it.
How the price is set
Fixed price, set at the end of the Discovery Sprint and sent as a private quote. What moves it: languages, modules, integrations and how much of an old system has to come along.

FAQ

What people ask us.

How much does it cost to build a custom website or internal platform?
The Discovery Sprint has a fixed price, and it ends with a fixed price for the build itself. What moves that price is the number of languages, modules and integrations, and how much of an old system has to come along. There is no hourly billing during a build: scope and price are agreed before anyone writes code. Book a call and you get a first read of scope and price, then a private quote.
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?
The team that scopes the project is the team that builds it, 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. CARE exists because a live product needs security updates, content changes and small improvements every month.

For example: 251 KB hero image weight, down from 1.3 MB. Estepona Golf

Get started

Tell us what you want to build.

Websites, apps, custom systems and AI for companies that need them in production in weeks. Fill in the form or book a 30 minute call: a senior engineer answers within 48 business hours with a first take on scope, timeline and price.

What do you need?
Budget
When

At least ten characters.

Answer in writing within 48 business hours. No newsletter, no automatic sequence.

Rather answer the full brief?

First step

Discovery Sprint

Two weeks to close scope, architecture and price before anything is built.

No price list. You get a private quote, in writing, after a short call.

Then, to build, always at a fixed price

Not ready yet?

AI-native digital studio for mid-market companies

POLARGATE, S.L. · CIF B24895005
Calle Electrónica 6, 28027 Madrid, Spain