Pulley

Cover Block

From the public record

Field	Value
Name	Pulley
Tagline	Expert judgment and AI to make permitting manageable, predictable, and fast for commercial projects [Pulley, retrieved 2026]
Headquarters	San Francisco, US
Founded	2020
Stage	Seed
Business Model	SaaS
Industry	Proptech
Technology	AI / Machine Learning
Geography	North America
Growth Profile	Venture Scale
Founding Team	Co-Founders (2): Yin Wu, Grant Oladipo [Y Combinator]
Investors / Programs	Susa Ventures; Y Combinator
Funding Label	Seed
Total Disclosed Funding	~$4.4M [SourceForge, 2026]; $4.4M over 1 round from 10 investors [Tracxn, 2026]

Links

From the public record

• Website: https://www.withpulley.com/
• LinkedIn: https://www.linkedin.com/company/pulleyhq/

The Short Version

PUBLIC Pulley sells permitting software for commercial construction projects, and it merits attention because it is trying to turn one of the slowest parts of the development workflow into a more standardized, software-assisted process, with an embedded Procore integration that points to ecosystem fit rather than a standalone point tool [Pulley, retrieved 2026] [LinkedIn, 2026] [Pulley, 2026]. Public materials describe the company as San Francisco-based and founded in 2020 by Yin Wu and Grant Oladipo, although one recruiting page says 2021, so the founding date should be treated with some caution pending fuller corroboration [Y Combinator] [Ashbyhq.com, retrieved 2026].

The product combines permitting expertise with AI and workflow software, including online application submission, document management, status tracking, automated notifications, compliance checks, custom permit plans, reviewer directories, and packet compilation tools [Pulley, retrieved 2026] [GetApp, 2026] [Sourceforge.net, 2026]. That differentiation appears to rest less on novel model infrastructure and more on embedding expert permitting judgment into a system of record for project teams, which is a sensible position in a category where operational nuance matters as much as raw automation [Pulley, retrieved 2026].

On team quality, the public record is thinner than investors would usually prefer at seed, but there are still a few useful anchors: Yin Wu is publicly identified as CEO and co-founder, and LinkedIn describes her as a three-time Y Combinator founder [TechCrunch, 2021] [LinkedIn, 2026]. The available source set does not establish much more about the operating bench, so execution capacity should be assessed through customer references and implementation evidence rather than biography alone.

On capitalization, public databases and review platforms point to about $4.4 net, 2026] [Tracxn, 2026]. The business model is presented as SaaS, and the near-term question is whether Pulley can translate product breadth and partner integrations into repeatable adoption across developers, contractors, architects, and retailers without relying too heavily on company-reported outcome claims such as approvals being up to 2x faster [Pulley, retrieved 2026] [The Org, retrieved 2026].

Over the next 12 to 18 months, the points to watch are straightforward: evidence of durable customer expansion beyond named references, proof that the Procore integration drives distribution or retention, and signs that geographic expansion, including the reported Denver push, can be replicated without a large services burden [Promptloop.com, retrieved 2026] [Permitting Talk, retrieved 2026] [Pulley, 2026]. If those signals firm up, Pulley starts to look less like a narrow workflow layer and more like category software for a permitting process that remains structurally painful for commercial projects.

Unconfirmed -- This section relies materially on company sources, with partial corroboration from LinkedIn, TechCrunch, Tracxn, GetApp, and SourceForge; several product and traction claims remain company-reported.

Taxonomy Snapshot

Axis	Value
Stage	Seed
Business Model	SaaS
Industry / Vertical	Proptech
Technology Type	AI / Machine Learning
Geography	North America
Growth Profile	Venture Scale
Founding Team	Co-Founders (2)
Funding	Seed, total disclosed about $4.4 million

The Company in Brief

PUBLIC

Pulley presents itself as a San Francisco company building software to make construction permitting more manageable and more predictable for commercial projects [Pulley]. The public record here is narrow but directionally consistent: the company website frames the product as an "expert permitting partner powered by AI," while Crunchbase lists Pulley in San Francisco and shows a 2020 founding year [Pulley] [Crunchbase].

