OpenFOAM development may sound a little fuzzy at first, but it describes what we’ve been doing for the longest part of our work with OpenFOAM: we have been developing custom libraries and applications for it. Most of the OpenFOAM development was done as part of our individual work at the universities. We started sourceflux with the goal in mind, to continue developing for OpenFOAM, but not only for our particular universities. We have extensive experience with code- and method-development in almost any area of OpenFOAM:

This covers anything from extending a solver to a transport equation (e.g. adding temperature to interFoam), to adding complete new functionalities to it (e.g. pressure-velocity coupling, fully implicit solvers). We have extensive experience in extending solvers by novel functionalities.
By simulation automatization we wean the automatization of the entire CFD workflow (or parts of it). This can be a taylor-made meshing tool, a method to configure and dispatch simulations automatically and automatic post-processing of the results. If you happen to simulate mostly similar geometries and setups, we can help you to automate the entire process and deliver a interface which requires just a few user inputs to launch the CFD workflow.
Of course, coupling OpenFOAM with any other library or tool is not necessarily the most straight forward task to tackle. External libraries can be anything from something as general as mySQL, boost or CGAL or specialized tools, such as potential flow codes or Finite-Element solvers for Fluid-Structure Interaction.
If the existing methods in OpenFOAM are not capable of accounting for your particular simulation needs, a new method might be necessary to be implemented. This can  be anything from a new pressure-velocity coupling method or transport model to an Immersed Boundary Method (IBM). With our expertise, we can deal with any degree of complexity.