A ready CRM holds the account, the conversation and the opportunity. It does not hold your operational step: the quote math, the technician job, the dealer split. That step stays in a sheet beside the CRM. A custom screen does not rebuild the CRM. It makes the step one record and speaks to the CRM through a field you name.
Draw the boundary in the brief
The account remains mastered in the CRM. The side screen holds the calculation, the job or the allocation. HED Creative asks for one sentence: which field was missing when you tried to run this step inside the CRM. Without that sentence the screen becomes a second CRM. Discovery runs from Berlin or Ankara.
What writes back
Release one does not move every column both ways. It writes back one status or one amount. A full sync is a later decision. The brief names which CRM you run and how the identity is read.
The screen is not a reskin of the pipeline. Sales stays in the CRM. Operations moves on the side record. Even when one person does both, the two jobs do not swell inside one form.
Who signs in
The role that opens the CRM and the role that opens the side screen are written separately. In many firms sales uses the first and operations the second. A shared login erases which system is master.
Where this code sits
The repository of the side screen is yours. The CRM licence stays where it is. The screen is not a customization lost inside the vendor, noted only in one person browser. The right to change it is in the handover.
Write the boundary on web app development. The morning miss can read the same source as an exception panel for management. The team that keeps both systems after launch is a software partner.