Realize your workflow goals faster

We package our services in hours and fixed cost. Hours can be used towards story building, advisory: story assessment and review, or advisory: sessions. We have a fixed cost for technical training and roadmap workshops. You purchase a volume of hours based on your needs.

The number of hours you need will depend highly on the stage of maturity for your workflow program and which service offerings you need. 

• If this is your first time building a workflow program, 115-170 hours is recommended. 

• If you are migrating from an existing platform to Tines, 190-300 hours are recommended.

• If you are running a large-scale program, 100-180 hours is recommended. 

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

Estimating hours for story building depends on complexity. Asking the following questions in advance can help our team scope your needs with you:

• How complex will the logic be?

• How many formulas and loops will be required?

• Will there be advanced formulas?

• Are we hitting multiple API endpoints? How many tools are you looking to interact with throughout the workflow?

• How much user interaction is required?

• Is there branching logic?

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

Since hours are scoped based on the type of work, we tend to stick to the original definition. However, we understand plans change and are open to reviewing the hours on a case by case basis.

You have the duration of your contract to use your hours. Hours expire at contract end and do not carry over to renewals. Having scoping conversations early on helps mitigate the risk of unused hours.

Yes, you always have the option to purchase additional hours if necessary to help achieve business outcomes. For story building and advisory hours, you will receive weekly progress reporting on your hours utilization.

The max hours bucket for advisory sessions that can be purchased is 30 hours. We will review exceptions on a case by case basis.

The Tines professional services team will work with you to meet your goals and objectives within your desired timeframe. Our project manager will work with you to get to a plan both teams are aligned on.

Tines reserves the right to require additional hours as needed.You can accelerate services timelines by contracting a dedicated resource or multiple resources. These are considerations we can discuss during the SOW 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 you will walk Tines through the following:

• High level description of each priority you’re looking to achieve

• Existing steps for the workflows today

• Any tooling that will need to interact with the workflows 

Within 72 hours of the call, we'll share an estimated level of effort (hours) 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, and this is typically done via some combination of VPN, VDI and contractor / service account access.

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. 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 prework like: 

• Identifying your top use cases by priority

• Documenting any existing workflows

• Testing your credentials for your tools

• 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.