What do Meta API and LEGO bricks have in common?
And why can it help your SaaS company focus on getting more licenses?
You are a SaaS company providing client services to other companies?
Your solution is a software addressing a particular business need that can be outsourced like communication & customer relationship platform, ticketing & after-sales support, purchasing & HR process?
This article is made for you!
SaaS solutions like yours can be used by clients as such. However most of the time your solution is more powerful once it’s integrated into your clients’ s tools: workflows are smoothed and data aggregated which make processes more efficient! I am not telling you anything new here!
Once you get a new client, the time comes to implement the integration needed. This is when it gets more complicated!
Indeed, each new customer has its own specificity. They are using different tools, have different protocols, file formats, and servers therefore the integration they need is not duplicable from one client to another.
Two scenarios here: either you are taking care of it (IT, implementation team) in coordination with your client’s technical team, or you let your client do the connections to your systems. Sometimes you choose one or the other option depending on the client’s size.
→ In the first scenario, your Tech team needs to have a custom approach for each new client. In addition, you (and in some cases your clients) have to maintain the solution and must have the ability to do so.
This is a time-consuming option for your Tech teams that are not focusing on their core production, but also for your sales teams that are managing the discussion with the clients. I have recently heard from a client that “as a SaaS company, my objective is to get more licenses and not to become an engineering services company”. This makes perfect sense, and I am sensing some of you are already waiting for the following to see how to avoid this!
→ In the second scenario, you can be faced with clients with no internal resources to manage the integration. In this case, it is best to have a partner you can advise them to go to.
In both cases, this is where Meta API can help you focus on your core business.
But before moving forward to tell you how, let’s recall some of your childhood memories of a game you have probably played with at least once: LEGO bricks!
With a set, you could either follow the instruction or build what your imagination told you to. The bigger the set was, the more infinite the possibilities were!
With Meta API, it works the same.
- our low code platform is the game,
- the set is the catalog of Connectors available in our catalog,
- the bricks are what we call a Spell — your custom integration built with the Connectors
To build your Spell, you select the Connectors you require and you only have to code the logic behind the business need. You can do so without having to understand the complexity behind the API. In other words, you don’t have to make the bricks yourself, you just have to use them the way you want! It’s faster and easier!
Let’s push the metaphor one step further :
Once you have built your first Spells, you can build a bigger construction by assembling and tweaking the existing bricks. The idea is to be more agile once you have a new client with a specific integration.
Using Meta API will enable you to reduce your client acquisition cost and increase your productivity so you can focus on your core business: developing and improving your product to get more licenses!
A lot of other features were used building these bricks like OAuth, Serverless hosting, and Monitoring. Let us show you how we can help! Book a demo here or Signup for free and start playing with you own Bricks now!
