Skip to content
MS DEV STUDIO

Service 03 / Business software

Software for the part of the business nobody sees

Internal systems that replace spreadsheets, shared inboxes and the one person who remembers how it works.

Discuss an internal system Open the configurator

Business software

Service 03

Best suited to
Operational teams
Typical scope
Workflow to application
Built for
Clarity and scale
Platform
Laravel / APIs

Starting at

EUR 6,500

Larger business systems, with more modules, roles and integrations, go beyond EUR 20,000. The scope is defined together, before the first line of code.

The price range is indicative and not a quote. Depending on the scope and details of the project, the final price may be higher.

The problem

Manual work should not be your integration layer

Critical work is often spread across spreadsheets, inboxes and disconnected tools. People move the same information repeatedly and the true status of an operation remains difficult to see.

A focused application turns those steps into one coherent workflow, keeps business rules explicit and gives every role the information required to act with confidence.

What gets built

An operational system,
not another workaround

The application is organised around the real operation: its roles, decisions, exceptions and connections with the rest of the company.

  • Workflow and domain model

    Business concepts, states and permissions translated into a clear technical foundation.

  • Operational workspace

    Dashboards and tools designed around the decisions each team member needs to make.

  • Client and partner portals

    Focused self-service experiences that expose the right data and actions securely.

  • Automation and APIs

    Reliable exchanges with existing tools, notifications and routine work handled automatically.

  • Deployment and long-term care

    Measured releases, monitoring and an architecture ready for the operation to evolve.

Boundaries

What is not included

  • Server, domain and third-party service costs, such as SMS, email or paid APIs
  • Moving existing data, unless agreed as a separate item
  • Further development and maintenance after delivery, agreed separately

Engagement

From fragmented steps
to one working operation

The application emerges from the workflow itself, with real users and edge cases present throughout design and development.

  1. 01 Understand

    Understand

    Map the operation

    Map the operation. Roles, decisions, data, exceptions and existing systems.

  2. 02 Shape

    Shape

    Model the rules

    Model the rules. Structure and interface tested against real scenarios.

  3. 03 Build

    Build

    Release the core first

    Release the core first. Useful stages that expose assumptions before they become debt.

  4. 04 Evolve

    Evolve

    Improve with the operation

    Improve with the operation. Monitoring, support and deliberate expansion after launch.

Under NDA

The work is real - the names are not mine to give

These systems run inside client companies. They hold customer records, pricing logic and internal process, which is exactly why none of them appear here by name or screenshot, and the sector is described only in general terms.

What follows describes what the systems do and how they are built. It does not describe whose they are. If that discretion is what you want for your own operation, it is the same discretion you would get.

Systems under NDA

Six systems,
without the client names

Each row is a system I built from the ground up. The sector is described in general terms; names, places and figures stay with the clients.

  1. Fleet-based services

    Operations and back office for a service company

    • Bookings and capacity planning
    • Pricing with promotions and vouchers
    • Fleet and inspections
    • Shifts, time tracking and payroll
    • Bank statement import and monthly close
    • Two-way sync between installations

    Laravel 11 · Blade · Alpine.js · MySQL

  2. Vehicle sales

    Operations and finance for a vehicle dealer

    • Stock with profit calculation
    • Deposits, instalments and trade-ins
    • Numbered PDF contracts
    • Four-eyes approval of changes
    • Sync with a classifieds marketplace
    • Exchange rates and financial reports

    Laravel 12 · Blade · Alpine.js · MySQL

  3. Healthcare / private practice

    Practice management for a private clinic

    • Calendar across rooms and practitioners
    • Patient records and history
    • PDF reports with a QR code
    • Tablet check-in with signatures
    • Loyalty programme
    • Ten roles with permissions

    Laravel 12 · Blade · Alpine.js · MySQL

  4. Fitness / personal training

    Operations platform for a personal-training business

    • Session booking by time slot
    • Coach payroll and payslips
    • Client portal with progress
    • Training plan builder
    • HR from candidate to contract
    • Tasks and notifications

    Laravel 13 · Blade · Alpine.js · MariaDB

  5. E-commerce

    Purchasing and price tracking for an online store

    • Offer matching by barcode
    • Competitor price history
    • Reorder suggestions and purchase orders
    • Import centre with rollback
    • Turnover and lost-sales reports
    • Connected to the WooCommerce store

    Laravel 12 · Blade · Alpine.js · WooCommerce API

  6. Non-profit

    Donor and pledge management

    • Statement import with column mapping
    • Imports that can be undone
    • Month-by-month arrears
    • Regional branch hierarchy
    • PDF reports
    • Two-factor login

    Laravel 12 · Blade · Alpine.js · MySQL

Business software

All six systems are in production. All of them are maintained continuously.

In production

6 of 6

Stack

Laravel 11–13

What these systems do

01

Records and relationships

Customers, contacts, companies and the history between them

02

Roles and permissions

Who sees what, who approves what, and a trail of who changed it

03

Documents

Contracts, offers and reports generated rather than typed

04

Scheduling and availability

Calendars, capacity and conflict detection

05

Integrations

Payment, accounting and third-party systems connected once

06

Reporting

Numbers the owner trusts enough to make decisions on

07

Migration

Years of spreadsheet history moved in without losing any of it

Project configurator

What would your project cost?

Six short questions, a price range right away and a PDF spec at the end.

Project type
Business software
Price range
EUR 6,500 – 9,000
Timeline:
8–12 weeks
Open the configurator

The price range is indicative and not a quote. Depending on the scope and details of the project, the final price may be higher.

Before we begin

Questions before
custom software

Custom development is useful only when it removes a real operational constraint. These are the questions worth answering first.

When the workflow creates meaningful business value and existing products force repeated manual work, fragile workarounds or compromises that cost more than a focused system would.

Yes. The current workflow is mapped first, including the informal rules hidden in spreadsheets and inboxes. The application can then be introduced in phases around real operational use.

Usually, yes. APIs, webhooks and scheduled synchronisation can connect internal tools, payment systems, ERPs and external services while keeping failure states visible and recoverable.

Roles, access boundaries, audit needs and data retention are defined during the architecture phase. Security is treated as part of the workflow, not as a final checklist item.

Yes. The system is structured for staged delivery, measured use and further development. Documentation and ongoing support preserve the context behind its decisions.

New engagement

Let us turn the workflow into software that fits

We can map the workflow, bottlenecks and system boundaries before deciding what needs to be built.

Start a conversation