The chronology is thin, so the safest reading is a simple one. Pulley appears to have been founded in 2020, later organized around a permitting workflow that combines software with domain expertise, and has since added integrations and category-specific messaging on its public site, including a Procore integration announced on its resources pages [Crunchbase] [Pulley]. A careers posting cited elsewhere describes the business as founded in 2021, but that date is not used here because this section is restricted to the company website and Crunchbase, and Crunchbase is the clearer source for the founding year [Crunchbase].

Within those limits, the core milestone set is straightforward: founding in 2020, headquarters in San Francisco, and subsequent public positioning around AI-assisted permitting for commercial development teams [Crunchbase] [Pulley]. Neither the company website nor Crunchbase, in the materials reviewed for this section, established a legal entity name or a fuller milestone history with dated operational markers, so this overview stays close to what can be confirmed directly [Pulley] [Crunchbase].

Single-source, plausible -- Confirmed in part by Crunchbase and the company website; founding year and headquarters are corroborated, while milestone detail remains limited in the reviewed public record.

What They Have Built

MIXED

Pulley is positioning itself as permitting workflow software for commercial projects, with the core product framed around making permit submission and review more manageable and faster for project teams [Pulley, retrieved 2026]. The public product description points to a fairly specific operating surface: online application submission, document management, status tracking, automated notifications, compliance checks, and integrations with adjacent construction systems [Pulley, retrieved 2026]. Third-party listings add more workflow detail, including custom permit plans, an automatic packet compiler for file merging and sheet separation, and a reviewer directory intended to help teams identify the relevant municipal contacts for a project [GetApp, 2026].

The more credible product signal is not the AI language itself, which remains company-led, but the way Pulley appears to sit inside existing construction software and permit operations. Pulley announced a Procore integration on its own site, and LinkedIn materials describe that integration as embedded rather than a loose export-import connection [Pulley, retrieved 2026] [LinkedIn, 2026]. Public-facing customer and company descriptions also indicate the product is used by developers, contractors, retailers, and architects to identify permitting requirements earlier, coordinate submittals, track status changes, and convert agency comment letters into operational tasks, although most of those claims trace back to company channels or marketplace profiles rather than independent product reviews [LinkedIn, retrieved 2026] [Sourceforge.net, 2026] [The Org, retrieved 2026].

The technical stack itself is not established in the available public evidence, so any stronger claim about model architecture, data moat, or deployment design would be inference rather than reporting. What can be said with support is narrower: Pulley is presenting a software layer that combines domain expertise with workflow automation in a category where process fragmentation is often the pain point, and it has at least one named integration partner in Procore [Pulley, retrieved 2026] [LinkedIn, 2026]. The headline performance claim, that customers commonly see up to 2x faster approvals, is company-reported and should be treated as directional rather than independently verified [Pulley, retrieved 2026].

Unconfirmed -- Core product and performance claims rely heavily on company materials, with partial corroboration from GetApp, LinkedIn, SourceForge, and The Org.

Market Size and Demand

From the public record Construction permitting is one of those markets where the pain is older than the software category, and the timing matters because the workflow is being pulled into larger preconstruction systems at the same time commercial teams are under pressure to shorten project timelines [Pulley, retrieved 2026] [LinkedIn, 2026].

The available public record does not support a clean TAM, SAM, or SOM for Pulley’s specific category, and it would be overstated to invent one from sparse vendor claims. What the evidence does show is a defined workflow wedge inside commercial construction software: permit planning, submittal assembly, status tracking, comment management, and integration into broader project systems such as Procore [Pulley, retrieved 2026] [GetApp, 2026] [LinkedIn, 2026]. That places Pulley in an adjacent market to construction project management and preconstruction software rather than a standalone category with well-cited public sizing in the materials provided [Pulley, retrieved 2026] [Pulley, 2026].

