Run a lean CRM inside your forms.

Three businesses, one set of forms: contacts, bookings and follow-ups as entries that point at each other.

See the plugins See how it works

Contact #4192 Nadia Okafor

Everything filed against one record.

Summer gala 12 June · 180 guests

Booked

Deposit call Owed by Friday

Due

Venue notes 2 files attached

Saved

One reference the team can quote

Illustrative experience

Contacts as entries
Bookings linked to the contact
A reference number people can quote

The finished experience

Everything about a customer in one place your team will use.

Because the team already lives in the forms, the records stay current instead of going stale in another platform.

A good fit for
Small teams whose CRM is mostly empty.

1

Make the contact the record

Every contact gets a reference the team can search for and say out loud.

GP Unique ID
2

Link the rest to it

Booking and follow-up forms look the contact up instead of retyping it.

GP Populate Anything
3

Start the next follow-up with context

Select the contact in a follow-up form and populate the details already on file. Your team records the next action without retyping the contact.

GP Populate Anything

Inspired by a real build

Spotlight: Turning Gravity Forms into a Lean CRM October 2025 See how Tony Schwartz ditched his CRM software for an enchantingly easy to manage Gravity Forms solution featuring database forms and more. Read the spotlight

What you’ll need.

Start with Gravity Forms. Add the capabilities this solution needs, then make the experience your own.

GP Populate Anything

Looks the contact up on the way in, so a returning customer is recognised rather than re-entered.

Explore GP Populate Anything

GP Unique ID

Stamps every record with an id your team can quote back.

Explore GP Unique ID

Taking it further

Add these optional plugins when your project calls for more.

Optional

GP Entry Blocks

Adds a staff table of follow-up entries filtered by next-action date. Configure staff-only list/detail access and editing permissions separately.

Explore GP Entry Blocks

Optional

GC Notion

Optionally sends CRM entries one way into an existing, authorized Notion database. The Gravity Forms records and workflow remain the source of this recipe.

Explore GC Notion

Before you start

One form per record type, linked by the contact’s ID.
Timed nonresponse reminders and workflow stages additionally require Gravity Flow. They are outside the linked-record base recipe.

Works alongside

Gravity Flow Required to reproduce the spotlight’s timed nonresponse reminders and workflow-stage automation; separate from the base linked-record recipe.

Sold and supported by their makers, not by us.

Get this built.

A plan covers how many of our plugins you run at once, and on how many sites. Here is what this one needs.

Required

GP Populate AnythingPerks
GP Unique IDPerks

Optional

GP Entry BlocksPerks
GC NotionConnect

Gravity Perks Advanced $169 /year

2 perks need Advanced or above — on up to 3 sites.

Gravity Connect Basic $59 /year

Only if you add GC Notion.

See plans for this solution

Every plan renews at the same price, and you can upgrade any time for the difference.

Make it fit
your project.

Is this really a CRM?

For a small team, close enough: it holds the contact, the history and the next step, and it is where they already work.

What about automation?

The featured business uses Gravity Flow for workflow stages and timed reminders after two or three days without a response. Reproducing those automations requires Gravity Flow and its configured workflow. This base recipe links records and fills follow-up forms; ordinary notifications do not supply those timed reminders.

Can we give staff a follow-up dashboard?

Optionally add Entry Blocks to list follow-up entries by next-action date. Restrict the list and detail views to authorized staff and configure edit permissions. This is a separate view to build, not a Populate Anything feature.

Can the records also go to Notion?

If your team already works in Notion, GC Notion can send selected fields to an authorized database. Configure this as one-way delivery and decide which records to send; it does not replace the existing follow-up workflow.