Every piece of work starts as a written scope you agree to before anything is built. 10xs, the AI software production system I created, does the build, and I'm responsible for it from scope to launch. You see every task and test as it happens. The code is yours from day one, in your repository.
I take on your product's engineering for as long as you need. At the start of each week we agree what ships that week. At the end of the week you get it: working, tested and in your repository. Anything that doesn't ship carries into the next week at no extra charge. You see every task and test as it happens.
Included: compute and AI for the build, testing, deployment, and defect fixes for the agreed period (fixed-price builds).
Not included: hosting and running costs after launch, domains, app store accounts, and paid third-party services your product uses. You pay those directly, so they stay in your name.
One product or feature, built for an agreed price. Describe it in a paragraph. Within a couple of days you get a written scope, a fixed price and an agreed timeline. I'm responsible from scope to launch: it's built and checked against that scope, I deploy it, and I fix any defects for an agreed period after.
Included: compute and AI for the build, testing, deployment, and defect fixes for the agreed period (fixed-price builds).
Not included: hosting and running costs after launch, domains, app store accounts, and paid third-party services your product uses. You pay those directly, so they stay in your name.
A paragraph: what the product does, who uses it, what "done" looks like to you. For a fixed-price build, I turn it into a written scope you can read in ten minutes, a fixed price and an agreed timeline. For an ongoing engagement, we agree each week's scope from your list. The scope is never edited after we start; it is what the work is measured against.
Every task, test and change as it happens, from day one. You talk to me, not a project manager. If you want something outside a project's scope, it gets its own quote and you decide.
Running software, the repository, and the proof: the test output and the commits. Not a status email that says done. If a claim was made during the work, you can see what was checked. When a fixed-price build ships, you can carry on as an ongoing engagement if you want.
I'll reply with the way of working that fits, and a price.