Demand appears to be driven less by discretionary software experimentation and more by schedule risk. Pulley’s own materials frame the value proposition around making permitting more manageable, predictable, and fast for commercial projects, while marketplace and profile sources point to concrete workflow features such as custom permit plans, packet compilation, reviewer directories, status-change alerts, and turning comment letters into taskable workstreams [Pulley, retrieved 2026] [GetApp, 2026] [Sourceforge.net, 2026]. The reported user base spans retailers, developers, contractors, and architects, which is directionally consistent with permitting as a cross-functional bottleneck rather than a niche departmental tool [The Org, retrieved 2026] [LinkedIn, retrieved 2026] [Built In NYC, retrieved 2026].

A second tailwind is ecosystem fit. The Procore integration matters because it suggests buyers want permitting data to sit inside existing construction workflows, not in a disconnected back-office system [Pulley, 2026] [LinkedIn, 2026]. That does not prove category scale on its own, but it does indicate where the budget line likely comes from: teams already spending on preconstruction, project controls, or development operations software may view permitting as an extension of those systems rather than a new software category [Pulley, retrieved 2026] [Pulley, 2026].

Regulation is both the source of the problem and a limit on how portable the solution can be. Permit workflows vary by jurisdiction, reviewer, and project type, which supports the case for software plus domain expertise, but it also implies operational complexity if the company expands city by city or region by region [Pulley, retrieved 2026] [Permitting Talk, retrieved 2026]. Pulley’s reported Denver expansion and customer examples from firms such as JLL Austin indicate that geographic replication is part of the thesis, though the public evidence here is still company-proximate and should be read cautiously [Permitting Talk, retrieved 2026] [Pulley, retrieved 2026].

Market sizing lens	Public evidence	Read-through for Pulley
Core permitting software	No third-party TAM/SAM/SOM surfaced in the provided research	Market size remains unquantified in the current public record
Adjacent construction software workflow	Pulley offers online submission, document management, status tracking, compliance checks, and integration features [Pulley, retrieved 2026] [GetApp, 2026]	Suggests the product sits inside a broader preconstruction software budget
Embedded ecosystem relevance	Pulley launched a Procore integration for permitting [Pulley, 2026] [LinkedIn, 2026]	Points to demand for permitting data inside established construction platforms
Buyer breadth	Reported users include retailers, developers, contractors, and architects [The Org, retrieved 2026] [LinkedIn, retrieved 2026]	Indicates the pain point cuts across several commercial project stakeholders

The main takeaway from the evidence is modest but useful: this looks less like a greenfield software category and more like a persistent operational bottleneck being absorbed into the wider construction tech stack. The opportunity depends on whether permitting software can become system-of-record infrastructure inside commercial development workflows, not simply a point tool for filing forms.

Unconfirmed -- Section relies heavily on company materials and secondary marketplace profiles, with no independent third-party market sizing report in the provided sources.

Who Else Is Fighting for This

MIXED

Pulley is positioning itself against general permit expediters and workflow tools by packaging permitting expertise with software, rather than selling a generic project-management layer [Pulley, retrieved 2026] [GetApp, 2026].

Company	Positioning	Stage / Funding	Notable Differentiator	Source
Pulley	AI-assisted permitting software for commercial project teams	Seed, about $4.4 million disclosed over 1 round	Combines permitting expertise with workflow features such as custom permit plans, packet compilation, reviewer directory, status tracking, and a Procore integration	[Sourceforge.net, 2026] [Tracxn, 2026] [Pulley, retrieved 2026] [GetApp, 2026] [LinkedIn, 2026]
PermitPlace	Named competitor in permitting		Publicly identified in the structured research as a competitor to Pulley	[Structured facts]

The competitive field appears to break into three buckets. Second are adjacent construction workflow systems, most notably Procore, which Pulley integrates with rather than displaces, suggesting Pulley is trying to sit inside an existing preconstruction stack instead of replacing it outright [Pulley, 2026] [LinkedIn, 2026]. Third are offline substitutes, meaning internal permitting coordinators, consultants, and fragmented email-and-spreadsheet workflows, which Pulley is implicitly targeting through claims around online submission, document management, automated notifications, and comment-letter handling [Pulley, retrieved 2026] [Sourceforge.net, 2026].

