How is this different from Cloud Elements?
Unlike Cloud Elements, Saasler offers a manual trigger for integrations. We have designed Saasler’s integrations specifically to increase user engagement with your application, increasing user satisfaction and reducing churn.
How is this different from Zapier or IFTTT?
Third-party products like Zapier or IFTTT merely allow you to sync data based on certain triggers you set up and nothing more. This process overcomplicates user experience, reduces engagement with your app, and adds extra cost. Saasler takes your integrations to the next level: you can not only sync data, but expand the functionality and usability of your SaaS product without getting distracted from your core feature development.
How is this different from MuleSoft or AppDirect?
We are a bootstrapped SaaS company; you are a bootstrapped SaaS company. Why work with firms tooled to service the Enterprise, with all the legal and business red tape that includes? With engineers you wouldn’t hire and finance departments that prohibit flexible and responsive partnerships?
How are active accounts defined?
A connected account is an account that does one or more calls per month.
An active account can have multiple users. So in essence, it’s the number of accounts that will count. For instance, if your users connect to Basecamp, only the main account would count. Not each individual user.
Example: If we had Basecamp as a client and we were to connect them to Freshbooks. Each company — Freshbooks and Basecamps — has one account with us. But each account has many team members or outside users. In this case, accounts are like connectivity points. There are 2 active accounts.
There are cases where some accounts are equivalent to number of users.
For example, when certain apps don’t have multi-user accounts (like SEOMoz), each new user that is added to the application represents a new active account.
On average, our clients have 5,000 to 10,000 accounts.
What is White Glove Setup versus a regular set-up?
With our White Glove Setup, we go over the requirements for a particular integration, and help suggest best approaches based on the needs of each type of user. From there, we set everything up and provide the necessary items so that your integration can be tested in the app. After that, we tweak and assist in deploying the integration to production. Essentially, we take care of all the little details from start to finish. All we need is someone on your end to help approve the requirements and that we have set up in the app. We take care of everything else.
You can also go self-serve with us; what we have called a “regular setup”. You’ll need to learn the tool, and set things up for yourself. It will take quite a bit more work for you to get things up and running, but it’s doable. It’s why most of our customers have chosen the White Glove Setup option.
What does the process look like to make sure the integration happens without a hitch?
If a user clicks on something, we make sure that it gets executed. We have a web hook that makes sure things get executed.
If we were to get started with you, what would you need from us?
We would need the following things from you, in order to get started:
- Copy of your API (if it’s not public).
- List of apps that you would like to integrate with. Also, if one of those doesn’t have a public API, then we’ll also need a copy of their APIs.
- Credentials for the apps you’d like to integrate with.
- Test accounts: created bogie/fake account. One for each account (on each side). If it’s something where we can’t sign up easily ourselves, then we’ll need the accounts to be created for us.
- Requirements for the integrations: we can help you define those. Or if you have similar integrations already completed, and you like the way they have been put together, then we’re more than happy to look at those. If there are changes or additions you’d like to see in your integrations based on previously completed ones, feel free to let us know.
How would that onboarding process look like? What can we expect?
- Kickoff call: to go over the objectives and requirements.
- Requirements document: From there we create a doc with all the requirements so that you can review them and approve them. We can have a follow-up call if needed.
- Integration work: We start working on the integration(s).
- Integration Demo: We demo the integration(s) to you over a call. If necessary, based on your feedback, we make changes to the integration(s).
- Code Setup: We set up the Saasler integration code in your app.
- Drink margaritas in Caribbean knowing you have gotten a lot more integrations with just a few hours of work :).
Overall, in our experience with our customers, we can move as fast as they do. So, the earlier we get the things we need from them, the faster we can start delivering on the integrations.
What if we need to unplug from service? What happens after then? Would we need to rebuild?
Just like any other SaaS product, yes, you would need rebuild the integration from scratch. As part of the transition, we would pass along all the authentication tokens so that if you wanted to build it yourself you could without having to have users reauthenticate. All relevant data like authentication tokens, settings, etc. would be exported and handed to you.
Unplugging from the service might end up costing you more than keeping it on. If the integration we built was successful for you, unplugging from it would certainly cost you more than the annual fee you would pay us.
I’m worried about handing over my data. How do you handle that?
If you’re using AWS or email, you are already handing over company data to third parties. If you’re using Zapier, you are losing complete control of your data. It’s like giving them the keys to your kingdom, without getting anything in return. We pride ourselves in keeping your data safe and secure as it goes through any integration we build.
How long does it take to set up?
After we have approval on the integrations on your end, it take from a couple of days to a couple of weeks, depending on the number of integrations required. You can always roll it your new integrations one at a time as they become available.
How much does it cost?
Plans start at $399/month, please see the pricing page for more details or contact us.
What will my users see?
Your users will never leave your site. They will install the integrations on your site using our white labeled integrations directory and trigger integration actions inside your app’s UI.
What your users won’t see is any need to leave your application to create integrations through something like Zapier. They also won’t face any additional learning curve or friction in integrating your app with external value-added apps.
What types of integrations can you do?
You can support many different scenarios when using Saasler, but here are some examples:
- Your user would like to send that new invoice he created in your app to Freshbooks or Quickbooks.
- Your user would like to invite her team to your product but he doesn’t want to type all those emails. Instead, she wants a nice way of selecting those emails from the company’s Google Apps account.
- Your user would like to send to a Mailchimp list the new leads that are created on your app, so he can send email campaigns to those users later using Mailchimp.
If you can dream up a way to add value to your app’s users using third-party app APIs, we can create an integration that unlocks and delivers that value.
How do integrations work?
Your users will see special buttons on your app that will allow them to perform additional actions based on the apps they’ve integrated. Check out this cool GIF: