ProgrammableMarketing/luminal.com (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 7
  • This quarter · 12
  • Big bets · 3
  • Wildcards · 1
Generated Nov 10, 2026
  1. Programmable
  2. Playbooks
  3. Luminal
Luminal logo

growth playbook · Nov 10, 2026

luminal.com (opens in a new tab)

Luminal growth playbook

Diagnosis

Luminal has a real technical edge: an open-source compiler with about 3,000 GitHub stars, a $5.3M seed, a live text model priced at roughly half a major rival's list price, and a team hiring kernel, compiler and cloud engineers. It is now hiring its first sales person, a Head of Growth, to take over founder-led sales.

The funnel doesn't yet show that edge. The homepage gives three speed claims that don't agree and none of them is sourced. The live price and model appear only on /pricing. The calculator prices on-prem only. The GitHub repo, docs and blog never point to the Cloud.

This playbook first makes the claims reproducible and the price visible, and links the open-source and content audiences to the Cloud. Next it builds proof for the first sales hire: reports, quality checks, customer stories and comparisons. The big bets are hardware partners and a public price-performance index.

Growth Score

6/10

Biggest Opportunity

Turn the compiler's measurable advantage (lower cost per token on the same hardware) into public, reproducible proof, and connect GitHub, docs and blog readers to a Cloud they currently never hear about.

Biggest Risk

Fireworks, Together AI and Baseten put their own throughput and price claims in front of the same buyers, with named customers. If Luminal's numbers can't be reproduced or don't agree with each other, engineers will discount them, and the new sales hire inherits that doubt.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Show the live per-token price on the homepage, where it is about half a major rival's list price

    Add the live model's three prices and a sign-up button under the hero.

    High impact First result in 2 weeks
  2. 2

    Make the homepage speed claims agree, and link each one to a dated, reproducible benchmark

    Find the run behind "3.2x vs vLLM" and write down its model, hardware, batch size and engine versions.

    High impact First result in 2 weeks
  3. 3

    Point the 3,000-star GitHub repo and the docs at Luminal Cloud

    Add a three-line "Run it hosted" block with a tagged link to the README.

    High impact First result in 2 weeks

02

Your idea portfolio

23 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 9 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 5Big bets · 8Fill-ins · 5Reconsider · 5
Effort →

Showing 23 of 23 ideas

This week 7

Quick wins with a clear first action.

  • 01

    The homepage gives three different speed claims for the same thing. The headline stat says "3.2x vs vLLM", the copy says "2-3x", and the only chart (GPT-OSS 120B on 8xH100 SXM) shows 36k against 26k tokens a second, which is about 1.4x vLLM and 1.3x TensorRT-LLM. None of them has a footnote, date or method, and the Benchmarks page has no report for that chart. Luminal's buyers are inference engineers, and they can do that division in seconds. Fireworks ("up to 4x") and Together ("up to 3.7x") make throughput claims to the same people. If a claim doesn't match the chart on its own page, Luminal loses the comparison before the first call.

    High impactLow effort First result in 2 weeks Founders

    First action

    Find the run behind "3.2x vs vLLM" and write down its model, hardware, batch size and engine versions.

    How to measure it

    Homepage to sign-up or call rate

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Trace each claim

      Find the run behind 3.2x, 2-3x, <10ms p99 and 0% overhead.

      Founders 1 day

    2. 2

      Choose the headline

      Keep the number the chart supports, or show the workload where 3.2x is measured.

      Founders 1 day

    3. 3

      Publish the GPT-OSS report

      Configuration, engine versions and settings, date and a reproduce command on /report.

      Cloud Inference Engineer 1 week

    4. 4

      Footnote every stat

      A one-line note and link under each homepage number.

      Founders 1 day

    5. 5

      Invite a rerun

      Ask two outside engineers or the Discord to reproduce it and post results.

      Cloud Inference Engineer 2 weeks

    6. 6

      Add to the sales kit

      The report link opens every first email and call.

      Head of Growth ongoing

    7. 7

      Rerun quarterly

      Against the newest engine versions, with the date updated.

      Cloud Inference Engineer quarterly

    First result
    2 weeks
    Cost
    Engineering time and one 8xH100 benchmark run
    Owner
    Founders

    Smallest test

    Add one line under the chart today: model, hardware, batch size, date and engine versions.

    Why it works

    Pick one headline number that the chart on the page supports. Or, if 3.2x is real, show the workload where it was measured: model, hardware, precision, batch size, context length and engine versions. Put a one-line footnote under every stat (3.2x, 2-3x, <10ms p99, 0% overhead) that links to a report page. Each report gives the date, the configuration, the vLLM and TensorRT-LLM versions and settings, and a command to reproduce the run. Add the GPT-OSS 120B run to /report so the homepage chart has a source. The new Head of Growth then gets a first sales asset that says: here is the run, rerun it on your hardware.

    Engineers trust a smaller number they can reproduce more than a bigger one they can't. Sourced, consistent claims turn the homepage into something people forward rather than argue with, and next to a reproduce button, a rival's unsourced "up to 4x" looks weaker.

    Ready to use

    ChecklistBenchmark claim checklist

    [ ] One headline number that matches the chart
    [ ] Model, hardware, precision, batch size, context length
    [ ] Engine versions and settings for every baseline
    [ ] Date of the run
    [ ] Reproduce command and container image
    [ ] A link from every homepage stat to its report
    [ ] An owner for the quarterly rerun

    Risks and how to handle them

    • The reproducible number is smaller than 3.2x

      A smaller number that holds up beats a bigger one a prospect disproves on a call; lead with cost per token where the gap is larger.

    • Baselines look badly tuned

      Publish the baseline settings and invite engine maintainers to suggest better ones.

    Evidence

    • Your websiteHomepage (checked twice on November 9, 2026): a headline stat "3.2x" labelled "vs vLLM"; body copy "Models compiled by Luminal consistently outperform existing inference engines by 2-3x on standard benchmarks"; a chart "Tokens/sec, GPT-OSS 120B, 8xH100 SXM" showing Luminal 36k, TensorRT-LLM 28k, vLLM 26k and PyTorch 3k (about 1.4x vLLM and 1.3x TensorRT-LLM); "<10ms" p99 latency and "0%" overhead. None of these has a footnote, date or methodology link, and no customer is named.Source
    • Your websiteBenchmarks page (/report): five reports (MiniMax-M2.5, DeepSeek-R1-0528 and Kimi-K2.5 on 8xH200; Qwen3.5-35B-A3B-FP8 and Qwen3-Coder-30B on one H100), each headlined by peak per-user decode speed (93.3 to 172.5 tok/s); no dates, methodology or comparison with vLLM, SGLang or TensorRT-LLM, and no report for the GPT-OSS 120B chart on the homepage.Source
    • Competitor researchRivals' own homepages: Fireworks claims "up to 4x the throughput of providers wrapping vLLM", says models are tested against each lab's reference ("KLD <0.007"), names customers such as Notion, Shopify and Cursor, and lists DeepSeek V4.1 Flash at $0.30 input and $1.20 output per million tokens; Together AI claims "up to 3.7x higher throughput" for its Together Compiler with case studies from Cursor, Decagon and Vercept; Baseten sells "The platform for inference, training, and execution".Source
    • HiringHead of Growth (Sales, San Francisco, posted November 7, 2026): "Be Luminal's first sales hire and take over our founder-led sales motion"; about 50% pre-sales (pipeline, discovery, closing) and 50% post-sales (onboarding, retention, expansion); 3+ years selling technical infrastructure.Source
  • 02

    The live text model on /pricing costs $0.1425 per million input tokens and $0.57 per million output tokens. Fireworks lists the same model at $0.30 and $1.20, so Luminal's list price is about half. That is the most direct proof of what the compiler does, but the homepage names no model and shows no price: only "Pay only for what you use".

    High impactLow effort First result in 2 weeks Head of Growth

    First action

    Add the live model's three prices and a sign-up button under the hero.

    How to measure it

    Homepage sign-up conversion

    Now
    –
    Target
    +25%
    By
    45 days

    Steps

    1. 1

      Pull the prices

      From /pricing, so there is one source of truth.

      Head of Growth 1 hour

    2. 2

      Measure speed

      Live tokens per second for the hosted model.

      Cloud Inference Engineer 1 day

    3. 3

      Design the strip

      Model, three prices, speed, one button.

      Founders 1 day

    4. 4

      Add the comparison

      One dated line with the rival list price and a source link.

      Head of Growth 1 hour

    5. 5

      Ship

      Homepage and the Cloud section.

      Founders 1 day

    6. 6

      Keep it current

      Check rival prices monthly and update the date.

      Head of Growth monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Head of Growth

    Smallest test

    Add the price line under the hero for two weeks and compare sign-ups.

    Why it works

    Add a strip near the top of the homepage with each live model, its input, cached-input and output prices, measured tokens per second, and a "Get an API key" button. Next to it, add a dated line comparing the price with the rival list price, with the source linked. Do the same for the image model. When the coming text model goes live, add a row instead of rewriting the page.

    A developer looking at inference providers can decide in seconds when the price is visible. A lower price is the easiest claim to check, and it backs up the speed story.

    Risks and how to handle them

    • Rivals cut prices

      Date the comparison and lead with Luminal's own price, not the gap.

    • Price wars attract low-value users

      Pair the price with speed and the on-prem path for larger teams.

    Evidence

    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
    • Your websiteHomepage offer: Luminal Cloud ("Managed serverless inference. Deploy in minutes, scale automatically, and only pay for what you use.") and On-Prem ("Licensed cloud or on-prem deployment", "Dedicated engineering support", "Custom kernel optimization", "Strict SLAs tailored to you", "enterprise-grade security"). The homepage names no hosted model and shows no per-token price.Source
    • Competitor researchRivals' own homepages: Fireworks claims "up to 4x the throughput of providers wrapping vLLM", says models are tested against each lab's reference ("KLD <0.007"), names customers such as Notion, Shopify and Cursor, and lists DeepSeek V4.1 Flash at $0.30 input and $1.20 output per million tokens; Together AI claims "up to 3.7x higher throughput" for its Together Compiler with case studies from Cursor, Decagon and Vercept; Baseten sells "The platform for inference, training, and execution".Source
  • 03

    The calculator compares an on-prem deployment with closed APIs. At its default workload (100,000 requests a day, 1,024 input and 512 output tokens) it recommends 8 GPUs at $14.6k a month. At the live Cloud list prices, the same token volume (about 3.1B input and 1.5B output tokens a month) would cost roughly $1.3k on the hosted text model, if that model fits the job. The calculator steers small and mid-size teams to the most expensive option Luminal offers and never shows them the cheapest one.

    High impactMedium effort First result in 3 weeks Head of Growth

    First action

    Write the Cloud cost formula from the /pricing rates and check it against the default inputs.

    How to measure it

    Calculator conversions

    Now
    –
    Target
    2x
    By
    60 days

    Steps

    1. 1

      Write the formula

      Tokens times input, cached and output prices.

      Head of Growth 1 day

    2. 2

      Find the crossover

      The volume where on-prem beats Cloud for each model.

      Cloud Inference Engineer 2 days

    3. 3

      Build the second answer

      Cloud and on-prem side by side.

      Founders 1 week

    4. 4

      Split the buttons

      Cloud to sign-up, on-prem to a call.

      Founders 1 day

    5. 5

      Update How We Calculate

      Show both methods.

      Head of Growth 1 day

    6. 6

      Track

      Conversions by answer type.

      Head of Growth weekly

    First result
    3 weeks
    Cost
    About a week of engineering
    Owner
    Head of Growth

    Smallest test

    Add one static line under the result: "On Luminal Cloud this volume costs about $X a month."

    Why it works

    Add a second answer to the calculator: Luminal Cloud cost at current per-token prices, with the cached-input price applied to an optional repeat-prompt share. Show both answers side by side, with a crossover point: below this volume use Cloud, above it talk to us about on-prem. Send the Cloud answer to sign-up and the on-prem answer to "Talk to an Engineer".

    Visitors get an honest answer for their size and a next step that fits. The on-prem pitch becomes more credible too, because the calculator clearly isn't only selling hardware.

    Risks and how to handle them

    • The calculator's models differ from the hosted model

      Label the Cloud answer with the hosted model, and suggest on-prem when a specific model is required.

    • Cannibalising on-prem deals

      Small teams were unlikely to buy 8 GPUs; Cloud keeps them until they cross over.

    Evidence

    • Your websiteCalculator: "Right-size your inference infrastructure"; Chat, RAG, Agent or Tools workloads on Qwen3-Coder-30B, MiniMax-M2.5, Kimi-K2.5 or DeepSeek-R1-0528 (H100/H200); at the default 100,000 requests a day (1,024 input and 512 output tokens) it shows OpenAI (GPT-5) $19.2k, Anthropic (Claude Sonnet) $32.3k and Luminal $14.6k a month for 8 GPUs, and "Save up to 55% with Luminal on-prem". It prices on-prem only, not the pay-per-token Cloud on /pricing; CTAs are "Talk to an Engineer", "Get Started" and "How We Calculate".Source
    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
  • 04

    luminal.com has no sitemap: /sitemap.xml returns 404 and robots.txt has no Sitemap line. There is no llms.txt either. The five benchmark reports, the calculator and pricing are the pages a buyer searches for (model plus hardware plus tokens per second, or cost per token), and nothing helps search engines or assistants find them.

    Medium impactLow effort First result in 3 weeks Founders

    First action

    Create sitemap.xml and add the Sitemap line to robots.txt.

    How to measure it

    Search clicks to reports

    Now
    –
    Target
    500 a month
    By
    90 days

    Steps

    1. 1

      Build the sitemap

      All public pages, with last-modified dates.

      Founders 2 hours

    2. 2

      Update robots.txt

      Add the Sitemap line; keep the content signals.

      Founders 10 minutes

    3. 3

      Write llms.txt

      What Luminal is, live models, prices, reports.

      Head of Growth 2 hours

    4. 4

      Title the reports

      Model, hardware and metric in each title and description.

      Cloud Inference Engineer 2 hours

    5. 5

      Submit

      Search Console and Bing Webmaster Tools.

      Founders 1 hour

    6. 6

      Watch

      Indexing and queries monthly.

      Head of Growth monthly

    First result
    3 weeks
    Cost
    $0
    Owner
    Founders

    Smallest test

    Ship the sitemap today and check indexing in two weeks.

    Why it works

    Generate a sitemap that lists the homepage, pricing, calculator, /report and every report page, careers, and the blog. Reference it in robots.txt. Add an llms.txt with a short description, the live models and prices, and links to the reports and docs. Give each report page a title and description built from model, hardware and the headline metric.

    Each report targets a long-tail query that engineers type when choosing hardware or a provider. A sitemap gets them indexed quickly.

    Risks and how to handle them

    • The content signals restrict AI use

      Decide deliberately which signals to allow; llms.txt only describes public pages.

    Evidence

    • Your websiteCrawl files (checked November 9, 2026): luminal.com/robots.txt holds content-signal rules but no Sitemap line, and /sitemap.xml and /llms.txt both return 404.Source
    • Your websiteBenchmarks page (/report): five reports (MiniMax-M2.5, DeepSeek-R1-0528 and Kimi-K2.5 on 8xH200; Qwen3.5-35B-A3B-FP8 and Qwen3-Coder-30B on one H100), each headlined by peak per-user decode speed (93.3 to 172.5 tok/s); no dates, methodology or comparison with vLLM, SGLang or TensorRT-LLM, and no report for the GPT-OSS 120B chart on the homepage.Source
  • 05

    The open-source compiler has about 3,000 stars and 254 forks, which makes it Luminal's biggest audience of engineers. But the README never mentions Luminal Cloud, and the docs live on a different domain (docs.luminalai.com), cover only the framework and don't link to luminal.com. Someone who stars the repo has no path to becoming a paying user.

    High impactLow effort First result in 2 weeks Founders

    First action

    Add a three-line "Run it hosted" block with a tagged link to the README.

    How to measure it

    Open-source-sourced sign-ups

    Now
    –
    Target
    100 a month
    By
    90 days

    Steps

    1. 1

      Write the README block

      Live models, price, curl example, sign-up link.

      Founders 2 hours

    2. 2

      Add a Cloud quickstart to the docs

      Key, endpoint, first request, limits.

      Cloud Inference Engineer 2 days

    3. 3

      Link the domains

      Docs header to luminal.com; site footer to the docs.

      Founders 1 hour

    4. 4

      Tag links

      UTM per source.

      Head of Growth 1 hour

    5. 5

      Tell Discord

      Announce the hosted path.

      Founders 1 hour

    6. 6

      Measure

      Sign-ups and spend by source.

      Head of Growth monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founders

    Smallest test

    Add one tagged link to the README and count sign-ups for a month.

    Why it works

    Add a short "Run it hosted" section near the top of the README: the live models, prices, one curl example and a sign-up link. Add a Luminal Cloud section to the docs with a quickstart (key, endpoint, first request), limits and pricing, and link the docs header to luminal.com. Use UTM tags so sign-ups from GitHub and the docs can be counted.

    Developers who already trust the compiler are the warmest Cloud prospects. One link turns open-source reach into revenue without new spend.

    Risks and how to handle them

    • The open-source community sees it as an upsell

      Keep it short and factual; the compiler stays fully open.

    Evidence

    • GitHubluminal-ai/luminal: about 3.0k stars and 254 forks, Apache-2.0/MIT, "a high-performance general-purpose inference compiler" in Rust; CUDA and Metal backends with ROCm on the roadmap; a PyTorch path via torch.compile(model, backend=luminal_cuda); links to docs.luminalai.com, a Discord server and luminal.com, but no mention of Luminal Cloud or its pricing.Source
    • DocsDocs at docs.luminalai.com (a different domain from luminal.com): Quickstart, Why Luminal, GraphTensor API, Modules, Compilers, Developers, Blog and Community for the open-source framework; nothing on Luminal Cloud, API keys or pricing, and no link to luminal.com.Source
    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
  • 06

    The blog is strong technical content: megakernels, speculative decoding, hardware arbitrage, AMD image generation. The latest post studies speculative decoding for the two text models Luminal sells, but like the others it ends with Substack subscribe prompts and no link to pricing, the calculator or sign-up. Its interactive explorer is hosted off luminal.com too.

    Medium impactLow effort First result in 2 weeks Founders

    First action

    Add the closing block to "How Much Does A Token Cost?".

    How to measure it

    Blog-sourced sign-ups

    Now
    –
    Target
    40 a month
    By
    90 days

    Steps

    1. 1

      Write the block

      Price, try link, calculator link.

      Head of Growth 1 hour

    2. 2

      Add to all six posts

      With UTM tags per post.

      Founders 2 hours

    3. 3

      Link the explorer

      From the explorer back to pricing.

      Founders 1 hour

    4. 4

      Plan on-domain mirrors

      luminal.com/blog with canonical tags.

      Founders 1 week

    5. 5

      Promote

      Each new post to Discord, GitHub and the newsletter.

      Head of Growth per post

    6. 6

      Measure

      Sign-ups by post.

      Head of Growth monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founders

    Smallest test

    Add the block to the latest post and count clicks for two weeks.

    Why it works

    Add a closing block to every post: what this means for your cost, the model price, "Try it with an API key" and "Estimate your cost" links, tagged by post. Link the blog from the site footer and add posts to the sitemap. Over time, mirror posts at luminal.com/blog so search credit builds on the main domain.

    Readers of a deep technical post are prospects at peak interest. A clear next step converts some of them, and on-domain posts strengthen luminal.com for search.

    Risks and how to handle them

    • Technical readers dislike sales copy

      Keep it to one factual line and two links.

    Evidence

    • BlogBlog on Substack (blog.luminal.com): six posts from November 2025 to November 2026: the seed announcement, "Compiling Models to Megakernels", "Producing The Perfect Token", "Hardware Arbitrage with Luminal and Positron AI", "Reducing Image Generation Cost with AMD and the Luminal Compiler" and "How Much Does A Token Cost?". The latest is a deep study of speculative decoding for the two text models on the pricing page (B300 GPUs, 18 batch sizes, contexts to 32,768) with an interactive explorer hosted off luminal.com; it ends with Substack subscribe prompts and no link to pricing, the calculator or sign-up.Source
    • Your websiteCrawl files (checked November 9, 2026): luminal.com/robots.txt holds content-signal rules but no Sitemap line, and /sitemap.xml and /llms.txt both return 404.Source
  • 07

    Luminal is hiring its first sales person to take over founder-led sales, half pre-sales and half post-sales. The calculator already collects what discovery needs (requests a day, input and output tokens, workload type, model) and ends in "Talk to an Engineer". If those answers travel with the request, the first call can start from the visitor's numbers instead of a blank page.

    High impactLow effort First result in 3 weeks Head of Growth

    First action

    Add hidden fields for the calculator inputs to the booking form.

    How to measure it

    Calculator-to-opportunity rate

    Now
    –
    Target
    40%
    By
    90 days

    Steps

    1. 1

      Map the fields

      Calculator inputs and outputs to form fields.

      Head of Growth 1 day

    2. 2

      Pass them through

      Hidden fields into the booking form and CRM.

      Founders 1 day

    3. 3

      Write the guide

      Volume bands, workloads, crossover point.

      Head of Growth 2 days

    4. 4

      Template the reply

      Restate their numbers and propose a test.

      Head of Growth 1 day

    5. 5

      Hand over

      Founders review the first ten calls with the hire.

      Founders 2 weeks

    6. 6

      Track

      Opportunities and win rate by volume band.

      Head of Growth monthly

    First result
    3 weeks
    Cost
    $0
    Owner
    Head of Growth

    Smallest test

    Pass just the requests-a-day field and see if first calls get shorter.

    Why it works

    Pass the calculator inputs and result (GPUs, monthly cost, savings) into the call-booking form, and from there into the CRM. Write a one-page qualification guide for the new hire based on those fields: volume bands, workload types and the Cloud-or-on-prem crossover. Reply within one business day with a short note that restates their numbers.

    Founder-led sales depends on context in the founder's head. Putting it in the form gives the new hire that context on day one and shortens discovery.

    Risks and how to handle them

    • The role is not filled yet

      Founders use the same fields until the hire starts.

    Evidence

    • HiringHead of Growth (Sales, San Francisco, posted November 7, 2026): "Be Luminal's first sales hire and take over our founder-led sales motion"; about 50% pre-sales (pipeline, discovery, closing) and 50% post-sales (onboarding, retention, expansion); 3+ years selling technical infrastructure.Source
    • Your websiteCalculator: "Right-size your inference infrastructure"; Chat, RAG, Agent or Tools workloads on Qwen3-Coder-30B, MiniMax-M2.5, Kimi-K2.5 or DeepSeek-R1-0528 (H100/H200); at the default 100,000 requests a day (1,024 input and 512 output tokens) it shows OpenAI (GPT-5) $19.2k, Anthropic (Claude Sonnet) $32.3k and Luminal $14.6k a month for 8 GPUs, and "Save up to 55% with Luminal on-prem". It prices on-prem only, not the pay-per-token Cloud on /pricing; CTAs are "Talk to an Engineer", "Get Started" and "How We Calculate".Source

This quarter 12

The core plays for the next three months.

  • 08

    The five reports are detailed (scenarios from chat to 32k-token agents, queue depth, time to first token), but none has a date, software versions, reproduction steps or a vLLM, SGLang or TensorRT-LLM run on the same GPU. One report gives best time to first token as both 0.189 s and 211 ms. The new Cloud Inference Engineer is hired to run model performance reviews, so this can be their standing output.

    High impactMedium effort First result in 1 month Cloud Inference Engineer

    First action

    Fix the time-to-first-token mismatch and add a date and versions to the Qwen3.5 report.

    How to measure it

    Report-assisted conversions

    Now
    –
    Target
    30 a month
    By
    1 quarter

    Steps

    1. 1

      Define the template

      Header fields, baseline and reproduce script.

      Cloud Inference Engineer 2 days

    2. 2

      Fix inconsistencies

      One value per metric.

      Cloud Inference Engineer 1 day

    3. 3

      Run baselines

      Best open engine on the same hardware.

      Cloud Inference Engineer 2 weeks

    4. 4

      Publish scripts

      In the GitHub repo.

      Compiler Engineer 1 week

    5. 5

      Update all five

      With dates and a changelog.

      Cloud Inference Engineer 1 week

    6. 6

      Add calls to action

      Try it hosted, or talk to an engineer.

      Head of Growth 1 day

    7. 7

      Make it routine

      A report with every new model.

      Cloud Inference Engineer ongoing

    First result
    1 month
    Cost
    GPU time for baseline runs and engineering time
    Owner
    Cloud Inference Engineer

    Smallest test

    Add a baseline column to one report.

    Why it works

    Add a standard header to each report: date, Luminal commit, driver and CUDA versions, precision, and a one-command reproduce script. Add a baseline column from the best open engine on the same hardware with published settings. Fix the inconsistent figures and add a changelog. Publish a new report with each model launch.

    Reports with baselines answer the buyer's real question: how much faster than what I run now, on my hardware. Dated reports also show steady progress.

    Risks and how to handle them

    • Baselines narrow the gap

      Report cost per token too, where the compiler's edge shows.

    Builds on

    Evidence

    • Your websiteQwen3.5-35B-A3B-FP8 report: four scenarios from 1,024 (Chatbot) to 32,768 (Tool Calling Agentic) input tokens; peak 172.5 tok/s per user and 9,774 tok/s system throughput at 256 users; safe queue depth falls from 131 (Chatbot) to 8 (Tool Calling Agentic); no date, software versions, reproduction steps or same-hardware baseline; best time to first token is shown as both 0.189 s and 211 ms.Source
    • Your websiteBenchmarks page (/report): five reports (MiniMax-M2.5, DeepSeek-R1-0528 and Kimi-K2.5 on 8xH200; Qwen3.5-35B-A3B-FP8 and Qwen3-Coder-30B on one H100), each headlined by peak per-user decode speed (93.3 to 172.5 tok/s); no dates, methodology or comparison with vLLM, SGLang or TensorRT-LLM, and no report for the GPT-OSS 120B chart on the homepage.Source
    • HiringEngineering hiring (four roles, San Francisco, posted November 7, 2026): a Cloud Inference Engineer to "Ship low latency, high throughput model serving on Luminal Cloud" (KV caching, paged attention, schedulers, autoscaling, model performance reviews; vLLM, SGLang or TensorRT-LLM experience); a Senior Compiler Engineer (a founding role) to "Develop backend code generation for multiple targets (NVIDIA, Trainium, AMD, TPU, etc.)" and build search-based kernel discovery in Rust; a Founding Kernel Engineer for agent-driven and search-based kernel writing; and a Compiler Engineer.Source
  • 09

    When a provider is faster and cheaper, engineers first ask whether the output has changed. Fireworks answers this on its homepage with a measured divergence from each lab's reference ("KLD <0.007"). Luminal's site says nothing about output quality, even though aggressive kernel search, fusion and speculative decoding (the subject of its latest post) are exactly what a cautious buyer worries about.

    High impactMedium effort First result in 6 weeks Founding Kernel Engineer

    First action

    Choose the prompt set and the reference implementation for the live text model.

    How to measure it

    Quality objections

    Now
    –
    Target
    -50%
    By
    2 quarters

    Steps

    1. 1

      Pick the measures

      Divergence, evals, greedy match.

      Founding Kernel Engineer 2 days

    2. 2

      Build the harness

      Reference and Luminal side by side.

      Founding Kernel Engineer 2 weeks

    3. 3

      Run the live models

      Text and image.

      Cloud Inference Engineer 1 week

    4. 4

      Publish

      A quality page per model, linked from pricing.

      Founders 2 days

    5. 5

      Gate releases

      Quality check in CI.

      Senior Compiler Engineer 1 week

    6. 6

      Equip sales

      One-line answer and link.

      Head of Growth 1 day

    First result
    6 weeks
    Cost
    GPU time and two to three engineer-weeks
    Owner
    Founding Kernel Engineer

    Smallest test

    Publish greedy-decode match on 500 prompts for the live text model.

    Why it works

    For each hosted model, publish a quality page: divergence from the reference implementation on a fixed prompt set, scores on two or three standard evals, and greedy-decode match rates, all rerun at each compiler release. Link it from pricing and every report. Make it part of the release checklist so a kernel change can't ship if it moves quality.

    Removing the hidden-quality-loss objection lets the price and speed claims land. It also gives the kernel team a guardrail that supports faster iteration.

    Risks and how to handle them

    • A measurable drift shows up

      Fix it before publishing; this is the point of the gate.

    Evidence

    • Competitor researchRivals' own homepages: Fireworks claims "up to 4x the throughput of providers wrapping vLLM", says models are tested against each lab's reference ("KLD <0.007"), names customers such as Notion, Shopify and Cursor, and lists DeepSeek V4.1 Flash at $0.30 input and $1.20 output per million tokens; Together AI claims "up to 3.7x higher throughput" for its Together Compiler with case studies from Cursor, Decagon and Vercept; Baseten sells "The platform for inference, training, and execution".Source
    • BlogBlog on Substack (blog.luminal.com): six posts from November 2025 to November 2026: the seed announcement, "Compiling Models to Megakernels", "Producing The Perfect Token", "Hardware Arbitrage with Luminal and Positron AI", "Reducing Image Generation Cost with AMD and the Luminal Compiler" and "How Much Does A Token Cost?". The latest is a deep study of speculative decoding for the two text models on the pricing page (B300 GPUs, 18 batch sizes, contexts to 32,768) with an interactive explorer hosted off luminal.com; it ends with Substack subscribe prompts and no link to pricing, the calculator or sign-up.Source
    • HiringEngineering hiring (four roles, San Francisco, posted November 7, 2026): a Cloud Inference Engineer to "Ship low latency, high throughput model serving on Luminal Cloud" (KV caching, paged attention, schedulers, autoscaling, model performance reviews; vLLM, SGLang or TensorRT-LLM experience); a Senior Compiler Engineer (a founding role) to "Develop backend code generation for multiple targets (NVIDIA, Trainium, AMD, TPU, etc.)" and build search-based kernel discovery in Rust; a Founding Kernel Engineer for agent-driven and search-based kernel writing; and a Compiler Engineer.Source
  • 10

    Pricing lists no free tier, and the minimum card top-up is $50. At $0.1425 per million input tokens, $50 buys hundreds of millions of tokens, far more than a developer needs to check speed and quality. For someone comparing three providers in an afternoon, a $50 charge is the step where they stop.

    Medium impactLow effort First result in 1 month Head of Growth

    First action

    Set up a test that grants credit to half of new sign-ups.

    How to measure it

    Paid activation rate

    Now
    –
    Target
    +30%
    By
    1 quarter

    Steps

    1. 1

      Size the credit

      Enough for a real test, small enough to limit abuse.

      Head of Growth 1 day

    2. 2

      Add abuse checks

      Verified email and card or GitHub sign-in.

      Cloud Inference Engineer 1 week

    3. 3

      Split traffic

      Credit versus $50 minimum.

      Founders 2 days

    4. 4

      Onboarding email

      First request, speed and price check.

      Head of Growth 1 day

    5. 5

      Measure

      Paid accounts and 30-day spend per arm.

      Head of Growth monthly

    6. 6

      Decide

      Keep the winner.

      Founders 1 day

    First result
    1 month
    Cost
    A few dollars per sign-up
    Owner
    Head of Growth

    Smallest test

    Give credit to sign-ups from GitHub only for one month.

    Why it works

    Give new verified accounts a few dollars of credit, enough for roughly a million tokens and a few images, with the $50 top-up required only after that. Alternatively, test a $10 minimum. Track which test produces more paying accounts after 30 days, not just more sign-ups.

    The product's advantages (price and speed) show up in the first few requests. Removing the payment step before that moment lets more developers see them.

    Risks and how to handle them

    • Free-credit abuse

      Require verification and cap credit per card or account.

    Evidence

    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
  • 11

    Cached input costs $0.0029 per million tokens, about 2% of the normal $0.1425. Agent and tool-calling workloads resend long, mostly identical prompts, and Luminal's own report tests them at 16,384 and 32,768 input tokens. The calculator offers Agent and Tools as workload types. For these teams the effective input price is a fraction of the headline, but nothing on the site works that out for them.

    High impactLow effort First result in 1 month Head of Growth

    First action

    Work out the 32k-token agent example at list prices.

    How to measure it

    Agent-workload revenue

    Now
    –
    Target
    25% of Cloud revenue
    By
    2 quarters

    Steps

    1. 1

      Model the example

      32k-token loop, 90% repeated prefix.

      Head of Growth 1 day

    2. 2

      Check cache behaviour

      Prefix rules and time-to-live, documented.

      Cloud Inference Engineer 2 days

    3. 3

      Write the page

      Example, prompt tips, sign-up link.

      Head of Growth 3 days

    4. 4

      Add the slider

      Cache share in the calculator's Cloud mode.

      Founders 2 days

    5. 5

      Promote

      Agent and coding-tool communities.

      Head of Growth 2 weeks

    6. 6

      Report cache hits

      Show each account its hit rate.

      Cloud Inference Engineer 2 weeks

    First result
    1 month
    Cost
    Staff time only
    Owner
    Head of Growth

    Smallest test

    Post the worked example as a short blog note with a sign-up link.

    Why it works

    Publish an "Inference for agents" page with a worked example: a 32k-token agent loop with 90% of the prompt repeated, cost per 1,000 runs at Luminal list prices against the normal input price, and how to structure prompts to get cache hits. Add a cache-share slider to the calculator's Cloud mode. Target the page at agent and coding-tool teams.

    Agent builders feel input-token cost most. Showing their real cost, not the headline price, makes Luminal much cheaper exactly where it matters to them.

    Risks and how to handle them

    • Cache economics are unsustainable at scale

      Confirm margin with the inference team before promoting.

    Builds on

    Evidence

    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
    • Your websiteQwen3.5-35B-A3B-FP8 report: four scenarios from 1,024 (Chatbot) to 32,768 (Tool Calling Agentic) input tokens; peak 172.5 tok/s per user and 9,774 tok/s system throughput at 256 users; safe queue depth falls from 131 (Chatbot) to 8 (Tool Calling Agentic); no date, software versions, reproduction steps or same-hardware baseline; best time to first token is shown as both 0.189 s and 211 ms.Source
    • Your websiteCalculator: "Right-size your inference infrastructure"; Chat, RAG, Agent or Tools workloads on Qwen3-Coder-30B, MiniMax-M2.5, Kimi-K2.5 or DeepSeek-R1-0528 (H100/H200); at the default 100,000 requests a day (1,024 input and 512 output tokens) it shows OpenAI (GPT-5) $19.2k, Anthropic (Claude Sonnet) $32.3k and Luminal $14.6k a month for 8 GPUs, and "Save up to 55% with Luminal on-prem". It prices on-prem only, not the pay-per-token Cloud on /pricing; CTAs are "Talk to an Engineer", "Get Started" and "How We Calculate".Source
  • 12

    Luminal's pricing page offers text and images from one prepaid balance with one set of API keys, and prices the image model the same as its maker's own API. So an app gets no price penalty for consolidating, and gets one bill, one key and one rate-limit conversation. The blog also shows the compiler cutting image-generation cost on AMD. The homepage pitches only text speed.

    Medium impactLow effort First result in 1 month Head of Growth

    First action

    Write one code sample that generates a product description and an image with the same key.

    How to measure it

    Multi-product accounts

    Now
    –
    Target
    20% of paying accounts
    By
    2 quarters

    Steps

    1. 1

      Write the sample

      Text and image, one key.

      Cloud Inference Engineer 1 day

    2. 2

      Build the page

      Use cases, price, sample.

      Head of Growth 3 days

    3. 3

      Link it

      From pricing and the homepage.

      Founders 1 hour

    4. 4

      Build the list

      Apps that publish both text and image features.

      Head of Growth 1 week

    5. 5

      Reach out

      Short note with the combined cost.

      Head of Growth ongoing

    6. 6

      Track

      Accounts using both.

      Head of Growth monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Head of Growth

    Smallest test

    Add one line to the pricing page: "One key, one balance for text and images."

    Why it works

    Write a "Text and images, one API" page aimed at apps that write and illustrate: marketing tools, e-commerce listings, presentation and design apps. Show a single code sample that does both, the combined price, and the image tiers. Use it in outbound from the new Head of Growth to teams that already use both kinds of model.

    Consolidation is a buying reason of its own. Same price plus less admin is an easy yes, and teams that use two products churn less.

    Risks and how to handle them

    • Image volume has thin margin at maker's prices

      Use images to win accounts and earn margin on text.

    Evidence

    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
    • BlogBlog on Substack (blog.luminal.com): six posts from November 2025 to November 2026: the seed announcement, "Compiling Models to Megakernels", "Producing The Perfect Token", "Hardware Arbitrage with Luminal and Positron AI", "Reducing Image Generation Cost with AMD and the Luminal Compiler" and "How Much Does A Token Cost?". The latest is a deep study of speculative decoding for the two text models on the pricing page (B300 GPUs, 18 batch sizes, contexts to 32,768) with an interactive explorer hosted off luminal.com; it ends with Substack subscribe prompts and no link to pricing, the calculator or sign-up.Source
  • 13

    The pricing page lists a second text model as "COMING SOON" with no price and no way to sign up for it. Developers want new open models the day they come out, and the provider that hosts one first, with numbers, gets the early traffic. Luminal's engineers already study this model in depth on the blog, and the Cloud Inference Engineer role exists to ship fast serving on Luminal Cloud.

    High impactMedium effort First result in At launch Cloud Inference Engineer

    First action

    Add a notify-me form next to the coming-soon model.

    How to measure it

    Launch conversion

    Now
    –
    Target
    25% of waitlist
    By
    30 days after launch

    Steps

    1. 1

      Add the form

      Email and expected volume.

      Founders 1 day

    2. 2

      Prepare serving

      Compile, tune and load-test.

      Cloud Inference Engineer 3 weeks

    3. 3

      Run the report

      Standard format with baseline.

      Cloud Inference Engineer 1 week

    4. 4

      Set the price

      From measured cost per token.

      Founders 1 day

    5. 5

      Launch

      Price, report, post, waitlist email.

      Head of Growth 1 day

    6. 6

      Make it a habit

      A launch playbook for every notable model.

      Cloud Inference Engineer ongoing

    First result
    At launch
    Cost
    GPU capacity for the new model
    Owner
    Cloud Inference Engineer

    Smallest test

    Add the notify-me form this week and count sign-ups.

    Why it works

    Replace "COMING SOON" with a "notify me" form. On launch day, publish the price, a benchmark report in the new standard format, and a short blog post, and email the waitlist. Set a standing goal of hosting notable open models within days of release, with a report each time.

    Launch-day interest is the cheapest acquisition there is, and a waitlist measures demand before capacity is committed.

    Risks and how to handle them

    • Capacity runs out at launch

      Use the waitlist volume answers to size capacity and stagger invites.

    Builds on

    Evidence

    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
    • BlogBlog on Substack (blog.luminal.com): six posts from November 2025 to November 2026: the seed announcement, "Compiling Models to Megakernels", "Producing The Perfect Token", "Hardware Arbitrage with Luminal and Positron AI", "Reducing Image Generation Cost with AMD and the Luminal Compiler" and "How Much Does A Token Cost?". The latest is a deep study of speculative decoding for the two text models on the pricing page (B300 GPUs, 18 batch sizes, contexts to 32,768) with an interactive explorer hosted off luminal.com; it ends with Substack subscribe prompts and no link to pricing, the calculator or sign-up.Source
    • HiringEngineering hiring (four roles, San Francisco, posted November 7, 2026): a Cloud Inference Engineer to "Ship low latency, high throughput model serving on Luminal Cloud" (KV caching, paged attention, schedulers, autoscaling, model performance reviews; vLLM, SGLang or TensorRT-LLM experience); a Senior Compiler Engineer (a founding role) to "Develop backend code generation for multiple targets (NVIDIA, Trainium, AMD, TPU, etc.)" and build search-based kernel discovery in Rust; a Founding Kernel Engineer for agent-driven and search-based kernel writing; and a Compiler Engineer.Source
  • 14

    Default limits are 60 requests a minute and 10 requests a second burst, and higher limits mean emailing sales. A team that likes the price will hit 60 requests a minute on its first production load test, at exactly the moment it is deciding whether to switch.

    Medium impactMedium effort First result in 6 weeks Cloud Inference Engineer

    First action

    Count how many accounts hit the 60-requests-a-minute limit last month.

    How to measure it

    Tier-2 accounts

    Now
    –
    Target
    +50%
    By
    1 quarter

    Steps

    1. 1

      Measure limit hits

      Accounts throttled, by spend.

      Cloud Inference Engineer 2 days

    2. 2

      Design tiers

      Spend thresholds and limits.

      Founders 2 days

    3. 3

      Build auto-upgrade

      Limits change on top-up.

      Cloud Inference Engineer 2 weeks

    4. 4

      Show in the dashboard

      Current and next tier.

      Cloud Inference Engineer 1 week

    5. 5

      Publish on pricing

      Replace the email-only line.

      Head of Growth 1 day

    6. 6

      Route top-tier requests

      To the Head of Growth.

      Head of Growth ongoing

    First result
    6 weeks
    Cost
    Two to three engineer-weeks
    Owner
    Cloud Inference Engineer

    Smallest test

    Manually raise limits for every account that tops up $500 and compare their spend.

    Why it works

    Publish usage tiers tied to lifetime top-ups (for example $50, $500 and $5,000), each with higher request and token limits, applied automatically. Show the current tier and the next one in the dashboard. Keep email for custom limits above the top tier, routed to the Head of Growth as an expansion lead.

    Self-serve tiers remove a stall at the point of adoption, and the top tier becomes a clean signal for sales.

    Risks and how to handle them

    • Capacity spikes from auto-upgraded accounts

      Tie the top tiers to autoscaling headroom.

    Evidence

    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
    • HiringHead of Growth (Sales, San Francisco, posted November 7, 2026): "Be Luminal's first sales hire and take over our founder-led sales motion"; about 50% pre-sales (pipeline, discovery, closing) and 50% post-sales (onboarding, retention, expansion); 3+ years selling technical infrastructure.Source
  • 15

    Half of the Head of Growth role is post-sales: onboarding, retention and expansion. Luminal's advantage is cost, and customers forget a cost advantage unless someone reminds them. The data for that reminder already exists: tokens used, cached share, and list prices that are about half a major rival's.

    Medium impactMedium effort First result in 1 month Head of Growth

    First action

    Build the report by hand for the top ten accounts.

    How to measure it

    Cloud net revenue retention

    Now
    –
    Target
    120%
    By
    2 quarters

    Steps

    1. 1

      Define the report

      Usage, cache share, spend, comparison, tip.

      Head of Growth 1 day

    2. 2

      Pull the data

      From billing and usage logs.

      Cloud Inference Engineer 1 week

    3. 3

      Send by hand

      Top ten accounts first.

      Head of Growth 1 day

    4. 4

      Automate

      Monthly email for all paying accounts.

      Cloud Inference Engineer 2 weeks

    5. 5

      Flag growth

      Fast-growing accounts to sales.

      Head of Growth monthly

    6. 6

      Measure

      Retention and expansion by cohort.

      Head of Growth quarterly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Head of Growth

    Smallest test

    Send the report to five accounts and ask if it is useful.

    Why it works

    Email each paying account a monthly one-pager: tokens and images used, cache-hit share, spend, the same usage at a named rival's published list price, and one tip to cut cost further (for example, prompt structure for cache hits). Flag accounts whose usage is growing quickly to the Head of Growth for an on-prem or committed-volume conversation.

    A visible saving each month justifies staying, and growth signals point sales at expansion before a competitor makes an offer.

    Risks and how to handle them

    • Rival prices change

      Date the comparison and use published list prices only.

    Evidence

    • HiringHead of Growth (Sales, San Francisco, posted November 7, 2026): "Be Luminal's first sales hire and take over our founder-led sales motion"; about 50% pre-sales (pipeline, discovery, closing) and 50% post-sales (onboarding, retention, expansion); 3+ years selling technical infrastructure.Source
    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
    • Competitor researchRivals' own homepages: Fireworks claims "up to 4x the throughput of providers wrapping vLLM", says models are tested against each lab's reference ("KLD <0.007"), names customers such as Notion, Shopify and Cursor, and lists DeepSeek V4.1 Flash at $0.30 input and $1.20 output per million tokens; Together AI claims "up to 3.7x higher throughput" for its Together Compiler with case studies from Cursor, Decagon and Vercept; Baseten sells "The platform for inference, training, and execution".Source
  • 16

    The homepage names no customers and shows no logos. Fireworks and Together lead with named customers and case studies. For a seed-stage provider, the buyer's biggest question is "who else runs production on this?", and today the site has no answer.

    High impactMedium effort First result in 6 weeks Head of Growth

    First action

    List the five happiest users and ask three for a 30-minute interview.

    How to measure it

    Deals that viewed a story

    Now
    –
    Target
    50% of closed deals
    By
    2 quarters

    Steps

    1. 1

      Shortlist users

      Clear, measurable results.

      Founders 2 days

    2. 2

      Interview

      Workload, before and after, switch time.

      Head of Growth 2 weeks

    3. 3

      Verify numbers

      From usage data.

      Cloud Inference Engineer 2 days

    4. 4

      Write and approve

      Customer sign-off on every number.

      Head of Growth 2 weeks

    5. 5

      Publish

      Stories page and homepage strip.

      Founders 2 days

    6. 6

      Use in sales

      Match the story to the prospect.

      Head of Growth ongoing

    First result
    6 weeks
    Cost
    Staff time and a small thank-you credit
    Owner
    Head of Growth

    Smallest test

    Publish one anonymised story with real numbers.

    Why it works

    Ask three current users (Cloud or on-prem) for a short story: workload, previous setup, cost per token and latency before and after, and time to switch. Where a name can't be published, describe the company by type and size and keep the numbers. Add a customer strip to the homepage and link the stories from pricing and the calculator.

    Peer proof is what turns a benchmark into a decision. Each story also tells the new sales hire which use cases to target.

    Risks and how to handle them

    • Customers won't be named

      Publish by company type with verified numbers.

    Evidence

    • Your websiteHomepage (checked twice on November 9, 2026): a headline stat "3.2x" labelled "vs vLLM"; body copy "Models compiled by Luminal consistently outperform existing inference engines by 2-3x on standard benchmarks"; a chart "Tokens/sec, GPT-OSS 120B, 8xH100 SXM" showing Luminal 36k, TensorRT-LLM 28k, vLLM 26k and PyTorch 3k (about 1.4x vLLM and 1.3x TensorRT-LLM); "<10ms" p99 latency and "0%" overhead. None of these has a footnote, date or methodology link, and no customer is named.Source
    • Competitor researchRivals' own homepages: Fireworks claims "up to 4x the throughput of providers wrapping vLLM", says models are tested against each lab's reference ("KLD <0.007"), names customers such as Notion, Shopify and Cursor, and lists DeepSeek V4.1 Flash at $0.30 input and $1.20 output per million tokens; Together AI claims "up to 3.7x higher throughput" for its Together Compiler with case studies from Cursor, Decagon and Vercept; Baseten sells "The platform for inference, training, and execution".Source
    • HiringHead of Growth (Sales, San Francisco, posted November 7, 2026): "Be Luminal's first sales hire and take over our founder-led sales motion"; about 50% pre-sales (pipeline, discovery, closing) and 50% post-sales (onboarding, retention, expansion); 3+ years selling technical infrastructure.Source
  • 17

    TechCrunch's seed coverage names Baseten, Together AI, Tensormesh and Clarifai as competitors, and Fireworks and Together market their own throughput multiples to the same buyers. Engineers search for "X vs Y" before switching providers, but luminal.com has no comparison pages, even though a list-price comparison for the shared text model already favours Luminal by about half.

    Medium impactMedium effort First result in 6 weeks Head of Growth

    First action

    Collect each rival's published price for the shared text model.

    How to measure it

    Comparison-page sign-ups

    Now
    –
    Target
    60 a month
    By
    2 quarters

    Steps

    1. 1

      Pick rivals

      Fireworks and Together first.

      Head of Growth 1 day

    2. 2

      Gather prices

      From each rival's own pages, dated.

      Head of Growth 2 days

    3. 3

      Run measurements

      Same prompts against each public endpoint.

      Cloud Inference Engineer 1 week

    4. 4

      Write pages

      Tables, sources, switching guide.

      Head of Growth 1 week

    5. 5

      Legal review

      Claims and trademarks.

      Founders 3 days

    6. 6

      Refresh

      Quarterly, with dates.

      Head of Growth quarterly

    First result
    6 weeks
    Cost
    Small API spend on rival endpoints and staff time
    Owner
    Head of Growth

    Smallest test

    Publish one page for the shared text model's price and speed.

    Why it works

    Publish one page per rival: per-token price for the shared models, measured throughput and time to first token from a dated run, quality check, limits, on-prem options and how to switch. Keep it factual and sourced, date every row and invite corrections. Start with Fireworks and Together, where a shared model makes the comparison concrete.

    Comparison searches are the highest-intent traffic, and a fair page builds the credibility the speed claims need.

    Risks and how to handle them

    • Outdated or disputed numbers

      Date every row, link sources and fix errors quickly.

    Builds on

    Evidence

    • Press coverageTechCrunch (November 17, 2025): a $5.3 million seed led by Felicis, with angels including Paul Graham and Guillermo Rauch; Y Combinator Summer 2025; Luminal sells compute like CoreWeave and Lambda but competes on compiler optimization; rivals named include Baseten, Together AI, Tensormesh and Clarifai, plus in-house optimization teams at large labs.Source
    • Competitor researchRivals' own homepages: Fireworks claims "up to 4x the throughput of providers wrapping vLLM", says models are tested against each lab's reference ("KLD <0.007"), names customers such as Notion, Shopify and Cursor, and lists DeepSeek V4.1 Flash at $0.30 input and $1.20 output per million tokens; Together AI claims "up to 3.7x higher throughput" for its Together Compiler with case studies from Cursor, Decagon and Vercept; Baseten sells "The platform for inference, training, and execution".Source
    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source
  • 18

    The On-Prem offer promises "enterprise-grade security", "Strict SLAs tailored to you" and "Licensed cloud or on-prem deployment", but the site gives no detail behind any of them. On-prem buyers have to get infrastructure and security teams to agree before a call goes anywhere. The first sales hire will spend many early calls answering the same questions by hand.

    Medium impactMedium effort First result in 1 month Head of Growth

    First action

    List the ten questions on-prem prospects asked most in founder-led calls.

    How to measure it

    On-prem sales cycle

    Now
    –
    Target
    -30%
    By
    2 quarters

    Steps

    1. 1

      Collect questions

      From past calls and emails.

      Founders 2 days

    2. 2

      Document deployment

      Hardware, drivers, architecture, updates.

      Senior Compiler Engineer 1 week

    3. 3

      Define SLA tiers

      Response times and support.

      Founders 2 days

    4. 4

      Answer security questions

      A standard questionnaire answered in advance.

      Founders 1 week

    5. 5

      Publish the summary

      An on-prem page linked from the homepage.

      Head of Growth 2 days

    6. 6

      Use in deals

      Send after the first call.

      Head of Growth ongoing

    First result
    1 month
    Cost
    Staff time; a formal audit later if deals require it
    Owner
    Head of Growth

    Smallest test

    Send a two-page draft to the next on-prem prospect and ask what's missing.

    Why it works

    Write a short on-prem pack: supported hardware and drivers, the deployment architecture (air-gapped or not, what leaves the network), update process, SLA tiers and response times, licensing model, and a security questionnaire answered in advance. Put a summary page on the site and share the full pack after the first call.

    Enterprise deals stall on unanswered questions. Answering them in advance shortens security review and makes a small team look ready for production.

    Risks and how to handle them

    • Promising more than a small team can support

      Publish only commitments the team can meet today.

    Evidence

    • Your websiteHomepage offer: Luminal Cloud ("Managed serverless inference. Deploy in minutes, scale automatically, and only pay for what you use.") and On-Prem ("Licensed cloud or on-prem deployment", "Dedicated engineering support", "Custom kernel optimization", "Strict SLAs tailored to you", "enterprise-grade security"). The homepage names no hosted model and shows no per-token price.Source
    • HiringHead of Growth (Sales, San Francisco, posted November 7, 2026): "Be Luminal's first sales hire and take over our founder-led sales motion"; about 50% pre-sales (pipeline, discovery, closing) and 50% post-sales (onboarding, retention, expansion); 3+ years selling technical infrastructure.Source
  • 19

    The compiler has 254 forks and a Discord community, and it is linked from both the README and the docs. Those are engineers who have already built something with Luminal. Nothing gives them a reason to show their work or bring their team onto Luminal Cloud.

    Medium impactLow effort First result in 1 month Founders

    First action

    Ask the Discord to share what they have built.

    How to measure it

    Referred paying accounts

    Now
    –
    Target
    15 a quarter
    By
    2 quarters

    Steps

    1. 1

      Call for projects

      Discord and a GitHub discussion.

      Founders 1 day

    2. 2

      Build the page

      Projects with short write-ups.

      Head of Growth 1 week

    3. 3

      Set up credits

      For contributors and featured builders.

      Founders 2 days

    4. 4

      Add referral links

      Credit when a referred account pays.

      Cloud Inference Engineer 1 week

    5. 5

      Monthly showcase

      Live in Discord; best one on the blog.

      Founders monthly

    6. 6

      Track

      Referred accounts and spend.

      Head of Growth monthly

    First result
    1 month
    Cost
    Cloud credit
    Owner
    Founders

    Smallest test

    Feature three community projects in the README this month.

    Why it works

    Launch a "Built with Luminal" page that features community projects, each with a short write-up and a link to the author. Give contributors and featured builders Cloud credit, plus a referral link that earns more credit when a colleague's account starts paying. Run a monthly Discord showcase and pick the best project for the blog.

    Recognition and credit cost little and turn the open-source community into a source of referrals and content.

    Risks and how to handle them

    • Few projects to feature at first

      Start with the team's own demos and examples from the repo.

    Builds on

    Evidence

    • GitHubluminal-ai/luminal: about 3.0k stars and 254 forks, Apache-2.0/MIT, "a high-performance general-purpose inference compiler" in Rust; CUDA and Metal backends with ROCm on the roadmap; a PyTorch path via torch.compile(model, backend=luminal_cuda); links to docs.luminalai.com, a Discord server and luminal.com, but no mention of Luminal Cloud or its pricing.Source
    • DocsDocs at docs.luminalai.com (a different domain from luminal.com): Quickstart, Why Luminal, GraphTensor API, Modules, Compilers, Developers, Blog and Community for the open-source framework; nothing on Luminal Cloud, API keys or pricing, and no link to luminal.com.Source

Big bets 3

Larger plays that can change the trajectory.

  • 20

    In May 2026 Luminal showed prefill on an H100 and decode on Positron's Atlas, with switching backends as "a single-line code change", and promised precise benchmarks in a later post. That post isn't in the archive six months later. Since then Luminal has published AMD image-generation work and is hiring to target Trainium, AMD and TPU. Every accelerator maker needs software that makes its chips easy to adopt, and Luminal is that software.

    High impactHigh effort First result in 1 quarter Senior Compiler Engineer

    First action

    Finish and publish the Positron benchmark post.

    How to measure it

    Partner-sourced pipeline

    Now
    –
    Target
    10 opportunities
    By
    2 quarters

    Steps

    1. 1

      Ship the Positron post

      Prefill and decode numbers, reproduce script.

      Senior Compiler Engineer 3 weeks

    2. 2

      Template the partner page

      Models, cost per token, script.

      Head of Growth 1 week

    3. 3

      AMD page

      From the image-generation work.

      Compiler Engineer 1 month

    4. 4

      Co-announce

      Joint post and social with each partner.

      Founders per partner

    5. 5

      Get listed

      In each partner's software ecosystem pages.

      Founders 1 quarter

    6. 6

      Add backends

      Trainium and TPU pages as they land.

      Senior Compiler Engineer ongoing

    7. 7

      Track

      Pipeline by partner.

      Head of Growth monthly

    First result
    1 quarter
    Cost
    Engineering time and hardware access, often provided by partners
    Owner
    Senior Compiler Engineer

    Smallest test

    Publish the Positron benchmark and ask Positron to share it.

    Why it works

    Publish the Positron prefill and decode benchmark. Then build a joint page for each hardware partner (Positron, AMD, then Trainium and TPU as backends land): supported models, cost per token on that hardware, and a reproduce script, co-announced with the partner. Ask each partner to list Luminal in its own software ecosystem and refer customers.

    Hardware vendors have large marketing budgets and customers who need software. Being the compiler that makes their chips usable puts Luminal into their sales conversations.

    Risks and how to handle them

    • Partners want exclusivity

      Stay hardware-neutral; that is the product's value.

    • Benchmarks disappoint on early hardware

      Lead with cost per token and the disaggregated setup, where mixed hardware wins.

    Builds on

    Evidence

    • Blog"Hardware Arbitrage with Luminal and Positron AI" (May 18, 2026): Positron's Atlas added as a compiler backend; prefill compiled for an H100 and decode for Atlas; switching backends is "a single-line code change"; precise prefill and decode benchmarks are promised in a later post, which the blog archive does not list as of November 9, 2026.Source
    • HiringEngineering hiring (four roles, San Francisco, posted November 7, 2026): a Cloud Inference Engineer to "Ship low latency, high throughput model serving on Luminal Cloud" (KV caching, paged attention, schedulers, autoscaling, model performance reviews; vLLM, SGLang or TensorRT-LLM experience); a Senior Compiler Engineer (a founding role) to "Develop backend code generation for multiple targets (NVIDIA, Trainium, AMD, TPU, etc.)" and build search-based kernel discovery in Rust; a Founding Kernel Engineer for agent-driven and search-based kernel writing; and a Compiler Engineer.Source
    • BlogBlog on Substack (blog.luminal.com): six posts from November 2025 to November 2026: the seed announcement, "Compiling Models to Megakernels", "Producing The Perfect Token", "Hardware Arbitrage with Luminal and Positron AI", "Reducing Image Generation Cost with AMD and the Luminal Compiler" and "How Much Does A Token Cost?". The latest is a deep study of speculative decoding for the two text models on the pricing page (B300 GPUs, 18 batch sizes, contexts to 32,768) with an interactive explorer hosted off luminal.com; it ends with Substack subscribe prompts and no link to pricing, the calculator or sign-up.Source
  • 21

    Luminal's pitch is that one compiler gets the most out of any accelerator: NVIDIA, AMD, Positron, and soon Trainium and TPU. Its own blog calls this "hardware arbitrage" and asks "How Much Does A Token Cost?". No one publishes a neutral, regularly updated cost per million tokens for the same model across different chips, because most providers run on a single vendor. Luminal is set up to do it.

    High impactHigh effort First result in 1 quarter Founders

    First action

    Choose three models and the hardware already supported, and define the cost method.

    How to measure it

    Referring domains to the index

    Now
    –
    Target
    50
    By
    2 quarters

    Steps

    1. 1

      Define the method

      Models, workloads, public hourly prices.

      Founders 1 week

    2. 2

      Run the hardware

      NVIDIA, AMD, Positron first.

      Senior Compiler Engineer 1 month

    3. 3

      Build the page

      Table, charts, dataset download.

      Head of Growth 2 weeks

    4. 4

      Partner review

      Each vendor checks its row.

      Founders 2 weeks

    5. 5

      Launch

      Blog post, press and community.

      Head of Growth 1 week

    6. 6

      Update quarterly

      New chips and models.

      Cloud Inference Engineer quarterly

    First result
    1 quarter
    Cost
    Hardware time across vendors, partly partner-provided
    Owner
    Founders

    Smallest test

    Publish one model on two chips as a blog post.

    Why it works

    Each quarter, compile the same few open models for every supported accelerator. Publish cost per million tokens (at public hourly prices), throughput and latency, with scripts to reproduce. Make the index a page on luminal.com with a downloadable dataset, and announce each edition with a blog post and partner quotes.

    An index gets cited by press, analysts and buyers each time it updates. It puts Luminal at the centre of the hardware conversation and shows the product working across chips at the same time.

    Risks and how to handle them

    • Seen as biased towards Luminal's partners

      Publish method and scripts and accept outside submissions.

    Builds on

    Evidence

    • Blog"Hardware Arbitrage with Luminal and Positron AI" (May 18, 2026): Positron's Atlas added as a compiler backend; prefill compiled for an H100 and decode for Atlas; switching backends is "a single-line code change"; precise prefill and decode benchmarks are promised in a later post, which the blog archive does not list as of November 9, 2026.Source
    • HiringEngineering hiring (four roles, San Francisco, posted November 7, 2026): a Cloud Inference Engineer to "Ship low latency, high throughput model serving on Luminal Cloud" (KV caching, paged attention, schedulers, autoscaling, model performance reviews; vLLM, SGLang or TensorRT-LLM experience); a Senior Compiler Engineer (a founding role) to "Develop backend code generation for multiple targets (NVIDIA, Trainium, AMD, TPU, etc.)" and build search-based kernel discovery in Rust; a Founding Kernel Engineer for agent-driven and search-based kernel writing; and a Compiler Engineer.Source
    • BlogBlog on Substack (blog.luminal.com): six posts from November 2025 to November 2026: the seed announcement, "Compiling Models to Megakernels", "Producing The Perfect Token", "Hardware Arbitrage with Luminal and Positron AI", "Reducing Image Generation Cost with AMD and the Luminal Compiler" and "How Much Does A Token Cost?". The latest is a deep study of speculative decoding for the two text models on the pricing page (B300 GPUs, 18 batch sizes, contexts to 32,768) with an interactive explorer hosted off luminal.com; it ends with Substack subscribe prompts and no link to pricing, the calculator or sign-up.Source
    • Press coverageTechCrunch (November 17, 2025): a $5.3 million seed led by Felicis, with angels including Paul Graham and Guillermo Rauch; Y Combinator Summer 2025; Luminal sells compute like CoreWeave and Lambda but competes on compiler optimization; rivals named include Baseten, Together AI, Tensormesh and Clarifai, plus in-house optimization teams at large labs.Source
  • 22

    Developers can already use Luminal as a PyTorch backend with torch.compile(model, backend=luminal_cuda), and the homepage says Cloud lets you "Deploy in minutes". But Cloud today sells fixed hosted models, and the open-source path stops at the developer's own machine. The step teams actually want is between those two: compile my model, measure it, then host it.

    High impactHigh effort First result in 1 quarter Senior Compiler Engineer

    First action

    Interview five open-source users about where they serve their compiled models today.

    How to measure it

    Custom endpoints live

    Now
    –
    Target
    25
    By
    2 quarters

    Steps

    1. 1

      Interview users

      Where and how they serve today.

      Founders 2 weeks

    2. 2

      Design the command

      Compile, upload, endpoint.

      Senior Compiler Engineer 2 weeks

    3. 3

      Build serving

      Custom graphs with scale-to-zero.

      Cloud Inference Engineer 2 months

    4. 4

      Price it

      Per token or per GPU-second.

      Founders 1 week

    5. 5

      Private beta

      Ten teams with custom models.

      Head of Growth 1 month

    6. 6

      Document

      README and docs quickstart.

      Compiler Engineer 1 week

    7. 7

      Launch

      Blog, GitHub release, Discord.

      Head of Growth 1 week

    First result
    1 quarter
    Cost
    A quarter of engineering for two to three people
    Owner
    Senior Compiler Engineer

    Smallest test

    Deploy one beta user's compiled model by hand and measure demand.

    Why it works

    Add a deploy command to the open-source tooling. It takes a model that already compiles locally, uploads the compiled graph, and returns a serverless endpoint on Luminal Cloud with scale-to-zero and per-token or per-second billing. Start with a private beta for teams with fine-tuned or custom models that the hosted catalogue doesn't cover.

    It turns every local user of the compiler into a potential Cloud customer, and serves custom models, which the fixed catalogue can't.

    Risks and how to handle them

    • Custom models are harder to serve efficiently

      Start with architectures the compiler already handles well.

    Builds on

    Evidence

    • GitHubluminal-ai/luminal: about 3.0k stars and 254 forks, Apache-2.0/MIT, "a high-performance general-purpose inference compiler" in Rust; CUDA and Metal backends with ROCm on the roadmap; a PyTorch path via torch.compile(model, backend=luminal_cuda); links to docs.luminalai.com, a Discord server and luminal.com, but no mention of Luminal Cloud or its pricing.Source
    • Your websiteHomepage offer: Luminal Cloud ("Managed serverless inference. Deploy in minutes, scale automatically, and only pay for what you use.") and On-Prem ("Licensed cloud or on-prem deployment", "Dedicated engineering support", "Custom kernel optimization", "Strict SLAs tailored to you", "enterprise-grade security"). The homepage names no hosted model and shows no per-token price.Source
    • Your websitePricing page: pay as you go, no subscription; DeepSeek V4.1 Flash live at $0.1425 per million input tokens, $0.0029 for cached input and $0.57 for output; GLM-5.3-Flash "COMING SOON"; Ideogram 4.5 images from $0.008 to $0.20, "the same as Ideogram's own API"; one prepaid balance and one set of API keys for text and images; $50 minimum top-up, credit does not expire, no free tier; default limits of 60 requests and 1,000,000 tokens a minute, with higher limits by emailing sales; no FAQ.Source

Wildcards 1

Unexpected experiments, each with a cheap way to test it.

  • 23

    "How Much Does A Token Cost?" comes with an interactive explorer of how speculation depth, batch size and context length change the cost of a token. It is hosted off luminal.com and linked only from a Substack post. The calculator, meanwhile, answers a much simpler question. The explorer is the kind of tool inference engineers bookmark and share.

    Medium impactMedium effort First result in 1 month Founding Kernel Engineer

    First action

    Move the existing explorer to a luminal.com path and link it from the calculator.

    How to measure it

    Tool-assisted sign-ups

    Now
    –
    Target
    50 a month
    By
    2 quarters

    Steps

    1. 1

      Move it

      luminal.com/tools/token-cost.

      Founders 2 days

    2. 2

      Add inputs

      Model, hardware, batch, context.

      Founding Kernel Engineer 2 weeks

    3. 3

      Show Luminal's price

      Next to the computed cost.

      Head of Growth 1 day

    4. 4

      Add embed and share

      So others can cite it.

      Founders 1 week

    5. 5

      Launch

      Engineering communities and Discord.

      Head of Growth 1 week

    6. 6

      Measure

      Users, links and sign-ups.

      Head of Growth monthly

    First result
    1 month
    Cost
    Two to three engineer-weeks
    Owner
    Founding Kernel Engineer

    Smallest test

    Link the explorer from the calculator and the README and count clicks.

    Why it works

    Move the explorer to luminal.com/tools/token-cost. Let visitors pick a model, hardware, batch size and context, and see cost per million tokens with and without speculation, alongside Luminal's own price. Add a "Run this on Luminal" button and an embed code so others can cite it. Add more models as they launch.

    A useful tool earns links and repeat visits that a blog post doesn't. On luminal.com, those visits build the main site and end one click from sign-up.

    Risks and how to handle them

    • Too technical for most visitors

      Keep the calculator as the simple entry and link the tool for depth.

    Evidence

    • BlogBlog on Substack (blog.luminal.com): six posts from November 2025 to November 2026: the seed announcement, "Compiling Models to Megakernels", "Producing The Perfect Token", "Hardware Arbitrage with Luminal and Positron AI", "Reducing Image Generation Cost with AMD and the Luminal Compiler" and "How Much Does A Token Cost?". The latest is a deep study of speculative decoding for the two text models on the pricing page (B300 GPUs, 18 batch sizes, contexts to 32,768) with an interactive explorer hosted off luminal.com; it ends with Substack subscribe prompts and no link to pricing, the calculator or sign-up.Source
    • Your websiteCalculator: "Right-size your inference infrastructure"; Chat, RAG, Agent or Tools workloads on Qwen3-Coder-30B, MiniMax-M2.5, Kimi-K2.5 or DeepSeek-R1-0528 (H100/H200); at the default 100,000 requests a day (1,024 input and 512 output tokens) it shows OpenAI (GPT-5) $19.2k, Anthropic (Claude Sonnet) $32.3k and Luminal $14.6k a month for 8 GPUs, and "Save up to 55% with Luminal on-prem". It prices on-prem only, not the pay-per-token Cloud on /pricing; CTAs are "Talk to an Engineer", "Get Started" and "How We Calculate".Source
More example playbooks and reviews
ProgrammableDigital

Show Luminal’s product working

Turn screenshots or the website into an animated product demo in its own brand, for the homepage, launch posts and outreach in this playbook.

Make a demo (opens programmable.digital in a new tab)

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • Mixpanel growth strategyA product intelligence platform combining product analytics, session replay, experiments, feature flags, metric trees and AI agents for…21 growth ideas
  • Pactimo growth strategyColorado cycling clothing brand: jerseys, bibs, thermal and outerwear, base layers and accessories in the Flyte, Summit, Ascent and Range…21 growth ideas
  • Supervest growth strategyAn alternative-investment platform that gives accredited investors and financial advisors fixed-rate notes backed by portfolios of…21 growth ideas
  • Humwork growth strategyA real-time marketplace where AI agents call verified human experts when they get stuck. A single MCP server, API or plugin routes the…22 growth ideas
  • Bestyfit growth strategyA Canadian online boutique, founded by Caro, selling Colombian-made compression leggings, sports bras and swimwear, mainly from the brands…21 growth ideas
  • Gateway Region YMCA growth strategyA nonprofit YMCA serving more than 260,000 people a year across St. Louis, eight Missouri counties and six Illinois counties: 25 branches…22 growth ideas
  • Wingman Law growth strategyAn AI-native personal injury law firm in San Francisco: attorneys direct AI agents that prepare case documents and communications for…22 growth ideas
  • Keeper Security growth strategyA zero-trust, zero-knowledge identity security platform: enterprise password management, KeeperPAM privileged access, secrets management…21 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 10, 2026, and cites them throughout. Luminal did not commission, review or endorse it, and Programmable is not affiliated with Luminal. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Luminal runs its business.

Something wrong, or do you represent Luminal? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 307 ideas

    Reconcile and source the homepage claims, show the live price, add a Cloud mode to the calculator, add crawl files, and connect GitHub, docs, blog and calculator to sign-up and sales.

  2. Days 31 to 6012 ideas

    Proof for the first sales hire: rigorous reports, quality parity, customer stories, comparisons and an on-prem pack; activation with trial credit, cache pricing, the text-and-image bundle, day-zero launches, self-serve limits, cost reports and community referrals.

  3. Days 61 to 904 ideas

    Commit to the big bets: accelerator partner pages, a public price-performance index, a local-to-Cloud compile path and the token cost explorer.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value lower cost per token than list prices elsewhere. The most cited problem: GPU spend that grows faster than revenue.

  • Speed from compiled kernels rather than hand tuning
  • Benchmarks that are hard to trust or reproduce
  • In their words: “cost per token”

Market

Competitive landscape

4 competitors compared: Fireworks AI, Together AI, Baseten and vLLM, SGLang and TensorRT-LLM.

  • Gap to exploit: Reproducible, dated benchmarks buyers can rerun
  • Fireworks AI: Lists the same text model at about twice Luminal's per-token price
  • Together AI: Broad platform, less focused on compiling for any accelerator

Hiring signals

Luminal posted five San Francisco roles on November 7, 2026, and they show the next stage.

  • Head of Growth: First sales hire, taking over founder-led sales; half pre-sales, half post-sales. Ideas 1, 7, 15, 16, 18.
  • Cloud Inference Engineer: Low-latency, high-throughput serving on Luminal Cloud and model performance reviews. Ideas 8, 13, 14.
  • Senior Compiler Engineer: Backends for NVIDIA, Trainium, AMD and TPU. Ideas 20, 21, 22.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks first (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence