KULIMO — Services
Custom Software Development Berlin: Automation That Frees Up Your Team
Custom software follows your workflows exactly, instead of forcing your team to adapt to the logic of an off-the-shelf program. KULIMO builds tailor-made internal apps for Berlin businesses: they automate repetitive manual work, cut down on admin effort, and give your team room to focus on what matters, your customers, not copying data between three systems.
Book a process intro call
- Quotes & cases
- Scheduling
- Lead capture
- Inventory
- Reporting
- Interfaces
- No license trap
- AI where it helps
Custom software Berlin: the essentials at a glance
This page shows when custom software pays off, what it costs, which mistakes get expensive, and what operations look like afterward.
Off-the-shelf or custom
An honest comparison, including the cases where off-the-shelf software is enough.
What we automate
Seven areas where manual work routinely disappears.
When it pays off
A four-step calculation you can do yourself.
Costs
What drives the effort behind custom software.
Common mistakes
Five patterns that make projects unnecessarily expensive.
Operations and maintenance
What happens after rollout, and what it costs.
Signs your processes are costing you money
Inefficiency rarely arrives with a bang; it hides in everyday work. The typical signals:
Excel is your company software.
Three spreadsheets, three versions, three editors, and nobody knows which one is current.
The same data is entered multiple times.
The order is in the email, the calendar, the invoicing software, and on a sticky note: typed four times, with four chances for errors.
Your tool zoo doesn’t talk to itself.
Appointments here, customers there, invoices somewhere else, and in between, copy-and-paste as the world’s most expensive integration.
Knowledge depends on one person.
“Only Ms. Krüger knows that” isn’t a process, it’s a risk, at the latest when she’s on vacation.
Routine tasks eat up skilled time.
Assembling quotes, sorting photos, retyping reports, shuffling appointments back and forth: work nobody was hired for that still piles up every day.
Each of these signals is a candidate for automation. The process audit shows which one comes first, not gut feeling.
Off-the-shelf or custom software? The honest decision
Not every process needs its own development, and anyone who sells you custom software for every problem isn’t acting in your interest.
| Your situation | Off-the-shelf software | Custom software |
|---|---|---|
| A proven tool covers 95% of your workflow | ✓ | |
| The process is industry-standard (accounting, email, calendar) | ✓ | |
| Your workflow is your competitive advantage and doesn’t fit any template | ✓ | |
| You bend your process to make it fit the tool | ✓ | |
| Per-seat license costs grow faster than your team | ✓ | |
| Several tools constantly have to be connected by hand | ✓ | |
| Your data must not leave the building | ✓ |
Our rule: Off-the-shelf where off-the-shelf is enough. Custom where your process is unique. Often the best solution is a combination: proven tools for the routine, and a tailor-made app for the one workflow that defines your business.
What we automate
Documentation & reports
Inputs become finished documents (appraisals, minutes, reports) instead of hours of writing. Legally sound, consistent, and exportable.
Quote and case management
One continuous process from first contact to invoice, without re-entering data at every step and with a clear status for everyone.
Scheduling and resource planning
Online booking, team calendars, capacity planning: the system handles the calls to reschedule appointments.
Lead capture & sales
Inquiries land in the system in a structured way instead of in an inbox, with prioritization, follow-up reminders, and tracking so no prospect gets lost.
Inventory, warehouse & assets
Vehicles, materials, equipment, rooms: recorded, findable, and with a full history. No more inventory by shouting across the room.
Knowledge and team organization
Instructions, responsibilities, and company knowledge centralized and searchable, so knowledge belongs to the company, not to chance.
Analytics & reporting
The metrics you actually steer by, automatically up to date, instead of monthly Excel tinkering.
From practice: automation running today
Vehicle appraisers: from paper stacks to digital cases
Damage documentation on site, case management, and legally sound PDF export with a digital signature: the entire appraisal process in one system.
View the application →Leads Radar: sales that doesn’t wait for luck
You define your ideal customer profile, the system searches markets and regions and delivers a prioritized list of matching business customers. Research that used to take days.
View the application →AI car photography: listings in minutes instead of hours
Shoot with the iPhone, and the AI handles cut-outs, backgrounds, and the catalog: professional vehicle listings without a photo studio.
View the application →Restaurant management: one system instead of four apps
Reservations, orders, and operations in your own solution, without platform commissions on every order.
View the application →All applications: View overview →
And what about AI?
Honest answer: AI is a tool within the process, not a replacement for the process.
Where AI reliably saves effort today, we use it: image processing (as in our car photography app), extracting data from documents and receipts, drafting recurring correspondence, and pre-sorting inquiries. These are real, measurable time savings.
Where AI is unreliable (binding decisions, legally sound statements, anything that has to be 100% correct), it stays an assistant under human control, or it stays out. Automation that produces errors your team has to fix afterward saves nothing.
In the process audit, we take a sober look at where AI genuinely speeds up your workflow, and where classic, deterministic automation is the better choice.
Your data, your software, your numbers
No license trap
Rented software costs per seat and per month: a line item at 5 employees, a budget at 50. Your custom software scales without a price tag for every new team member.
Your data sovereignty
Hosting in Germany or entirely on your own infrastructure, including a clear answer to the GDPR question of who has access: you.
No vendor lock-in
Code, data, export options, and documentation belong to you. You’re not chained to a vendor that raises its prices as soon as switching becomes painful.
Built to grow
New modules, new roles, new locations: the technical foundation for this is described on our page about web app development.
The path to your own solution
Process audit
We look at your actual workflow: where is there manual work, duplicate data entry, waiting time?Outcome: a prioritized list of bottlenecks, plus an honest assessment of what off-the-shelf software can solve.
Smallest effective release
Which feature set solves the biggest problem first? We start focused instead of with a two-year requirements spec.Outcome: a clearly defined first step.
Delivery in stages
Short cycles, testable milestones, and feedback from the people who work with it every day.Outcome: a solution your team has already embraced at launch.
Operations & growth
Hosting, security, training, and further development based on what everyday use reveals.Outcome: software that grows with you instead of going stale.
When custom software pays off: the simple math
The question isn’t whether custom software costs more than a subscription. The question is what the manual work it replaces costs you.
Step 1: Measure the time
Take the task that comes up most often. How many minutes does it take today, and how often does it occur each week? These two numbers are the basis for any honest decision about custom software.
Step 2: Estimate the replaceable share
Realistically, not all of the effort disappears. Expect sixty to eighty percent; the rest remains checking and deciding, and that’s how it should be.
Step 3: Add the cost of errors
Duplicate data entry causes errors, errors cause rework and occasionally lost orders. These costs don’t show up in any time sheet, but they’re real.
Step 4: Compare over the lifetime
Custom software is a one-time investment with an ongoing maintenance share, not a price per seat per month. From around ten to fifteen users, the comparison with rented software almost always tips in its favor.
From spreadsheet to application: a typical journey
Almost every project starts the same way: with a spreadsheet that was once meant as a stopgap and now carries the business.
Week 1: reading the spreadsheet
We look at the file as it has grown, including color codes, comments, and the three columns nobody can explain anymore. It contains the real process, usually more completely than any process description.
Week 2: extracting the core
Which fields are actually used? Which rules are hidden in the formulas? The result is a data model that follows how you work instead of reorganizing it.
Weeks 3 to 6: the first release
Capture, search, edit, export. Nothing more. This lean version goes into real use early, because that’s the only place where it becomes clear what’s really missing.
From week 7: refining
Now come the things that stand out in everyday use: a report, a status field, a reminder. At this point, custom software grows far more precisely than any concept written in advance.
What custom software costs, and how to gauge it
Flat rates would be unprofessional. Four factors reliably determine the effort.
Number of workflows
A single process with an overview, a detail view, and an export is manageable. Once quotes, orders, invoices, and follow-up come together, the scope of the custom software grows accordingly.
Roles and permissions
A team with identical permissions is quick to set up. Separate views for office staff, field staff, and management mean more logic, and more testing.
Integrations
Every connection to accounting, inventory management, or calendars is a small project of its own, depending on how well the other system is documented.
Data migration
Existing data is rarely clean. Cleanup and migration are a separate line item that we plan for early instead of discovering at the end.
That’s why we scope custom software to the smallest effective version: the one workflow that eats up the most time. This first release is usually in use within a few weeks and funds the next one through the working time it saves.
Five mistakes that make custom software expensive
In practice, these patterns cost more than any technical decision.
The spec that covers everything
If you plan for two years, you build past reality; by the time it’s finished, the process has changed. Custom software is better built in stages that are each usable on their own.
Planning without the future users
When only management describes the workflow, the very exceptions that define everyday work are missing. The best custom software fails on an edge case nobody mentioned.
Rebuilding the standard
Accounting, payment processing, map services: proven solutions already exist for these. Custom software pays off where your workflow is unique, not for what works the same everywhere.
Pushing migration to the end
Legacy data is rarely clean. Leaving migration until last pushes back the launch. We review existing data as soon as the data model is in place.
No budget for operations
Software ages. Without budget for updates, security, and small adjustments, in three years the new solution becomes the same problem you’re trying to solve today.
How to tell the solution is being adopted
Success doesn’t show in the feature list but in behavior. Three observations say more than any report.
The side spreadsheets disappear
When nobody keeps their own file “just to be safe” anymore, the application covers the workflow completely. If side lists keep appearing, a feature is missing, and that’s the best blueprint for the next release.
The questions change
At first, people ask how something works. Later, they ask whether something could work differently. That shift is the most reliable sign that custom software has become part of everyday work.
New colleagues don’t need training
Anyone who knows the workflow should understand the interface within half an hour. If not, the problem is the user guidance, not the people.
We check these three points specifically about eight weeks after launch. The result is usually a short list of small adjustments, and that’s exactly what makes the difference between an application that gets used and one that gets tolerated.
Operations, maintenance, and ongoing development
After rollout begins the part that decides the next several years. Four points should be planned in from the start.
Updates and security
Libraries are updated, vulnerabilities closed, and backups regularly test-restored. We follow the recommendations of the BSI (German Federal Office for Information Security).
Data protection in ongoing operations
Retention periods, access rights, and logs need maintenance. Alongside the GDPR, the legal basis is the German Federal Data Protection Act (BDSG).
Small changes, fast
A new field, an additional report: with well-built custom software, that takes days, not quarters. That’s exactly where the quality of the architecture shows.
Knowledge not tied to one person
Documentation, readable code, and a second point of contact. Custom software must never depend on one particular person being available, neither on your side nor on ours.
FAQ
Frequently asked questions about custom software
What exactly is custom software?
Software developed specifically for your workflows, as opposed to off-the-shelf software built for the average of many companies. It maps your process, not the other way around, and includes exactly the features you need, without the bloat.
When does custom software pay off, and when doesn’t it?
It pays off when your workflow is unique, several tools are connected by hand, license costs grow with your team, or data sovereignty is mandatory. It doesn’t pay off when a proven off-the-shelf tool covers almost all of your needs, and in that case we’ll tell you so.
How long does development take?
That depends on the first release: a focused tool for one process is ready for use much sooner than a solution with many integrations. After the process audit, you receive a binding stage plan, and the first usable version deliberately comes early.
Can our existing tools be connected?
Usually, yes, through integrations with accounting, calendars, email, payment providers, or inventory management. We clarify what makes sense and can be implemented cleanly during the audit.
Who owns the code and the data?
You do. Including documentation, export options, and, if you wish, operation on your own infrastructure. Switching providers remains possible at any time, and that’s intentional.
Does my team need technical knowledge?
No. The interfaces are built for the people who work with them every day, including onboarding and clear instructions. Good internal software explains itself through the workflow, not through a manual.
Won’t AI soon replace custom software?
AI changes what software can do, but it doesn’t replace the mapping of your processes, permissions, and data. We build AI in where it reliably saves effort and leave it out where precision is mandatory. The result stays the same: your software, your process.
What do the costs depend on?
On the feature scope of the first release, the number of integrations, the requirements for hosting and data protection, and your ongoing support needs. After the audit and scoping, you receive a fixed-price quote with no hidden line items, along with a comparison against your current license and time costs.
How long does it take to get a first usable version?
For a clearly defined workflow, we plan for six to twelve weeks until the first release is in productive use. The deciding factor is rarely the technology but how quickly you decide internally which process moves into the custom software first.
How much does maintenance cost per year?
As a guideline, plan on about fifteen to twenty percent of the development cost per year. That covers hosting, updates, backups, security checks, and a budget for small adjustments. Planning custom software without this line item only pushes the costs further down the road.
Can multiple locations work with it?
Yes. The application runs in the browser, there’s nothing to install, and every location sees the same data. Different permissions, numbering sequences, or languages per location can be set up without duplicating the custom software.
What happens if we end our collaboration?
You receive the source code, data, and documentation in full and in usable form. The application keeps running on your infrastructure, and any other development team can take over. There’s no license that expires and no key we hold on to. With custom software, that’s the decisive difference from rented software.
Do you also continue work on an existing application?
Yes, provided the code is readable and the database is structured in a way that makes sense. We start with an audit of the architecture, dependencies, and open security issues, then tell you honestly whether further development or a rebuild is more cost-effective. In about half of all cases, taking over is worth it, especially where business logic has grown over years.
Which process costs your team the most time?
In the intro call, we pinpoint exactly that one process and clarify honestly whether a tailor-made app, an off-the-shelf tool, or a combination solves it best. No obligation, concrete, and no sales pressure.
Book a process intro call