FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Comparing develop...docs/go-to-market · levelcodeai/levelcode · GitHub

Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: levelcodeai/levelcode
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: develop
Choose a base ref
Could not load branches
Nothing to show
{{ refName }}
...
head repository: levelcodeai/levelcode
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: docs/go-to-market
Choose a head ref
Could not load branches
Nothing to show
{{ refName }}
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 1 file changed
  • 1 contributor

Commits on Aug 21, 2026

  1. docs: go-to-market plan, sequenced behind three gates

    Written against the actual repos rather than a template. Every number is read out of
    the code or computed from prices the code itself records.
    
    THE FINDING THAT SETS THE SEQUENCE. lib/levelcode.rb carries an unresolved note from
    the team — the plan caps were sized against an older ~$0.66/$3.41 flagship and want
    re-checking. Costed at the current list prices in that same file, one fully-consumed
    plan-month:
    
      Pro   $20  ->  $18.10   +9%
      Pro+  $40  ->  $41.65   -4%
      Max   $60  ->  $65.20   -9%
    
    Pro+ and Max sell below cost at full burn with no prompt caching; only a high cache
    rate pulls them back above water. The structural read matters more than the numbers:
    margin comes from UNUSED allowance, not usage — so the heaviest, most vocal users are
    the least profitable, which inverts the usual instinct for a developer tool that
    selects for exactly those people.
    
    The number that settles it is already recorded: usages.cached_input_tokens, per row.
    One query. That is why it is a gate and not a footnote.
    
    TWO CORRECTIONS I MADE TO MY OWN DRAFT.
    
    The IPv6 claim was wrong on first pass. `dig +short AAAA www.levelcode.ai` printed a
    CNAME and I read it as "www is dualstack, the apex is not". Re-checked: neither name
    has AAAA, and neither does the Elastic Beanstalk load balancer behind them. The whole
    stack is IPv4-only. The fix is also ordered — dualstack the load balancer FIRST, then
    add the records, because an AAAA resolving to nothing serving is a hard failure rather
    than a slow one.
    
    A claim that macOS is "roughly a third of professional developers" is softened to a
    directional statement, flagged for confirmation against a current survey before it goes
    in a deck. It was recalled, not sourced.
    
    Also corrected a stale memory in passing: credit_wallets.product now separates LevelCode
    from thin.ly for reporting, and levelcode_stripe_id is gone. My note said the opposite.
    
    Phases: 0 gates (IPv6, margin, claims-vs-build) -> 1 instrument -> 2 position ->
    3 channels in order -> 4 pricing -> 5 scale gates. Deliberate omissions (no Windows, no
    enterprise, no launch event) are listed with reasons so they can be argued with.
    ndemianc committed Aug 21, 2026
    Configuration menu
    Copy the full SHA
    976bc10 View commit details
    Browse the repository at this point in the history
Loading

Back | FazBrowse Home | New Git URL