How Disrupt Social Scaled a Forex Investment Tracker Beyond Its 100-Investment Limit Using Airtable and Make Automation

Ajackus partnered with Disrupt Social — a performance marketing agency managing a forex investment fund tracker — to redesign a broken Airtable automation architecture that was approaching its capacity ceiling, rebuilding it with Make-powered inter-row relationships and cost-optimised workflows that eliminated the scalability cap without requiring any platform migration.

Services

Low-Code/No-Code Development

Technologies

Airtable | Ajackus.com
Disrupt Social | Ajackus.com

100+

Investment Capacity Unlocked

Zero

Platform Migration Required

2

Cost-Optimised Make Workflows Built

Overview

Executive Summary
Client
Challenge
Goals
Journey
Results
Technology
Takeaways
FAQ

Executive Summary

The Problem

A forex investment fund managed by Disrupt Social’s client was tracked in Airtable using a weekly automation that created new columns for each week’s data — a design flaw that made the system brittle, manually intensive, and structurally incapable of scaling beyond approximately 100 investments. With 80 investments already recorded, the ceiling was imminent and the client had no reporting or dashboard capability.

The Solution

Ajackus redesigned the Airtable data structure with a row-based weekly tracking table and integrated Make automation to establish inter-row relationships that Airtable’s native automation engine cannot support natively. Two workflow variants were built — one for full data population, one for defined-week cost control — to prevent Make subscription costs from escalating as the fund grew.

The Result

The redesigned system operates seamlessly within Airtable without any platform migration, handles investments beyond the previous 100-investment ceiling, and retained all existing table structures for a smooth transition. The client immediately requested additional enhancements for parallel investment classes — a direct signal of confidence in the rebuilt foundation.

Client

Disrupt Social is a performance marketing agency specialising in direct-to-consumer brands, with expertise in creative media buying and data-driven marketing strategies. The engagement in question was on behalf of a Disrupt Social client managing a forex investment fund — tracking individual investor positions, weekly growth figures, deposits, withdrawals, and closing balances across a growing investor base. The client had self-built an initial Airtable tracking system that functioned at small scale but contained a fundamental automation design flaw that was preventing the fund from expanding beyond its existing investor count.

Industry Advertising / Performance Marketing
Use Case Forex investment fund investor and performance tracking
Platform Airtable + Make (no migration required)
Engagement Type Low-Code/No-Code Redesign

Challenge

The Bottom Line

The existing Airtable automation was built around a column-per-week data model that was both structurally flawed and approaching a hard capacity ceiling — the client needed the system redesigned to be scalable, maintainable, and capable of supporting reporting and analytics, all without migrating away from Airtable.

The forex investment tracker had been built with a pragmatic approach to Airtable automation: every week, a new set of columns was created to capture that week’s opening balance, growth amount, and closing figure for each investment. This worked at small scale, but it carried a compounding structural problem — the base was growing wider every week, and Airtable’s native automation engine could not create the inter-row relationships needed to analyse investment performance across time without those ever-multiplying columns.

Automation Architecture Hitting Its Design Limit

The column-per-week automation model was unsustainable by design. Each weekly run added three new columns to the base — opening balance, growth amount, closing balance — meaning the table structure grew by three columns per week indefinitely. After months of operation, the base had become wide, difficult to query, impossible to report on coherently, and structurally incompatible with any row-based analytics or dashboard tool. The automation was not broken in the conventional sense — it ran every week — but it was building an increasingly unmanageable data structure with every execution.

Approaching the Investment Capacity Ceiling

Airtable’s native automation had an effective ceiling of approximately 100 investments for the existing data model. With 80 investments already recorded, the client was approaching that ceiling and had no viable path to growth within the current architecture. Continuing to add investors without a structural fix would either break the automation entirely or require manual intervention with every new addition — neither of which was acceptable for a fund under active management.

No Reporting or Dashboard Capability

Fund managers and investors need analytical visibility: performance trends over time, comparison across investment classes, and summary views of opening and closing positions. The column-per-week model made structured reporting impossible — each week’s data lived in a different column, preventing any time-series analysis without significant manual data reshaping. The client had no dashboard and no way to build one without first fixing the underlying data structure.

Goals

