How would you design an OmniScript that branches significantly based on an early answer — for example, personal versus business applications?

There are two viable patterns and the choice depends on how much the branches diverge.

1. Conditional views within one OmniScript work well when the branches share most of their Steps and differ in a handful of fields or one extra Step. Put a conditional view on the Steps and elements that differ, driven by the answer captured early on. The advantage is one script, one data JSON, one save routine.
2. Separate OmniScripts joined by a Navigate Action are better when the branches diverge heavily — different data, different save logic, different lengths. The entry script captures the branching answer and navigates to the appropriate specialised script, passing context.
3. Reusable OmniScripts cover the middle ground: extract the shared portion (address capture, identity verification) into a reusable script and embed it in both branches so it is maintained once.
4. The warning sign that you chose wrong: a single OmniScript where most elements carry a conditional view is a script that should have been split, and a set of near-identical scripts is a set that should have been merged.