Haiori is a software studio founded and led by Daniel Șotropa, a senior software engineer and team leader. We design and build web platforms and business applications around the people who use them.
Daniel started Haiori on 1 August 2026. He leads engagements and remains hands-on in engineering, technical decisions and review. He continues his professional work in enterprise software alongside building the studio. When a project needs more hands, he brings in a small circle of trusted senior contractors.
Agree the users, workflows, priorities and acceptance criteria
Develop the application and integrations in increments you can see and test
Agree the deployment environment, responsibilities and readiness checks
Provide the agreed code and documentation, with maintenance and further work scoped explicitly
Understand the task before choosing the technology. Make the application reviewable as it develops. Explain the technical choices and leave the agreed code, documentation and operating knowledge with the client. These are practical responsibilities throughout delivery.
Bring an application idea, a workflow to improve or a technical question. We discuss the people, scope and constraints, then agree a useful next step. Shape covers development; Think provides definition and direction; Scale improves workflows and ongoing use.
Daniel brings senior engineering and team leadership experience to the studio. His professional contracting engagements are distinct from Haiori client projects. The studio’s work is described according to what has actually been built and its current delivery status.
A clear owner, a meaningful need and a manageable first release give a project a useful starting point. We discuss budget, dependencies and support requirements so the commitment fits the people available to deliver it.
Daniel remains your direct technical contact. Contractor roles, delivery capacity and ongoing support are agreed for the engagement.
Useful software begins with an ordinary question: what does someone need to get done? That question stays relevant from the first conversation through design, implementation and handover.
