Laravel development for companies in Waiblingen

There are firms in the Rems valley leading the world in their niche that nobody outside their industry has ever heard of. That is typical of the Rems-Murr district. A large share of the businesses are family-run, many for several generations, and attention is not among their aims.

Mechanical engineering is the load-bearing pillar, with packaging technology forming a focus of its own and a centre of expertise right in Waiblingen. Electrical engineering and electronics come on top. From Stuttgart the valley is minutes away.

When the spreadsheet reaches its limit

The most common reason for a call from this area is a spreadsheet. It has grown over years, somebody set it up once, eight people now work with it, and there are four versions in different states.

That is not an oversight but the most sensible solution as long as it works. It tips at a recognisable point. When two people write into it at once. When nobody can say any more who changed a figure. When the file is so large that opening it takes a while.

For us, a spreadsheet like that is the best foundation there is. It describes the process more precisely than any specification, because it came about under real conditions. We read the data model out of it and translate it into an application with roles, states you can trace and reports at the press of a button. The approach is described under Laravel development.

Bringing isolated tools together

The second common case: over the years several small solutions have appeared, each sensible in itself. A program for quotations, a database for service dates, a list for spare parts. What connects them is people, carrying data from one place to the next.

That works remarkably long and gets expensive at exactly the moment somebody is away. When bringing them together, the technical side is rarely the problem. What is difficult is agreeing which source is right when two systems show different figures. That question belongs at the start, because the whole data model follows from it.

We keep it small where it may stay small

Not every undertaking needs a large project. Sometimes the most honest answer is that an application for two processes is enough and the rest stays in the spreadsheet. We would rather say that than sell a scope nobody needs.

The other way round holds too: when we notice that an undertaking is considerably larger than it sounded in the first conversation, we say that as well, and before anybody signs anything.

What comes afterwards

An application carrying a working process is not finished at launch. Security updates arrive regularly, requirements change, and at some point somebody asks for a report nobody had thought of. How we look after that day to day is under maintenance and support.