The redesign needed to remove the capacity ceiling, fix the automation architecture, and create a foundation for reporting — all without requiring the client to migrate away from Airtable or retrain on a new platform.

Goal Success Criterion
Eliminate the investment capacity ceiling System handles investment count beyond 100 without manual intervention or automation failure
Fix the column-per-week data model Weekly data captured in rows, not columns — base structure does not grow wider each week
Enable inter-row relationship logic Make automation establishes weekly links between investment records that Airtable’s native engine cannot support
Control Make subscription costs Two workflow variants built — full population and defined-week modes — prevent operation count escalation
Retain existing Airtable tables Zero migration required — all existing investment records preserved and accessible in the redesigned structure
Create a reporting-ready data foundation Row-based weekly structure enables dashboard and analytics views without data reshaping

Journey

The Ajackus team approached the Disrupt Social engagement with a constraint-first design philosophy: the solution had to work within Airtable, had to preserve existing data, and had to control ongoing automation costs as the investment fund grew. Rather than recommending a migration to a more capable platform, the Ajackus team identified a structural redesign that addressed all three constraints simultaneously.

Data Structure Redesign in Airtable

The Ajackus team replaced the column-per-week model with a row-based weekly tracking table. Each week’s data for each investment is captured as a new row, recording the opening balance, profit percentage, calculated profit value, any deposits or withdrawals, and the closing balance. This structure is inherently scalable — adding a new investor or a new week adds rows, not columns — and is directly compatible with Airtable’s reporting and view capabilities. The redesigned table structure also makes historical performance analysis straightforward: filtering by investor or by date range returns clean, consistently structured data without any manual reshaping.

Make Automation for Inter-Row Relationships

Airtable’s native automation engine cannot create relationships between rows in the same table — a limitation that makes week-over-week calculations (opening balance = previous week’s closing balance) impossible without external automation. The Ajackus team integrated Make to establish these inter-row links, building a workflow that runs each week to create the appropriate relationship between each investment’s current and prior week records. Make’s more flexible trigger and action model allowed the Ajackus team to implement logic that Airtable’s native automations fundamentally cannot execute — making it the correct tool for this specific requirement rather than an over-engineered addition.

Cost-Optimised Dual Workflow Architecture

Make charges based on the number of operations executed per workflow run. As the investment fund grows and the number of weekly records increases, a single unrestricted workflow would consume an increasing number of operations per run — potentially escalating the client’s Make subscription tier. The Ajackus team addressed this proactively by building two workflow variants: a full-population workflow for comprehensive data processing, and a defined-week workflow that limits operations to a specific number of weeks, controlling cost at scale. The client can choose which variant to run based on their current operational needs, giving them direct control over their automation costs as the fund grows.

Results

The redesigned system operates seamlessly within Airtable — no migration, no retraining, no disruption to existing records — with the structural capacity to grow well beyond the previous 100-investment ceiling and the data foundation needed for dashboard and reporting development.

100+

Investment Capacity Unlocked

Zero

Platform Migration Required

2

Cost-Optimised Make Workflows Delivered

What went well:

Operational Improvements

  • The hard investment capacity ceiling of ~100 records has been removed — the row-based weekly structure scales with fund growth without any structural changes or manual intervention
  • Weekly data entry is now consistent and structured: opening balance, profit percentage, calculated profit, deposits/withdrawals, and closing balance are captured in a single row per investment per week
  • All existing investment tables and records were retained intact — fund managers required minimal retraining and experienced no disruption to ongoing operations during the transition
  • The dual-workflow architecture gives the client direct control over Make operation consumption, preventing subscription cost escalation as investor count grows

Technical Achievements

  • Make automation establishes inter-row relationships in Airtable that its native automation engine cannot support, enabling accurate week-over-week balance calculations without manual data entry
  • Row-based data model is directly compatible with Airtable’s views and reporting capabilities — the client now has a reporting-ready data foundation without additional tooling
  • Two Make workflow variants (full-population and defined-week) provide operational flexibility and cost control across different fund management scenarios

Business Validation

  • The client immediately requested additional enhancements to support parallel investment classes — a direct signal that the redesigned foundation met their operational requirements and that they trust the architecture to support further development
  • Fund managers reported satisfaction with the solution, confirming that the redesign addressed their core pain points without introducing operational complexity

