FAQ

Questions that come before
the first conversation.

Cost, duration, operations, handover and training — answered briefly, so you know where you stand before you get in touch.

Money and time

What it costs and how long it takes

What does it cost?: We can name a price once we have seen your system. The route there is short: a conversation, then a written review with prioritised risks and effort estimates. On that we can give you a quote we will stand by.
Fixed price or time and materials?: We decide that with you, for each engagement separately. Anyone quoting a fixed price against an unknown starting point adds a risk premium, and you pay for it. So we keep the first step small until the scope is certain enough for a fixed price.
How long until something runs?: We name a duration once we have seen the system. Before that we can only commit to the order of work: you get working increments and judge the progress on them yourself.
Can we book you for two days?: Yes — that is what advisory and architecture review is for. You get a written assessment: the places where the system is most likely to fail or get expensive, ordered by urgency, each with an effort estimate and one concrete next step. You can pass the document on internally.

Working together

Where do you start?: With the data model and the tenant boundaries, before the first screen exists. Changing either later means a migration. A screen, by contrast, can be rebuilt in an afternoon.
What if you advise against something?: Then we tell you, and say why. The most useful answer is often that a project can be smaller than planned — including when that shrinks our own scope.
Can you give references?: By name only with written permission, and we do not have that yet. What we can show is the sectors we work in, and the register of the systems themselves.
Which sectors do you work in?: Software companies, Payments, Music rights and licensing, Media and content production.

Afterwards

Do you run it as well?: Yes — that is the part we keep: deployment, database operations, monitoring, and provider migrations when they come due. How long we ran a given system is recorded in the register.
What if we want to take it in-house?: Then we hand it over. That is a service like any other: operational documentation, documented architecture decisions, a walkthrough for your team, and a transition period in which we stay reachable.
What happens if we stop working with you?: Then the system carries on without us. That is what the documented architecture decisions and the swappable providers are for — explicitly so for AI features, where lock-in to one provider gets expensive fastest.
Can you train our team?: Yes. Languages and frameworks, development tooling including AI assistance, and handover of a system together with its operational documentation. On your own codebase rather than a sample project, if you want it that way.
Do you do AI?: Yes, with versioned prompts, a fixed output format, and evaluation that shows when the model is wrong. Cost control and provider independence are part of it. Where a language model adds little, we say so before anything gets built.

Not covered

Then send it to us. You get the answer directly, and questions that come up more than once end up here afterwards.