Platform7 min read

Data Modeling & Structure

The Complete Guide to Custom Fields: Modeling Real-World Business Data

Every business captures details that make it unique. Custom fields provide typed, validated data storage that powers forms, templates, filters, and workflows.

SHPI Architecture & Data TeamPublished in Platform Architecture
Executive Summary

Core Takeaways & Operational Summary

Storing critical trade details in unstructured "Notes" fields leads to dropped balls and missed deliverables.

Typed custom fields (currency, date, dropdown, boolean) enforce clean data entry across your team.

Custom fields act as dynamic merge tags in proposals, contracts, and work order templates.

Field validation ensures mandatory project specifications are completed before deals advance.

The Problem

The Cost of Unstructured Data in Business Operations

When software cannot adapt to the specific metrics of your trade, critical project parameters get scattered across email threads, paper notes, and WhatsApp messages.

01

The "Notes Field" Trap

Sales reps paste client requirements into free-text boxes, making it impossible to filter, sort, or automate tasks based on those specifications.

02

Missing Delivery Deadlines

Without a dedicated date field with automated alerts, promised client completion dates get buried in conversation logs.

03

Inconsistent Data Entry

Different team members write "L-size", "Large", "LG", and "100cm", corrupting reporting filters and inventory planning.

04

Gated Customization in Legacy CRMs

Traditional CRMs cap custom fields at 10 on starter plans, demanding expensive enterprise upgrades for basic customization.

The Architecture

SHPI Custom Fields: Typed, Validated, Everywhere

Add tailored fields across Contacts, Accounts, Deals, Invoices, and Custom Modules with native support in forms and document templates.

Signage & Large Format Print

Field Application
Operational Context:

Fields: Substrate Type (Select: Acrylic / Foam / DiBond), Width (Number), Height (Number), Finishing (Multi-select: Hemmed / Eyelets / Laminated).

Measured Result:Exact measurements automatically feed into machine cut files.

Vehicle Wrap & Fleet Branding

Field Application
Operational Context:

Fields: Vehicle Make/Model (Text), VIN (Text), Installation Bay (Select), Artwork Approval Date (Date).

Measured Result:Job scheduling aligns with physical bay availability.

Legal & Compliance Advisory

Field Application
Operational Context:

Fields: Jurisdiction (Select), License Renewal Date (Date), Retainer Type (Select), Certified Lead Counsel (User).

Measured Result:Automated warnings 60 days before regulatory renewals.
Workflow

How Custom Fields Flow Across the Platform

How business data flows continuously across stages without manual handoff friction.

01
DefinitionStage 01

Create Typed Property

Choose field type, label, placeholder text, and validation rules (e.g. required).

Handoff:Appears in record drawers
02
IntakeStage 02

Capture via Web Form

Map the field to Form Studio for direct submission by customers on your website.

Handoff:Auto-populates CRM record
03
EnforcementStage 03

Stage Transition Gate

Ensure mandatory fields are completed before a deal moves to Won.

Handoff:Guarantees complete job data
04
OutputStage 04

Dynamic Template Merge

Template Studio inserts custom field values directly into customer PDF contracts.

Handoff:Zero manual reformatting
System Specifications

Supported Field Types & Features

Detailed operational capabilities and architectural maturity for this capability set.

Capability ModuleMaturityOperational Impact
Rich Typed Options
AvailableText, Textarea, Number, Currency, Date, Select, Multi-select, Checkbox, and URL.
Required & Default Values
AvailableEnforce completion rules and set sensible initial states.
Relational Record Pointers
AvailableLink records across modules (e.g. link a Job to a Customer and Equipment).
Filter & Search Integration
AvailableFilter pipeline boards and table views using any custom field criteria.
Template Merge Tags
AvailableUse any custom field variable directly in PDF and web document layouts.
Calculated / Formula Fields
PlannedNative computed expressions (e.g. Width × Height × Unit Cost).
Transparent Analysis

SHPI Custom Fields vs. HubSpot Properties vs. Spreadsheets

Examining data integrity, ease of customization, and cost constraints.

Operational Dimension
SHPI Business OSUnified Foundation
HubSpot Custom PropertiesSpreadsheets / Manual
Plan Restrictions
Unlimited custom fields across all records on standard plans
Strict caps; requires $500+/mo Professional tier for advanced fieldsUnlimited columns, but no type checking
Document Integration
Native merge tags in Template Studio for instant PDF rendering
Requires third-party integrations (PandaDoc, WebMerge)Manual copy and paste into Word templates
Data Validation
Strict typing (dates, currencies, numbers, dropdown options)
Strong validation, but complex property group managementNo validation; anyone can enter invalid dates or text
Relational Linking
Native cross-module linking between default and custom entities
Limited to standard contact-company-deal model on lower tiersVLOOKUP formulas that frequently break
Best Suited For
Growing operational teams needing tailored data without paywalls
Corporate marketing teams managing thousands of lead attributesQuick informal note-taking
Specialist Fit

Where HubSpot Custom Properties may be the better choice

HubSpot offers extensive calculated rollups, enterprise field audits, and deep integration with Salesforce data sync architectures.

SHPI Advantage

Where SHPI Business OS is the better choice

SHPI provides unlimited custom fields without enterprise pricing gates, integrates natively with PDF generation, and keeps operations lightning-fast.

Execution Plan

Best Practices for Custom Fields

A practical sequence to adopt this capability without operational disruption.

01
Step 01

Prioritize Dropdowns Over Text

Use Select fields rather than free text whenever there are standardized choices to ensure clean filtering.

02
Step 02

Group Related Fields Logically

Organize properties into clear sections (e.g. "Specifications", "Shipping", "Billing Details").

03
Step 03

Mark Only Critical Fields Required

Do not overwhelm staff with 15 mandatory fields; require only what is needed to execute the job.

04
Step 04

Audit Field Usage Quarterly

Archive fields that team members no longer use to maintain a clutter-free interface.

Common Inquiries

Answers to Common Questions

Straightforward answers to the most common questions about adopting this in your operations.

Can I add custom fields to invoices as well as contacts?

Yes. Custom fields can be added to Contacts, Accounts, Deals, Invoices, Catalogue items, and Custom Modules.

What happens to existing records when I add a new custom field?

Existing records seamlessly adopt the new schema. If you set a default value, it can be applied to existing entries.

Can custom fields be displayed on public web forms?

Yes. Form Studio allows you to drag custom fields directly onto public-facing client intake and enquiry forms.

Can we filter deals by custom field values?

Yes. You can filter visual pipeline stages and table views using any custom attribute, such as project type or target completion date.

Start simply

Build the operating system
your business actually needs.

Start with customers, deals, and invoices. Add forms, workflows, documents, dashboards, and custom modules as your business grows.

For small businesses that have outgrown spreadsheets without wanting heavyweight enterprise software.