A contact record that survives contact with reality
People change roles, companies merge, and the same person arrives as a lead three times in a quarter. Contact data decays whether or not anyone is watching. This part of Golden Porch exists to slow that decay down.
People and companies, linked
A contact belongs to a company, and both keep their own history. When someone moves on, the relationship history stays with the company and follows the person too.
Duplicates caught early
Matching runs when a record is created, not as a monthly clean-up. Clear duplicates merge automatically; ambiguous ones go to a review queue with both versions shown.
History without filing
Calls, emails and meetings attach themselves to the right record. Nobody has to remember to log an activity for the timeline to be complete.
Fields you define, validated on the way in
Every team ends up needing fields the standard set does not cover — contract renewal dates, account tiers, whatever your business actually runs on. Custom fields carry types and validation rules, so a date field holds dates and a picklist holds one of the values you allowed.
Required-field rules can apply per stage rather than globally, which keeps early-stage records quick to create without letting incomplete data reach the point where it matters.
Lead capture and routing
Leads arrive from forms, imports and the API. However they get in, they land in the same queue and follow the same routing rules — by territory, by round-robin, by account owner, or by whatever combination your team has settled on.
Routing is visible rather than magic. Each lead shows which rule assigned it and why, which turns "why did I get this one" from an argument into a two-second answer.
Segments and lists
Saved segments update themselves. Define the conditions once — industry, region, last activity, open deal value — and the list stays accurate without anyone rebuilding it. Segments can drive automation rules and reports as well as being read directly.
On importing: most teams arrive carrying years of accumulated mess. The importer maps fields, previews the result, and shows what it thinks is a duplicate before anything is written. It is worth spending an afternoon on this rather than importing everything and cleaning up later.
Getting data out
Any view can be exported to CSV, and the API exposes the same records programmatically. There is no export fee and no tier where export is disabled. A CRM you cannot leave is a CRM you should not enter.
Next: how deals move
Contacts are where it starts. The pipeline is where it either progresses or quietly stops.
Pipeline & deals