Who fixes it when it breaks
This is the page that decides the purchase, so it is written plainly. What is yours, what is ours, what happens at three in the morning, and how you leave.
Yours from day one
Every account the systems run on, from hosting and model APIs to messaging and analytics, is opened in your name and paid from your card. The repository with the code, prompts and configuration is yours. So is the documentation, written as we build, not after.
Ours to keep running
Monitoring on every system, around the clock. Failure response within four working hours. Model migrations, platform compliance, prompt and playbook updates, and the monthly report. This is the subscription.
Changed only with you
Anything a customer of yours might read or hear, whether a chatbot answer, a follow-up message or a published article, changes only after you approve the sample. Everything behind it we change, test and report.
Three in the morning, a system stops
The monitor pages us. Within four working hours we have either fixed it or told you what broke and when it will be back. The incident and the fix go into the monthly report. You do not find out because a customer told you.
Most incidents are not our code. They are a platform changing an API, a carrier tightening a rule, a model being retired. That is the reason the subscription exists: keeping a system alive in 2026 is a job, and it is ours.
Why code and not a drag-and-drop canvas
Our systems are written as code, not assembled in a visual workflow tool. That is an honest trade and you should hear both sides of it.
What you gain: versioning, so every change is recorded and reversible; tests, so a change to one step cannot silently break another; and the ability to run six systems for years without a canvas that nobody can read any more. Every visual tool we have used works beautifully for three workflows and becomes unmaintainable at ten.
What you give up: the ability to open a canvas and drag a box yourself. Changing a code-based system takes an engineer: ours while you subscribe, or anyone you hire after. We would rather say that here than have you discover it in month seven.
How you leave
After the included period, cancel in any month by email. On the last day you keep the repository, the accounts, the documentation and the published content. We provide six weeks of handover support for whoever comes next, at no charge. The clause is in the contract in these words.
We put it there on purpose. A subscription should be renewed monthly on results, not held together by the difficulty of leaving.
Ask us anything on this page, on the call
Free, and useful even if you never work with us: you leave with a one-page map of which system fits, what it costs, and what it takes from your side.
4300 Biscayne Blvd, Miami, FL 33137 · info@datik.click