Predictika · DevSecOps platform subscription quotes

An AI sales agent's GitLab subscription quote, checked before it goes out

An AI sales agent prepares a GitLab subscription quote: plan, where it runs, users, compute minutes, storage, Enterprise Agile Planning seats, Secrets Manager and GitLab Credits. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published plan and add-on rules and returns a verdict, every reason and the figures it computed.

Scope: GitLab Free, Premium and Ultimate on GitLab.com, Self-Managed and Dedicated: users, compute minutes, storage, Enterprise Agile Planning seats, Secrets Manager and GitLab Credits. See everything this validator covers

This validator models GitLab subscription quotes as published on the GitLab pricing page, not just the scenarios shown below.

  • Plans and deployment — Free, Premium and Ultimate on GitLab.com or Self-Managed; Dedicated is an Ultimate-level, sales-arranged option. The Free plan on GitLab.com allows 5 users in a private top-level group.
  • Add-ons — compute minute packs and storage packs apply to GitLab.com only; Enterprise Agile Planning seats need Ultimate; Secrets Manager is for Premium and Ultimate on GitLab.com; GitLab Credits on a self-managed instance need version 18.8 or later.
  • Limits and totals — included compute minutes (400, 10,000 and 50,000 a month by plan) against the pipelines planned, the fixed 500 GiB project limit on Premium and Ultimate (10 GiB initially on Free), and the first-year total at published list prices ($29 per Premium user per month billed annually, $10 per 1,000 compute minutes, $5 per month per 10 GiB of storage billed annually, $15 per Enterprise Agile Planning user per month, $1 per GitLab Credit).

Any GitLab subscription quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: Ultimate and Dedicated seat prices (GitLab does not publish them, so these quotes go to approval), volume discounts and GitLab Flex commitments, partner and marketplace pricing, trials, the open source, education and startup programs, and external agents.

The AI sales agentBuilds the subscription quote from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
Free plan capped at 5 users, but only in a private group on GitLab.comOnly with care
A validation rule on plan, deployment and group visibility. It works, but the same cap does not apply to self-managed or public groups, so each exception is another condition to maintain.		Plan, deployment, group visibility and user count are in one request and checked together.
Add-ons that exist only for some plans or some deploymentsOnly with care
Product rules per add-on: packs on GitLab.com only, Enterprise Agile Planning on Ultimate only, Secrets Manager on Premium and Ultimate on GitLab.com. Every new add-on or availability change is another rule to write and retest.		Every add-on is checked against the plan and deployment on every call.
A project larger than the plan allows, even with extra storageOnly with workarounds
The limit depends on the size of a customer's largest repository, which is not a product choice on the quote. It needs a custom field and a rule that knows buying storage does not lift the 500 GiB ceiling.		The largest project size travels with the quote and is compared with the plan limit.
Planned pipelines against the minutes the plan and packs provideOnly with care
A calculation of included minutes plus packs compared with a planned figure; doable, but it is custom logic that someone has to own.		Included minutes, packs and the planned usage are computed together on every call.
Credits on a self-managed instance that is too oldOnly with workarounds
The quote has to carry the instance version and a rule has to compare it with a minimum that changes with releases.		The version is a field of the quote and is checked against the minimum.
A stated total that does not match the list pricesOnly with care
A free-entry total can be compared with a computed one, but the comparison has to be written and kept in step with every price change.		The stated total travels with the quote and is compared with the computed first-year total.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved or a step is completed, so a rep often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
1The quote has 0 users; at least 1 is needed.
2The Free plan on GitLab.com allows 5 users in a private top-level group; the quote has 6 users.
3GitLab Dedicated includes everything from Ultimate; it is not offered with the Free or Premium plan.
4GitLab Dedicated has no published price and is arranged with GitLab sales; a person should confirm it.
5GitLab does not publish an Ultimate price (contact sales); the total on this quote leaves out the Ultimate seats and a person should confirm the price.
6Compute minutes apply to shared runners on GitLab.com; a self-managed instance runs on its own runners, so the 3 compute minute packs on the quote do not apply.
7The storage add-on applies to GitLab.com namespaces; it is not sold for a self-managed instance (4 packs on the quote).
8The planned pipelines need 12,000 compute minutes in the first month; the plan and the packs on the quote cover 10,000.
9The planned pipelines need 12,001 compute minutes in the first month; the plan and the packs on the quote cover 12,000.
10The planned pipelines need 500 compute minutes in the first month; the plan and the packs on the quote cover 400.
11Enterprise Agile Planning seats are an add-on for GitLab Ultimate subscriptions only (10 seats on the quote).
12Secrets Manager is available for Premium and Ultimate on GitLab.com only; Self-Managed and Dedicated are listed as coming soon.
13A Premium or Ultimate project on GitLab.com has a fixed limit of 500 GiB, and buying storage does not raise it; the largest project on the quote is 600 GiB.
14A Free project on GitLab.com has an initial 10 GiB limit and the quote buys no extra storage; the largest project is 20 GiB.
15The pricing page lists the storage add-on for Premium and Ultimate but its FAQ says Free namespaces can buy storage; a person should confirm 2 packs on a Free plan.
16GitLab Duo Agent Platform on a self-managed instance needs version 18.8 or later; the quote has version 18.6.
17The quote states a first-year total of $9,000.00; the published list prices give $12,430.00.
18Enterprise Agile Planning seats are an add-on for GitLab Ultimate subscriptions only (2 seats on the quote).

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Small team on GitLab.com: Twelve users on the Free plan with 6,000 pipeline minutes

    
The agent's request. Please quote a GitLab Free subscription for 12 users on GitLab.com, with pipelines that need 6,000 compute minutes in the first month and a largest project of 8 GiB. The quote states a first-year total of $0.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Free plan limited to 5 users. The Free plan on GitLab.com allows 5 users in a private top-level group; the quote has 12 users.
    • 
      
  • Compute minutes do not cover planned pipelines. The planned pipelines need 6,000 compute minutes in the first month; the plan and the packs on the quote cover 400.
    • 
    

    
