v2.4 · Computed fields are live

Sales and marketing fields,
fixed automatically.

FieldSwap watches every Account, Contact, and Opportunity field in your CRM. When values drift, we refresh them — with a source you can audit on every write.

Get started · pay as you go See how it works

No card · self-serve

app.fieldswap.com / northwind / pipelines
Northwind

Pipelines

This week ▾+ New pipelineJL
Pipeline
Field
Rows
Status
ICP refresh — weekly
Account.Industry
12,431
Fresh · 2h
Headcount drift
Account.NumberOfEmployees
8,902
Stale · 14d
Contact title refresh
Contact.Title
22,188
Fresh · 6h
ICP score (computed)
Account.ICP_Score__c
4,310
Fresh · 1d
NorthwindContosoVandelayPied PiperHooliInitechWonkaSoylent
How it works

Four steps. No webhooks to babysit.

Connect once, pick the fields that matter, and let the pipelines run. One credit per written row — not per seat.

01 · Connect

Connect your CRM

Salesforce or HubSpot. Read-only by default; you grant write scope per field.

02 · Select

Pick fields to watch

Account.Industry, Contact.Title, Account.ICP_Score__c — anything FieldSwap can resolve.

03 · Map

Map your sources

Choose which source fills each field, with fallbacks if the first one misses.

04 · Run

Run on a cadence

Daily, weekly, or on record write. One credit per written row — not per seat.

Live · streaming

Watch the rows update. In real time. With receipts.

Every write is a row in the audit log: timestamp, source, before and after. Nothing changes in your CRM without a record of why.

  • Timestamp, source, and before/after on every write
  • CSV-exportable audit log
  • Field-level RBAC
  • 1,240,699 rows enriched, all time
The problem

If you've set up the same enrichment workflow five times, this is for you.

01

You're paying for five tools that should be one.

A line item for person data. Another for company data. Another for verification. Another for intent. Another to glue it together. Each renews. Each gets reviewed. Each makes you defend a stack you didn't pick.

02

Your CRM is half-empty.

Half your contacts are missing phone numbers. A third have job titles from 2022. Your team is on LinkedIn right now, filling gaps by hand because nothing wrote them in.

03

Setup takes a week. Maintenance takes forever.

Every new client means rebuilding the same workflows. New API keys. New field mappings. Then someone changes a property in the CRM and it all stops working.

The product

One platform. Many sources. Your CRM, automatically.

Configure once. Data flows automatically — on triggers and on schedule. Enrichment, owned-site intent, and refresh, in one place instead of five.

  • Enrichment that runs itself — a waterfall per field
  • Owned-site intent, scored straight to a CRM field
  • Triggers + scheduled refresh, no Zapier to babysit

Enrichment that runs itself.

Waterfall
Try primary person provider by email · job_title, linkedin_url, seniority$0.04 / hit
↓ if miss — secondary provider by domain + name · job_title, phone$0.02 / hit
↓ if miss — direct-dial provider mobile · phone_mobile$0.08 / hit
Write → CRM contact fieldsper hit, not per lookup
Enriched · 30d12,403 contacts
Intent

Know who's visiting before they fill out a form.

Drop our pixel on your owned sites — main domain, microsites, client portals. We resolve anonymous visits to companies and people with a co-op identity graph, and write intent scores straight to a CRM field.

  • Resolves anonymous visits to companies and people
  • Intent scores write to a CRM field — no new dashboard
  • Additive to your existing intent platform, or a replacement
  • Your sales team sees a number on the record they already live in
Triggers + Refresh

Set it once. Stay fresh forever.

Triggers handle new data: when intent ≥ 70 and page = /pricing, enrich and notify #sales-hot. Schedules handle old data: refresh every contact older than 90 days, in client-defined batches. Plain language. No Zapier.

  • Plain-language triggers — no Zapier
  • Scheduled refresh in client-defined batches
  • The waterfall runs the same on fresh and stale records
  • Nothing rots in your CRM. Nothing needs a person to remember.
Built for agencies, by an agency

If you run revenue for more than one company, you'll feel this difference.

Multi-client by default

Most tools assume you're one company with one workflow. We assume you're juggling five.

Per-client workspaces keep each client's data, pipelines, and intent network isolated. Credentials don't leak across accounts; audit logs scope to the client whose data you touched.

Reusable playbooks onboard a new client in 30 minutes by cloning a vertical template — PI law, B2B SaaS, multifamily, fintech. Start from a working pipeline, edit the parts that don't fit.

Know your COGS on every account — and defend your margin in QBRs.

Per-client workspaces
Isolated
data, pipelines, credentials
Reusable playbooks
30 min
onboard from a template
Per-client cost dashboard
To the cent
COGS by line item

Built for fractional operators and agencies.

Replace your stack. Keep your CRM.

How it compares
Enrichment Standalone enrichment platformOne vendor · lower per-hit
Intent data Third-party intent providerOwned signals · no third-party fees
Email verification Standalone verification toolBuilt-in · included
Reverse ETL Reverse ETL or stitched-together ZapsNative Salesforce + HubSpot
Setup per client A week of recipe-building30 min from a template
Cost transparency Aggregated credits, opaque markupOne credit per write
Three flat plansOne vendor
Pricing

Priced for operators, not enterprises.

$0.05 / credit

Pay as you go

No monthly fee. For trying FieldSwap on a real pipeline. Credits billed as used. 1 connected CRM.

$49 / mo

Starter

1,500 credits included. For a single pipeline and one CRM. Community Slack.

$199 / mo

Pro

10,000 credits included. Salesforce + HubSpot. Audit log + RBAC. Unlimited seats. One credit = one row written.

Under the hood

Built on the data infrastructure your team will inherit.

CRM native

Read + write to any Salesforce or HubSpot field. Bi-directional sync.

API access

REST + webhooks. Pipelines are versioned YAML.

Confidence scoring

Every value carries a source and a score. You set the floor.

Tenant isolation

Each workspace runs in its own database schema.

Audit log

Before/after on every write. Queryable, exportable.

Export anytime

Full audit log, CSV + Parquet, no lock-in.

FAQ

Questions we get on every call.

Clay is a pipeline tool — you build flows that ingest a list and write somewhere. FieldSwap is a per-client workspace that lives next to your CRM. You don't run a list; the CRM is the list. New contact, new visit, scheduled refresh — pipelines fire automatically. The agency primitives (workspaces, per-client cost, vertical templates) are the model, not a feature on top.

You point. We swap.

Connect your CRM. Pick fields. Done. Sales and marketing fields, fixed automatically — built for RevOps teams who don't want to babysit their CRM.

30 min average setup · $0 monthly minimum · 0 webhooks to babysit · or email hello@fieldswap.io