OBLIQ was founded by a software engineer and a renewable energy engineer with a business development background. We build software around the way a team already works, and we are wary of AI that nobody in the room can explain.
Both co-founders stay directly involved in every project. You get the technical view and the business view from the same two people who made the decisions.
Every engagement starts with the workflow, the people who run it, and the constraints they work within. The technology is chosen to fit that picture, not the other way round.
You know who is doing what, and you can talk to the people making the decisions. On our projects, those are the two co-founders.
We pick the architecture to fit the requirements, not the fashion. Testing, documentation, and handover are planned from the first conversation, because the code will outlive the project.
Co-Founder · Software Engineering & AI Solutions
Alessandro is the software engineer at OBLIQ. He builds the applications and integrations and is the one who has to maintain them afterwards, which shapes how he builds them. His interest in AI is practical: where it saves a team real time, and where a person should still check the output.
Co-Founder · Business Development & Renewable Energy
Katarzyna is a renewable energy engineer with project management and business development experience. She works out which operational problems are worth solving with software, and keeps the scope tied to what the users and the business need rather than what is technically interesting.
Between them they cover the engineering and the business side of a project. Both want AI that is useful, that a person can understand, and that a person can overrule.
Four rules we hold ourselves to, from the first conversation to the support after launch.
We start with your workflow, goals, and constraints before choosing the technology.
Where AI is involved, a named person reviews the output before anything with consequences happens.
Agreed milestones, regular updates, and the founders' email addresses. No account manager in between.
Tests, documentation, and a proper handover are part of the scope, so someone else can pick the code up later.