Engagement terms.
The principles every OCTYN engagement runs on. Each engagement is governed by the written agreement you sign, which carries these and the fixed price; where the two differ, the agreement wins.
A call, the Consult, then one price.
The first conversation is with the people who would build the system. If there is a fit, the Consult comes next: a paid mapping of your operation that sets the baseline and the architecture.
The price of the build comes after the Consult, as one fixed figure, in writing. You know the whole cost before anything is built. Running the system after launch is a monthly fee.
One partner for every system.
A company that will run several systems can have OCTYN as its long-term technical partner for a set term: one Consult for the whole operation, each new system priced in writing at the partner rate before its build starts, and one monthly fee, fixed for the term, that runs and updates every system up to the number agreed at signing.
What is yours.
Your data, specs, configuration and system code. OCTYN’s general tooling and methods stay OCTYN’s.
The documentation to run the system yourself comes with it, so taking it over is always an option.
Where it lives and what the system reads.
With you wherever it needs to. The system runs on your accounts or your infrastructure where the work calls for it, and it reads only what the job needs.
An NDA is yours on request, before the first call if you want one.
Where a person decides.
Every system is drawn with the steps a person closes marked on it, and the system never closes a step marked that way. You decide which steps those are, and the Consult writes them down.
How models are used in what OCTYN builds.
The systems use AI models for work that needs reading or judgement, such as sorting what comes in, research and first drafts. Where a model’s output leads to something that matters, a person signs off before it happens, or the step is checked before it runs.
Which models and providers a system uses is written into its architecture and handed over with it.
Run, kept current, or handed over.
OCTYN runs the system. It is kept current as the services under it change, and re-set when your company changes: a new product, a new market, a new way of working.
You can also take it over, with the documentation to do it.
What we say no to.
Not everything needs automating. Some work is better done by a person, and the Consult says which. If nothing in your company is worth building a system for, we say so, and the map and baseline are still yours.
OCTYN names a client only with their permission.
Questions about any of this? Ask on the call.
The first conversation is with the people who would build it. If there is a fit, the Consult comes next.