# A long-term technical partner, for every system your company runs.

For a company that will run on several systems, OCTYN can be its long-term technical partner. One Consult maps the whole operation. New systems are built at the partner rate, each fixed in writing, and one monthly fee, fixed for the term, runs and updates every system up to an agreed number. The same people map, build and run all of it.

## The partnership over time

One Consult maps the whole operation. Each system gets a fixed price in writing at the partner rate, is built, then runs. The next waits until its process settles. One monthly fee, fixed for the term, runs every system that is live.

## Who it is for

### A new company

Building its operation from the start, and wanting one partner to put each system in place as it grows.

- The first process already works and already takes people.
- More processes will follow as the company grows.
- You would rather not hire a team to build and run them.

### An established company

Moving much of its work onto systems, and wanting one partner who already knows the company, not a new firm for every project.

- Several teams do the same work by hand every week.
- Past projects each left behind something nobody runs.
- You want one set of people answerable for all of it.

## Is a partnership right for you?

Signs it fits:

- More than one part of the company runs on work done by hand.
- At least one process already works and just takes people.
- You would rather have one partner than a firm per project.
- You want the systems run and kept current, not handed over.

Signs it is early:

- Only one piece of work needs a system.
- No process has settled yet.
- You are comparing hourly rates.

Two or more signs that fit: book a mapping call. Early, or not sure: send the problem from the homepage form, and a person replies within two working days.

## How it runs

- **The mapping call**: The first conversation, about the whole company, with the people who would build every system.
- **The Consult**: The whole operation mapped and measured as it runs today, not one workflow.
- **The roadmap**: Every system worth building, in order, and the partnership agreed on it: the term, the partner rate, the monthly fee and how many systems it covers.
- **Build, run, next**: Each system is priced at the partner rate before its build starts, then built, measured against its baseline and run.
- **Kept current**: Every live system watched, updated and re-set as the company changes, under one monthly fee that stays fixed for the term.

## One system at a time, or one partner for all of them

| | One system at a time | As a partner |
| --- | --- | --- |
| The Consult | One per project, each starting from nothing | One for the whole operation, kept current as the roadmap moves |
| The commitment | One system, one agreement | A set term, agreed up front |
| The price of each build | Fixed, in writing, for that one system | Fixed, in writing, for each system, at the partner rate |
| Running them | A monthly fee for each system, added as it goes live | One monthly fee, fixed for the term, for every system up to the agreed number |
| Who does the work | The people who built that one system | The same people for every system, from the first to the last |
| The next system | Starts with a fresh mapping | Starts from a company already mapped and people who already know it |

## What it gives you

- **The partner rate**: Every new system is built at the partner rate, below the price of the same build on its own, and still fixed in writing before it starts.
- **A fee that does not move**: One monthly fee runs and updates every system up to the number agreed at signing. It stays fixed for the whole term, however many of those systems go live.
- **Each system starts faster**: The operation is already mapped and the people already know it, so each next system starts from what the last one learned.
- **One set of people to call**: The people who built every system answer for all of them. No account manager in between, and no second firm working around the first.

## What stays the same

- Every build has its own fixed price, in writing, before it starts.
- Every system is yours: data, specs, configuration and code.
- Every system is drawn with the steps a person closes, and never closes them.
- Any system can be taken over at any time, with the documentation to run it.

## Questions

- **How long is a partnership?**: A set term of six to twelve months, agreed before it starts. A longer term brings a better partner rate.
- **What does the monthly fee cover?**: Running every live system up to the number agreed at signing, and keeping each one current: fixes, updates as the services under it change, and re-setting it when the company changes. A new capability is a new build, at the partner rate.
- **What if we need more systems than agreed?**: Each system beyond the agreed number adds a step to the monthly fee, and the size of that step is set at signing, so the cost is known before anyone asks.
- **Do we have to build the whole roadmap?**: No. The term commits you to the partnership, not to every build. Each system is priced on its own, at the partner rate, before its build starts.
- **What if we only need one system today?**: Then a partnership is probably early. Start with the Consult for that one; a partnership fits once a second system is on the roadmap.
- **Is a new company too early for this?**: Not if one process already works and takes people. That is the first system. The rest wait on the roadmap until each process settles, so nothing is built around work that is still changing.
- **Can we take the systems over later?**: Yes. Your data, specs, configuration and system code are yours, and each system comes with the documentation to run it yourself.

## Related

- [The Consult](https://octyn.co/consult)
- [Engagement terms](https://octyn.co/engagement-terms)
- [The three families](https://octyn.co/systems)

Canonical: https://octyn.co/partner-with-us