Why not simply rebuild what you need with Claude? Airtable seems to me as a prototyping product. Once you know what you want, formulate it as product objectives

Why not simply rebuild what you need with Claude? Airtable seems to me as a prototyping product. Once you know what you want, formulate it as product objectives and ask Claude how it could be implemented from scratch. Dont even give it any ideas about Django. Just ask it what technologies are sensible for what you need, read and verify its answers, lock in a stack, plan your features and implement them. You will be surprised how many things you could not fix in Airtable or where awkward workarounds can be solved much more elegantly if you (or Claude) consider them straight in the design phase. Just make sure to start with your objectives and _maaaybe_ desired workflows to avoid biasing Claude too much and that you end up rebuilding Airtable.