30 business application examples, by department and by industry

A business application, sometimes called line-of-business software, is software built around a process specific to your business: a quote with complex pricing rules, a service visit at a customer site, a production order, a file that moves between five departments. This catalogue gives 30 concrete examples, grouped by department and then by industry, each with what it replaces and the signal that says it is worth building.

Most lists of "business application examples" stop at software categories: CRM, ERP, HR, accounting. Those are products you buy. The examples below are the processes companies end up building for, because no standard product fits them well.

If you want the definition first, and how a business application differs from an ERP or a packaged product, read what is a business application. Here we go straight to use cases.

How to read these examples

Each example follows the same pattern: what was there before (often a spreadsheet, paper and email), what the application does, and the signal that the need is real. None of them is a client project: they are needs that come up from one company to the next. Some also exist as off-the-shelf software; we say so when that is the case, because it is often the better option.

Examples by department

Sales

1. Quote configurator. Before: a pricing spreadsheet only the most senior salesperson understands. The application applies price lists, options, customer discounts and measurements, then produces the quote. Signal: two salespeople give two different prices for the same request.
2. Referrer tracking. Architects, engineers, accountants who recommend you without buying. The application links each deal to its referrers and measures their influence. Signal: you do not know who brings you your best projects.
3. Reseller portal. Distributors check stock and their own prices, and place orders. Signal: the sales team spends its days answering "is it in stock?".
4. Tender management. Bids, lots, submission deadlines, required documents, outcomes. Signal: a missed submission deadline.

A standard CRM covers the classic sales cycle well. These examples cover what falls outside it, when selling does not follow a simple funnel.

Production and the shop floor

1. Production order tracking. Before: paper job cards pinned to a board. The application follows each order step by step, with time recorded on a tablet. See our guide to production tracking software.
2. Batch traceability. Which material, supplier, machine and operator for each batch shipped. Signal: a product recall that would take days to reconstruct.
3. Equipment maintenance. Preventive maintenance plans, breakdowns, parts replaced, history per machine. Signal: the same failures keep coming back and nobody connects them.
4. Non-conformance management. Report at the workstation, analysis, corrective action, verification. Signal: quality forms pile up with no follow-through.

Field teams

1. Field service management. Technician scheduling, job sheets on a phone, report, photos, customer signature, invoicing triggered. Our article on custom field service software goes into detail.
2. Inspections and site surveys. Guided forms, annotated photos, report generated on site. Signal: reports are retyped in the office every evening.
3. Delivery rounds. Stop order, proof of delivery, incidents. Signal: "never received" complaints you cannot check.
4. Stock counts and readings. Barcode counting, discrepancies reported immediately. Signal: an annual stocktake that shuts the warehouse for two days.

Purchasing and logistics

1. Purchase requests with approval rules. Who requests, who approves depending on the amount, which budget is used. Signal: purchases discovered when the supplier invoice arrives.
2. Goods receiving and inspection. Quantities, discrepancies, damage, photos. Signal: supplier disputes lost for lack of evidence.
3. Order picking. Optimised pick lists, barcode checks. Signal: recurring shipping errors.

Human resources

Payroll and core HR administration belong to off-the-shelf software. Custom work covers what is specific to your organisation.

1. Rotas and on-call schedules with specific rules: skills required per post, shift patterns, constraints from a collective agreement.
2. Certification and mandatory training tracking, with an alert before expiry. Signal: an employee sent to a site with an expired safety certificate.
3. Onboarding of new hires: equipment, access, training, buddy. Signal: a new starter with no laptop on day one.
4. Reviews and objectives when the framework is specific to the company.

Finance and administration

Bookkeeping stays in accounting software. Around it:

1. Progress billing, by milestone or stage of works, with deposits and retentions. Signal: every progress invoice takes half a day of calculations.
2. Credit control, staged reminders and disputes. Signal: nobody can state the outstanding balance per customer without an hour of work.
3. Commission calculation for a network of agents or resellers. Signal: disputes every month.
4. Specific reconciliations, for example three-way matching between purchase orders, deliveries and supplier invoices.

Customer service and quality

1. Customer portal: order tracking, documents, requests, with each customer seeing only their own data. Signal: the phone rings to ask where an order is. See our guide to custom client portals.
2. After-sales and warranty management, from return to credit note.
3. Regulatory registers specific to your activity: inspections, periodic checks, waste, traceability required by a customer.

Management and cross-functional

1. Contracts and renewals: due dates, notice periods, price reviews, with an alert before each key date. Signal: a contract renewed by default, or lost for lack of a reminder.
2. Internal knowledge base: procedures, technical sheets, standard answers, found by a plain-language search. Signal: the same questions asked of the same colleague every week.
3. Asset management for vehicles, tools or loaned equipment: assignment, checks, returns. Signal: equipment nowhere to be found when a job starts.
4. Management dashboard connected to the applications above, so the figures shown are the ones from the field. Our article on custom business dashboards compares this route with BI tools.

Examples by industry

Two regulatory notes, both French examples of a wider pattern. In healthcare, health data is a special category of personal data under Article 9 of the GDPR, and France goes further: hosting health data on behalf of a third party requires an HDS-certified host, under Article L.1111-8 of the French Public Health Code, as explained by the French digital health agency. In training, France's Qualiopi certification is required to access public and pooled funding, and a business application can produce the evidence auditors ask for as the work happens. Our article on custom software for training providers covers that case.

An example we publish ourselves

Izi-Devis is quoting and invoicing software for building tradespeople, designed, developed and run by LPR Studio itself. It is vertical software: built for one trade, its documents and its obligations, including e-invoicing. It shows where the line between the two worlds sits: for a tradesperson it is off-the-shelf software; for us it is a business application designed as close to the job site as possible. We do not name applications built for clients: named projects are presented in meetings.

What these 30 examples have in common

Reading the list again, four traits keep coming back:

• a process that already exists, spread across several tools;
• company-specific rules: prices, approvals, checks, exceptions;
• several people or departments working on the same file;
• a visible cost of error: a lost dispute, a job billed wrongly, a recall that cannot be traced.

If your process ticks three of these four boxes, it is a candidate. If it ticks only one, a well-kept spreadsheet or an off-the-shelf tool will do.

When off-the-shelf software is the better choice

Do not commission what follows the same rules for everyone: accounting, payroll, email, e-signature, online payments, generic document management. Specialist vendors build regulatory changes into their subscription, which custom software would have to redo each time. A good business application connects to these tools instead of replacing them.

In well-served industries (real estate, private healthcare practices, hospitality), compare the trade's own software first. Custom development then makes sense for a specific add-on, not for rebuilding everything.

Web, mobile and AI: a few pointers

• Web for office teams: nothing to install, instant updates.
• Mobile, or a mobile-friendly web app, for field work: technicians, drivers, site managers. Plan for offline use if coverage gaps are common.
• AI for reading and sorting tasks: classifying emails, extracting data from a scanned purchase order, summarising a history. It adds to a business application; it does not replace one.

From example to your own project

1. Pick one process from the list, the one that causes the most errors or re-keying.
2. Describe it as it really is, exceptions included, by asking the people who do it every day.
3. Gather the real documents: spreadsheets, forms, standard emails. They are your best specification.
4. Size what is at stake: time spent, errors, delays. Our guide to the cost of a custom business application helps you set that against a budget.
5. See it before you pay for it. We build a free visual prototype, presented by video call within 5 working days, from your real documents. See your software before you pay explains how to prepare.