1 Airtable
Best for operations teams taking requests from the whole company
Intake has an awkward shape. A few people work the queue and everyone else only submits and waits. Airtable ranks first because its pricing matches that shape. Only users with edit permission on a base are charged, and read-only collaborators and form submissions are not. The operations team pays for its own seats and the rest of the company can still send requests and see where they stand.
Watch for. Each base is capped at 50,000 records on Team and 125,000 on Business. A busy request queue needs an archiving habit from the start.
- How it charges
- Per seat with edit rights, billed yearly, top plan quoted
- Main limit
- Team caps a base at 50,000 records and 25,000 automation runs a month
2 Custom build by Black Badger
Best for requests that need routing rules and a requester view
Black Badger publishes this guide and builds custom software, and request systems are a large share of what we build. Custom ranks second because intake gets complicated fast. A facilities request, a purchasing request and an access request each need different fields, a different approver and a different clock. We build one entry point with those rules behind it, and every employee can sign in to follow a request. There is no per-seat fee and you own the code.
Watch for. If your requests all follow one simple path, a form on a product will do. A build starts with discovery and a written scope.
- How it charges
- One-time build scoped in writing, then running costs such as hosting
- Main limit
- Needs a scoping call first, and suits companies of 50 or more employees
What a custom build involves, and how to ask about one
3 Jira
Best for requests that behave like tickets with a defined workflow
Jira ranks third. A request works like an issue, and Jira is built around issue tracking with workflows you can configure. A request can move through defined states with an owner at each one. Standard and Premium have published prices. It ranks below Airtable because it is priced per user, and a business department that only wants to submit a request often finds an issue tracker heavy.
Watch for. Automation allowances are per user, from 400 steps a month on Standard to 750 on Premium. Routing rules draw on them.
- How it charges
- Per user, with a free plan to 10 users and Enterprise quoted
- Main limit
- Free stops at 10 users, Premium needed for sandboxes and unlimited storage
4 monday.com
Best for intake queues that other departments watch on a board
monday.com ranks fourth for intake. A board is a clear way to show a queue, and guest access starts at the Standard plan. It ranks here because routing a request is automation, and the allowance is 250 actions a month on Standard and 25,000 on Pro. Private boards, useful for sensitive requests such as access or pay queries, start at Pro.
Watch for. Multi-level permissions are listed on Enterprise. If requesters must see only their own items, ask how that is done on Pro.
- How it charges
- Per seat, billed yearly, from 3 users, Enterprise quoted
- Main limit
- Pro caps automations at 25,000 a month, portfolios need Enterprise
5 Asana
Best for requests that turn straight into assigned tasks
Asana ranks fifth. When a request is a task for someone, a task tool handles it directly, and unlimited automations on Starter and Advanced mean routing rules cost nothing extra. It ranks lower for intake because the price is per user, and the facts we read do not say how people who only submit a request are counted.
Watch for. Ask Asana how requesters outside the operations team are licensed before you plan a company-wide rollout.
- How it charges
- Per user, billed yearly or monthly, Enterprise quoted
- Main limit
- Portfolios need Advanced, resource tools and SSO need Enterprise
6 Smartsheet
Best for request logs that feed a grid the team already runs
Smartsheet ranks sixth for intake. If the request log is already a sheet, keeping it in a grid with approvals and unlimited automations on the Business plan is the least disruptive path. It is last here because pricing is per member, with a 3 member minimum on Business, and the facts we read do not describe how requesters who are not members are treated.
Watch for. The comparison table marks API calls as unavailable on Pro. If requests must flow to another system, start from Business.
- How it charges
- Per member, billed yearly or monthly, Enterprise quoted
- Main limit
- Pro stops at 10 members and 250 automations a month, no API calls