Where the standards we work to come from
Good IT rarely fails on the technology. It fails on care, on missing documentation, and on nobody feeling responsible.
Khodor Kassem has worked in corporate environments where every change had to be documented, justified and approved before it went anywhere near a system. He then took responsibility for the entire IT of a mid-sized company, where the same care was needed but no procedure existed for it. Ruknova grew out of that combination.
The deciding factor was something that repeats itself in every other company: IT gets bought in pieces. One provider looks after the network, a second the phone system, a third the website. When something jams, each points at the next, and the managing director ends up sorting it out. Keeping those areas together is how we close that gap.
What follows from that has less to do with technology than with orderliness. Every change is recorded, every recommendation explained, every set of credentials belongs to the client. It is unspectacular and goes unnoticed for months. It shows on exactly one day: when something fails, when an audit is due, or when somebody else has to carry on.
What is not up for negotiation here
Six commitments you can check in day-to-day work. Where a number, a date or a time belongs in one, it is stated.
No second round of explaining
You get a reply from somebody who knows your environment, rather than a ticket number and a form. Whoever set things up at your site also knows why that ageing terminal server is still running, and does not have to read their way in when something breaks.
Your access details
What you get from us comes as a list: administrator passwords, port assignments, licence keys, contract terms, the configuration state of the firewall. Every item goes out to you again when it changes, not only when we part ways. A successor can start with it the same day, without having to ask us for anything.
No commission
We are tied to no manufacturer and have no quota to fill. Before any larger purchase, ask us why we are proposing this particular device. If the answer consists only of product names, keep asking, with us as with any other provider.
The way back is tested
A backup only counts as tested here once a file has been restored and opened. Whatever we notice while doing it, we record with the date and put in front of you, even when it is uncomfortable. A green tick in the backup report counts as an indication, not as proof.
Plain language, no acronyms
What we write to you should be something your commercial director can pass on without asking questions. If our report contains an abbreviation we have not explained, mark it. We will rewrite the paragraph.
A no at the right time
If a project is not a technical fit for us, we say so in the first conversation and name someone better placed for it. A commitment that gets withdrawn later costs you more time than a straight answer on the phone.
One call before you sign
Thirty minutes on the phone is enough for the question of whether we suit each other. Bring along what you paid for IT last year and what for. That shows us where you stand faster than any list of requirements.
Book an intro call