Question 1

What does eligibility screening do?

Accepted Answer

Given a building's age, zoning, and use, it determines whether a conversion qualifies for a ministerial (by-right) path or requires discretionary review — before design time is spent on a path that won't work.

Question 2

How is existing-building compliance different from new-construction code check?

Accepted Answer

Existing-building work runs against the alteration/existing-building code (IEBC) and conversion ordinances — not only new-construction code. plinth.OS is built for that less standardized rule set.

Question 3

What does Otto handle?

Accepted Answer

Otto assists with discretionary and site permits — variances, conditional use permits, grading, encroachment, environmental clearance — with hearing-date tracking and commission context. A licensed architect or reviewer signs off before anything is filed.

Question 4

Does AI file permits for us?

Accepted Answer

No. A licensed architect or reviewer signs off before anything is filed — human sign-off is a trust feature, not a limitation.

Question 5

How does pricing work?

Accepted Answer

Three flat tiers: Starter at $0/mo, Studio at $5,000/mo, and Enterprise custom. There is no success-fee layer on customer-facing pricing.

Question 6

What's on the roadmap?

Accepted Answer

The permitting core is what we sell today. Directional next: conversion-specific procurement and cost estimation, construction change-order and condition-of-approval tracking, and digital twin handover for converted assets — see /roadmap.

Question 7

Who is plinth.OS for?

Accepted Answer

Architects at small-to-mid practices (under 50 staff) doing renovation, addition, and conversion work — especially adaptive reuse and office-to-residential.

Question 8

Who owns our project data?

Accepted Answer

You do. Anonymized eligibility and conversion-outcome data licensed to insurers, lenders, and municipalities is opt-in only — same wording as the Pricing footnote.

For press & investors