“I'd give Softr a strong 8.5/10 for your proposed use case.”
“Custom branding | Your logo, colors, fonts, and domain.”
“User groups | Separate customers, managers, and administrators.”
“Data permissions | Restrict customers to their own records.”
“Forms | Easy request submission.”
“Integrations | Connect to Airtable, HubSpot, SQL databases, and other data sources.”
“Automations | Trigger notifications and workflows when requests change.”
“Mobile responsiveness | Customers can use the portal on their phones.”
“Softr also offers native databases, so you don't necessarily need Airtable or another external database.”
“I'd consider it particularly suitable if you want a professional-looking portal that is relatively quick to build, easy to maintain, and doesn't require extensive coding.”
“Softr charges based partly on the number of people logging into your portal.”
“If you eventually need sophisticated ticket routing, SLA management, escalation rules, complex approval chains, or extensive reporting, you may need integrations or external automation tools.”
“Softr is flexible, but it isn't the same as developing a completely bespoke application.”
“You need to configure record-level permissions correctly so that Customer A cannot access Customer B's requests.”
