Custom software and business applications
Most companies do not suffer from a lack of software. They suffer from software that does not talk, and from spreadsheets that hold the rest together.
- Expertise
- Product & software
- Nature
- Internal app, back-office, business tool
- Scope
- Scoping · product · interfaces · architecture
- Stack
- TypeScript · PostgreSQL · documented API
- Ownership
- Code, data, and documentation delivered
The project in practice
- Who it is for
- SMEs repeating data entry, relying on a critical spreadsheet or needing to connect existing tools.
- What is delivered
- Process mapping, priority scope, interface, business rules, permissions and acceptance testing. Migration and integrations are planned around the systems involved.
- Budget and conditions
- €12,000 – €16,000 excl. VAT
Calculator reference for standard business software. Roles, migration, interfaces and deployment constraints determine the quote.
- What the quote defines
- Scoping compares keeping, connecting and replacing. Code, data and documentation are handed over as agreed; licences, operation and further changes are separated from initial development.
Why the spreadsheet always comes back
A package imposes its model. When your craft diverges — and it always does somewhere — teams invent workarounds: a parallel spreadsheet, a hijacked column, a shared folder, a naming convention only one person knows.
Those workarounds are the best specification that exists. They describe exactly what the official tool cannot do, and what the craft actually does. We always start by listing them.
The goal is not to replace everything. It is to build the missing web tool, connected to the ones that already work, and to remove the double entry that costs most — in time and in errors.
From observation to production
- 01
Understand
We watch people work. Real flows, roles, edge cases, regulatory constraints, the moments it jams. Serious scoping is worth months of misdirected development.
- 02
Prototype
Manipulable mockups on the screens that carry the value, before the code. An interface is judged by using it, not by describing it — and a rejected prototype costs days, not a season.
- 03
Build
An explicit architecture: a defensible data model, business rules in the right place, a documented A connection that allows two pieces of software to communicate., tests on what is expensive to break — then observable deployment. The aim is that another developer can take over the project.
- 04
Ship and follow
Progressive production, training, observation of use. The first weeks always reveal things nobody had said: that is when you correct them.
How we work
- Scope is written and negotiable; what is deferred is said, not forgotten.
- You see something real running on a regular cadence, not a progress report.
- Data is modelled to last: that is what costs most to fix later.
- Documentation is part of delivery, not an option.
- You stay owner of the code and the database, and free to change vendor.
See the work behind this expertise
Current studio projects showing product, design and development decisions.
What we get asked most
The answers we give anyway at the first conversation.
How do you know custom work is justified?
A few signals: your teams keep spreadsheets to compensate for the official tool, you pay licences for features you do not use, or a central rule of your craft cannot be expressed in the package. If none apply, stay on what you have.
Can you take our current data?
Yes, and it is a stage of its own: extraction, cleaning, model mapping, verified import. A sloppy migration fails a project that succeeded technically.
What if we change vendor?
Nothing blocking, provided it is planned from the start: versioned and delivered code, a standard database, a documented A connection that allows two pieces of software to communicate., a written deployment procedure. That is our default way of working.
Do you work with our in-house developers?
Yes, often: as reinforcement on part of the product, taking over an existing system, or scoping and architecture with internal execution. The mode is decided from your resources.
What often comes with it
Apps, business tools, and infrastructure: what keeps an activity running every day.
- Product & softwareWeb applicationsCustom web applications: complex journeys, real time, roles, and data. Reached from a browser, with no install and no store.
- Product & softwareAI solutionsWire AI into your business tools: automate repetitive work and give time back to teams. Agents under human control, data in Europe.
- Product & softwareSaaS developmentCustom SaaS development: multi-tenant architecture, subscriptions, roles, and operations. A studio that runs its own SaaS in production.
- Product & softwareInfrastructure & securityDeployment, hosting, CI/CD, authentication, backups, and observability. Put a product in production and keep it safe without slowing its evolution.
A business tool to build or take over?
Tell us the problem, not the spec. We will scope together what is justified.
Start a project Reply on business days · contact@anym.fr