Client
BuildingLink
Role
Lead Product Designer, Product Management
Type
Proptech SaaS, AI-augmented design

Property managers run capital projects and vendor work in spreadsheets, email, and tools their boards never open. BuildingLink was retiring its Alterations module and needed something bigger: a project tool with a Kanban board, vendor bidding, maintenance tracking, and automated board reporting.
I led design on the feature and used it to test a new workflow. Claude turned raw inputs into structured product documents, and Figma MCP let it build screens from BuildingLink's real design system. The decisions stayed with me and the product team.
Where AI fit into my process
The leverage came before any screens. I built four linked documents with Claude, and each one fed the next. By the time work reached Figma, the AI knew the customer problem, the scope, the screen inventory, and the design system rules. That's why the output looked like BuildingLink.

Opportunity brief
I gave Claude our brief template, three customer interview transcripts, help docs, and a scoping call recording. It drafted the problem, scope, flows, and open questions, and tied customer quotes to the features they supported.

User story inventory
Claude wrote the user stories and a first-pass estimate. I added confidence ratings that turned a single number into a range (193–237 points), next to a blank column for engineering's final estimate.

Design brief
A page-by-page inventory of 17 screens, each with its purpose, actions, and linked epics. It became the design checklist and caught easy-to-miss touchpoints in other modules.
Design system speccing
This is the key document. It condenses our design system into decision rules, such as dialog vs. new page or snackbar vs. alert, plus required states for every screen. Claude loads it before speccing anything.

Challenges and solutions
Challenge
AI screens that don't look like the product
AI design tools are fast, but they default to generic patterns. Left alone, they produce screens that look like any SaaS app, not BuildingLink, and they skip the loading, empty, error and permission states every real screen needs. Cleaning that up by hand would wipe out the time saved.
Solution
Figma MCP plus a design system Claude understands
Claude built screens with real BuildingLink components and tokens, with loading, empty, error, and permission states included.


Challenge
Boards never look at project trackers
Every property manager we interviewed had tried an outside tool that their board ignored.
Solution
Details that go to the board
Board members rarely log in, so the details page is built to be scanned in seconds: status and progress at the top, key facts in one row, then attachments, assigned vendors with bid dates, and a running activity log. Everything they’d ask about is on one page.

Challenge
Vendor bids buried in email
Requesting and comparing bids happened entirely outside the system.
Solution
A guided bid flow with a no-login vendor page
Property managers request bids from the project. Vendors respond through a simple link with no account needed. Bids are compared side by side, and a winner is picked in one click.


Property manager in Atlanta
© 2026 Brian Needles. Designed in Philadelphia.