ServiceSoftware development
Custom software built around the way your business works
Our custom software service designs, builds and runs the application your business needs when off-the-shelf tools no longer fit: a customer platform, a back office, a booking or quoting system, a directory or a document generator. Every project ships the same way — separate development, acceptance (uat) and production environments, a preview address for each branch, builds on GitHub Actions, Docker, health checks, daily snapshots — and the code and data stay yours.
What we do for you
- A short discovery to map your process, the people who use the tool and the data it handles
- A written scope: what the first version does, what it does not, and how we will know it works
- Design of the screens with the people who will use them
- Development in small, reviewable changes, each one visible on its own preview address
- Three environments — dev, uat and prod — so you test on real conditions before anything reaches users
- Integrations with the tools you already use (payments, email, calendar, CRM, ads, shop) — see API integrations
- Hosting with health checks, daily snapshots and rollback, or hand-over to your own infrastructure
- The code in a repository you control, and documentation for whoever maintains it next
Who it is for
- Fits: businesses whose process is their edge and that spend hours bending generic tools to it
- Fits: companies running on spreadsheets, email and copy-paste between three tools
- Fits: organisations that need a platform for their own clients or partners (bookings, campaigns, courses, quotes)
- Does not fit: needs a standard tool already covers well — we will tell you to buy it
- Does not fit: native iOS or Android apps — we build responsive, installable web apps; native apps are something we have not shipped yet
What we have built and run
Examples from our own work, anonymised by sector and country, with their real stage:
| Software | Sector / country | Stage |
|---|---|---|
| Creator-marketing platform: creator profiles, brand campaigns, generated PDF "passports" | Marketing, South Africa | Live |
| Booking and customer platform with dashboards, customer base migrated from a previous booking tool | Restaurant group | Live |
| Management SaaS for training organisations (Next.js + Postgres) | Training, France | Live |
| Quote assistant with separate dev, uat and prod environments | Safari travel, Southern Africa | Built, three environments |
| Client cockpit | Wind energy, France | Built |
| Password-protected hub indexing 23 courses from Drive and GitHub | Education institute, Germany | Live |
| Directory of more than 4,900 sworn translators; a sports directory | Directories | Live |
| Document generators producing letters and regulatory documents in the buyer's name | Digital products | Live |
| E-learning platform selling SCORM courses with certificates | Training | Live |
How we ship: the same discipline on every project
- Three environments. dev for work in progress, uat (user acceptance testing) for you to try with realistic data, prod for your users. Nothing jumps from a laptop to production.
- A preview per branch. Every change gets its own address, so you can click through it before it is merged.
- Builds on GitHub Actions, never on the production server. GitHub describes Actions as a CI/CD platform where workflows are YAML files in the repository and "each workflow run executes in a fresh, newly-provisioned virtual machine" — so a build cannot disturb the live service.
- Docker Compose. The application, its database and its workers are declared in one file, the same way in every environment.
- Health checks. Each service declares a health check; Docker can wait for a dependency to be healthy before starting what relies on it. Our monitoring reads the same checks.
- Snapshots and rollback. Daily snapshots of the server, and a rollback to the previous version if a release fails its checks.
- Humans merge. Our developers work with AI coding agents (Claude Code), under review. Branch protection can require approving reviews and passing status checks before a merge; on our projects, a person approves every merge.
From idea to production, step by step
- Discovery. Who uses it, what they do today, what data is involved, what must never go wrong.
- Scope. A short written scope with the first version's boundaries. If the idea is still uncertain, we start with an MVP or prototype.
- Build in slices. Each slice is a working piece you can click on a preview address.
- Acceptance. You test on uat. We fix, you approve.
- Release. Deployed to prod after checks pass, with rollback ready.
- Run. Monitoring, backups, small changes, under maintenance and support if you want us to keep it running.
What you own
The code lives in a repository you control (or is transferred to you), with the instructions to build and run it. Your data lives in your database and your accounts — payment, email, analytics. If we stop working together, someone else can pick it up. When the software handles personal data on your behalf, we act as your processor: the GDPR requires that you use only processors offering sufficient guarantees of appropriate technical and organisational measures, and that the processing be governed by a contract (Article 28), and it expects means to restore availability and access to data in a timely manner after an incident (Article 32). Our snapshots and rollback are part of that answer.
What we need from you
- A person who knows the process and can decide, available for short weekly reviews
- Real examples: documents, exports, screenshots of the tools you use today
- Access to the accounts the software must connect to, in your name
- Time to test on uat before each release
Questions we get
Do you build mobile apps?
We build responsive web apps that work on phones and can be installed on the home screen. We have not shipped native iOS or Android apps yet, and we say so.
Who owns the code?
You do. It lives in a repository you control or is transferred to you, with what is needed to build and run it elsewhere.
Do you use AI to write code?
Yes, our developers work with AI coding agents such as Claude Code. Every change is reviewed and a person merges it; nothing goes to production without passing the checks.
Can I see progress before release?
Yes. Each branch has its own preview address, and the uat environment lets you test with realistic data before anything reaches your users.
Where will it be hosted?
On a server we run with Docker, health checks and daily snapshots, or on your own infrastructure if you prefer. The same setup runs in every environment.
Sources
- GitHub Docs — Understanding GitHub Actions (checked 2026-10-06)
- GitHub Docs — About protected branches (checked 2026-10-06)
- Docker Docs — Compose application model (checked 2026-10-06)
- Docker Docs — Compose file reference: services (healthcheck, depends_on) (checked 2026-10-06)
- GDPR, Chapter IV (Articles 28 and 32) — CNIL edition (checked 2026-10-06)