Notes // 03 · 1 min read

What “you own it” actually means: your accounts, your code, your prompts

Ownership is a checklist, not a slogan. Here's exactly what should be in your name when a build is done.

Everyone says you'll own it. Very few spell out what "it" is. Here's the checklist we hold ourselves to. When a build is done, every line should be true.

The checklist

  1. Your accounts. Hosting, database and AI model accounts are in your name and billed to you. Not ours, passed through with a markup.
  2. Your code. It lives in your repository. You can read it, copy it, or hand it to someone else.
  3. Your prompts. The instructions the AI follows are written down and kept with the code, not buried in someone's chat history.
  4. Your data. It sits in your database and exports in a click.
  5. Your documentation. Written for the people who use the system, not for engineers.
  6. Your call. You can remove our access in an afternoon, and nothing stops working.

Red flags

  • "It runs on our platform."
  • Logins you don't control.
  • A monthly fee that's more than what the software actually costs to run.

Why we work this way

Because the goal is the handover. We build it, train your team to run it, and step back. If we disappeared tomorrow, your system should keep running on Monday. That's the test.

What will you take off your plate?

Tell us what you're working on. We'll figure out where AI can help.