.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
Writing code got cheap. Knowing what to build did not.
Most engagements still revolve around what's now fast: a scoping document, an hourly rate, an off-site team, and a delivery date a quarter away. By the time you see something real, the requirement has moved.
We put a senior team inside your business instead. One fixed price for the whole arc, agreed before we start. If week one tells us you shouldn't build it, we say so.
We sit with the people who live with it daily, not only those who commissioned the project.
Week one ends with a narrow, specific definition, and an explicit list of what we are not building yet.
Working software from week two, visible daily, so wrong assumptions cost an afternoon instead of a sprint.
Your systems, your data, your constraints, rather than a clean-room prototype.
Tests, monitoring, access controls, and the things that make software safe to run without us.
Documentation your engineers can pick up, delivered while we are still there to answer questions.
.svg)
.svg)
What does "forward deployed" mean if our team is distributed?
It means we work inside your systems, your meetings and your channels every day, rather than reporting in from outside. Week one is on-site wherever there is an office to sit in, because that is when being in the room matters most. After that we stay in your tools with daily contact, and come back on-site as often as the work needs it. Travel within Europe is included in the fixed price.
What happens if week one concludes we should not build it?
We say so, rather than building something to fill the remaining weeks. You keep the written problem definition, the evidence behind it, and our recommendation for what to do instead, which is often smaller and cheaper than what you came to us for. If you decide to stop there, you pay for week one and the rest of the engagement is cancelled.
Who owns what you build?
You do. Everything we build for you transfers to you, and we are glad to work under your own IP terms rather than ours. Where we use open-source or third-party components we tell you which ones and under what licence before they go into the build, so nothing arrives with conditions you discover later.
What does an engagement cost?
One fixed price for the full four-to-eight-week arc, agreed before we start, from €30,000 for a four-week engagement. Price follows scope and team composition rather than hours worked, so it does not move if the work takes longer than we expected.
How quickly can you start?
Typically two to three weeks from the first call to the start of week one: a scoping call, then the contract, then access to your systems. Access is usually the slowest of the three, so it is worth starting that early on your side.
What about NDAs, security and access to our data?
We sign your NDA and work inside your environment and your own access controls. Sigli is ISO/IEC 27001 certified, manages company devices through Microsoft Intune, and works to DORA requirements with financial-sector clients.
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.webp)
.webp)
