12 Review & continuity
Remote engineering partnership (B2B)
Full-stack engineering capacity for your product under a B2B contract with a registered Serbian company — in your repositories and your working hours.
Outcome: More engineering capacity, with clear ownership and a clear contract.
A remote engineering partnership adds a full-stack engineer to your team under a B2B contract with FILIP VOLF PR DEUS INŽINJERING, the registered Serbian company behind DEUS Engineering. You work directly with the engineer who builds the system.
It suits a product that needs more engineering than the current team can give, or one part of it owned end to end, when hiring is not the right step yet. If you mainly need one existing application kept current, software modernisation & maintenance is the closer fit.
Typical needs
- A roadmap bigger than the current team
- A part of the product that needs one engineer to own it end to end
- A B2B contract with a registered business, not an informal arrangement
What you receive
- Work through your repositories, tickets and code review
- Decisions, status and documentation written down as part of the work
- Contracting and invoicing company to company
Approach
How the work runs.
- 01
Scope and terms in writing
Scope, terms and pricing are agreed in writing before work begins, and the contract and invoices run company to company, with FILIP VOLF PR DEUS INŽINJERING.
- 02
Inside your workflow
Work happens in your repositories, tickets and chat, and every change goes through your branch rules and code review — not a parallel process you have to supervise.
- 03
Decisions written down
Status, decisions and the reasons behind them are recorded in tickets, pull requests and documentation as part of the work, not kept in someone’s memory.
- 04
Ready to hand over
Code, documentation and context stay in your repositories, so your team can carry the work on without depending on DEUS.
Technologies
- GitHub
- GitHub Actions
- TypeScript
- Python
The engineer who does this work is the founder, Filip Volf — you work with him directly.
Questions
About this service.
How is this different from a custom software & SaaS project?
A custom software & SaaS project has a defined scope and an end: DEUS takes responsibility for delivering one system, from the data model to deployment and handover. A partnership instead adds engineering capacity to your team, working on your roadmap and priorities through your own tickets and code review. When the work has a fixed scope, a defined project is usually the better shape.
Can we take over the work ourselves later?
Yes. Nothing is kept outside your systems: code and documentation are in your repositories, and tickets and the reasons behind decisions are in your own tools. Ending the partnership means finishing or handing over the work in progress — not a migration — and your team carries on from there.
What about language and working hours?
English for specifications, code review and documentation, Serbian for conversations whenever that is easier. Working hours are Central European Time, the same as Zagreb, Vienna and Berlin, so meetings, reviews and releases fall inside your working day.
Related services
- 01
Custom software & SaaS
Outcome: One system of record instead of scattered tools.
- 10
Technical audit & architecture consulting
Outcome: What to fix first, what can wait — and why.
- 11
Software modernisation & maintenance
Outcome: The software you already rely on, safe to change again.
Next step
Let’s talk about what you’re building.
Describe what you need built or fixed, how the work runs today and the constraints. You get clarifying questions or a first outline of the approach — by email, in English or Serbian.