2. Small team on GitLab.com: The agent resubmits after fixing the errors

    
The agent's request. Please quote a GitLab Premium subscription for 12 users on GitLab.com, with pipelines that need 6,000 compute minutes in the first month and a largest project of 8 GiB. The quote states a first-year total of $4,176.00. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 12 user(s); the plan includes 10,000 compute minutes and 144 credits a month; first-year total of $4,176.00 at published list prices.
    • 
    

    
3. Self-managed Premium with credits: 150 self-managed users with compute packs and credits on version 18.6

    
The agent's request. Please quote a GitLab Premium subscription for 150 users on a self-managed instance (version 18.6) and a largest project of 60 GiB, plus 5 compute minute packs and 1,000 GitLab Credits a month. The quote states a first-year total of $62,000.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Compute minute packs are GitLab.com only. Compute minutes apply to shared runners on GitLab.com; a self-managed instance runs on its own runners, so the 5 compute minute packs on the quote do not apply.
    • 
      
  • Duo Agent Platform needs a newer version. GitLab Duo Agent Platform on a self-managed instance needs version 18.8 or later; the quote has version 18.6.
    • 
      
  • Stated total does not match. The quote states a first-year total of $62,000.00; the published list prices give $64,250.00.
    • 
    

    
4. Self-managed Premium with credits: The agent resubmits after fixing the errors

    
The agent's request. Please quote a GitLab Premium subscription for 150 users on a self-managed instance (version 18.8) and a largest project of 60 GiB, plus 1,000 GitLab Credits a month. The quote states a first-year total of $64,250.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated total does not match. The quote states a first-year total of $64,250.00; the published list prices give $64,200.00.
    • 
    

    
5. Self-managed Premium with credits: The agent resubmits after fixing the errors

    
The agent's request. Please quote a GitLab Premium subscription for 150 users on a self-managed instance (version 18.8) and a largest project of 60 GiB, plus 1,000 GitLab Credits a month. The quote states a first-year total of $64,200.00. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 150 user(s); the plan includes 10,000 compute minutes and 1,800 credits a month; first-year total of $64,200.00 at published list prices.
    • 
    

    
6. Platform team and Ultimate: Forty users on Premium with planning seats and an 800 GiB project

    
The agent's request. Please quote a GitLab Premium subscription for 40 users on GitLab.com, with pipelines that need 9,000 compute minutes in the first month and a largest project of 800 GiB, plus 15 Enterprise Agile Planning seats and Secrets Manager. The quote states a first-year total of $16,620.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Enterprise Agile Planning needs Ultimate. Enterprise Agile Planning seats are an add-on for GitLab Ultimate subscriptions only (15 seats on the quote).
    • 
      
  • Project over the fixed storage limit. A Premium or Ultimate project on GitLab.com has a fixed limit of 500 GiB, and buying storage does not raise it; the largest project on the quote is 800 GiB.
    • 
    

    
7. Platform team and Ultimate: The agent resubmits after fixing the errors

    
The agent's request. Please quote a GitLab Ultimate subscription for 40 users on GitLab.com, with pipelines that need 9,000 compute minutes in the first month and a largest project of 450 GiB, plus 15 Enterprise Agile Planning seats and Secrets Manager. The quote states a first-year total of $2,700.00 (the Ultimate seats are priced by GitLab sales). It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Ultimate seat price is not published. GitLab does not publish an Ultimate price (contact sales); the total on this quote leaves out the Ultimate seats and a person should confirm the price.
    • 
      
  • Order summary. 40 user(s); the plan includes 50,000 compute minutes and 960 credits a month; first-year total of $2,700.00 at published list prices.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares a GitLab subscription quote: plan, where it runs, users, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published plan and add-on rules and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote a GitLab Premium subscription for 150 users on a self-managed instance (version 18.6) and a largest project of 60 GiB. The quote states a first-year total of $62,000.00. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with three findings, all in one answer. Compute minutes apply to shared runners on GitLab.com; a self-managed instance runs on its own runners, so the 5 compute minute packs on the quote do not apply. GitLab Duo Agent Platform on a self-managed instance needs version 18.8 or later; the quote has version 18.6. The quote states a first-year total of $62,000.00; the published list prices give $64,250.00.
    6. 
      
  6. The validator returned three blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other and against the stated total.
    7. 
      
  7. What this shows: for free plan capped at 5 users, but only in a private group on GitLab.com, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the instance version to 18.8 and the stated first-year total to $64,250.00. It removes the compute minute packs.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. The quote states a first-year total of $64,250.00; the published list prices give $64,200.00.
    12. 
      
  12. Two findings cleared. Still blocking: stated total does not match.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the stated first-year total to $64,200.00.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The validator also returns the line-item quote. It starts with GitLab Premium; the other line is on screen.
    18. 
      
  18. The earlier finding is cleared, and the validator's total, $64,200.00, matches the quote.
    19. 
      
  19. Three problems caught in one call, fixed in two passes, and a clean $64,200.00 quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    20.