What makes the record unique.
The handle and the legal anchor. Survives renames, dedups on import, reconciles against accounting.
Account name · External ID
[ 01 ] Free reference card
PDF · A4 + Letter
The 14 fields every
SMB client record needs.
A vendor-neutral, one-page printable. Fourteen fields, seven groups, with the type and the report each one unlocks. Built for the operator whose sheet has eighty columns and serves nobody.
syncek.com / resources / 14-fields.pdf
PDF
Reference · v1 · 2026
14 fields. 7 groups. One printable page.
[ 01 ]Identifiers2 fields
[ 02 ]Contact2 fields
[ 03 ]Segmentation2 fields
[ 04 ]Value2 fields
[ 05 ]Lifecycle2 fields
[ 06 ]Ownership2 fields
[ 07 ]Audit2 fields
Field · Type · Why it matters
Sheet · 1 of 1
The recurring quote
“My sheet has 80 columns and I don't know which ones to keep.”
Most CRMs ship with eighty fields on the Company object. Most spreadsheets grow to eighty columns. Both happen for the same reason — nobody decided what to drop. A field that's blank on 70% of records can't anchor a report. It's noise.
The 14 below are the decision. Used every week, they beat eighty columns nobody fills in.
[ 02 ] The structure
Seven groups cover the working record.
Every workable client record sits in one of seven groups. Two fields each. The grouping is vendor-neutral — it works whether you run a CRM, a flexible database, or a spreadsheet that hasn't broken yet. New field? Name its group first.
How the team reaches the account.
One human you talk to, one canonical pointer at the public surface. Stored as relations, not free-text.
Primary contact · Website
Which bucket the account belongs to.
Stored as text, you get 200 strings. Stored as a select, you get a chart axis and a filter that works.
Industry · Size band
The financial weight, in numbers reports can sum.
Annualized expected value plus what's actually in motion this week. Currency-typed, with a column footer.
Account value · Open pipeline
Where the account stands today.
Status as a tight select; last touch as a date. Powers the “stale > 30 days” filter that drives weekly outreach.
Status · Last touch
Who is responsible internally.
One name attached. Powers personal queues, escalation rules, and the “what's mine?” view that keeps reps honest.
Account owner · Source
When and by whom — automatic.
Auto-only. Cohort analysis, list hygiene, and the cheapest accountability signal you have.
Created date · Last modified by
Need a fifteenth?
Name its group first. A real-estate CRM adds property type to segmentation; an agency adds retainer model to value.
Group placement keeps the record coherent.
[ 03 ] The 14, group by group
Pick the type before you pick the name.
A field's type decides what reports it can produce. Currency gives you a column footer. Single-select gives you a chart. Free text gives you a column. Same name, different type, different decision surface.
| Field | Type | Why it matters |
|---|---|---|
| [ 01 ] Identifiers · 2 fields | ||
| Account name | text · unique | The human handle. Every other field hangs off it. One canonical spelling — inconsistent names are the leading cause of duplicate records. |
| External ID | text · unique | Tax ID, VAT, EIN — the only field guaranteed to be globally unique and stable. Lets you dedup on import and survive a renamed company. |
| [ 02 ] Contact · 2 fields | ||
| Primary contact | relation | The one human you talk to. Stored as a relation, a person's email change updates everywhere automatically. |
| Website | URL | A single canonical pointer at the account's public surface. The root domain, not a deep link. |
| [ 03 ] Segmentation · 2 fields | ||
| Industry | single-select | As text, 200 unique strings. As a select, a chart axis and a filter. Same field, different type, different decision surface. |
| Size band | single-select | Headcount as a number is noise. As a band — 1–10, 11–50, 51–200, 200+ — it's a filter, a chart axis, and a pricing-tier proxy. |
| [ 04 ] Value · 2 fields | ||
| Account value | currency | A currency type gives you a sum, an average, and a column footer. Annualized expected value, not lifetime. |
| Open pipeline | currency · rollup | Computed via relation rollup from open deals. Tells you what's in motion this week — the answer to which accounts deserve a touch? |
| [ 05 ] Lifecycle · 2 fields | ||
| Status | single-select | Lead, Active, Paused, Churned covers ~95% of SMB books. Each new option doubles the explanation cost for every new hire. |
| Last touch | date | Without it, the answer to when did we last talk? is a guess. With it, the answer is a sort. |
| [ 06 ] Ownership · 2 fields | ||
| Account owner | user reference | Every record needs a name attached. “The team owns it” means nobody owns it. One owner, even if two people genuinely co-work on the account. |
| Source | single-select | Referral, Inbound, Outbound, Event, Partner. Captured once, at creation. Backfilled source is folklore, not data. |
| [ 07 ] Audit · 2 fields | ||
| Created date | date · auto | Cohort analysis, win-rate-by-vintage, list hygiene — none of it works without it. Auto-only. If a human can edit it, it's no longer a fact. |
| Last modified by | user ref · auto | The cheapest accountability signal you have. When a record changes and a report breaks, “who touched it last” closes the loop in seconds. |
[ 04 ] Download · free PDF
Get the printable card.
One page, A4 and Letter. Three columns: field name, type, why it matters. Print it, tape it next to the monitor, hand it to the next hire on day one.
Download the PDFPDF
The card is on its way.
Check your inbox in a minute. If it doesn't arrive, look in spam or write to hello@syncek.com.
[ 05 ] The posture
A field set, not a configuration project.
Field design is a half-hour decision, not a quarter-long project. Ship the 14, run them for a month, then add — never the other way around.
-
[ 01 ]
Define the 14.
Use the set above as the starting template. Adjust the segmentation buckets and the lifecycle options to match your book. Leave the structure intact.
-
[ 02 ]
Migrate the existing book.
Map your current columns onto the 14 fields. Anything that doesn't map gets archived in a separate file — not deleted, just out of the way.
-
[ 03 ]
Run the set for a month.
No new fields. No “let's also track…” If a question can't be answered, write it down.
-
[ 04 ]
Add the fifteenth only when you reach for it twice.
One moment of “I wish I had this” is folklore. Two moments is a signal. The discipline of waiting is what keeps the record at fourteen instead of eighty.
[ 06 ] FAQ
The questions we get most.
Short answers. The long-form reference covers the rest.
What is the 14-field reference card?
A single-page printable PDF that lists the 14 fields a small-business CRM client record needs, grouped into 7 buckets: identifiers, contact, segmentation, value, lifecycle, ownership, audit. Each field carries its type and the report it unlocks.
It's vendor-neutral by design — the same set holds whether your client book lives in a CRM, a flexible database, or a spreadsheet that hasn't broken yet.
Who is the card for?
Operators at 1–50 person teams setting up or rebuilding a client database. Founders, ops leads, agency directors, freelancers — anyone who ended up running the company's client book because somebody had to.
If you have a CRM admin and a RevOps team, this card is below your floor. It's for the operator who already wears five hats and needs a reference, not a configuration project.
Is this tied to Syncek?
No. The 14-field set is vendor-neutral. The same fields apply whether you run Syncek, HubSpot, Pipedrive, Notion, Airtable, or a spreadsheet. We wrote it because we kept being asked the same question and there was no good reference to point at.
If you're curious about Syncek after reading the card, the long-form article and the product live one click away. If you're not, the card still works.
What format is the download?
A single printable PDF. Both A4 and US Letter sized so the same file works on either side of the Atlantic. Three columns — Field name · Type · Why it matters — with group headers for the 7 groups.
The English and Spanish versions are separate files. Tick whichever boxes you want when you submit the form.
Will I be added to a sales sequence?
No. Email is used to send the PDF and the occasional Syncek update — that's it. No phone, no company size, no drip nurture, no “just checking in” follow-ups. Unsubscribe is one click.
Honest pricing. No per-seat surprises. Same posture on the email list.
How often should I audit my CRM fields?
Every six months for the field set itself, every quarter for the option lists inside select fields. Fields accumulate by inertia — someone asks for a one-off column, it gets added, nobody removes it.
The audit asks three questions per field: completion rate, report usage, removal cost. If a field can't pass two of three, retire it.
What if my industry needs a field that isn't in the 14?
Add it — but name its group first. A real-estate CRM might add property type to segmentation. An agency might add retainer model to value. A recruiter might add seniority to segmentation.
If a new field doesn't fit any of the seven groups, it usually belongs on a different object — a deal, a person, a contract — pretending to be a column.
Where can I read the long-form version?
The full article — field by field, type by type, with examples and 12 deeper FAQs — is at syncek.com/blog/crm-field-design-for-smbs. The card is the printable. The article is the reference.
[ 07 ] One last thing
A record is a tool, not a museum.
Fourteen fields, used every week, beat eighty columns nobody fills in. Print the card, run it for a month, see what your weekly review actually needs.