Staff repeatedly copy information between systems.
Custom software for SMEs
Custom software for processes your existing tools don't handle.
VertexWare builds custom business software for small and medium-sized companies with manual workflows, disconnected systems, and ageing applications. You work directly with the engineer doing the implementation.
Tallinn · Working across the EU · English · German · Spanish
Operational problems
VertexWare may be a good fit if…
An important workflow depends on spreadsheets.
An internal application no longer has a maintainer.
Old software is becoming risky to change.
Existing SaaS tools almost solve the problem but leave a gap.
You are considering custom software but are not sure it is justified.
Services
Software for the work that actually needs doing.
process-automation
Process Automation
Automate repetitive business work such as copying data, generating documents, handling approvals, validating imports, and preparing reports.
- Staff copy data between systems.
- A workflow depends on spreadsheets and repeated manual checks.
- Documents, approvals, imports, exports, notifications, or reports are prepared the same way every time.
What this can improve
- Less duplicate data entry
- Fewer manual preparation steps
- A process that can be checked when something fails
internal-tools-integrations
Internal Tools & Integrations
Connect the systems you already use and build the tools needed to fill the gaps between them.
- A quoting, customer, inventory, or administration task has no suitable tool.
- Your CRM, ERP, portal, or reporting system does not share the data people need.
- Existing SaaS products almost fit, but an important task remains manual.
What this can improve
- One place to complete the task
- Data exchanged without repeated re-entry
- A focused tool that keeps the SaaS products already working
legacy-modernisation
Legacy Software Modernisation
Modernise critical software without a big-bang rewrite.
- An unsupported Java or Spring runtime makes changes risky.
- Tightly coupled code and weak documentation slow maintenance.
- The system needs migration, but the business cannot pause for a rewrite.
What this can improve
- Supported runtimes and dependencies
- Smaller areas that can be changed safely
- Less risk when future changes are needed
software-rescue
Software Rescue & Maintenance
Take over software that no longer has a reliable maintainer.
- The application has been abandoned or poorly documented.
- Releases are unstable and dependencies are unknown.
- An unattended backlog and technical debt make ordinary changes risky.
What this can improve
- A reliable build and deployment process
- Known dependencies, risks, and next changes
- An agreed maintenance or handover arrangement
Selected work
Client work
German Government via European Dynamics · 2023–present
Modernising a Public-Sector Infrastructure Application
SIB-BW2 manages street-object infrastructure for public-sector stakeholders. The application required ongoing feature work, bug fixes, quality work, and migration from an older Java/Karaf runtime to a current stack.
Result
The team is migrating the application from Java 8/Karaf to Java 21/Spring Boot while development continues.
Read the case studyKleiberit GmbH · 2019–2023
Digitising Manufacturing Workflows and Access Control
Kleiberit needed operational workflows and internal software to support resource ordering, access control, laboratory records, and manufacturing-related processes.
Result
Resource ordering had a redesigned process and supporting software.
Read the case studyWorking relationship
Work directly with the engineer building your software.
- You work directly with Luis throughout the project.
- There is no account-management layer between you and the implementation.
- Scope and assumptions are written down before development starts.
- You receive the agreed source code and project documentation.
- After launch, the application can be handed over or maintained under an agreed support arrangement.
- Projects range from focused audits and small integrations to longer application development and modernisation work.

Direct contact
The engineer behind VertexWare
Luis Martin Schick is founder and lead software engineer. His work includes industrial process software, public-sector infrastructure systems, Java/Spring modernisation, data migration, reporting, and technical documentation.
VertexWare OÜ is registered in Estonia and based in Tallinn.
Luis Martin SchickDelivery
How a project works
- 1
Understand the problem
Review the current workflow, software, data, and constraints.
- 2
Define the scope
Agree what will change, what will not, and how the result will be checked.
- 3
Build and review
Deliver small versions that you can test before moving on.
- 4
Launch and hand over
Deploy the solution, document it, and agree how future maintenance will work.
Low-risk entry
Software & Process Audit
Know something needs to change, but not what to build? I review the current process or system and provide a written recommendation covering the main problems, risks, what to build, buy, integrate, or leave unchanged, rough scope, dependencies, and next steps.
See the audit offerDecision rule
Not every problem needs custom software
- Use an existing product when it solves the problem well.
- Do not automate a rare or unstable process.
- Choose configuration when it closes the gap.
- Do not build when the likely saving does not justify development and maintenance.
Custom development makes sense when the process is specific enough that off-the-shelf tools create more work than they remove.
Questions worth answering before a build
How much does custom business software cost?
It depends on scope, integrations, data quality, and operational risk. After the initial conversation, I recommend a small next step and provide a written estimate before implementation. I do not publish made-up price ranges.
How long does a typical project take?
The timeline depends on the workflow, integrations, data, and release scope. Projects can be focused audits or small integrations, or longer application development and modernisation work.
Who maintains the application after launch?
I can hand the application over with source code and documentation, or continue maintaining it under an agreed support arrangement.
Can you work with existing software?
Yes. I review the current code, runtime, data, deployment, and operational risks before recommending an upgrade, integration, partial replacement, or no change.
Can you take over software built by somebody else?
Yes. I start by getting the application building reliably, identifying infrastructure and dependencies, recovering deployment knowledge, and documenting immediate risks.
Do you work with companies outside Estonia?
Yes. VertexWare is based in Tallinn and works remotely with companies across the EU.
Do you work in German?
Yes. Stakeholder communication and technical documentation are available in English, German, and Spanish.
When does custom software not make sense?
When a standard product solves the problem well, the process is rare or unstable, configuration is enough, or the likely saving does not justify development and maintenance.
What if an off-the-shelf product already solves the problem?
I will recommend it. VertexWare can help assess, configure, or integrate it and only build the missing gap when that creates enough value.
Have a process or software problem worth checking?
A short conversation is enough to decide whether an audit, a small build, or no custom software is the right next step.
Request a 30-minute consultation