Vertiqa Help← Back to app

Pipelines

Configure pipelines, install template packs, build custom packs, and generate opportunity pipelines with AI.

The pipelines settings page is where you manage how work moves through Vertiqa. You can still edit individual pipelines, but opportunity pipelines now also support Pipeline Packs: curated templates, custom builder drafts, and AI-generated drafts that publish through the same review lifecycle.

Layout

  • Entity-type tabs — leads, opportunities, and any vertical-specific pipelines.
  • Opportunity actions — start from scratch, generate with AI, or browse template packs.
  • Drafts — saved Pipeline Pack drafts you can resume or discard.
  • Pipeline list — each active pipeline for the selected entity type.
  • Preview / config — stages, probabilities, required fields, provenance, and available template upgrades for the selected pipeline.

Common tasks

  1. Start from scratch for a custom opportunity Pipeline Pack draft.
  2. Generate with AI when you want Vertiqa to create a draft from a plain-language business description.
  3. Browse Templates to install a curated pack or customize it first.
  4. Edit a pipeline — update stages, probability, required fields, and transition rules.
  5. Publish a draft only after review. Drafts must be saved before they can publish.

Pipeline Packs

Pipeline Packs bundle an opportunity pipeline with its stage structure, custom fields, vocabulary, navigation labels, and allowed workflow definitions. Publishing a pack creates or updates the live pipeline through the Kernel lifecycle; it does not create a separate data model.

The three setup paths are:

  • Template install — install a curated pack from the gallery.
  • Customize first — open a template as a draft, edit it, then publish.
  • Generate with AI — create a governed draft from a prompt, review it in the builder, and publish only after approval.

Tips

  • Keep pipelines short. Five to seven stages is usually enough; more fragments the data and confuses reporting.
  • Use packs for durable operating models, not one-off experiments.
  • Required fields are a good way to enforce hygiene. They should capture information the team genuinely needs before a deal advances.
  • Don't change probabilities frequently. Forecasts are only as trustworthy as the numbers they are built on.

Related

Last reviewed