Tallyby Outpost

Theme

Start for free

Developer tools

For monitoring and observability tools: which SDK guides bring teams whose usage pays.

Monitoring and observability tools are installed by an engineer from an SDK guide, run on a free quota, and paid for when events, logs or hosts grow past it. Tally ties each usage invoice to the visits behind it, from the SDK page an engineer followed to the quota email that brought them back to upgrade.

Start for free

14 days free, no card needed.

01How they sell

  • UsageBilled by events, spans, log volume or hosts, with a monthly quota and overage above it.
  • FreemiumA free quota for small projects, with limits on retention and alerting.
  • SubscriptionTeam plans with seats, longer retention and on-call features, monthly or annual.

02Payments it reads

  • StripeMetered plans through Stripe; overage invoices and annual renewals are read.
  • PolarDeveloper-first monitoring products bill metered usage through Polar; metered cycles are read.
  • PaddleObservability tools selling to companies worldwide use Paddle for tax; transactions and adjustments are read.

What Tally can't read

  • Events, logs and traces your customers send are never read.
  • Plans bought through a cloud marketplace are billed by the cloud provider and aren't read.
  • Open-source agents and self-hosted editions that never pay show up only as docs visitors.

03Where buyers come from

  • SDK install guidesAn engineer adding monitoring to a framework searches for that SDK's setup and follows the guide step by step.
  • Error message searchesSearching an error leads to a post or docs page that explains it, with your tool beside the fix.
  • Quota emailsEmails warning that a project is near its quota bring engineers back to upgrade; a UTM on the link counts them.
  • Engineering blogs and talksPosts on debugging an outage send readers who want the same visibility.
  • AI assistantsEngineers ask an assistant how to monitor a service and get pointed at tools.

04What Tally answers

  1. Which SDK's guide brings teams that pay?

    Each SDK guide's landing page has a row in the page breakdown with visitors and revenue, so the Python, Node and Go guides are compared on money.

    Sources with revenue

  2. How many projects that send a first event go on to pay?

    Send tally('first_event') from the dashboard when a project's first event arrives; the goals view gives completions, converting visitors and their revenue, which is activation measured in money.

    Goals and funnels

  3. Did the quota warning email bring the upgrade?

    The upgrade's receipt shows the visits behind it; if the credited visit carries the quota email's campaign, that email brought them back.

    Receipts

  4. Do accounts from AI assistants grow like accounts from search?

    Lifetime value by first source sets the AI channel's accounts beside search's on lifetime revenue, overages included, and on repeat rate.

    Lifetime value

05Numbers worth watching

Median time to buy
The median time from first visit to first payment, which covers the free quota's runway.
Lifetime value by first source
Lifetime revenue by first source, the figure that captures overage growth.
Coverage
The share of revenue linked to a visit, which falls when upgrades happen inside the dashboard without the visitor's id.
Visitors from AI assistants
Visits from AI assistants recommending a monitoring tool.

06An example

Example

Lifetime value by first source

All time: every payment since 1 Nov 2025. The period above doesn't apply.

First sourceCustomersLifetime revenueAverage valueRenewalsRepeat rate
GoogleOrganic Search325$40,560$12584552%
ChatGPTAI Assistants126$21,071$16739161%
Direct178$18,216$10237444%
NewsletterEmail94$17,362$18535769%
Hacker NewsOrganic Social84$11,741$14022755%
x.comOrganic Social115$10,190$8916133%
RedditOrganic Social84$9,016$10716040%
PerplexityAI Assistants42$6,342$15110157%
Every source1,048$134,498$1282,61651%

A customer is a visitor linked to a sale, counted under the source of their first visit. Lifetime revenue is net of refunds and chargebacks; repeat rate is the share who paid more than once (a renewal, an upgrade or another purchase). $13,167 from 426 payments not linked to a visitor is in no row.

Fig. 1Lifetime value by first source on the example site. For monitoring tools, compare sources once overage invoices have had a few months to arrive; early averages miss the growth.

07Setting up

  1. Next.jsPut the tag in the root layout of the docs and dashboard app, so SDK guides and the upgrade page share visitors.
  2. StripeAdd tally_visitor_id to the Checkout Session's metadata and subscription_data when a project upgrades, so overages follow.
  3. Add UTMs to links in quota and usage emails.

08Questions

  • Annual contracts and monthly overages: how do both show?

    As payments on their subscriptions, each taking the first payment's link; the annual payment lands on its day, overages on theirs, and lifetime value adds them up per source.

  • Do we need the tag in our dashboard?

    Only if you want in-app steps such as the first event as goals, or the upgrade page to pass the visitor's id; the marketing and docs pages are enough for sources.

  • Our users send us events from their apps. Does that count as traffic?

    No. Events sent to your platform aren't visits; only pages carrying the tag on your own site are counted.

More in developer toolsEvery business