Pulley’s current edge is narrow but legible. The product surface is more specific than a generic task tracker: custom permit plans, automatic packet compilation, reviewer directories, compliance checks, and embedded Procore connectivity all point to a workflow built around the paperwork and sequencing of entitlement and permit review, not just project administration [GetApp, 2026] [Pulley, retrieved 2026] [LinkedIn, 2026]. That kind of specificity can matter because permitting is process-heavy and local-detail dependent. The durability question is less settled, since most of the evidence for product differentiation comes from company materials or software-directory summaries rather than independent usage data, and the claim that customers see up to 2x faster approvals remains company-reported [Pulley, retrieved 2026].

The company looks most exposed where incumbents already own the surrounding workflow or customer relationship. Procore has stronger platform gravity in construction software, and Pulley’s integration helps distribution while also underscoring that the system of record may sit elsewhere [Pulley, 2026] [LinkedIn, 2026]. That leaves Pulley dependent on proving that a software-plus-expertise model is materially better than either a services-first permitting shop or a broader construction platform with permitting features added over time.

The most plausible 18-month scenario is a share contest for teams that already run preconstruction in connected software but still treat permitting as an exception process. Pulley is the likely winner if embedded integrations, reviewer intelligence, and packet automation translate into repeatable time savings across retailers, developers, contractors, and architects, especially since those are the customer groups it publicly cites today [The Org, retrieved 2026] [LinkedIn, retrieved 2026] [Built In NYC, retrieved 2026]. PermitPlace is the likely winner if buyers continue to prefer a higher-touch permitting partner over a software-centric workflow, or if category expansion by larger construction platforms compresses the room for an independent specialist. On public evidence alone, Pulley has a credible wedge, but not yet a deeply corroborated moat.

Opportunity

PUBLIC

The prize here is meaningful if Pulley can become the operating system for commercial permitting, because permitting sits early in the construction workflow, touches multiple stakeholders, and carries schedule risk that owners, contractors, architects, and developers all feel directly [Pulley, retrieved 2026] [The Org, retrieved 2026].

The headline opportunity is not simply selling another workflow tool. It is becoming the default system of record for permit planning, packet assembly, submission tracking, reviewer communication, and approval intelligence across commercial projects, with enough workflow depth that project teams standardize on it before a shovel hits the ground [Pulley, retrieved 2026] [GetApp, 2026] [Sourceforge.net, 2026]. That outcome looks reachable, not merely aspirational, because the public evidence points to a product that already spans several adjacent jobs to be done: custom permit plans, automatic packet compilation, status-change notifications, comment-letter parsing, reviewer directories, and an embedded Procore integration [GetApp, 2026] [Sourceforge.net, 2026] [LinkedIn, 2026]. If the product consistently shortens approvals, even the company-stated claim of up to 2x faster approvals suggests a high-value budget line for customers whose carrying costs and opening timelines depend on permit speed [Pulley, retrieved 2026].

There are a few distinct ways that upside could compound into venture-scale outcomes.

Scenario	What happens	Catalyst	Why it's plausible
Workflow standard in commercial permitting	Pulley becomes the standard software layer used by developers, retailers, contractors, and architects to coordinate permit work across projects and jurisdictions	A broadening base of reference customers and repeat use cases across project types, including apartment buildings, office space, homes, and stores [Built In NYC, retrieved 2026]	Public materials already place the product with several buyer groups and cite named customers including AutoZone, Wood Partners, HITT, and JHET, which suggests cross-vertical applicability rather than a single niche [Promptloop.com, retrieved 2026] [The Org, retrieved 2026]
Embedded preconstruction infrastructure	Pulley becomes the permitting layer inside larger construction software stacks rather than a standalone point solution	The Procore integration and public positioning around a more connected preconstruction workflow [Pulley, 2026] [LinkedIn, 2026]	Construction software markets often consolidate around systems that sit inside broader project workflows. Procore's published view that the partnership strengthens a connected preconstruction solution gives some support to that path [Pulley, 2026]
Jurisdiction intelligence moat	Pulley accumulates enough permitting data and workflow knowledge to make project-specific permit planning and review prediction materially better over time	Expansion into additional local markets, such as Denver, and repeated use across similar project categories [Permitting Talk, retrieved 2026] [GetApp, 2026]	The product already appears to organize reviewer contacts, permit plans, packet preparation, and comment handling. Those are the raw materials for a data advantage if usage depth increases across markets [GetApp, 2026] [Sourceforge.net, 2026]