Why It Worked

Constraints Defined the Solution

The Ajackus team treated the client’s platform preference — stay in Airtable, retain existing data — as design requirements rather than limitations to work around. This constraint-first approach led directly to the Make integration decision: rather than recommending a migration that would have solved the scalability problem by abandoning the existing system, the Ajackus team identified the specific automation capability gap (inter-row relationships) and filled it with the right external tool.

Cost Engineering Built In from the Start

The dual-workflow architecture was not an afterthought — the Ajackus team identified the Make operation-cost risk during the design phase and addressed it before building. By delivering two workflow variants, the client received not just a functional solution but an operationally sustainable one: the cost of running the automation scales predictably as the fund grows, rather than escalating in ways the client did not anticipate.

Root Cause Fixed, Not Symptoms

The original automation produced correct output each week — the problem was architectural, not functional. A lesser fix would have extended the existing column-per-week model to handle more investments, deferring the structural collapse rather than eliminating it. The Ajackus team redesigned the data model from the rows up, so the scalability issue and the reporting limitation were both resolved by the same structural change rather than requiring separate workarounds.

Frequently Asked Questions

Why couldn't Airtable's native automation handle the inter-row relationship logic?

Airtable’s native automation engine is designed to trigger actions based on record events — new record creation, field changes, and similar — but it cannot create or query relationships between rows within the same table. The forex tracker required each week’s opening balance to be derived from the previous week’s closing balance for the same investment, which is a cross-row lookup that Airtable’s native automations fundamentally cannot execute. Make’s more flexible workflow model, which can query and update arbitrary records based on custom logic, was the correct tool for this specific requirement.

How does the dual Make workflow architecture control costs as the investment fund scales?

Make charges based on the number of operations executed per workflow run. As the investment count grows, each weekly run processes more records — and more records means more operations. The Ajackus team built two workflow variants: a full-population workflow that processes all investments comprehensively, and a defined-week workflow that limits processing to a specified number of recent weeks, reducing operation consumption for routine weekly runs. The client can select which variant to use based on their current operational requirements, giving them direct control over their Make subscription costs as the fund continues to grow.

How was the existing Airtable data preserved during the redesign?

The Ajackus team designed the new row-based weekly tracking table as an addition to the existing Airtable base rather than a replacement of it. All existing investment records, investor data, and historical entries were retained in their original tables and remain accessible. The transition was structured so that fund managers could continue operating during the redesign period, with the new table structure taking over weekly data capture from the point of implementation forward. No data was migrated, re-entered, or lost during the process.

How quickly can Ajackus redesign a broken Airtable or no-code automation system?

Ajackus has a dedicated Low-Code/No-Code practice with expertise in Airtable, Make, Zapier, and related platforms. For scoped redesigns like the Disrupt Social engagement — where the problem is architectural rather than requiring a full rebuild — Ajackus can typically assess, design, and deliver the fix within a focused short engagement. The Disrupt Social work was completed efficiently because the Ajackus team correctly diagnosed the root cause (data model architecture, not automation configuration) before writing a single workflow.

Can Ajackus build no-code solutions that remain within a client's existing platform?

Yes — and the Disrupt Social engagement is a specific example. Rather than recommending a migration to a more powerful tool, the Ajackus team identified the precise capability gap within Airtable (inter-row relationships) and bridged it with Make, keeping the client on their preferred platform while solving the structural problem. Ajackus’s approach to low-code engagements prioritises the minimum viable tooling change consistent with solving the client’s actual problem — not the most technically impressive solution.

What engagement model does Ajackus use for low-code and no-code projects?

Low-code and no-code engagements at Ajackus typically operate under the Team Augmentation or Managed Delivery model, depending on whether the client has existing in-house capacity. For scoped redesign or automation projects like Disrupt Social, Ajackus delivers under Managed Delivery — taking ownership of problem diagnosis, solution design, and implementation. For clients who want to maintain ongoing Airtable or Make development capability, Ajackus can provide augmented engineers who embed with the client’s operations team on a flexible basis.

We're Ajackus
We combine design, engineering, and speed to deliver beautifully crafted, scalable products.