Need an Airtable architect to build a relational schema and a new clean Airtable base.

Budget: 27000 UAH Deadline: 4 days

I can take Phase 1 as a paid stage of the audit - 800 USD for 4 working days, aiming for 18-24 hours. The hourly estimate is 40 USD/hour, but for the first stage, a fixed price is better, as the result should be a schema map, architecture memo, and migration plan. NDA - yes, we are ready to work.

We had a similar approach in corporate systems, where we turned chaotic operational logic into a proper data model, roles, statuses, dashboards, and support rules. Yes, we transformed flat structures into relational models. I would start not from automation but from the entity model - signals, advisors, products, gates, recommendations, decisions, sources, artifacts, responsibilities. Then - a separate Sandbox base, linked records, lookups, rollups, required fields, views for roles, and migration map. In the live base, we do not make changes without agreement, read-only or normal export.

Questions for a precise framework
> Can you provide an export schema or read-only access to the base without personal tokens?
> Should Phase 1 cover both directions equally deeply, or is the Product catalog more important than the Feedback system at the first stage?

Examples
> https://business.ingello.com/forma-bpm - close in terms of process logic, statuses, and work rules
> https://business.ingello.com/platforma - corporate platform with roles, departments, and management structure
> https://business.ingello.com/vorfahr - example of product SaaS and systematic work with data

A short walkthrough as a final artifact after the stage - ok, within the rules of the exchange. More details about Ingello Systems for FLH here =)
> https://systems-fl.ingello.com/ua Expand

Budget: 15000 UAH Deadline: 6 days

Good day. I read carefully. What is needed is not cosmetic work, but structural work: an audit of the current Airtable base, which has grown organically and become flat, designing a clean relational schema for two directions (feedback system and product catalog with about 400 entries, around 100 active), building a new clean base separately in a sandbox, documentation and recommendations for migration, without changes in production without agreement.

My strength here is in relational data modeling: I constantly design schemas for the backend (entities, keys, relationships, normalization where needed, and conscious denormalization where justified for reporting). The approach for your case: first, I will analyze the current structure and indicate what is actually used, what is duplicated, and what can be combined or removed; then I will design entities and relationships (signal log, advisors, feedback intake, synthesis, and product catalog with lifecycle and gate logic) through linked records with lookup and rollup for the necessary dashboards. I will build the new base in a separate instance, not touching your production, and separately describe the migration plan.

I would like to clarify the depth: do you need just the audit plus the designed schema with documentation, or also the full implementation of the new base and data transfer? And is there an export of the current structure (list of tables and fields) so that I can assess the volume more accurately?

Budget: 7000 UAH Deadline: 7 days

Hello, Viktor!

I have experience with Airtable architecture - restructuring flat databases into relational schemas, linked records, lookup/rollup logic, interfaces, and views.

My approach:
Phase 1 - audit of the current database (via read-only or export/screenshots, without touching production), identifying duplicates and unnecessary tables, designing a clean relational schema for the Feedback System and Product Catalog. Schema map + architectural memo.
Phase 2 - I build a clean database in a separate Sandbox: tables, relationships, views, interfaces, migration map, documentation for the team.

NDA - no problem. I have experience with operational systems of similar complexity. Approximately 10-12 hours for Phase 1.

I am ready to discuss the details. Expand

Budget: 27000 UAH Deadline: 6 days

We already have a practically ready similar solution for the operating system with products, statuses, roles, reports, and a migration map - it can be quickly adapted to your Airtable base, we can discuss it here, I'm available ))

For Phase 1, I would estimate the audit and architectural recommendation at 24-32 hours, I can take the first stage for 28,000 UAH fixed and 6 working days. We are ready to work under an NDA. We won't touch the production base without agreement - analysis through read-only access, export, screenshots, or description of the structure, and all construction will be done in a separate Sandbox base.

The approach is as follows - first, we analyze the actual use of tables, fields, views, and reports, then we build a proper relational schema for signal log, advisors, intake, synthesis, gates, recommendations, product catalog, lifecycle, and reporting. Next, we prepare the schema map, primary keys, linked records, lookup and rollup logic, governance rules, and migration map, so the team doesn't return to chaos in two weeks - the eternal classic, the base won't tame itself =)

I also see sense in immediately laying the groundwork for cautious automation - not AI/MCP to live Airtable, but controlled scenarios in the new base, for example, generating operational artifacts, checking mandatory fields, status transitions, and reporting.

Let me clarify 2 things.
> How many tables are currently in the live base and can we get at least a schema export or read-only access?
> For Phase 1, is it more important for you to receive only the architecture memo, or also a prototype of the new structure with 3-5 key tables in the Sandbox?

Examples of similar systems Ingello.
> https://business.ingello.com/platforma - corporate platform with roles, processes, and management logic, close to your operating system.
> https://business.ingello.com/forma-crm - CRM and business processes, useful as an example of data structuring, statuses, and team work.
> https://business.ingello.com/fractal - process automation and agent logic, may be useful for the future layer of automation after the clean schema.

Main profile on systems - https://systems-fl.ingello.com/ua

As a result of Phase 1, you will receive not just advice, but a working map - what to keep, what to merge, what to move to linked records, how to transfer 400 products, and how the team can maintain the base without duplication and manual pain. Expand

Budget: 7000 UAH Deadline: 12 days

Good day! I have done exactly that — transferring Airtable, which grew organically and became flat, into a proper relational schema with links between tables and clean statuses. I agree with your approach: not to touch the working database, to create a clean one in a separate Sandbox, verify it with your data, and only then migrate. Regarding the feedback system and the catalog of ~400 products, I already see the core entities with statuses and gate logic. I am ready in 12 days: schema plus migration documentation. Just let me know, do you have Airtable on a paid plan?