Most engineers I know keep a folder. Half-built products, domains bought at 1 a.m., a repo named final-v2-really-final. Mine had one too.
What changed this September is that the folder got a name, a legal form, and a standard.
The name is Nishan Systems. It is a Berlin studio for software, brand, and marketing. This post is the honest version of why it exists, what it builds, and how it fits next to a day job that already asks a lot of me.
The Word: What "Nishan" Means
Nishan is Kurdish. It means mark: a sign, a target, something built to be seen and to last.
I picked it because it works as an instruction, not just a label. Every engagement should end with the client holding something more permanent than what they walked in with. Not a launch. Not a handoff date. A mark that is still there, still working, months later.
Berlin supplies the second half of the standard. Nothing ships until it is right, and "good enough" is not a category that exists here.
Three Stops: Apprentice, Lead, Founder
The path to this point was not planned in advance, but it has a shape.
- 2020, SINC NOVATION Group. I started as an apprentice who did not know what a REST API was. I learned that code is a way of thinking in systems, not a list of syntax to memorise.
- 2024, Oracom. A call center that was growing into AI products, and a seat in the architecture decisions that came with it.
- July 2026, Team Lead. I now lead the developers at Oracom Intelligence, the IT department of Oracom GmbH. The work stopped being only code and started being people too.
Each step changed what I carry. First it was code. Then systems. Then a team. The studio is the next step, and it is not away from the work. It is toward owning all of it: the software a business runs on, the identity it is recognised by, and the marketing that puts it in front of the right people.
The Beaver Principle
The best explanation of how the studio works is an animal most engineering companies never mention.
Beavers are nature's other engineers. Ecologists call animals like them ecosystem engineers: species that create, significantly modify, or maintain a habitat for everything else living in it. A beaver does not adapt to the landscape. It rebuilds it into dams, ponds, and wetlands.
Then the interesting part happens. WWF's overview of beaver dams lists slower stream flow, water soaking back into the ground, sediment and pollutants trapped instead of carried on, and habitat for fish, amphibians, and birds. The beaver builds for its own reasons. The ecosystem downstream benefits from work it never did for credit.
The Beaver Principle: Build with total precision. Never for applause. Let everyone downstream benefit from the work.
That is the whole philosophy. It is also the test I apply to every system: does it still work perfectly when no one is watching?
What the Studio Builds
Nishan Systems takes on three kinds of structural work, under one standard instead of three vendors who never talk to each other:
- Software: the systems a business actually runs on.
- Brand: the identity it is recognised by, built with craft, not template output.
- Marketing: the visibility that puts it in front of the right people, from technical SEO to performance work.
The positioning is deliberately narrow. The studio is small enough to hold every detail to the same standard, and that is on purpose.
One Branch at a Time
Here is the rule I care most about: each new branch is added only after the previous one has proven it can hold weight.
In practice, that means the studio starts with local-business work: a website and local search presence for a hair salon and barbershop with two locations. Only when that holds does the next branch open. It is slower than the usual "launch everything" approach. It is also how you avoid building a structure on ground that has not been tested.
The Honest Part: A Studio Beside a Day Job
I lead developers at Oracom Intelligence. The studio runs beside that role, not instead of it.
That constraint shapes everything about the schedule. It is one more reason the studio is small, focused, and sequenced instead of sprawling. My team gets the same lead on Monday morning that it had before. The studio has to earn its hours from the margins, not from theirs.
Three Rules the Studio Runs On
- Nothing ships until it is right.
- The rule: If a detail is wrong, the work is not finished.
- In practice: Precision is an obligation to the client, not a mood.
- Senior attention, every time.
- The rule: The person who scopes the work is the person who builds it.
- In practice: No handoff to a junior team the client never met.
- Built to last, not built to launch.
- The rule: Success is measured by whether the system still holds months later.
- In practice: A project is judged on its sixth month, not its handoff day.
Final Thoughts: Build Where No One Is Watching
Most of what makes software good is invisible. The migration that never fails, the page that loads fast on a bad connection, the brand system that still looks right two years and ten contributors later. Nobody applauds those. Everyone downstream benefits from them.
That is the bet behind Nishan Systems: work built right the first time is the only kind that keeps paying the people who rely on it.
If you run a small or mid-sized business and need software, identity, or marketing built to hold, the studio lives at nishansystems.de, and the studio page on this site covers how it works. If you would rather talk engineering leadership or team culture, the contact form is the right door.