Pay if it works*

What does ‘works’ mean?

We agree on what your system needs to achieve before we start building it.

  1. An agreed scope

    The quote and contract define the deliverables, price and acceptance tests before work begins.

  2. A result you can verify

    We test the implementation against those criteria together and document the results. Meeting the agreed criteria triggers the payment obligation under the contract.

  3. Delivery after payment

    Final delivery and installation follow payment, including the final checks agreed for your environment.

Tools, licences, infrastructure and ongoing maintenance are agreed separately. Any external costs require prior approval.

How it works

One connected ecosystem. Your team in control.

From a request in a conversation to a result your team can review. We connect people, tools, and agents in a workflow with shared context.

  1. Your work channel
  2. Orchestrator agent
  3. Cloud environment
  4. Human review

The journey of a task.

Each task connects the request, the decisions, and the evidence behind the result.

  1. The conversation is the starting point.

    Your team raises a need in its usual channel: a question, a repetitive task, or an improvement. The request starts a conversation to clarify the expected outcome.

    For example: preparing a report with information from several tools.

  2. Context gives the request meaning.

    The orchestrator gathers available information from authorised sources: documentation, projects, conversations, or internal systems. When information is missing, it asks the team.

    Sources and required permissions are agreed for each implementation.

  3. The orchestrator organises the work.

    The need becomes a plan. The orchestrator agent coordinates specialised agents and skills: instructions and tools prepared for specific tasks.

    Scope, decisions, and the conditions for moving forward stay linked to the task.

  4. Execution has its own environment.

    Agents work in an isolated cloud environment prepared with the project's tools and context. Access is limited to what has been agreed with the team.

    The infrastructure can adapt to your systems and the requirements of the work.

  5. The result comes back with evidence.

    Your team receives the result and the relevant checks: changes, files, tests, or a summary of the work. People can review it, request adjustments, and decide what happens next.

    Human review before publishing or performing actions that require approval.

People remain in charge of the decisions.

Defined permissions

We connect the sources and tools needed for the agreed scope.

Explicit approvals

We define which actions may run and which require human validation.

Context and traceability

The request, decisions, and results stay associated with the task.

Bring this workflow to your team.

We start by understanding how you work and what you need to improve.

Let’s talk