← All work
Case study Acquired

Custom Tables for Act!: Build Your Own CRM Data

A visual table builder that let Act! users model their own data — no developer, no schema migration, no support ticket. Swiftpage acquired it and now ships it as a first-party feature of Act!, for both Windows and web.

Out of the box, Act! CRM knows about contacts, companies, groups and opportunities. Real businesses track a lot more than that: mortgages, insurance policies, service contracts, serial-numbered inventory. Without somewhere to put that data, people end up with fields called “Policy 1”, “Policy 2” and “Policy 3”, and a spreadsheet on the side for everything that doesn’t fit.

Custom Tables fixes that. It’s a visual table builder that lets Act! users model their own data with no developer, no schema migration and no support ticket. It worked well enough that it was acquired, and it now ships as a first-party feature of Act! on both Windows and the web.

What Custom Tables does

The idea is to give people spreadsheet-like flexibility while keeping the data where it belongs: inside the CRM, attached to the right records.

  • Unlimited tables, attached to real records. Each table shows up as a one-to-many tab under contacts, companies, groups or opportunities, so one client can have as many policies or contracts as they need.
  • Nested tables. Tables can live inside other tables. A support contract can expand to show every service incident logged against it.
  • Views that work like a spreadsheet. Search, filter and sort a list view for a single record or across the entire database, then drill into the detail view.
  • Calculated fields and lookups. Do the maths between fields to cut down on manual entry, and turn table lookups into contact or opportunity lookups that feed straight into Word and email merges.
  • Excel export. Export any list view to Excel with exactly the columns you want.

Where it shines

Mortgage brokers store every mortgage under the client and filter the whole book by maturity date, lender or amount, which makes renewal season a lot less scary. Insurance brokers do the same with policies, split by type. Wealth managers track assets, liabilities and accounts to work out a client’s net worth.

Support teams use nested contract and incident tables to report on service against each agreement, and the same structure works nicely for project tracking. Companies selling high-value products import inventory, assign serialized items to the buyer, and filter by warranty or tier for targeted follow-up offers. Pre-built templates for industries like mortgages, insurance, realty, tech support and even car sales mean most people don’t start from a blank page.

Designing for data that lives in someone else’s database

The trickiest constraint was that custom tables live in the customer’s own Act! database. That’s great for users (the tables sync and upgrade right along with everything else), but it means every schema decision is permanent. You can’t just run a migration on thousands of databases you’ll never see. So the table definitions had to be self-describing, forgiving of older versions, and boringly predictable.

Getting acquired turned out to be a strange kind of code review. The product had to survive somebody else’s architecture, release cadence and support team. That meant a lot of architectural changes, and I won’t pretend all of them were fun. But seeing it ship to thousands of users as part of Act! itself, and keep them happy for years, is one of the things I’m proudest of.

Under the hood

Custom Tables is built in C# on the Act! CRM SDK, storing its data in Microsoft SQL Server alongside the rest of the Act! database. DevExpress powers the desktop designer and grids, and ASP.NET handles the web side, so the same tables work whether you’re in Act! for Windows or Act! in the browser.

Visit the product pagefor Custom Tables for Act!

More case studies

Flagship

Act4Outlook

Two-way Act! and Outlook sync, now with AI

In production

Mailmerge for Act!

Personal email campaigns, sent from Act!