Partners
Engineering for software firms and system integrators
When a client project needs a component your team does not build every day — an AI workflow, a geospatial pipeline, a data-processing or automation module — we build it inside your delivery, to your process and standards.
What we build for partners
- AI components: provider layers, retrieval over documents and agent workflows, delivered with an evaluation set. Enterprise AI.
- Geospatial components: cadastral and map data pipelines, validation and terrain-aware rendering. Geospatial & PropTech.
- Data processing and reconciliation between systems that disagree.
- Operations automation with explicit failure states, alerts and manual paths. Operations automation.
How a partner engagement works
- 01
Brief under NDA
You share the component’s scope under a mutual NDA — ours or yours, or your client’s.
- 02
Acceptance criteria in writing
Interfaces, tests and performance targets are agreed before the build starts.
- 03
Build inside your delivery
In your repository, with your branching, CI and code review; we follow your coding standards.
- 04
Handover to your team
Documentation, runbook and a knowledge-transfer session, so your team owns the component afterwards.
Working terms
- Your client stays yours. We work under your name and do not contact your client without your agreement.
- Fixed scope or reserved hours. Milestone-based delivery, or a capacity block of reserved monthly hours.
- Clear ownership. Delivered work passes to you, or to your client, when the related milestone is paid. See enterprise engagement.
- Invoicing in TRY, EUR or USD, per milestone.
Where we fit best
- The component has clear inputs, outputs and interfaces to the rest of the system.
- Acceptance can be tested, not only reviewed.
- One senior engineer can own it end to end, from design to handover.
How we size work and keep it continuous is described under delivery capacity.
Frequently asked questions
- Can you work under our NDA and subcontract terms?
- Yes. We can sign your NDA and work under your subcontract, with a statement of work per component.
- Will you join calls with our client?
- Only if you want us to, and as part of your team.
- Who owns the code?
- You, or your client, once the related milestone is paid; tools we owned before the project are licensed non-exclusively so the delivered system can be maintained freely.
- How do we start?
- Send a short description of the component through the project form or to projects@zerentechnologies.com. A mutual NDA can come first.
Have a project in mind?
Send a short description. If you need a mutual NDA first, we will send ours before you share details.