Book 30 minutes

Thirty minutes, and we stop at thirty. No preparation needed and nothing to read beforehand. Carsten takes it, or Ilyes if the question is technical depth rather than hands.

You'll get a straight answer on five things: whether the thing you're describing is worth doing, roughly what size of job it is, whether the right fix is a tool you configure, something built custom, or a bit of both, whether we're the right people for it including when we're not, and what the planning would cost if it's worth doing at all.

That last one matters. You leave a free call knowing the price of the next step, fixed, and we don't revise it afterwards. Planning is paid work and it isn't deducted from the build.

We'll also tell you which of the four paths you're on, and how much of the technical leading we'd be doing on it. That runs from holding the decisions the way a cofounder would, down to your team deciding and us building.

Sometimes the answer is that you don't need us. There's a tool on the market that does it, or what you actually need is somebody on staff. We'll say so.

Afterwards we'll write it up and send it to you: what we heard, what kind of build suits it and why, and what working with us would look like. Yours to keep and to forward.

We publish how much of our week is already committed. Right now 8 of 12 developer days per week are still available.

If we're full when you call, we'll tell you a date rather than taking the work and finding out in month two. If your problem isn't one we're good at, we'll say that too, and we'll usually know which kind of person you should be talking to instead.