For agencies and studios

We can take part of the build

If your team is at capacity, we join the project and close an agreed scope: the whole system, the server side, integrations or an AI component.

Discuss a partnership

The terms

The three things people ask about in the first conversation. We answer them before the work starts, not after.

🏷️

Under your brand

We work as a development partner. How the client is spoken to, and through whom, is agreed before we start: entirely through you, jointly on technical calls, or directly within an agreed set of questions.

📋

Scope is fixed up front

Tasks, deliverable, timing and how the work is accepted are agreed before it begins. If it turns out along the way that more is needed, that is a separate agreement rather than an invoice that quietly grew.

📦

The code stays with you

We hand over the source, the instructions and the documentation for the part we built. No key pieces held back on our side, and no dependency on us being around after delivery.

What we usually close

The scope follows what your team is missing right now, not a package decided in advance.

The whole system

From architecture to delivery, when the agency has the client and no free team for this particular project.

The server side

Data model, application logic, API. The interface stays with you, and the seam between us is described by a contract.

Integrations

Connecting to external systems and registries: exchange, failure handling, retries, logging.

An AI component

A single block inside someone else's product: document search, request handling, data labelling. With stated limits on what it answers for.

How it works

It starts with a short conversation about the task: what exists, what is in the way, and which part of the work needs taking off your hands. Then the scope and the acceptance terms are put in writing, and only then does the build begin.

Along the way we show working versions rather than percentage-complete reports. That way a mismatch in understanding surfaces in the second week instead of on the day of delivery.

At the end we hand over the code, the deployment instructions and the documentation for the part we built. Support after delivery is discussed separately and is not assumed by default.

What we do not do

So that a call does not end with the discovery that we are not a fit.

  • We do not take on a scope that cannot be described in words before the work starts.
  • We do not approach your client behind your back.
  • We do not keep parts of the code without which the result does not run.
  • We do not promise dates that depend on someone else: approvals, access, data from a third party.

Discuss a partnership

Tell us which part of the work you need and by when. We will say whether we take it on and what it needs from your side.

Discuss a partnership