Daniel Ortega
Managing Director
Sample entry. Leads scoping and is the named contact on most engagements. Twenty years across software delivery and IT operations.
Company
There is no account manager between you and the people building your system. The person who scoped the work is the person who delivers it, and the one who answers when you call.
The team
Managing Director
Sample entry. Leads scoping and is the named contact on most engagements. Twenty years across software delivery and IT operations.
Head of Engineering
Sample entry. Owns architecture and delivery standards, and runs the build teams on custom software projects.
Head of Cybersecurity
Sample entry. Runs assessments, hardening programmes and incident response, and handles NIS2 and GDPR readiness work.
Cloud and Platform Lead
Sample entry. Responsible for migrations, platform engineering and the delivery pipelines behind everything we run.
How we are organised
Every engagement has a named person who owns it end to end.
Whoever scoped the work stays on it through delivery.
You talk to the people building it, not to a layer in front of them.
Documented work, so support never depends on one person being available.
Questions
A named lead for the engagement, and the engineers doing the work. We are deliberately small — there is no account management layer to pass you between.
Work is documented and shared rather than held in one person’s head, so cover does not mean starting the conversation again. That is a deliberate operating rule, not a happy accident.
Yes, and we would prefer it. Thirty minutes, no slide deck, no obligation — we will ask about your process before suggesting anything.
Get in touch
We use what you send to reply to you, nothing else.