Custom internal tools and business apps for SMEs

When custom web application development makes sense

When an order moves between email, Excel and phone calls, it becomes hard to see who acts next. First we check whether your existing software can be configured to do the job. A new application is not always the right answer.

• Existing software: when it already supports your workflow but needs clearer configuration or an agreed team process.
• System integration: when both tools work but you manually copy data between them.
• A custom application: when you need order workflows, approvals, user roles or records that your current tools cannot support.

What the first useful version solves

We choose one process with a clear beginning and end. For example: an order received, its data checked, a task assigned and a completed record. This is an illustrative example, not a client's private application.

• One entry point: the agreed data and documents in one place.
• A clear next step: status, responsible person and due date.
• Exception handling: incomplete or duplicate requests go to review instead of moving on automatically.
• A traceable outcome: who approved what and when the work was completed.

How we check that the solution works

Before development we agree the scope, user roles and success criteria. The quote separates development from hosting, external licences, data migration and ongoing maintenance. Replacing every system is not automatically part of the first version.

We check the prototype with the people who will use the application. Before handover we test an ordinary case, missing data, duplicate entry and a rejected approval. We also check what each role may view and change.

During the pilot we compare processing time, corrections and open requests with the previous way of working. Further features follow real use rather than a long wish list.

What we need for a useful estimate

You do not need a technical specification. For the first conversation, describe one concrete task. Remove confidential data from any examples before sharing them.

• How the task starts, who is involved and what counts as completion.
• How often it repeats and where you spend the most time.
• Which tools you use and whether their data can be accessed.
• An anonymised form, spreadsheet or document and the most common exception.

Frequently asked questions

• How much does an internal application cost? Smaller applications for a clearly defined process start at EUR 2,500 excluding VAT. More complex multi module systems run EUR 8,000 to 25,000 excluding VAT. The final scope and price are confirmed in a written quote.
• Will the application connect to our accounting system? It depends on your solution and licence. With systems such as Pantheon, Minimax or SAOP a connection is technically possible via API or structured export; I verify feasibility for your specific case before estimating.
• Who owns the application? You do. The code is yours, the access is yours, the infrastructure is in your name.
• Do we have to replace all our software? No. We first check what already works. If configuration or a connection between existing systems solves the problem, there is no need to build an entirely new application. Integration feasibility depends on access, licences and data quality.
• Can we see other clients' internal applications? We do not publish clients' private applications or business data. The website shows generic demonstrations and publicly accessible projects. Your workflow is presented in a separate prototype using agreed test data.