Why should you pay for features you don't use? Usage based pricing removes hassle of limitations and cuts the costs. It helps your business grow.
Get StartedSee how costs drop as you grow. Whether you are a startup or corporation, we got you covered with our tiered pricing
Why should you be paying for the features you don’t use?
We bill per Usage Points. Each feature has it’s own score. You’re paying only as much as you use the product. You can start with as little as 1 usage point.
Entities are like modules. For example Accounts, Contacts, Leads etc. Points per each entity.
Basic fields are fields without automation. These are fields which are filled manually or via API and do not generate anything by themselves. Points per each field.
Advanced fields are automatically generated, calculated or anyhow automated. For example you need auto-number for document or calculate sum of the invoice. Points per each field.
Types define what kind of data is being stored in field. Checkbox (boolean), dropdown, multi-select and more. Points per each type.
Validators check field entry to be correct. For example you need phone number to be in specific format. Points per each validators.
Relations help connect entities. For example an account will have multiple contacts - that's clearly a relation. Points per each relation.
Actions are tiny buttons next to each field. They make one single action e.g. initiate a phone call or send an email. Points per each action.
Widgets are like plugins to your entities. They enrich functionality of your record cards. For example barcode generator would be a widget. Points per each widget.
Every person you give authorisation to your Platform is considered a user. Points per each user.
Your entity has fields. They make up a form. Every time you fill in a form a record is being created. Points per 1 thousand records. If you have only 1 record, we will bill for 1 thousand. If you have 1001 record, we will bill per 2 thousands and so on.
Sources are where you get data and send data. This are external integrations. For example you need your ERP system data to be sent to Platform. Is will create a source. Points per each source.
Mutators transform data. For example, your source will be sending date in US format YY/DD/MM and you need European format for invoice, for example like DD/MM/YYYY. Points per each mutator.
We bill per Usage Points. Each feature has it’s own score. You’re paying only as much as you use the product. You can start with as little as 1 usage point.
Flow is like a process. We bill per each flow. Points billed per flow monthly.
Nodes are business process units. For example - Sales rep should send an email equals to one node.
Trigger is a function which is capable of initiating node execution in a background. For example you would like to send notification once reply from customer is received. Billed per trigger monthly.
Actions are automations inside flow. Send message, send push and more. These all are action. Billed per action monthly.
Transitions are connections between nodes. It's when you are doing something else after something happened. Billed per transition monthly.
Sometimes you want things to happen when particular conditions are met. This is exactly what this feature does. Billed per condition monthly.
Integrations allows you connect information sources, API and more. Billed per integration monthly.
When you need to store temporary data inside flow we bill for that. Billed per each flow where data needs storage monthly.
Each time you initiate Node execution it's an execution. Billed per 1 thousand executions monthly.
When you send webhook from Flow. Billed per 1 thousand webhooks monthly.
When you need processing incoming webhooks. Billed per 1 thousand incoming webhooks monthly.