Skip to main content
CursorLinkedIn

Vercel built its Queues product using Cursor, resulting in significant improvements in PR throughput and cycle time.

Source

LinkedInAug 6, 2026
likes
415
comments
12

Post

Vercel built Queues, one of its most important new infrastructure products, entirely with Cursor. Power users saw a 54% increase in PR throughput, an 89% decrease in PR cycle time, and a 27% decrease in resources allocated per feature. "Cursor's harness allowed agents to ground themselves in production AWS environments with real resources. Agent-led testing was a significant part of meeting our quality bar with Vercel Queues," said Joe Haddad, Distinguished Engineer at Vercel. Learn more: https://lnkd.in/gZ3wvHAF

linkedin.com/posts/cursorai_how-vercel-used-cursor-to-build-queues-ac...Read the full source

Extracted by Autobound

From the Signal API record
Signal
LinkedIn

What this signalsCompany posts often show what the team is pushing right now.

The full record

From the Signal API record

Topics and mentions

Tags

  • Product Development
  • Software
  • Product Launch

Initiatives

  • building new infrastructure products

Technologies named

  • Cursor
  • AWS

Extraction

Detected
Aug 13, 2026
signal_type
linkedin-post-company
signal_subtype
linkedinPost

Use this data

Get every LinkedIn signal for Cursor and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Cursor this week?”

  2. Send it to your own tools

    The Signal API returns LinkedIn signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full linkedin-post-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/1a938490-cd70-4567-8efb-93f63fb38d34 returns this record as JSON. POST /v1/companies/enrich returns every signal for cursor.com.

{
  "signal_id": "1a938490-cd70-4567-8efb-93f63fb38d34",
  "signal_type": "linkedin-post-company",
  "signal_subtype": "linkedinPost",
  "detected_at": "2026-08-13T11:48:49.207+00:00",
  "company": {
    "name": "Cursor",
    "domain": "cursor.com"
  },
  "data": {
    "tags": [
      "Product Development",
      "Software",
      "Product Launch"
    ],
    "summary": "Vercel built its Queues product using Cursor, resulting in significant improvements in PR throughput and cycle time.",
    "post_url": "https://www.linkedin.com/posts/cursorai_how-vercel-used-cursor-to-build-queues-activity-7491158429806247936-R1RD",
    "num_likes": 415,
    "post_text": "Vercel built Queues, one of its most important new infrastructure products, entirely with Cursor.\n\nPower users saw a 54% increase in PR throughput, an 89% decrease in PR cycle time, and a 27% decrease in resources allocated per feature.\n\n\"Cursor's harness allowed agents to ground themselves in production AWS environments with real resources. Agent-led testing was a significant part of meeting our quality bar with Vercel Queues,\" said Joe Haddad, Distinguished Engineer at Vercel. \n\nLearn more: https://lnkd.in/gZ3wvHAF",
    "initiatives": [
      {
        "topic": "building new infrastructure products",
        "urgency": 0.7
      }
    ],
    "posted_date": "2026-08-06T15:49:08.659Z",
    "num_comments": 12,
    "technologies_mentioned": [
      {
        "name": "Cursor",
        "status": "using"
      },
      {
        "name": "AWS",
        "status": "using"
      }
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.