Tallyby Outpost

Theme

Start for free

Software as a service

For workflow automation: which integration pages bring builders whose runs keep growing.

Workflow automation is found through thousands of integration and template pages, tried free, and paid for in tasks or runs once a workflow becomes part of someone's job. Tally ties every plan and usage invoice to the visit behind it, which turns those thousands of pages into a ranking by money.

Start for free

14 days free, no card needed.

01How they sell

  • UsagePlans priced by tasks, operations or executions per month, with overages or a move up a tier as workflows multiply.
  • FreemiumA free tier with a small monthly run allowance and a cap on multi-step workflows.
  • SubscriptionTeam and business plans with shared workspaces, billed monthly or yearly.

02Payments it reads

  • StripeTiered and metered plans through Stripe; overages and tier changes arrive as invoices on the subscription.
  • PolarDeveloper-leaning automation tools bill through Polar, whose metered subscription cycles are read.
  • PaddleUsed by automation platforms selling worldwide with tax handled for them; transactions and renewals are read.

What Tally can't read

  • Runs and tasks counted inside your product aren't read; only what they are billed as is.
  • Self-hosted installs of an open-source edition pay nothing and never show as revenue.
  • Revenue shares that partner apps pay you by bank transfer aren't read.

03Where buyers come from

  • Integration pages in searchPages for connecting one app to another rank for very specific searches and bring people with a workflow already in mind.
  • Template libraryReady-made workflows give new users a start, and the template a buyer landed on says what problem they came with.
  • Community forumThreads solving one edge case bring builders stuck on the same step.
  • Automation YouTubeCreators show full builds from trigger to last step, and viewers may copy the exact workflow.
  • Partner app listingsApps you integrate with list you in their own directories, sending their users your way.

04What Tally answers

  1. Which of our integration pages bring paying users?

    The page breakdown lists landing pages with their visitors and the revenue credited to them; with thousands of integration pages, sort by revenue to find the handful that earn.

    Sources with revenue

  2. Are AI crawlers reading our integration pages?

    AI crawlers' requests are counted by crawler, operator, purpose and page in their own view, apart from visitors; since they seldom run a script, the Express, Next.js or Cloudflare Workers server snippet is what reports them.

    AI crawlers

  3. Do overages come from the same channels as upgrades?

    Every metered invoice and tier change is added to the customer's first source, so lifetime value ranks channels by what their builders' workflows grew into.

    Lifetime value

  4. How many visits does it take before a builder pays?

    Path to purchase gives visits before buying and the median time, with the pages buyers saw; integration pages that turn up in many paths are where workflows start.

    Path to purchase

  5. Did that forum thread send anyone who paid?

    Open the sales credited to the forum: each receipt shows the visits behind it, with the forum as the referrer of the credited visit and the method that linked the payment.

    Receipts

05Numbers worth watching

AI crawler requests
AI crawler requests across integration pages, a sign of which ones assistants are learning from.
Revenue by source
Revenue by landing page, which sorts thousands of integration pages into the few that pay.
Renewals
Renewals by first source; with usage pricing, a growing renewal is a workflow that stuck.
Visits before buying
Visits before the first payment, which shortens when templates do more of the setup.

06An example

Example

Reading time

38s

median per pageview

Scroll depth

59%

average depth, of 27,242 views measured

Read to the end

27%

of measured views reached 90% or more

What they read

29,292 pageviews · last 30 days

Open a page to see how far down people read it, and how buyers read it before paying.

  2. /pricing5,531 views78% scrolled on average58s reading time, median

    58s

    reading time, median per view

    78%

    scrolled, on average

    5,531 views · 5,199 with a measured depth

    How far down they read

    Share of measured views that scrolled at least this far

    1. 25% — reached a quarter of the page:95%
    2. 50% — reached half of the page:84%
    3. 75% — reached three quarters of the page:69%
    4. 90%+ — reached the end of the page:48%

    Buyers before paying vs didn't buy

    • Buyers, before paying149 views · 107 buyers96% scrolled on average,1m 41s reading time, median
    • Didn't buy5,347 views · 3,819 visitors61% scrolled on average,44s reading time, median

    35 views by buyers after paying are left out of both.

    Buyers are visitors whose first sale came after viewing this page; only their views before that payment count.

Reading time runs only while the tab is visible and the visitor is active; it's the median per view. A view with no engagement report counts as 0s of reading. Its scroll depth is unknown, so it's left out of every scroll figure rather than counted as 0%. 27,242 of 29,292 pageviews have a measured depth.

Fig. 1What they read on the example site, buyers against everyone else. For automation software, compare integration and template pages: the ones buyers read closely are where workflows get decided.

07Setting up

  1. Next.jsIf integration pages are generated by a Next.js app, the tag in the root layout covers them all, and the middleware snippet reports AI crawlers on the same pages.
  2. PolarPolar checkouts take metadata: set tally_visitor_id there and each later metered cycle carries the same link.
  3. Send tally('workflow_on') when someone switches on their first workflow, a step worth tracking as a goal before anyone pays.

08Questions

  • Our pricing is per task. Does a busy month count as a new sale?

    No. Overages and tier changes are invoices on the same subscription, credited to its first payment's source; they raise that source's lifetime value instead of adding customers.

  • Can we keep our own test runs on localhost out?

    Visits from localhost don't count unless the tag has data-allow-localhost, so building and testing on your own machine stays out of the numbers.

  • Is the free tier's traffic dragging our conversion down?

    It is part of it: conversion is paying visitors over all visitors. Read revenue per visitor and lifetime value by source alongside it, which show what the free tier's visitors become.

More in software as a serviceEvery business