...
The application may be built from using standard technologies such as Node.JS, React, and a SQL database. Since the frontend is developed separately from the backend, and all solutions involve the construction of the frontend (likely standalone React or similar app), primary work will consist in building a robust backend.
The work will consist of build building a set of API endpoints for the API-first approach that would interface with a database backend and a management user interface, similar to that of Airtable with any custom features specific to the particular business needs of the project. For this approach, use of open source software may be valuable, such as an open source alternative to Airtable nocodb.
...
Another possibility is to use the existing Airtable backend to manage the data and use the Airtable API to build a new frontend with React or some other framework. This approach will provide the best effort-to-value ratio for the end user by deferring the backend work and focusing on the user experience.
Backend improvements can be done incrementally to address acute pain points, while clarifying the full set of requirements to determine whether a brand new backend is actually necessary or can be accomplished using a hybrid solution of Airtable backend in combination with auxiliary tools such as CHEFs and automation scripts.
...
Decouple front end from the backend and develop them separately
Develop front end using react React or a similar framework first, while maintaining the current Airtable backend as a management interface
Fully understand the product roadmap to avoid developing one feature at a time using a system that may not meet final goals, however:
Assess whether Airtable backend can be augmented to address current deficits related to data entry (for example automating data input from CHEFs), API integrations (for example by running a standalone script to do periodic imports from external systems) and process integration (for example by using CHEFs in combination with automation scripts to drive those processes)
Determine if available SaaS governance tools are capable of meeting the business needs. Check for the availability of APIs for the possibility of driving the existing frontend using the off-the-shelf product instead of Airtable
If none of off-the shelf products are appropriate and sufficient developer resources are available, develop a custom backend application and host it on a cloud
If developing a custom management backend in the future, try to avoid developing the management interface from ground up, leverage instead leveraging existing packages, like nocodb or build an interface in Service Now