What working with us looks like

Each engagement starts with one clear question and ends with your team running the result. In between, our engineers work inside your team and every change is tested on your own work.

01

A first project with one clear question

First comes a 30-minute conversation with one of our engineers, for which we need no access to your systems. Together we pick one process, team or model, decide which work to test it on and agree how quality will be judged. Before anything starts, we agree with you who gets access, how data flows and which model endpoints are used.

02

Built together with your people

Before changing anything, we measure how the work runs today. Then our engineers build with your team on real tasks, changing a single thing at a time so that each result has a clear cause. People keep reviewing the work, and the automated checks keep running the whole time.

03

Yours to run

We check the results on live work, not only on past cases. You receive the code, configuration, test sets, runbooks and measurements, with the reasoning written down, and we step back once your team runs it with confidence.

We agree the timeline and what you receive once we understand the problem.

Ways to work with us

A scoped project

One process, team or model, with a clear question and the measures agreed at the start.

Engineers in your teams

Our engineers join your teams part-time for a project, or are placed with you for longer when the roadmap needs more people.

Training

Hands-on sessions on your own work, remotely or on site in Germany and Poland, in English, German or Polish.

Staying up to date

A monthly review of what has changed in tools and models, and a monthly workshop for your teams.

The first three apply to every service line, and all four can be combined.

What you can count on

  • No model or tool vendor pays us, so our recommendations follow your results.
  • We work inside your own repositories and infrastructure, and a data processing agreement covers it.
  • We report figures by team, task and model, and never score individual people.
  • Your people learn the setup while we build it, so it keeps working without us.

Your contact at Cloudsail

One of our engineers is your contact from day to day. They work inside your team, get to know your systems and bring in colleagues from Cloudsail when the work calls for them.

Mickey Graf, who founded the company, has worked on machine learning in production since 2017.

Meet the team

Where coding agents are heading

Agents will write a growing share of software, inside a harness that someone maintains, while people decide the scope and approve each merge. That is what we mean by a software factory. We build towards it one repository at a time, at the pace your checks allow.

Our post on the autonomous software factory

Questions

How long does a project take?

You get an estimate after the first call, once we understand the problem.

How is a project priced?

The first call is free. After it, you receive a written price based on the scope and the size of your organisation, before any work starts.

Can your engineers stay with our team for longer?

Yes. Besides project work, we place engineers with your team for longer periods, with the length and the scope agreed with you.

What if we have a works council?

We help you brief it early, before anything goes live, and keep all reporting at team level.

Talk to an engineer

Bring one piece of work you would like to improve. The call takes 30 minutes and needs no access to your systems or your data.

Booking runs on Google Calendar.

Prefer to write first? Leave your email and a few lines, and we reply with times.

The button prepares an email in your own email program, for you to send. Privacy policy (draft)