@joshdance 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.

@matt_jdavis We do that as well. We have two types of integrations. In context and full sync. We can handle the authentication, error handling, API limits, custom objects or property mapping in third party apps(Salesforce, NetSuite, etc) and can even deploy custom functions to go beyond. These are integrations that take weeks and even months to develop. Would love to schedule a call with you to show you more. Here’s is my availability: Saasler.com/j.

@startstorms Great to see you here! We do support a few things in the HR/Recruting space. With the way we’ve built the product, we can handle the weird types of integrations in some of the legacy systems found in that space.

@pvptowers Thanks for the comments. We are not trying to compete with the likes of Zappier or IFTTT our solution is meant to bring a back a bit of the control lost to some of these product back to the SaaS developers. Building a great product takes a lot of effort and our belief is that product teams can eat their cake and have it too by focusing on building a great product and a great API. We take it from there, by leveraging their API to do all the integrations and interface elements needed to do the integration. Comparing it to the aforementioned products is just not a good comparison for this reason. Our integrations can do a lot more that those and are meant to be completely in context for the user making it a build vs buy desicion. We’ve found that our customers are better off building the right things in their core product as opposed to more integrations.

@jonathant Thanks for your message. I understand that you are not competing with IFTTT and Zapier. My point was that your value proposition is to save development time/cost (if I am readying your site correctly) But the way I see it is I have 3 options. 1) Pay my developers to build out every integration I want = expensive. 2) Pay my developers to build out the top 5 - 10 requested integrations, then just integrate with Zapier and IFTTT for everything else (and take the "that will be good enough for now approach") 3) Use your solution which in the short term may be cheaper, but with 60 minute polling and 500 account limit probably won't suit most applications and therefore I'm going to go on your higher tier and pay 600, 700, 800? (not sure) a month? Which to be honest is going to add up quickly. If I adopt that approach then there will be a break point where I may as well just pay developers to build the direct integrations anyway. My question still stands on who your target audience is. Maybe it's not early stage startups? (which is cool if its not). I'm just trying to say that if you are targeting new/pre-seed startups then I am 100% your target market, and my feedback is that pricing would be an issue for me. If however you are targeting startups that have already raised a bunch of cash then my opinion is invalid as Im not the customer you are trying to acquire. But if I had raised $500k or something then I probably have the cash and resources to build the integrations anyway.

@pvptowers Thanks for continuing to ask questions. Here's a summary fo respones: 1. Correct. Building it yourself is always an option and depending on the case, it might be critical to do so. We haven't seen many of those cases. 2. This is definitely a good approach since it solves for a lot of the cases. Building integrations with Zapier and IFTTT can good practice, if you don't mind loosing a bit of control over your customers data, regardless if you are building the integrations yourself or using a service like Saasler. 3. We can definetly work with early stage startups at lower prices, assuming the volumes are less. We've found that our customers typically price their offerings above $1000/month and even at $100/month, it still makes sense just by being able to add a few extra customers. If you are early stage Saasler is even more cirtical and necesary since not only do you need to worry about building your product and making sure it's diffentiated enough, having to deal with the integrations will help rub off some of the benefints of existing platforms and allow for faster growth - not to mention the fact that they can focus on their product. Most of our customers are not that early stage. Generally more mature and have teams in the dozens. 4. The 60 minute polling is not such a big issues as you mention. Primarily because of the way that those integrations work. They are triggered by the end user and thus are immediate - no delays. Added a new Gif as an example. 5. There's always a breakpoint as with any product. For instace usign somethign like Heroku or AWS's RDS DB vs having your own devops team. Our assumption is simple: why reinent the wheel with somethig like integrations if you can use that time on moving your roadmap forward. Hope this helps clarify things and happy to answer any more questions you might have.

@jonathant Awesome, good to know that the 60 minute polling isn't an issue for triggered tasks. That makes a huge difference. If you end up launching a super early stage startup pricing structure or a price per action/trigger message me back. I know I would immediately be a customer. I can see how if you have a SaaS product at $1000 per month, then your pricing makes a ton of sense. My startup is pitched much lower end free with $9 per user, per month (to add some context as to why the $399 seems expensive to me)

@pvptowers It would be great if we can schedule a call and figure out a way we can help you. Pricing is not the most important things to us but rather making sure that what we do adds value. Here's my availability: saasler.com/j

@robbiejfrye thanks for your support through out the process!

@goldy_arora 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.

@jbritten It really depends on what you are trying to do and integrate with. The polling feature is not the primary method used in this type of integration. It is user triggered. Most companies that need faster polling are using the growth version which is usually used to sync to enterprise type products with tons of custom objects. That’s where the real power comes in. You are right. You can definitely have one of your developers spend four to eight weeks doing a complex integration and then maintain it and keep up to date with changes, support and other work required around a piece of code you develop. Our customers find it better to focus on their product than integrations since it’s something we can help them build without having to worry about them. There are obviously trade offs for each approach and your mileage will vary, but if anything buying your team focus is then most important thing imo. We’re also the difference between closing and not closing a sale. For B2E companies that have lost deals just because they lacked an item in the buyers checklist like an integration. Once it becomes a priority to build it, it can can typically break havoc on your product team in order to get that integration team. Or you could just use us ;) How. Many times have product managers had conversations with Sales people about how they’ll be able to tackle an integration that could help close more deals in the “next quarter”? We solve for that. And typically getting one new client far outpaces the cost of ournintegrarions - when you can get either 500 or more to offset the cost. Btw, accounts are not users. An account can have many users so it’s actually pretty good when you look at it from that perspective.