About us
Software you own, built by people you can name
We are a small delivery team that builds the layer operations run on — the one that moves a record between the systems you already bought and applies each rule in exactly one place.
Small is the strategy, not a stage we are growing out of. The engineer who designs your architecture is the one who answers when you call, and everything we build leaves with you: code, configuration, credentials.
Who we are
Engineers who would rather fix the process than sell you a platform
TechnoVSKY exists because most companies do not have a software problem. They have four systems bought years apart, a spreadsheet holding the gap together, and a person whose Sunday night goes into rebuilding the same report.
We work in three practices — enterprise systems, the integration layer between them, and the automation that makes the layer pay for itself. They are sold separately everywhere else and delivered together here, by one team that stays with an engagement from discovery to handover.
That team has shipped scheduling a clinic can be audited on, bag tracking a kitchen can trust at the doorstep, and a booking flow that holds four verticals in three languages and three currencies.
Our vision
A region whose companies own the systems they run on
Too much of the software this region depends on is rented, opaque, and impossible to leave. A licence renews, a vendor disappears, and the company that has been feeding the system for six years cannot get its own data out in a usable shape.
We are building the opposite, one engagement at a time: systems documented well enough for somebody else to maintain, owned outright by the business paying for them, and boring enough that nobody has to think about them on a Sunday.
The measure we hold ourselves to is simple — a year after handover, your team should be changing the system without us.
Why TechnoVSKY
Four commitments we put in writing
Not values on a wall. Each of these is something you can hold us to during the engagement, and check after it.
You own all of it
Code, configuration and credentials are handed to you at the end — all of it, not a deployment you cannot rebuild. There are zero licences to buy from us, then or later.
One named engineer
Your account has a person on it, not a queue. The engineer who designs the architecture is the one who answers the call about it eighteen months later.
A price fixed before we start
Phases, dates and a price per phase, agreed in writing. No open day rate that keeps discovering new work the deeper it gets.
Working software, every two weeks
Something real goes live at the end of each phase, so you are judging software your people can open rather than a deck about software.
Meet our management
Two people, both reachable
No account layer between you and the people making the decisions. These are the two names on every engagement.
Kareem Sharaf
Chief Executive Officer
Runs the company and the client side of every engagement: what is in scope, which phase it lands in, and the price fixed in writing before anyone starts. He is the one who would rather lose a proposal than discover the scope halfway through it.
Abdullah Alharisi
CTO & Solution Architect
Owns the shape of what gets built: where each business rule lives, how the layer moves a record between systems, and what the handover document has to contain for your team to take it from there. The architecture decisions end at his desk.
Now tell us which process is costing you the most
One call, ninety minutes, no charge. You leave with an opinion whether or not you leave with us.