Engagements / Commercial and operational terms
Clear engineering responsibility, agreed around the work.
Choose reserved weekly capacity for ongoing engineering or a defined project with agreed deliverables. A paid technical assessment is an optional way to establish scope when the system or problem is not yet understood well enough to estimate responsibly.
Engagement formats
Weekly engineering engagement
Reserved engineering capacity for existing software, recurring needs or an ongoing workstream. We agree the weekly commitment, availability, responsibilities and communication cadence. Agreements can be renewed weekly or monthly. Capacity is limited and confirmed before engagement.
Defined engineering project
A fixed project price can fit an understood implementation, integration, migration or technical improvement. The proposal defines deliverables, exclusions, milestones, responsibilities, assumptions, payment schedule and change process.
Technical assessment
A paid investigation can establish the architecture, risks, technical boundary or acceptance criteria when the work cannot yet be scoped responsibly. It is optional and does not require continuing into implementation.
Progress and communication
- Agree a communication cadence suited to the commitment and work.
- Material blockers and risks are communicated when discovered.
- Decisions, assumptions and scope changes are written down.
- Meetings resolve ambiguity; they do not substitute for visible work.
Timing and capacity
Bounded implementation work is normally planned in phases measured in weeks. The timeline depends on access, external providers, client decisions and uncertainty discovered during implementation.
I work with a limited number of clients at a time. Capacity and the earliest realistic start date are confirmed before a proposal is accepted.
Ownership and continuity
Bespoke source code and project-specific deliverables become the client’s property after the related invoices have been paid in full.
Pre-existing tools, reusable components, general engineering methods and know-how remain mine. Where a pre-existing component is included, the client receives the rights required to operate, maintain and modify the system. Open-source and third-party components remain under their original licences. The final contract controls the precise terms.
Source code normally lives in the client’s repository and production infrastructure in client-controlled accounts where practical.
Architecture decisions, deployment and recovery instructions, known limitations and handover items are documented where the system requires them.
Scope stays within what one accountable engineer can responsibly deliver. A broader team is recommended when the work needs one.
Business and security
Engagements begin with a written agreement or proposal covering scope, exclusions, payment model and responsibilities. Contracting and invoicing identity are disclosed before work begins.
I can sign a reasonable mutual NDA. When I process personal data, I can enter into an appropriate DPA after systems, subprocessors, data locations and security obligations are understood.
- Least-privilege access and separate development and production credentials.
- No secrets in source control; use the client’s approved secret management where available.
- Rotate or remove access at the end of the engagement.
- Minimise locally stored client data and use synthetic or redacted data where practical.
- External AI use with client material requires explicit approval and data minimisation.
When software is not the right answer
If an existing product, a simpler integration or a process change solves the problem more safely, I will say so. The initial investigation is also about determining whether custom software is justified at all.
Explore engineering expertise
Weekly and project work can apply to any of the engineering areas described on the expertise overview.
About the engineer
Read Serhii’s professional background or discuss a potential engagement.
Commercial transparency FAQ
Can we reserve weekly engineering capacity?
Yes. We agree the weekly capacity commitment, availability and responsibilities before work begins. A commitment can be renewed weekly or monthly by agreement. Capacity is limited, and the fee reserves that defined amount of engineering time rather than unlimited access.
Do you publish a fixed rate?
No public rate is shown. The written proposal sets the agreed commercial model and scope.
How often will we see progress?
We agree on a communication cadence that fits the commitment and work. It can range from one concise weekly update to more frequent coordination for a short implementation.
Who owns the source code?
The client owns bespoke project deliverables after related invoices are paid in full. Pre-existing reusable materials remain mine, with operating and maintenance rights for included components.
Can you work in our existing repository?
Yes. A client-controlled repository is the normal default.
Can you sign an NDA or DPA?
I can sign a reasonable mutual NDA and an appropriate DPA when the work makes me a processor of personal data.
What happens after launch?
Handover items and any stabilization period are defined in the proposal. Ongoing maintenance, response times and on-call support are separate unless explicitly included.
What happens if scope changes?
Material changes are written down and approved before implementation proceeds under the changed boundary.
Are you available full-time?
I work with a limited number of clients. Capacity and the earliest realistic start date are confirmed before a proposal is accepted.
What if the project needs more than one engineer?
I will say so. Scope stays within what one accountable engineer can responsibly deliver, and a broader team should be involved when the work clearly requires it.
Discuss an engineering engagement
Tell me about the work.
Share the system, the technical challenge, expected timeline and approximate commitment. A formal specification is not necessary.
Contact Serhii ↗