A small software company, close to the work.
We make our own products and build software for other people. Design and engineering stay in the same conversation, from deciding what to build to how it behaves on an ordinary Tuesday.
The name, and the mark.
uhyar means “wise” in Pashto, the language spoken where the company began. We chose it as a standard rather than a claim: ask good questions, make considered choices, and keep learning from the people who use what we build.
The mark is one stroke, a lowercase u and h drawn without lifting the pen, and one dot held in the bowl of the u. The stroke is “uh”, the pause before a good answer. The dot is the answer. On these pages there is only ever one, and it moves as you read: from the logo to the full stop of a heading, and on to the one act that waits for you.
Muhammad Sadeeq.
Founder, uhyar
I started uhyar to build software I could stand behind, from the first design decision to the way it behaves after launch. That means staying close to the work: watching how a school office or a laboratory actually runs before deciding what the software should do, and staying reachable to the people who depend on it afterwards.
klasmint came first, and it is in use today. sahireport is being built the same way, with a laboratory’s daily routine in front of us. Alongside those, we take on a few projects a year for other people, and I am involved in each of them.
If you write to us, you are writing to me. Tell me what the work looks like now and what you would like it to look like. That is enough to start.
hi@uhyar.comThree things we hold to.
Understand the work first.
Look at how people actually do the job before deciding what the software should do. The workarounds tell us as much as the brief.
Carry the mechanical part.
Retyping, remembering, reconciling: the software should do that. People should be left with the decisions.
Make decisions visible.
Explain the trade-offs, show work early, and write down the choices that will matter to the next person maintaining it.