How it works

How Pensero measures delivery, and what you do with it

Every piece of work scored in delivery points, with cost and quality beside it.

How a delivery point is scored

  1. Step 1

    What we measure

    Code changes, reviews, tickets, documents, discussions and agent sessions in connected tools. A contribution earns points only when there is evidence that it is meaningful. Activity alone earns nothing.

  2. Step 2

    How we measure it

    Magnitude × complexity. Magnitude is the size of the real change (XXS 0.15 · XS 0.5 · S 1 · M 3 · L 5 · XL 8). Complexity is how hard it was to deliver (1.0 → 3.0), across code, system design, delivery, communication and ownership.

  3. Step 3

    Worked example

    An example work item in the product: Add workspace setup to self-serve onboarding. Large 5.0 × Medium 2.0 = 10.0 points.

Consistent criteria and traceable evidence

  • Teams
  • Providers
  • Humans
  • Agents

The same criteria, calibrated against Pensero’s benchmark

Every point traces back to

  • Pull request
  • Ticket
  • Document

What discourages gaming

  • BoilerplateLock files, generated code, migrationsRemoved
  • MagnitudeCapped
  • Reverts and duplicatesNo credit0.0

Nothing is counted twice. Scores can change when new evidence comes in.

What is not in the point

Magnitude×Complexity=Points

Not in the formula. Pensero shows them beside the point

  • Cost
  • Time
  • Quality

Engineering teamsusing Pensero

  • Internet Brands
  • Happy Scribe
  • Perk
  • ClosedLoop
  • Stord
  • Tuio
  • Persuit
  • SEAT CODE
  • Cubbo
  • Elfie
  • Caravelo
  • ShopMy
  • iAhorro
  • Hum Capital
  • Exoticca
  • Zynap

Connected in an hour. Your first baseline in a day.

  1. 1 hour

    Connect

    Connect GitHub, Jira, Devin and your AI assistants, in your own repos or your client’s. Pensero only needs read access, and nobody changes how they work.

  2. 1 day

    See your baseline

    Every piece of work is scored on one scale, whether a person, an AI-assisted engineer or an agent did it. You see four measures: AI cost per delivery point, model fit, agentic maturity and defect cost.

  3. 1 week

    Benchmark and price

    Compare your numbers with 200+ organizations. You come out with a price per delivery point you can defend in a proposal.

No guesswork. The baseline places you on all 5 levels.

  1. 1x
    L1

    Human-only

    Humans write all the code

  2. +30%Most teams are here
    L2

    AI-assisted

    Engineers write with AI tools like Copilot or Cursor

  3. +50%
    L3

    AI reviews

    Humans write, AI checks the work

  4. 3x
    L4

    Orchestrated agents

    Agents carry out whole tasks, humans direct and review

  5. 4x
    L5

    Fully autonomous agents

    Agents start and deliver work, humans govern

Your firm allocates delivery, not hours. Pensero certifies it.

Agents cut the humans a project needs. Priced per delivery point, your firm keeps the gain from every point.

  1. PenseroConnects GitHub, GitLab, Jira, Linear, Copilot, Cursor, Claude Code and Devin, in the cloud or on-prem.

  2. PenseroThe 200+ organization benchmark makes the quote comparable and credible.

  3. PenseroScores every PR and ticket as it happens.

    Pensero Agents page with example data: weekly delivery by agentic maturity level, and the top agents by delivery points.
  4. PenseroDelivers the evidence inside the workflow, through MCP.

    Pensero Quality tax with example data: defect cost 6%, rework rate 11% and revert rate 1.4%, and the weekly share of delivery that went to bug fixes.
  5. PenseroMeasures what held, so your track record compounds.

Other tools measure activity. Pensero certifies delivery.

Pensero scores accepted delivery points as a neutral operator: one unit across humans, vendors and agents.

  1. Captures the whole workflow: code, tickets, docs, agents, tokens.
  2. One unit, calibrated on 200+ organizations and 2M+ PRs and tickets.
  3. Acts inside the workflow: 80% of traffic through MCP.
  4. Does not deliver the work, so no vendor grades its own return.
  5. Rules both sides rely on: acceptance and dispute.

Add workspace setup to self-serve onboarding

  • Pull request #429110.0
  • PR: Add workspace setup step6.0
  • Ticket edit · ONB-4125.4
  • Comment on ONB-4123.0

Coding agents

Pull request #4291

12 files · +284 −92

MeasuresTheir own activity

Client acceptance

VCVarrow CTOAccepted

Certified by Pensero10.0 pts

Ready for your client’s security review

Pensero reads the client’s systems with read access only and runs where the client needs it to.

See the Pensero trust center →
  • SOC 2 Type II

    GDPR compliant and HIPAA aligned.

    • Secured by Sprinto: SOC 2Type II
    • Secured by Sprinto: GDPRCompliant
    • Secured by Sprinto: HIPAACompliant
  • SAML SSO and SCIM

    Audit logs and 24/7 monitoring.

  • Cloud, on-premise or hybrid

    Pensero Cloud, an EU deployment or the client’s own cloud account.

  • Configurable retention

    Custom APIs, MCP access and a contractual SLA.

  • “Automation, standardization, and time savings was our primary goal.”
    Nick TraylorHead of Engineering, StordRead story →
  • “And the best part: it was truly plug-and-play — we were live in just one day.”
    Jean-François LegourdCo-founder, Elfie
  • “With Pensero we go 4x faster.”
    Andrew EyeCEO and Founder, ClosedLoopRead story →
  • “It’s a plan of going step by step, moving on a quarterly basis.”
    Jordi AbadCTO, SEAT CODERead story →
  • “Now we went from 70% to 30% maintenance… it’s where we want it to be.”
    Ignasi VegasCEO and Co-founder, CubboRead story →