Direct answers, including no.

You do. Source code, service accounts, store listings, domain settings and documentation are yours. We should never be the only people who can log in.

Credentials do not belong in the repository. If a vendor requires a personal account during setup, that is temporary, and it should be moved into an account you own before handover. Leaving should always be possible.

It depends on what the written scope says about stopping, and on what has already been paid for. You keep the discovery document either way. Weekly builds exist so there is always something you can open.

Work that has been completed and paid for is handed over. We will not hold source to force a continuation. A stop is a reason to close the accounts cleanly, not a reason to invent a penalty.

Yes, when the work needs one. We read the document before signing. We will not sign terms we cannot keep, and we will not sign a clause that would prevent us from using general methods on other work.

If a mutual NDA is the better shape, we will say so. An NDA is not a substitute for a written scope.

Yes. We can design and write the whole product, or sit next to an existing team. Product design is delivered as working front-end code for that reason.

It depends on access, on who owns the repository, and on whether the in-house stack is one we can work in. We are not a staff-augmentation bench. If you need extra hands on an existing backlog, that is probably not us.

Yes. That is what Scope is for. A short paid discovery. We write down what is being built and what is not, and you keep the document either way.

A rough idea is enough to start that conversation. It is not enough to start a build. If the idea is still a feeling rather than a task, we will say so on the call.

The scope is agreed before we start, in writing. A change is discussed before it enters the build. It is not absorbed in silence and it is not a surprise on the invoice.

What happens next depends on the change. Replacing one thing with another of similar size can stay inside the same shape. Adding work is new scope. We will say which of those it is before anyone writes more code.

We don't do brand identity, marketing sites you'll never edit, or ongoing ad campaigns. We don't staff long-term retainers. If a spreadsheet already solves your problem, we will tell you so.

We also do not take hardware procurement, foundation-model training, or unattended model judgement in a consequential workflow. Replacing an entire business system is not an automatic part of building a tool. If the request is outside what we do, we will say no rather than stretch the definition.

Nothing automatic. There is no retainer to drop out of, because we do not require one. Hire us for a project, not a subscription.

Source, accounts and documentation are handed over so that the next person can run what was built. If you want a later change, that is a new scope. If something is broken and you want us to look, that is a new conversation. We will not keep a standing ticket queue.

The people who design and write the work. There is no account layer in between. That is the point of a small studio, and it is also a limit: we do not scale a project by adding a bench of unused names.

This site does not introduce individuals. The work is offered as a studio. If a named counterpart matters for your procurement process, say so on the call and we will say whether that can be arranged.

Because we are not using client names, logos or testimonials here. The projects under Work are self-initiated, labelled as such, and built to show how the studio approaches a problem.

That is a thinner public record than a case-study site. It is also an honest one. We will not invent a commission to fill the gap.

A short paid discovery first. After that, the build is either a fixed fee against a written scope, or time and materials. Which one depends on how stable the scope is.

We do not publish rates or project totals here, and the enquiry form does not ask you for a number either. Money comes up on the first call, once we both know what the work actually is. If the scale is wrong for either of us, that call is the cheapest place to find out.