Stackby vs. Superblocks

Based on my experience, I can provide specific scenarios where Stackby is well suited and others where it may be less appropriate: Project Management: Stackby is an excellent choice for project management scenarios. Its ability to create custom databases, track tasks, assign responsibilities, and collaborate in real-time makes it highly effective for managing and monitoring project progress. CRM and Sales: Stackby is well suited for managing customer relationships and sales processes. Its customizable database structure allows for organizing customer information, tracking leads, managing deals, and generating reports. The ability to integrate with other tools further enhances its usefulness in CRM and sales workflows. Content Planning: Stackby is a great fit for content planning scenarios. Users can create databases to manage editorial calendars, track content ideas, assign tasks to team members, and monitor content performance. Collaboration features facilitate seamless content collaboration and ensure timely publishing.

Superblocks is great for building internal tools for your company. We have our finances running on Superblocks, our client services running on it, as well as a lot of internal tooling for our product. You can build full-apps using their API builder, Workflow builder, Scheduled Jobs, and UI builder. All without having to handle your own infrastructure. It's meant to be one extra abstraction layer on top of other developer infrastructure tools like AWS, Vercel, etc.

• Ability to collaborate with team members on the same spreadsheet
• Ability to integrate multiple tools for centralized utilization (i.e. Facebook, Google Analytics, project management, etc.)
• Ability to send SMS and messages using integration with Twillio and Whatsapp
• All spreadsheets/databases securely saved in the cloud instead of on local hard drive(s)

• Easy to use User Interface builder for building internal apps
• Scheduled Jobs and Workflow builder in multiple languages
• API builder for support your User Interface for your internal apps

• Implement the same views available on desktop into the mobile app
• Internal automations (like Airtable)
• Ability to implement and display info as a dashboard (like Airtable)
• Polish up the formatting of formulas, inputting them causes user frustration due to the formula input cursor jumping around
• Better intelligence and ease of inputting data in bulk i.e have the fields automatically identify what data is being input and format appropriately (like Airtable does)

• More flexibility on UI component designs

Stackby is overall pretty easy to use, especially if you're used to something like Airtable or SmartSuite. Some of the pages seem like near exact clones (though they put their own creative spin on things). I'd prefer a slighty fresher interface (like SmartSuite), but I'm willing to sacrifice that for the better price and great customer service.

Extremely responsive, helpful, and friendly support (unlike many other SAAS teams out there).

I have also tried Ora.Pm. Infinity has better graphical interface, but nowhere near as many features and the UI isn't as effective (i.e, moving around with keys). Grist has a much more technical interface and it comes from being more of a database/interactive spreadsheet vs Stackby. Grist has much more functionality in terms of formulas, but is much harder to learn to use and less other functionalities. Ora.PM is more of a test at a task management app, and doesn't compare - Stackby is much better.

• Positive impact on organising my marketing so I contact advertisers in an appropriate time frame and don't lose hours figuring out what's happening.
• Positive impact on organising challenges so that people feel more connected and supported, leading to future sales.
• Positive impact on understanding data so that I can use it more effectively.

• We've saved thousands of developer hours that would have otherwise spent on maintaining infrastructure