Approval-tracked IT request portal for small teams

What to build

A no-code IT request portal for small-to-mid IT teams (5-50 employees) that replaces a shared inbox and spreadsheet: a ticket intake form, role-based approval chains (manager then IT sign-off), status tracking, and an audit trail of who approved what and when. Ship it first as a Softr + Airtable template, then as a standalone SaaS add-on with SLA reminders and offboarding checklists.

IT teams below the budget/scale of ServiceNow or Jira Service Management are still running approvals through a shared inbox and a spreadsheet, which breaks down on audit trails, visibility, and accountability — a lightweight no-code portal can fill that gap without enterprise ITSM overhead.

Demand

IT managers at small-to-mid companies want governance (who approved this access, when, and why) without buying an enterprise ITSM seat license; the trigger is usually a compliance ask or a messy offboarding that a spreadsheet couldn't catch.

• r/nocode (Reddit)Complaint

  Original post: "How can we build a governed IT request portal with approval workflows? Right now, it's a shared inbox and spreadsheet." — direct evidence of a team outgrowing informal tools and asking how to formalize approvals.

• Independent source countOther

  Only 1 independent source identified for this signal, with a low historical match score (0.56) and no prior corroborating matches — demand signal is real but thin.

Stack

• Airtable (data model + approval status)
• Softr (portal UI + client logins)
• Make or Zapier (SLA reminder automation, Slack/email notifications)
• Airtable Automations (approval routing logic)
• Stytch or Softr built-in auth (role-based access)

Solo + AI difficulty

The core build — intake form, Airtable base, Softr front end, basic approval stages — is a 1-2 week MVP for a solo builder using no-code tools; the hard parts are getting role-based visibility correct (so requesters can't see internal approver notes) and building a trustworthy audit/retention log, which may need a custom logging layer outside Airtable's native history. Packaging it well enough to sell (templates, docs, onboarding) often takes longer than the build itself.

Entry threshold

Low barrier: can be built solo in days to weeks using no-code platforms like Softr, Airtable, or similar; the main work is good workflow and permissions design rather than new technology.

Window

6-12 months

Where to find first users

• r/nocode and r/sysadmin
• Softr and Airtable template marketplaces
• Product Hunt launch targeting 'IT ops' and 'no-code' tags
• Cold outreach to IT managers at 20-200 person companies via LinkedIn

Competitors

• ServiceNow
• Jira Service Management
• Freshservice
• Zendesk

Counter-signals & risks

• Established enterprise ITSM vendors (ServiceNow, Jira Service Management, Freshservice, Zendesk) already offer approval workflows and may have or release lightweight/SMB-tier plans that undercut a new no-code template.

• Low historical match score (0.56, no prior matches) suggests this is a weak or unvalidated signal with limited corroborating demand evidence beyond the single Reddit post.

• Building on Softr/Airtable risks vendor lock-in, scaling limits, and pricing changes that could undermine unit economics or reliability for compliance-sensitive use cases like audit trails.