Service

Custom Software

Custom software for processes that off-the-shelf software only covers through workarounds — almost always as a web application, from analysis through data model and development to operations.

Overview

What it is — and what it includes.

Custom software is software tailored to a company’s processes — as opposed to off-the-shelf software, which makes processes adapt to its own rules. At Batunet, it is almost always built as a custom web application: used in the browser, with its own data model, roles and interfaces to existing systems. We build such systems where requirements are complex, business-critical and long-term.

Scope of services

  • Requirements and domain analysis
  • Architecture and data model
  • Implementation as a web application with backend, frontend and APIs
  • Development with tests and reviews
  • Integration into existing systems
  • Operations, maintenance and ongoing development
Use cases

Which projects it fits.

Typical situations companies bring to us — and where we have published work on them.

  1. Processes spread across several tools

    Quotes, projects, materials and billing describe the same work but live in separate tools and are reconciled by hand. Custom software brings them together on one shared data model — structured around your company’s business areas.

  2. Rules no standard product knows

    Special terms for dealers and sub-dealers, credit balances instead of a shopping cart, commissions split between member and operator: where the business model itself is what’s special, off-the-shelf software only covers it through costly customization.

  3. A portal for customers, dealers or partners

    External users need to submit orders, view data or manage listings — each with their own roles, permissions and workflows. We build the portal together with the system behind it, not as a facade in front of it.

  4. A grown system that has to keep running

    The existing application carries the business but is technically outdated or hard to change. We take it over, secure the existing knowledge and renew the foundation step by step in live operation instead of rewriting it in one go.

How a project runs

From the first conversation to a running system.

Every project follows the same four steps. You see and review interim results along the way, not only at the end.

  1. 01

    Understand the goals and requirements

    The first conversation, with our management, is about the process that isn’t working well today. We clarify stakeholders, data and connected systems — and tell you honestly whether custom software is the right path or whether a standard product is enough.

  2. 02

    Plan the solution and architecture

    We also uncover the requirements nobody has spelled out. From these come the scope, the data model, the key architecture decisions and the order of implementation — all written down.

  3. 03

    Build and review together

    The hardest business path is built end to end first, then the breadth — in small steps you can see and review, with tests where errors are expensive.

  4. 04

    Launch and keep supporting

    After launch, we take over operations, maintenance and further development if you wish. The project-specific source code and documentation are handed over to you.

What working together looks like in detail →
Outcome

What you have in hand at the end.

  • A system that fits your processes — not the other way around

  • You own the source code and documentation of your system

  • A foundation that stays extensible for years

Questions

Questions about Custom Software

  • When does custom software pay off compared to off-the-shelf software?

    When your process is a competitive advantage, no standard solution covers it, or customizing off-the-shelf software becomes more expensive than targeted custom development.

  • Do we own the source code?

    Yes. The project-specific source code and the agreed project artifacts — documentation, configuration, migrations — are handed over to you. Open-source and third-party components used remain under their own licenses. You stay technically independent — including from us.

Let’s talk about your custom software.

Briefly describe the process off-the-shelf software doesn’t cover, or the system that needs to be replaced or developed further. Your first conversation is directly with our management.