Start with the one that costs you the most.

Not a discovery call about your data strategy. A connector nobody will maintain, a report rebuilt every month, a migration stuck on mapping, a number you can no longer defend. Whichever it is, what breaks and what it feeds is enough for us to tell you whether this is something we can run.

What happens next

Three steps, and the first reply is not a calendar link.

We read what you sent

Before anyone replies. If you named a source system and a destination, we will have looked at whether we can read the one and write the other.

Expect a reply within one working day. It comes from one of the three founders, because there are only three of us.

You get a scope or an honest no

If it looks like a fit, we come back with what we would build, what we would need from you, and roughly how long it takes.

If it does not look like a fit, we say so and why. A bad engagement costs us more than a lost one.

The first flow is deliberately small

One source, one destination, one defined data flow. Bounded engagements run four to eight weeks once source access and acceptance criteria are known.

Every engagement leaves behind something running, versioned, and monitored. Not a report about what should be built.

Tell us what breaks.

What goes wrong, what it feeds, and who notices when it does. If you already know the source system or have sample records, mention it and we will ask for them.

What we will ask for eventually

Not now, but it is worth knowing what a scoped engagement needs, because gathering it is usually the slowest part:

  • System access, read-only, scoped to the tables the flow needs.
  • Documentation or sample records, so we can see the shape of the data rather than the shape of the schema.
  • A target contract. What has to arrive, in what form, for the destination to accept it.
  • A named technical owner who can supply access, explain the source, approve mappings, and accept the result. Every engagement needs one, and engagements without one do not go well.

Worried about what access means before you send anything: source systems are read-only, scoped to a named set of tables rather than a whole schema, and where a system cannot be reached from outside your network a connector runs inside your perimeter and opens an outbound tunnel. No inbound firewall rules. Everything is hosted in the EU.

We are not SOC 2 or ISO 27001 certified. If a certification is a hard requirement for your procurement process, better that you hear it here than in a fourth meeting.