Which stack do you build on?
Yours. If you have a repo, a database, and somewhere to run code, we build there. If you don't, we set up the minimum (a repo, Postgres, a host like Railway) in your accounts, not ours.
Who owns the code?
You do. It lives in your repository from the first commit, with a license to the system and no platform of ours underneath it. If we stop working together, nothing turns off.
What happens when the model changes?
You swap it. The harness (memory, context, tools, access rules, audit) doesn't depend on which model is underneath. When a better or cheaper one ships, or a provider changes its terms, the switch is a configuration change, not a rebuild.
Do you maintain it after launch?
If you want us to, ongoing maintenance and infrastructure is part of the line. If you'd rather run it yourself, the handoff includes the build log, documentation, and a session with whoever owns it on your side.
Is this like hiring a developer?
Closer to a standing build capacity than a hire: harness-first discipline on every piece of work, you own everything that ships, and you scale it up or down by scope instead of managing headcount. If a workflow needs continued delivery after launch, not just one build, that's included, not a separate negotiation. If the backlog is on a codebase we didn't build, that's AI Engineering Sprints instead: same discipline, staffed from day one.
Can we see something you've built?
We don't name clients. What we can show you in full is our own operation (outbound, content, scheduling, an ops watchdog) built and run on the same harness, with the kill switches and audit trail you'd be getting.