Indigo Trigger

— Colophon

How this site answers.

We tell clients that a revenue system should be inspectable: you should be able to see what it did and why. This page applies the same standard to our site.

The type

Headlines and body are set in Newsreader. Interface labels, navigation, and data are IBM Plex Mono. Libre Franklin is the supporting sans. Three faces, each with one job.

The press

Public-site structure and shared copy are reviewed in source alongside the implementation. Editorial stories, events, partner records, media, and site alerts remain managed in Payload.

What the assistant will and will not do

This is a working tool, not a general-purpose chatbot. Its limits are explained here so you know what to expect.

  1. 01

    Every answer stays inside one named revenue workflow. The scope is visible on screen while you read it.

  2. 02

    It uses approved, published Indigo Trigger sources and cites the matching page. It does not browse the open web.

  3. 03

    It does not quote prices, promise timelines, or invent a number. Those come from a person, in a conversation.

  4. 04

    When the published material cannot support an answer, it says so and directs you to the team.

The shop

Designed and built for Indigo Trigger LLC of Portsmouth, New Hampshire, by Built Revenue. Corrections and better ideas to info@indigotrigger.com.

Built byBuilt Revenue