CRM: Require chosen properties before a deal can enter a stage
HubSpot pipelines let admins mark properties as required per stage (conditional stage properties), so a deal cannot move to 'Proposal' without amount and close date; this sits in Sales Hub Professional (https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines). Our crm_stages only store name, probability, position and won/lost flags (lib/schema/baseline.ts:119), and the move endpoint accepts any drag (app/api/crm/deals/[id]/move). Forecasts and reports are only as good as amounts and close dates, and small teams have no ops person cleaning data. Offering this for free is a cheap differentiator. First scope: required_fields JSON on crm_stages edited in PipelinesEditor, a modal on board drag or stage change that asks for missing values, enforced server-side in the move route and the v1 API. Priority: medium. Effort: M. Compared with HubSpot.
Comentários 0
Ainda sem comentários.
Entre para comentar