Proposal
Puts scope, timeline and price in writing.
- What is included
- What is not
- Stages and schedule
- Price and payment plan
How the work runs, the agreements that bind it, the technologies in use, and what is in progress right now.

September 2026onwards, there is room for new work.
Design and code in one hand
Design and development come from one hand. Where an interface will slow down, which decision reaches the database, and what belongs in the layout rather than the code are parts of a single decision — and when they are split between teams, the gap between them becomes the client's problem. No handover in the middle, nothing lost in the handover.
An automation that cannot show its work is not trusted
Every agent that leaves this studio records the decisions it makes. Asking a model a question is easy; giving it a responsibility and being able to audit it afterwards is not — and an automation you cannot audit shows you only the outcome when it gets something wrong. A system that keeps a record can be opened up: which input led to which decision. That is what makes handing a job to it a reasonable thing to do.
Each document is filled in per project; what follows is which one settles what.
Puts scope, timeline and price in writing.
Defines what each side is bound to.
Mutual: each side protects the other's information.
Defines what "done" means.
Keeps what follows delivery separate and optional.
This list is not maintained by hand; it is derived from what the published projects actually declare.
Say what you want built; a written proposal follows within two business days.
September 2026 onwards, there is room for new work.