Custom software

Custom software for your company, built in phases by a team that answers in writing

Internal tools, customer apps and integrations with what you already run (Shopify, your ERP, invoicing). We start with a two-week diagnostic and follow with a fixed-price MVP. The code and the hosting are yours from day one.

TALK TO A CTO

Tell us what you want to build. You get a written reply within 24 hours.

A CTO reads your case and replies with a first take: what is worth building custom, what a standard tool already solves, and where to start.

No call unless you want one: the reply arrives by email, with phases and the next step.

WHAT WE BUILD

What a company needs built custom (and what it doesn't)

We build what sets you apart and configure what already exists. If Shopify, an ERP or an invoicing tool already solves a piece, we tell you before we quote.

Aisle of a warehouse with shelves of boxes

Internal tool / back office

Customers, orders, stock, suppliers and follow-up, with roles per department. Synced with your store or ERP.

A hand holding a smartphone in a living room

An app for your customers

Account area, order status, notifications. Web and mobile (iOS and Android) from one codebase, on the same base as the internal tool.

A laptop showing source code on a sofa

Integrations and data

We connect what you already use: Shopify, ERP, invoicing, email marketing, marketplaces. We migrate the history and leave your data in one database.

HOW A PROJECT RUNS

Four phases, each with a deliverable and a fixed price

Nothing starts without a contract and nothing is paid before a phase is done. First we understand the business; then we build.

01.

Diagnostic and design

Two weeks to understand the business, decide what goes custom and what doesn't, and close scope, architecture and calendar.

2 weeks · deliverable: technical spec and roadmap
02.

Fixed-price MVP

The first useful version, usually the internal tool, built in two-week sprints with a demo at the end of each.

6 weeks · price fixed when the diagnostic ends
03.

Second phase

Customer app, integrations or new modules on the same base. Quoted with what the first phase taught us.

by phase · each with its own contract
04.

Operations and maintenance

Keep the operation in-house or hire monthly maintenance separately. No lock-in: the decision is yours at any time.

optional · no minimum term
A team planning a project around a whiteboard

YOURS FROM DAY ONE

The code, the data and the hosting are yours

The question we hear most before signing: what happens if tomorrow you want to continue without us. Answer: you continue, without asking permission.

  • Code in your repository

    We work in your GitLab or GitHub from the first commit, documented so an in-house team can take over.

  • Hosting in your name

    We set up and run the cloud in an account you own (AWS, GCP, Scaleway…). The keys are yours.

  • A standard, widespread stack

    TypeScript or Python, Node.js or Django, React, PostgreSQL. Your technician can maintain it without depending on us.

  • Data in one database

    We migrate spreadsheets and history into PostgreSQL and connect the tools you already use; nothing stays in silos.

  • Security by design

    Roles and permissions per department, backups, encryption and access logs from the first version.

  • Confidentiality

    We sign a standard mutual NDA within 24 hours before we see your code or your data.

PRICING AND TERMS

A fixed price per phase, a contract from the start

No ballpark ranges before we understand the business: the diagnostic fixes the price of the next phase, and so on.

  • A formal contract from day one and payment in instalments at the start of each phase
  • The diagnostic is deducted from the MVP if you build it with us
  • Optional monthly maintenance, with no minimum term or long notice period
  • Public funding: we tell you which programme fits and who files it before you count on it
Server racks with cabling in a data centre

FAQ

What companies ask before commissioning custom software

How do you usually work: phases, timelines, communication?

Always in phases. A two-week diagnostic closes scope, architecture and calendar; then a fixed-price MVP of about six weeks in two-week sprints with a demo at the end of each; then further phases on the same base. You have a direct channel with the team and a weekly written update.

Is hosting included, or is it on us?

We set up and operate the cloud in an account in your name (AWS, GCP, Scaleway or the provider you prefer). You pay the provider directly, so it is yours from day one and nothing depends on us.

After delivery, who handles maintenance and updates, and with which technologies?

Your choice. You can keep the operation in-house or hire monthly maintenance separately, with no minimum term. We use TypeScript or Python, Node.js or Django, React and PostgreSQL: a standard stack your technician can maintain.

How are payments structured?

By phase, with an instalment at the start of each one. No single payment at the end and no payment before a phase is agreed in writing.

Do you work with a formal contract from the start?

Yes. A contract covers each phase: scope, deliverables, calendar, payments, intellectual property (yours) and data protection. We also sign a mutual NDA before we see your code or data.

Are there public grants or subsidies for this kind of project?

Sometimes. We tell you which programme fits your company size and project (Kit Digital in Spain, regional innovation lines, public procurement of innovation) and who files it, before you count on it in the budget.

Can you give me a price range before the diagnostic?

We can give you the entry packages on the pricing page and the cost calculator as a reference, but the real price of each phase is fixed at the end of the diagnostic: the state of your data and your integrations change the cost too much to guess earlier.

Who owns the code, and how do you protect our information?

You do, from the first commit, in your own repository. Before we see anything, we sign a standard mutual NDA that covers source code, architecture, data and business plans.

Tell us what you want to build

A CTO replies in writing within 24 hours with phases, team and next step.