Quality Plus Contracting - New Business - September 2026

Collects the entity list only. No licence numbers yet.

• The Repeater is the right native component here. It supports Text, Date and Currency children, and allows up to 30 instances at run time, which covers Caroline's 19-entity worst case.
• Go_Live_Date__c is optional. Caroline confirmed these dates are usually unknown at booking.
• Entity-level Onboarding_Fee__c is optional and defaults to blank, because the full fee normally sits on the parent.
• The paste box is a Long Text Area plus an Apex invocable that splits on newlines. A Repeater cannot be pre-populated from a collection natively, so the paste route needs that Apex step.
• The entity name is a Required Text child. That is what blocks Next on a blank row and prints "Complete this field." It matters because Name is the only field Salesforce genuinely requires on Account, so a blank row would fail the insert and roll back the whole batch.

Why this screen exists. 32% of the 610 sub-entity opportunities already in the org sit on an Account that existed before the opportunity, and 185 of those were already customers. Creating blindly would make the Account dupe problem worse.

• The real hazard is not duplicates. Sales_Rep_Opportunity_Trigger_Account_Contact_owner_Update fires on ISNEW() of an Opportunity and writes Account.OwnerId and every related Contact.OwnerId from the opportunity owner. Linking a sub-entity opp to an existing Account silently transfers that Account away from its current AE. That is why the owner column is on this screen.
• Matching keys. There is no EIN or tax-ID field on Account, even though the breakout is EIN-level in practice. HS_Normalized_Domain__c is Text(255), External Id, Unique Case Insensitive, and is the only reliable key. Name matching needs human confirmation, and Website cannot be trusted on its own because 153 Accounts hold a free email domain there.
• Why a Data Table and not a Repeater. A Repeater cannot contain a lookup or Record Picker, so per-row account search is not possible inside one. A multi-select Data Table fed by an Apex search is native, scales to 19 rows, and returns the selected rows as a collection.
• Linking to an existing Account is normal, not an exception. A second sub-entity opportunity on one Account is also legitimate: S+B James Construction and S+B James California are two entities on one Account two months apart.

Be honest about this screen. Two behaviours drawn here are not native Flow:

• Live totals as you type. A Repeater's child components cannot react to other children of the same Repeater. Natively, the variance can only recalculate when the screen is submitted, so the pattern would be a "Check totals" button that loops back to this same screen.
• The Apply remainder and Balance buttons. Flow screens have no arbitrary mid-screen action buttons. These need either the same loop-back pattern or a custom LWC.
• Recommendation: build this one screen as a custom LWC and leave every other screen native. The arithmetic is the whole reason this wizard exists, so live feedback is worth the one component. An inline-editable Data Table (Spring '26) gets close, but still cannot show a running remainder as she types.

The maths, which is native either way:

• Total TM per row is MAX() of that row's SKU counts, not the sum, because that is how Total_Team_Members__c is defined.
• Entity ACV = sum(licences × PEPM) × 12, the same maths Gross_Miter_ACV_Update runs after insert. The wizard writes the licence counts and PEPM rates only. It must not write Gross_Miter_ACV__c, or the flow overwrites it.

What gets created, and what already blocks it. verified live, not from the repo

• One insert, never two. Records must be created straight at StageName = "Booked" in a single Create Records element. A create-at-Qualifying followed by an update to Booked trips Opportunity_must_hit_all_stages, which only Cameron and Dan are exempt from.
• Creating at Booked is allowed: Stage_Must_Start_in_Qualifying carves out Sub Entity, and Opportunity_must_hit_all_stages is gated on ISCHANGED(StageName), false on insert.
• Fill_in_Contracted_Entity_for_Sub_Entity needs Contracted_Entity__c in the same insert as Entity_Type__c. No bypass, and it re-fires on every later save.
• Booked_Details is the real blocker, and it is Dan's later-edit trap. No ISCHANGED guard, so it re-fires on every save of a booked opportunity forever. It needs both Win_Story__c and Miter_Use_Case__c, and Bypass_Validation__c does nothing against it. The two flows that used to fill Miter_Use_Case__c are Obsolete.
• Require_Complex_Tax_Fields_When_Booked needs Operating_in_Complex_Tax_States__c and Number_of_Operating_States__c. It does honour Bypass_Validation__c, set inside the Create element.
• Two ways to solve both. Add NOT(ISPICKVAL(Entity_Type__c, "Sub Entity")) to each rule, or run the creation as sfdc-access. Both rules exempt that user on $User.Id and on CreatedById, so its records stay exempt permanently, including later edits.
• Record type. Stay on Standard. Sub_Entity has zero records and is not available to the admin profile, so setting it would error.
• Volume. 95 active Opportunity-triggered flows fire once per record, 47 of them Rattle.
• Rocketlane fans out. RLSTAGEWH6463OPPORTUNITY publishes a platform event for every row on insert with no filter. Confirm with the Rocketlane admin whether their project rule filters on Entity_Type__c before this ships.
• Row locks. Siblings share one parent. Sum_up_Miter_ACV_Fields runs per sibling and each run writes the parent and every other sibling. UNABLE_TO_LOCK_ROW is expected, not remote.
• Close date is not yours to set. Update_Close_Date_Automatically overwrites CloseDate with today for a Booked record.
• Caution: the local repo holds 26 rules, 20 active. Live holds 38, 30 active, and four shared rules differ live. Build against the org.

Not built in this POC. Re-running the wizard on a deal already broken out, and adding a single entity after booking. Both are real needs; both are phase 2.