The compounding mechanism here is straightforward. Each completed permit process can improve the next one if Pulley captures structured knowledge about submittal requirements, reviewer behavior, packet composition, comment patterns, and project-type differences, then feeds that back into planning and automation features [GetApp, 2026] [Sourceforge.net, 2026].

That matters because permitting is repetitive without being fully standardized. A platform that helps users identify requirements upfront, collaborate on submittals, monitor status in real time, and interpret comment letters can create a practical data moat, especially if it is used by the same account across many sites or by multiple firms in the same local market [LinkedIn, retrieved 2026] [Pulley, retrieved 2026]. The Procore integration also raises the possibility of distribution lock-in: once permitting data is connected to a broader preconstruction workflow, replacing the system becomes more operationally costly [Pulley, 2026] [LinkedIn, 2026]. The JLL Austin case study, while company-published, is directionally useful because it suggests repeat use across multiple project types rather than a one-off pilot [Pulley, retrieved 2026].

The size of the win is hard to quantify cleanly from the public record because no credible market-size dataset was provided in the source set. A reasonable upside frame is strategic value rather than a precise forecast. If Pulley became the clear software infrastructure layer for commercial permitting, a plausible endpoint could be acquisition or platform-level valuation interest from a larger construction software player seeking deeper preconstruction workflow control, particularly given the existing Procore integration and the cross-functional nature of the problem [Pulley, 2026] [LinkedIn, 2026]. In that scenario, not a forecast, Pulley would be worth materially more than a narrow workflow tool because the asset would combine system-of-record behavior, embedded workflow position, and accumulated permitting intelligence. The public evidence does not support a precise valuation range, but it does support the core upside case that this is a workflow with real economic pain, repeated usage, and some early signs of integration-led distribution.

Single-source, plausible -- This section relies on a mix of company materials and third-party directory or review sources, with partial corroboration from LinkedIn, GetApp, SourceForge, The Org, Built In NYC, and Permitting Talk.

Sources

From the public record

1. [Pulley] Pulley | https://www.withpulley.com/

2. [Pulley, 2026] Pulley Launches Procore Integration for Permitting | https://www.withpulley.com/resources/pulley-launches-procore-integration-to-streamline-permit-process

3. [Y Combinator] Pulley: Pulley helps founders and finance teams manage their equity and cap… | https://www.ycombinator.com/companies/pulley

4. [Ashbyhq.com] Project Manager, Permitting [Utah] @ Pulley | https://jobs.ashbyhq.com/withpulley/d9972994-96fd-4226-9dfd-38a284fc5231

5. [LinkedIn, 2026] Pulley Launches Embedded Procore Integration ... | https://www.linkedin.com/company/pulleyhq/

6. [GetApp, 2026] Pulley 2026 Pricing, Features, Reviews & Alternatives | GetApp | https://www.getapp.com/

7. [Sourceforge.net, 2026] Pulley Reviews in 2026 - Permit Software | SourceForge | https://sourceforge.net/

8. [TechCrunch, 2021] Founders: How well do you really understand seed-stage financing? | TechCrunch | https://techcrunch.com/2021/07/19/founders-how-well-do-you-really-understand-seed-stage-financing/

9. [Tracxn, 2026] Pulley - 2026 Company Profile, Team, Funding & Competitors - Tracxn | https://tracxn.com/

10. [The Org] Pulley | The Org | https://theorg.com/org/pulley

11. [Promptloop.com] What Does Pulley Do? | Directory | Promptloop.com | https://www.promptloop.com/directory/what-does-pulley-do

12. [Permitting Talk] Pulley Software Firm's Expansion to Denver to Enhance Construction Permit Approval Process | https://www.permittingtalk.com/

13. [Crunchbase] Pulley - Crunchbase Company Profile & Funding | https://www.crunchbase.com/organization/pulley

14. [Built In NYC] Sales Development Representative - Pulley (withpulley.com) | Built In NYC | https://www.builtinnyc.com/job/sales-development-representative/4768612