Custom software terms, explained simply.
32 short definitions to understand a project, read a quote or ask a provider the right questions.
A
- Acceptance testing
The phase where the client tests the delivered application against a planned list of journeys before approving it for launch.
- API
An interface that lets two pieces of software exchange data automatically and in a controlled way, for example a business app and an ERP.
Learn more →
B
- Back office
The part of an application reserved for the internal team: managing orders, customers, content and settings. Customers have no access to it.
Learn more →- Business app
Software designed for a specific use within a company: orders, scheduling, field work, customer follow-up. It often replaces spreadsheets or ill-fitting tools.
Learn more →
C
- Clickable mockup
A visual prototype where you can click from screen to screen as in the future app, before any code is written. It avoids costly misunderstandings.
- Client portal (extranet)
A secure online space where your customers, partners or resellers view their information, track orders or download documents.
Learn more →- Code ownership
The right to use, modify and develop a piece of software’s code. Without a written transfer, it stays with the provider who built it.
Learn more →- Core Web Vitals
Three Google metrics on a page’s loading experience: LCP (main content display), INP (responsiveness) and CLS (layout stability).
Learn more →- CRM
Customer relationship management software: contacts, deals, interactions, follow-ups. It can be bought off the shelf or built to measure.
Learn more →- Custom software
Software designed and built for a specific company, based on its processes, rather than bought as is off the shelf.
Learn more →
E
- E-invoicing
A phased obligation in France to send and receive business-to-business invoices in a structured format, through an approved platform.
Learn more →- ERP
Enterprise resource planning software that brings several business functions together: purchasing, stock, sales, accounting. Often powerful but heavy for a small business.
Learn more →
F
- Fixed price or time and materials
Two ways to bill a project: a set price for a defined scope (fixed price), or payment for time spent (time and materials).
Learn more →- France or EU hosting
Storing an application’s data and servers in France or another European Union country, under European law.
Learn more →
G
- GDPR
The European regulation on personal data protection: it governs what a company collects, why, for how long and how it protects it.
Learn more →
M
- MVP
A first version of a product limited to essential features, to use it quickly and decide what comes next with real feedback.
Learn more →
N
- No-code
Tools that let you build an app without programming, such as Bubble, Glide or Airtable. Quick to start, sometimes limited in security and growth.
Learn more →
O
- Offline mode
An app’s ability to work without a network, then sync data once the connection is back. Essential for field teams.
Learn more →- OWASP Top 10
The reference list of the ten most critical security risks for web applications, published by the OWASP Foundation and used in audits.
Learn more →
P
- Penetration test
A simulated attack run from the outside by a specialist to find exploitable flaws. It complements a code and configuration audit.
Learn more →- PWA
A web app you can install on phones and computers from the browser, without going through app stores, that can work offline and send notifications.
Learn more →
R
- Requirements document
A document describing what an application must do: goals, users, features, constraints, budget and timeline. It is the basis for quotes.
Learn more →- Reversibility
The ability to change providers by getting back the code, data, documentation and access, with no loss and no lock-in.
Learn more →- RLS (row-level security)
Rules set directly in the database so that a user can only read or change the rows they are allowed to.
Learn more →
S
- SaaS
Software rented online by subscription, often billed per user per month. Quick to adopt, increasingly expensive as the team grows.
Learn more →- Scoping
A 1 to 2-week phase at the start of a project to define the need, users, priorities and scope. It ends with a fixed quote.
- SSO (single sign-on)
Signing in to several applications with one account, for example a Microsoft 365 or Google account managed by the company.
Learn more →
T
- Technical audit
A review of the code, configuration, security and performance of a website or app, ending with a list of fixes ranked by priority.
Learn more →- Technical debt
The shortcuts taken in code that make every change slower and more expensive, like interest building up.
Learn more →- Technical due diligence
An audit of software before an acquisition or investment: code ownership, security, technical debt, key-person risk, real costs.
Learn more →- Two-factor authentication (2FA)
A login that asks, on top of the password, for a temporary code sent to or generated on another device. It blocks most account takeovers.
Learn more →
W
- Webhook
A message sent automatically from one piece of software to another when an event happens, such as a payment received or an order created.
Learn more →
A term missing or still unclear?
Ask in a 30-minute call: I answer without jargon, and tell you whether custom software makes sense for your project.
Book a call