Pirros Is GitHub for Construction Drawings, With Reusable Details

01 /The Concept

Pirros calls itself "GitHub for the construction industry" on its Y Combinator profile – and unlike most companies that borrow that framing, it actually means the library half of what GitHub does, not just the collaboration half.

The platform is a repository for architectural and engineering drawings, organized into project catalogs. Managing a construction project's drawing set – multiple floors, projections, structural systems, detail levels – across a team of designers is genuinely messy. Version control alone is a recurring headache. Pirros addresses that.

But the core value proposition is something more specific: reuse. A typical new construction project is roughly 50% standard elements – components that appear in nearly every building of a given type. And around 90% of those standard elements have already been designed at some point by someone in the firm. The problem is that designers usually don't know this, can't easily find the prior work, and default to redrawing everything from scratch. The time cost is substantial.

Pirros makes those prior drawings searchable by multiple criteria and parameters. When a designer needs a specific structural detail for a new project, they can find and pull a version that was created for an earlier job – then make minor adaptations rather than starting from zero. Each adaptation cycle also improves the component: past errors get corrected, edge cases get handled, and the improved version becomes the new standard. Reuse doesn't just save time; it compounds quality.

The platform integrates natively with Revit, the dominant design software in the industry. Components pull automatically into Pirros with keywords and metadata, and can export back into new Revit projects. Designers can mark favorite components and share links with colleagues, building shared libraries alongside their personal ones.

Pirros was founded last year, graduated from Y Combinator with $500K, brought on approximately 30 client firms, and has now raised $2M in follow-on funding.

02 /Why It Matters

Construction is one of the last large industries where digital transformation has lagged badly relative to the revenue scale involved. That lag creates persistent opportunity for new platforms, but with an important qualification: the gap isn't in design software – that's been mature for decades. The gap is in the business processes that surround design work.

Digs, [covered earlier](/review/sozhrjom-ego-po-kusochkam), raised $7M while still in beta by building a collaboration platform for designers, builders, and homeowners on residential construction and renovation projects. AllSpice, [covered here](/review/glavnye-dengi-u-konservatorov), took the same "GitHub for engineers" framing and applied it to electronics hardware design – emphasizing team collaboration rather than individual CAD work – and raised $9.8M including $6M in a single round this past July. ResearchHub, with Brian Armstrong as co-founder, raised $5M [with a similar collaborative repository model](/review/s-pravilnym-podhodom-tut-est-dengi) for scientific papers.

What these examples share is a focus on process infrastructure rather than creation tools. Pirros fits that pattern precisely: it doesn't compete with Revit; it makes Revit's output reusable in a way that compounds across projects.

The "GitHub for X" framing typically emphasizes version control and team collaboration – the features that GitHub itself foregrounds. Pirros is notable for leaning into the other major function: a library of components available for reuse and modification. That's the feature that makes the platform's ROI immediately calculable in hours saved per project.

03 /Opportunities

Construction is not uniquely characterized by reusable-element workflows. The same pattern – large portions of new deliverables assembled from prior-work components, with significant search friction preventing reuse – appears across professional services broadly.

B2B sales is an obvious case: proposals are routinely assembled from prior proposal sections adapted to new clients, and presentation decks are built from existing slides rearranged and updated. There's no dedicated platform for managing that content at the component level – most teams use shared drives with inconsistent naming conventions and hope for the best.

Kive, [covered previously](/review/fig-chego-najdjosh), demonstrates the model in photography: a platform that auto-tags a photographer's image library so they can search for prior shots matching specific creative criteria rather than reshooting from scratch. It raised $8.8M, with $7M in a single round. The underlying idea – structured metadata over a component library to enable intelligent retrieval – is the same one Pirros applies to construction drawings.

The generalizable product form is a component library with intelligent search, purpose-built for a specific category of professional work where new deliverables are substantially assembled from prior ones. Architecture, electronics, B2B sales, creative production, legal documents, and engineering specifications all fit that pattern. The first platform to establish itself in each category will own a durable workflow asset that compounds in value as the library grows.