Discovery, Build, Run.

A fixed-price scope, a fixed-price build, and a monthly run-rate where the engineer who built it is the same person responding to alerts.

No phased proposals that balloon. No procurement gauntlet. No "implementation partner" handing you off to a junior team. Three named phases, one team, end to end.

The three phases

Discovery

Fixed-price. We document your goals, sources, audiences, and the definitions that anchor them. The output is a written engagement document — the traveling definition every later answer references back to.

Build

Fixed-price. Your sources sync into your private repository. Goals get their canonical queries. Stakeholders go on the digest list. The repository goes live in your environment.

Run

Monthly run-rate. The team that built it is the team that answers your alerts. New sources, new goals, new questions — included in the rate up to a stated cadence.

Discovery — naming the problem

A Profonti engagement starts with a conversation, not a checklist. We listen for the questions that have been answered different ways for different audiences, and we write down the version that your leadership wants to be canonical.

The Discovery output is a single document — your engagement document — that names:

Goals. The questions you actually want answered. Phrased as business outcomes, not table joins.
Audiences. Who's asking (CEO, CFO, COO, field operator, board) and what answer-shape they need (digest, dashboard, alert, deck).
Sources. The systems where the answers live today — even if the answer today is half-spreadsheet, half-tribal-knowledge.
Definitions. The terms that anchor everything else: "active customer", "completed engagement", "qualified pipeline". Whose definition wins, and what its boundary cases are.

Discovery is fixed-price because the scope is well-defined. You're buying a written document, not consultant time.

Build — landing the repository

Build is where the repository goes live in your environment.

Cluster bring-up. Your private Profonti instance is provisioned on your AWS / Azure / GCP account — or your colocation rack, if you have one. It is yours from day one; the perpetual license attaches to your copy of the code.
Source connectors. Each source from Discovery gets a connector. Ingest runs incremental + idempotent; the first pull catches up, subsequent pulls track watermarks. We document how to add new sources later.
Canonical queries. Each goal from Discovery gets one or more named queries. They're written, reviewed, and committed alongside the engagement document. The questions can evolve; the queries evolve with them.
Audience wiring. Digest lists, alert rules, channel destinations (email, Slack, Teams, SMS). Every recipient is named in the engagement document.

Build is fixed-price because Discovery defined the boundaries. New scope means a new Build, not a change order.

Run — the engineer-on-call stays

Run is the difference between a project and a system.

Most consulting engagements end at Build: the lights come on, the contractor leaves, and the customer is alone with software they didn't write. Profonti's Run phase keeps the same team on your alerts, your new goals, and your new sources.

Engineer-on-call. The same person who wrote the canonical queries for "monthly active customers" is the person who answers when the number looks wrong on a Monday.
Alert-driven, not ticket-driven. Profonti itself fires alerts when thresholds move; the engineer-on-call rotation responds.
Evolving definitions. The engagement document evolves with your business; we update queries, audiences, and digests in sync. The document is the source of truth — not a Slack thread.
New goals, new sources. Included in the monthly rate up to a stated cadence. Beyond that cadence, you have an explicit conversation about expanding scope; nothing is hidden.

Run is monthly because the work is monthly. New questions arrive every month; new sources come online every quarter. The rate reflects the ongoing relationship, not a slice of a bigger pre-paid bucket.

Built for operators who don't want a dashboard project

The Profonti process is fastest for mid-market operators who already know what they want to know. You don't need a six-month BI rebuild; you need a working answer your CFO can quote. The engagement shape fits when:

You have a small number of high-stakes questions and a clear sense of which systems hold the data.
The questions are the same most months — the data behind them is what changes.
Leadership wants the same answer regardless of who's asking, and is willing to commit a definition in writing.
You'd rather hire a team-on-call than build an analyst function from scratch.

What's delivered at each phase

Discovery: A written engagement document — goals, audiences, sources, definitions. Plus a sync sandbox you can poke at before committing to Build.
Build: Your repository live in your environment, populated, with canonical queries, audience routing, and the first digest.
Run: A monthly retainer for the same engineering team. New sources, new goals, new digests as your business evolves.

Pricing, in plain English

Three engagement phases. One monthly run-rate.

Discovery is fixed-price. Output is your engagement document and a sync sandbox you can validate.
Build is fixed-price. Output is your repository, live, populated, routed.
Run is monthly. Engineer-on-call. New sources, new goals, new questions — included in the rate up to a stated cadence.

No per-seat pricing. No per-question pricing. No surprise infra bills — the cluster is yours.