“I did like 57 different demos... and none of them work.”

The problem

Paradigm had already invested heavily in Airtable, but the system was starting to strain under real operational complexity.

Listings, deals, commissions, documents, trust accounting, and trade record sheets all had to work together. In practice, too much of it still depended on manual work, duplicate records, and awkward workarounds between Airtable, QuickBooks, Google Drive, and older real estate software.

Kevin had already tried the market.

“I did like 57 different demos, right? Like every single tool or system that's available and none of them work. That's why I went this Airtable route.”

The issue was not finding software. The issue was finding something flexible enough to support how the brokerage actually operated.

The team needed a system that could handle:

• complex commercial real estate deal structures
• commission splits across multiple agents and roles
• trust and deposit handling
• Trade Record Sheet generation
• QuickBooks accuracy to the penny
• document and compliance workflows that were not pure chaos

As the brokerage grew, Kevin was clear about the real constraint.

“I need to get this to a spot where I can do this job for way more agents than we have now. Right now, if we continue to grow our team, we can't do this.”

The approach

We did not treat this as a simple CRM build.

The first priority was getting the backend right. Properties, units, listings, deals, commissions, roles, transactions, and accounting logic all needed a more robust structure before any front-end decisions could be trusted.

That is the same principle behind Build vs Rent when off-the-shelf software doesn’t fit how you work. The problem was not just interface polish. It was underlying data and process design.

The architecture evolved into a cleaner split:

• Attio for front-office CRM and pipeline work
• Airtable for back-office transactions, compliance, and deal operations
• n8n for automation and QuickBooks workflows
• QuickBooks Online as the financial source of truth
• Google Sheets and Drive for templated documents and file handling

That gave Paradigm a setup where the front end could change over time without breaking the core business logic.

What we built

Database restructure for real estate operations

The original schema mixed together concepts that needed to stay separate.

We reworked the base around a clearer structure, including distinct records for properties, units, listings, deals, and role-based relationships. This reduced duplication and made it possible to support multiple offers, multiple commission participants, and more accurate downstream calculations.

That foundation mattered because duplication in this kind of system is not just messy. It creates accounting and compliance risk.

Commission automation tied to actual deal logic

Commission splits were not simple flat percentages.

The system had to support internal agents, co-op agents, referrals, co-list situations, owner exceptions, and lease-specific overrides. Instead of forcing everything into one brittle formula, the build combined automated calculations with manual override fields where nuance mattered.

This gave Paradigm a system that could handle real-world exceptions without collapsing every time a deal got slightly unusual.

QuickBooks integration for cleaner back-office work

A major part of the build was pushing deal and commission data from Airtable into QuickBooks in a way that stayed usable and auditable.

The workflows covered:

• invoice creation
• bill creation
• journal entries where required
• project and customer mapping
• deposit handling
• syncing returned QuickBooks values back into Airtable

QuickBooks remained the financial source of truth. Airtable handled operational logic and record creation, but the final numbers had to match QuickBooks exactly.

That is also why we leaned toward one-way operational syncs wherever possible. You don’t need more tools, you need better systems applies especially hard when accounting data is involved.

Trade Record Sheet generation

Trade Record Sheets were one of the biggest reasons for the project.

The goal was to replace expensive, rigid legacy tooling with an in-house process that still met compliance needs. We built templated generation workflows using Airtable, automation triggers, and Google Sheets so the data could flow into a structured document rather than being assembled manually each time.

This part of the build needed to account for:

• money in and money out
• deposit paths
• agent payouts
• AR values
• transaction grouping by Trade Record ID
• formatting suitable for audit and operational review

Document automation and compliance groundwork

Document handling had become another major bottleneck. File naming, signatures, and compliance requirements were inconsistent across agents and transactions.

A document classification and extraction proof of concept was built using AI, with production architecture moving toward n8n-based processing and staging. The idea was not to throw AI at everything. It was to use it where it reduced repetitive manual review without creating more cleanup work later.

That matches the broader approach in a practical approach to no-code for your business. The goal is not maximum cleverness. The goal is a workflow people can actually rely on.

The outcome

Paradigm did not end up with a perfect all-in-one real estate operating system overnight.

What they did get was more valuable: a back-office architecture that was substantially closer to being scalable, auditable, and owned in-house.

By the end of the engagement, the project had delivered:

• a stronger Airtable schema for deals, listings, roles, and transactions
• commission automation that could handle real brokerage scenarios
• major QuickBooks workflows for invoices, bills, journal entries, and syncing
• Trade Record Sheet generation tied to live transaction data
• a clearer split between front-office CRM and back-office operations
• a path away from expensive legacy tools and duplicate manual entry

The project also surfaced the hard truth that some processes in commercial real estate are more complicated than they first appear. That was useful in itself. It allowed the team to pause full cutover, clean up fragile areas, and move toward a more controlled go-live instead of forcing a rushed launch.

“The payoff, the value to bring all of this in-house and to automate it... to be able to remove the pain points... I'm still in a good category here.”

That is probably the best summary of the build. It was not about making things look more modern. It was about reducing pain, increasing control, and building an operational backbone Paradigm could actually grow on.

Start with a blueprint

If your operations depend on a mix of spreadsheets, accounting tools, folders, and software that almost works, the first step is usually not another subscription. It is mapping the system properly.

Book a blueprint session