Realize your workflow goals faster

We package our services in credits. You purchase a defined volume of credits based on your needs. Credits are equal to the outcomes you are looking to achieve. Learn more about our packaging model here. 

Estimating outcomes should be based on story complexity. Asking the following questions in advance can help our team scope your needs with you:

• Is there branching logic?

• How many tools are you looking to interact with throughout the workflow?

• Will it call on other workflows (i.e. send to story)?

Not always. A single outcome can require more than one workflow or ‘story’, and therefore occupy more than 1 license spot. For example, one outcome might translate to more than one story (ie: a phishing workflow could encompass a couple stories and a couple send to stories).

The number of credits you need will depend highly on the stage of maturity for your workflow automation program. 

• If this is your first time building a workflow automation program, 20-30 credits is recommended. 

• If you are migrating from an existing platform to Tines, 33-53 credits are recommended.

• If you are running a large-scale program, 18-32 credits is recommended. 

Our highest impact programs include a mix of technical training, story building, and advisory services.

The length of a services engagement varies based on the outcomes agreed upon during

scoping. Below are some example thresholds based on outcomes:

• 3 weeks for up to 2 outcomes

• 12 weeks fo up to 6 outcomes 

• 20 weeks for up to 10 outcomes

We always agree to the outcomes and timeline during the scoping process.

Please see our professional services agreement here.

The call is 60 minutes to discuss your workflow initiative and goals. 

Ahead of the scoping call, potential subscribers will fill in a scoping spreadsheet. During the call, we'll talk through the spreadsheet and the customer will walk through the existing steps for their use cases today. Ideally, we talk through any tooling that will need to interact with the workflows as well. 

Within 48-72 hours of the call, we'll share an estimated level of effort and associated cost with you to review.

Yes. To deliver the services effectively, we’ll need to grant your dedicated Tines team temporary access to your tenant. We can discuss how to provision this with our roles and your SSO provider, if needed. 

Support is there to answer technical questions and troubleshoot issues within your Tines tenant. Services are to deliver outcomes, support your building, and discuss your business strategy with Tines. For a full overview of our support services, please see our Support Reference Guide.

You can find information on our partner portal here. If you already have a signed agreement in place but don’t have access to the portal, contact partnerportal@tines.com.

There are three tactical areas to focus on in preparation for a migration below. For a more detailed look at migration, see our blog post, ‘Migrating from legacy SOAR platform to Tines: a step-by-step guide.”

1. Set up: Does our team have the necessary access to your systems included those that are on-prem?

2. Prerequisites: Execute on the pre-work including the following,

   1. Identifying your top use cases by priority

   2. Documenting any existing workflows

   3. Testing your credentials for your tools

   4. Identifying stakeholders within your team

3. Collaboration

   The key to migration success is close-collaboration between your team and ours. The best, most efficient programs include our teams meeting regularly for office hours and your team providing timely feedback on each use case.