When you look at any app store you might think: There is an app or software for everything. But this is not true. Not every problem has yet been solved. Furthermore, some solutions do not match the individual needs of a company. That is why we develop customized software - for all the unsolved software problems out there.
Three common reasons why customers ask us to develop customized software solutions
Automation: The customer wants to drive automation processes in the company as efficiently as possible. For this he needs an individual software solution. The software shall take into account the specifics of the company while not being expensive.
Business or product idea: The customer has the idea for a new business model or a new product. He also already knows that he needs software that will help him to achieve his corporate goals. We help him to not get bogged down. To do so, we focus on what creates value in software development and leave out what does not bring any benefit but costs a lot.
Technology leadership: The customer plans to keep technology leadership for a new market or a new business area - or wants to become successful in a new territory. This requirement often includes a customized software solution that exactly fits the business field or market.
Individual software with established technology
We build software with modern architecture - and with suitable and proven architecture patterns
We build web apps: SPA, PWA or with Electron. We primarily rely on Angular, React or Vue. When speed is essential, SSR is the choice for us with the help of modern frameworks such as Gatsby or Next.js.
For the backend we often prefer the classical way: with a mostly .NET- or Node.js-based backend and a classical API. Serverless functions allow us to also implement lightweight and cost-effective backends.
The database within the product is either relational or document-based. We have a long history as an Oracle partner with the Oracle database. By now we often use MSSQL or PostgreSQL. Regarding the document-based databases, we work with NoSQL databases - such as Azure Cosmos DB solutions, CouchDB or MongoDB.
We operate on iOS or Android either via Cordova or natively.
Our infrastructure runs on Microsoft Azure. This enables us to technically implement any application. We have a wide range of deployments for various compliance needs in Germany and Europe.
We start with intense consulting - not just with any software development
For us, a new project doesn't start with the first line of code. It starts with one or several meetings with the customer and with intense and detailed consulting. We do so, because we want to understand exactly what it is about before we get started. Only when we know your problem we are able to consult what is the best way for you and with regard to your financial resources.
Why is intensive consulting on agile software development so important?
We could just take it easy and get started first. But our experience of over three decades shows: this is a bad idea. It is much better and also much more efficient if we only develop as much - and for as long - as it is appropriate for the product. That is why we take a lot of time to get to the bottom of your core problem. Based on this, we develop possible solutions: the software you really need. This is customized software development.
„Sometimes our customers already have very specific ideas about what they want. Sometimes they just have an initial idea. And sometimes they already have software but are not satisfied with it. We want to get to the core of the matter with intensive consulting.“
IT pioneer Detlef Pahl - Head of Individual Software Development OHB Digital Services
Close to the customer: Why we rely on agile software development
After the comprehensive consultation, the agile development process is an iterative cycle and not a linear process without the possibility of intervention. For companies that have to assert themselves in an increasingly digital environment, this is a real benefit. In short cycles, you always have the opportunity to do a check on everything:
Does the project go in the right direction?
Are the ideas from the beginning of the project still compatible?
Did the basic assumptions for the project change?
Did we gain new insights that will advance the product?
Has the desired success been achieved with the versions that are already in use? If so, are we done? If not, what do we need to change?
→ With these checks you can respond to uncertainties in agile software development - without having to start from scratch again.
In the past we have questioned the clear ideas of our customer in many agile software projects. We will certainly do the same in your project. This "challenging" is not a self-purpose, but leads to better results. Because sometimes the rock-solid basic assumptions are no longer that rock-solid when you talk about them. The result: The software project is often much more simple than initially assumed.
Agile software makes change controllable
Of course, there are also projects or products in which software development is very linear - from conception to rollout. But the phrase “this is how it has to be and no other way is accepted” is becoming weaker and weaker, especially in individual software development. We have been observing this for a couple of years.
"In the case of customized software, the proportion of agile software development is significantly increasing. From my point of view that’s not a surprise given the rapid change in the world. Companies have to respond quickly to a new environment. That works very well in an agile process."
IT pioneer Dr. Arne Gausepohl - Managing Director OHB Digital Services
The pressure on companies is increasing. If they fail to implement the strategic projects within a certain (and usually short) period of time, the project “dies” - or the company is left behind completely. The corona pandemic has uncovered that there is a lot of catching up to do when it comes to digitalization. Furthermore the strategic development processes are often too cumbersome.
Our theory: You will be successful as a company if you manage to constantly focus on the right topics, the right methods and the right technology. Losers in this development cannot change their business model quickly enough - and they cannot survive the change.
We build intelligent and clear software
Software always plays a role in these changes. Software drives change and software also makes change controllable. Even today, we no longer program applications that only carry out simple tasks. Instead, we build apps that allow users to solve complex problems quickly. You should not only be able to make decisions quickly, but also do your work with software that you love.
The agile development of individual software products has obvious advantages
Agile software development avoids risks: In agile projects, we avoid unnecessarily rigid technical and contractual frameworks. If the environment changes during implementation, we can react very flexibly and avoid risks for the customer.
Agile software development avoids wrong decisions: In agile projects, we work transparently for the customer. Everyone who is involved can make the best possible decisions.
Agile software development avoids misdevelopments: We made good experiences with short feedback loops between the customer and the development team. This is how we avoid unnecessary misdevelopments.
"With today's web technologies, pulling up a project is a breeze. We use technologies that have outgrown their infancy and use them to build solid applications with a modern architecture. The applications convince with a clear separation of responsibilities, solid database design and good cuts in the services."
IT pioneer Renee Rickling - software developer at OHB Digital Services
Not only Scrum: We also use these methods for agile software development
Agile software development: Methods like Scrum and Kanban often come straight to the table. But which agile method is the right one? Opinions differ on this. For some it is Scrum, for others it is Kanban. And if so, then it has to be exactly the same as the Scrum Guide.
We don't agree with that and don't think in terms of a several pattern. Of course, we also largely rely on Scrum: short cycles, iterative processes and small steps. But we have adapted Scrum in a way that it fits to us. Because it is crucial for success to see yourself as a team that develops the products in close cooperation. This is much more important than just the choice of the method.
Our teams represent agile values much more than that we follow a strict development method. The team decisions are the basis of a project or a team:
Are all people on board we need to get the project started?
Do we have the required funds?
Do we have a team that deserves the name “team”?