Browse by hub
Name the hub before you name the app.
Most of these builds need two hubs and a clear tier. A fourth hub usually means the scope has grown.
Capture and nurture
Forms, campaigns, and the source fields sales will audit. Professional is the usual floor once workflows branch.
Pipeline and quotes
Deals, playbooks, sequences, and native quotes. Seat-based forecasting stays here.
Tickets and knowledge
Pipelines for support, SLAs, and the customer portal you already pay for.
Pages partners can open
Membership-gated pages are how several portal recipes avoid a custom app.
The record everyone shares
Properties, datasets, and the hygiene step before any automation is trusted.
Custom objects
Custom objects are on higher tiers. Each recipe that needs one lists that tier at the top.
Two hubs, then stop and check.
- 01
Name the work
Capture, pipeline, tickets, or the shared record. The hub follows the work.
- 02
Name the tier
Custom objects and branched workflows sit on higher tiers. The recipe says which one.
- 03
A fourth hub
Usually means the scope grew. Write the new job down before you buy the seat.