About
A practice built around clear technology decisions
Serghei Ciovaga is an independent business technology practice in Chișinău. The work is to help a company decide which systems it needs, introduce them with care, and leave the team able to run them.
The practice works with owners and operations managers who are responsible for a living business. They are usually deciding whether to replace a tool, approve a vendor, or stop a routine that wastes the week. They do not need another catalogue. They need a recommendation they can stand behind.
Engagements are personal in scale. There is one named contact, written notes, and a scope that is agreed before paid work starts. The practice does not sell software licenses and does not take a commission that depends on which product the client buys.
Meetings are held in English. Written deliverables are in English. Conversations can be in Chișinău or remote. On-site time, when it is useful, is part of the written scope.
Professional approach
The first duty is to understand the operation. A system that looks efficient in a demonstration can still fail the exception that happens every Tuesday. People who do the work are part of the discovery, not an audience for a later announcement.
Recommendations are specific. They name what to do, what to leave, and what would make the advice wrong. If a client already has a supplier, oversight can sit beside that supplier. The supplier keeps the technical role.
Principles
- Clarity before software
- The business problem is named before a product is compared. A purchase is not treated as progress by itself.
- Written recommendations
- Advice that matters is written down. A conversation is not the only record of what was decided.
- Vendor independence
- The client buys from the vendor. The practice is paid by the client for the work in the proposal.
- Plain language
- Notes are meant to be read by the people who will live with the result, not only by a project sponsor.
- Agreed scope
- New work is discussed before it is added. A retainer has a reserved volume so small requests stay visible.
- Honest fit
- If the practice is the wrong help, that is said early. Legal, accounting, and round-the-clock monitoring sit outside the work.
Methodology
The method is the same shape on a short brief and on a longer project. The depth changes. The order does not.
- Separate the operation from the tools Describe the work as it happens, including the exceptions.
- Name one decision at a time A crowded brief hides the choice that actually matters.
- Prefer a tool the company can run A system the team cannot operate is not a saving.
- Leave notes that stand alone The team should be able to use the result without the practice in the room.
Values
Care for time
Meetings have a purpose. Drafts are shared when they are ready to be corrected, not as a stream of fragments.
Respect for the current team
Staff who already keep the operation moving are a source of truth. They are not treated as an obstacle to a new system.
No inflated claims
The practice does not promise a revenue figure, a headcount reduction, or a transformation. It promises the work described in the proposal.