01
EU data residency by default
Product runtimes on our own infrastructure across the EU (Germany, France) and North America (Canada). See our security posture.
Custom AI software development, first slice first.
A founder-led AI studio in Poland (EU). We build the working product, not the deck: a production-ready first slice in four weeks, against a written scope and a fixed first milestone, scoped and priced before kickoff.
Updated:
Scope
What the first milestone actually contains.
Four things you can point at when the four weeks are up.
01
One spec, one feature path, one core flow
One written spec, one deployed feature path with authentication, one core flow and one durable surface. Success criteria and an explicit out-of-scope list are agreed before a line of code is written, so the scope cannot drift while the build runs.
02
The stack, and why it is boring
Well-understood, widely used technology that any competent team can read, maintain and extend after the engagement ends.
03
What ships in week one
Authentication, one core flow and one durable surface are working in week one, not in week three. Deployment, monitoring and backups are wired from day one, so nothing is bolted on at the end and no milestone ships without a way back.
04
What you own afterwards
The repository, the infrastructure, the runbooks and the operational dashboard are yours. No vendor lock-in and no per-seat licence: the stack stays yours, and your own team can run it without us.
Every custom AI software development engagement starts with a written scope and a fixed first milestone. Data stays in the EU by default, every subprocessor is named on the subprocessors page, and a Data Processing Agreement is published. Our security posture, the trust index and the products we have already shipped on the work page are public.
The defaults come from the frameworks rather than from taste: the map-measure-manage discipline is the NIST AI Risk Management Framework, and the security checklist a first slice inherits is the OWASP Top 10 for LLM applications.
Engagement
How we engage.
Discover, validate, build, ship, operate, iterate. The same six steps, in that order, on every contract.
01
Discover
A few sentences describing the problem. We read it, ask the questions that matter, and decide on the spot whether we can help. No discovery funnel, no deck.
02
Validate
We demand a spec before we ship a line: scope, success criteria, an explicit out-of-scope list, and a fixed first milestone scoped and priced before kickoff.
03
Build
The person you email writes the code. No juniors, no handoffs. Boring, well-understood technology with no vendor lock-in, so the result stays maintainable by someone other than us.
04
Ship
One deployed feature path with authentication and one core flow, released through CI/CD. The four-week mark is the gate to extend, refine or stop.
05
Operate
Uptime monitoring, daily encrypted backups with a monthly restore drill, and host metrics. We hand over the operational dashboard, not just the code.
06
Iterate
Weekly to monthly tune cycles against the metrics that matter to your business, using real users and real complaints rather than a feature wishlist.
The full method, including what you see from us daily, weekly, monthly and quarterly, is on the process page.
Limits
What we do not take on.
Four requests we decline, and the reason each one fails.
01
Pure design exploration without a spec
A project whose deliverable is still an idea after a week of work cannot be scoped, priced or measured. We need a written spec before the first milestone exists.
02
Marketing-site rebuilds
Not our work. If you need a site, we can point you to a good agency. If you need a working product behind the site, that is the work we take.
03
Long engagements with no fixed milestone
An open-ended contract has no gate, so it has no end. Every engagement starts with a fixed first milestone that can be extended, refined or stopped.
04
Work with no nameable success metric
If you cannot say in one sentence which number will say it worked, we cannot write a success criterion for it. A milestone without one is guesswork.
Other ways to work with the studio: AI workflow automation for the processes that eat your week, AI integration services when the software already runs, and EU AI Act compliance for systems in scope of Regulation (EU) 2024/1689, Annex III. Every service starts with the same fixed first milestone. The full list is on the services page.
Trust signals
Proof close to the decision.
Three signals buyers can verify before they start a conversation.
02
Founder-led delivery
The person you contact stays close to the work, from written scope through operation. See how we work.
03
We ship products before we take yours
The studio builds its own products and publishes their status: four case studies on our work page, one of them live on its own domain today. The same people and the same method is what a custom AI engagement gets. See the work.
Questions
What founders and CTOs ask before kickoff.
How long does the first milestone take?
Four weeks from kickoff to one deployed feature path. Week one delivers authentication, one core flow and one durable surface, with CI/CD, monitoring, backups and the operational dashboard already wired. The four-week mark is a gate: you extend, refine, or stop with a running slice in hand.
Who actually writes the code?
The person you email writes the code, end to end. There are no juniors and no handoffs between a sales team and a delivery team. The same person answers your questions in the daily written update, joins the weekly call, and signs off the scope. Ownership does not change hands mid-project.
What stack do you use, and can we keep it?
Boring, well-understood technology, chosen so a system stays operable and portable. The specific components are shared with clients under the engagement, not published on this site. Nothing proprietary, no vendor lock-in, and the repository, infrastructure and runbooks stay yours. We hand over the operational dashboard, so another team can run it.
What does the first milestone cost?
A fixed first milestone, scoped and priced before kickoff. The figure for your project is written into the scope together with success criteria and an explicit out-of-scope list, and it does not move once signed. Ask for the number in your first message and you get it in the reply.
What do you need from us to start?
A few sentences describing the problem, and one metric that says it worked. We read it, ask the questions that matter, and tell you plainly whether we can help. If we can, we propose the first milestone: one written spec, one deployed feature path, one core flow, one durable surface, and an explicit out-of-scope list.
Where does our data run?
EU-first data residency by default. Application runtimes are hosted in the EU, every subprocessor is named on our subprocessors page, and a Data Processing Agreement is published for signature. Personal data stays under GDPR with the processing record you can read, not a promise you have to trust.
One paragraph is enough to start.
We take on a limited number of contracts each year. If your paragraph names these three things, one reply can tell you whether it’s a fit.
- The problem What is done by hand today, and by whom.
- The metric The one number that will say it worked.
- The deadline The date it has to work by.