Theme

Start for free

Software as a service

For no-code tools: which tutorials and templates bring builders who publish and pay.

A no-code tool is learned before it's bought: people watch tutorials, clone a template, build for a few evenings and pay when they want to publish or go past a limit. Tally ties each plan to the visits that led to it, so you can see which teachers, templates and partners bring builders who finish.

Start for free

14 days free, no card needed.

01How they sell

  • FreemiumBuild for nothing, pay to publish on a custom domain, remove the badge or go past limits on records, runs or storage.
  • SubscriptionPer-app or per-workspace plans, monthly or yearly; agencies building for clients can hold many apps on one account.
  • UsageSome charge for workflow runs, records or storage above the plan's allowance, so an app that takes off pays more without a new sale.

02Payments it reads

  • StripePlans and usage charges through Stripe subscriptions; metered invoices and upgrades are read beside the first payment.
  • PaddleUsed by builder platforms that sell worldwide and want a merchant of record to handle tax; transactions and renewals are read.

What Tally can't read

  • Templates and components that creators sell each other in a community marketplace aren't read unless the sale runs through your own connected account.
  • Visits to the apps your users build and host with you are their visitors, not your prospects; Tally counts them only if you put the tag there, so don't.
  • Payments your users take inside the apps they build go to their own accounts and aren't read.

03Where buyers come from

  • YouTube build-alongsHour-long tutorials send viewers who have already watched the product work; their first visit may come days after the video.
  • Template galleryTemplates you can clone rank in search and bring people with a specific app already in mind.
  • Expert and agency directoryCertified experts build for clients and open accounts in the client's name; a UTM per partner shows which experts bring paying apps.
  • Community forumThreads that rank in search bring people stuck on the same problem someone else already solved.
  • Third-party coursesPaid courses that teach your tool send cohorts who sign up within days of each other.

04What Tally answers

  1. Do builders from YouTube tutorials stay on a paid plan?

    Lifetime value by first source shows customers, lifetime revenue, renewals and repeat rate per source, so a creator whose viewers publish once and leave is told apart from one whose viewers keep an app running.

    Lifetime value
  2. How long do builders stay free before they publish and pay?

    Path to purchase measures the median time and visits from first visit to first payment and lists the pages buyers saw on the way; documentation pages near the end are often where a builder got unstuck.

    Path to purchase
  3. Which step in building do people abandon?

    With the tag in the editor, send goals for steps like first page added, data connected and publish clicked; the funnel shows each step's completions and what the visitors who finished it paid.

    Goals and funnels
  4. What happens in the editor when a new builder gives up?

    Session replay, off until you turn it on and with inputs masked, plays back editor sessions so you can see the moment someone stops, without reading their data.

    Session replay
  5. Which templates bring paying builders rather than tourists?

    The page breakdown lists template pages with the revenue of the visitors who landed on them, beside their visit counts.

    Sources with revenue

05Numbers worth watching

Visits before buying
Visits before the first payment; builders who need many sessions before paying are still learning, which docs can shorten.
Goal conversion
The share of visitors who reach publish, the step that sits right before paying on a publish-gated plan.
Revenue by source
Revenue behind each tutorial channel, template and partner, rather than their sign-up counts.
Renewals
Renewals by first source, which separate one-off projects from apps that keep running and keep paying.

06An example

Example
  1. Glad HamsterCustomerBerlin, Germany · Desktop · FirefoxRedditOrganic Sociallatest visit: 4 pages/blog/stripe-fees+2/thanks3 visits3m 08s median6m 42s longest$49

    Visits, last 30 days

    Whole journey
    1. RedditOrganic Social
      /blog/stripe-fees/pricing/signup/thanks

      4 pages · 6m 42s engaged · 1 goal$49 credited to this visit

    2. Directtyped or bookmark
      /pricing/docs

      2 pages · 1m 36s engaged

    3. GoogleOrganic Search
      /blog/stripe-fees/

      2 pages · 3m 08s engaged

  2. Cosy CapybaraAustin, United States · Mobile · SafariGoogleOrganic Searchlatest visit: 2 pages//pricing1 visit1m 11s engaged–

    Visits, last 30 days

    Whole journey
    1. GoogleOrganic Search
      //pricing

      2 pages · 1m 11s engaged

  3. Spry BisonToronto, Canada · Desktop · ChromeChatGPTAI Assistantslatest visit: 4 pages/compare+2/docs/api2 visits3m 57s median5m 44s longest–

    Visits, last 30 days

    Whole journey
    1. ChatGPTAI Assistants
      /compare/pricing/docs/docs/api

      4 pages · 5m 44s engaged · 1 outbound click

    2. PerplexityAI Assistants
      /compare

      1 page · 2m 09s engaged

  4. Snug CapybaraCustomerLeeds, United Kingdom · Desktop · EdgeNewsletterEmaillatest visit: 2 pages/changelog/2 visits1m 41s median2m 34s longest$120

    Visits, last 30 days

    Whole journey
    1. NewsletterEmail
      /changelog/

      2 pages · 2m 34s engaged

    2. Directtyped or bookmark
      /

      1 page · 48s engaged

  5. Bubbly LlamaUtrecht, Netherlands · Mobile · Chromex.comOrganic Sociallatest visit: 1 page/blog/launch-week1 visit1m 04s engaged–

    Visits, last 30 days

    Whole journey
    1. x.comOrganic Social
      /blog/launch-week

      1 page · 1m 04s engaged

  6. Velvet PenguinBengaluru, India · Desktop · ChromeHacker NewsOrganic Sociallatest visit: 3 pages/blog/stripe-fees/docs/pricing1 visit4m 56s engaged–

    Visits, last 30 days

    Whole journey
    1. Hacker NewsOrganic Social
      /blog/stripe-fees/docs/pricing

      3 pages · 4m 56s engaged

Fig. 1The visitor list on the example site, with a buyer's journey unfolded. For a no-code tool, follow a builder's sessions from the first tutorial visit to the publish that came before paying.

07Setting up

  1. React and ViteIf the editor is a single-page app, add the tag to its index.html; with hash routes, add data-hash so each screen counts as a page.
  2. StripePut the visitor's id in the Checkout Session's metadata and subscription_data when someone upgrades from inside the editor.
  3. Send tally('published', { plan }) when a builder publishes, so publishing becomes a goal you can follow to revenue.
  4. Leave the tag off the apps your users host with you; only your marketing site and the editor should carry it.

08Questions

  • Do usage charges above the plan count as new sales?

    They're invoices on the same subscription, so they take the link of its first payment and add to that source's revenue rather than starting a sale of their own.

  • An agency opens an account for its client. Who is the buyer?

    Whoever's browser or email is linked to the payment. If the client pays with an email your site identified, the client's visits are credited; the agency's visits stay separate unless the agency pays.

  • Can we see who is building right now?

    The live view shows who is on the site at this moment, on a globe or a flat map, with their source and pages; with the tag in the editor, that includes people building.