CUSTOM SOFTWARE · DEAL OPERATIONS
Replacing a generic CRM with the way healthcare deals actually move.
A two-sided operating platform for advisors, healthcare-facility listings, documents, and vetted private-equity buyers.
- Industry
- Healthcare real estate
- Role
- UX architect & project manager
- Relationship
- Prior team work
- Period
- 8-month product build
- Documented proof
- 40% faster inquiry-to-close
System model
Conceptual · not product UI
Advisor
Manages opportunity
Facility
Single asset or portfolio
Deal
The operating center
Buyer
Vetted access
Documents
Files · photography
Permissions
Who can see what
The model organizes the transaction, rather than treating it as notes attached to a contact.
01 / Constraint
The old system understood contacts. The business ran on deals.
Healthcare real estate transactions involved advisors, vetted buyers, hundreds of facility listings, documents, photography, access rules, and both single-property and portfolio opportunities. An off-the-shelf CRM could store names, but it could not represent the work around them.
02 / Analysis
Model the business before designing the screens.
The team mapped the operating objects, their relationships, the permissions each participant needed, and the actions that moved a deal forward. That model became the product architecture.
System architecture
Objects, permissions, and actions before interface polish.
The original product is private. This diagram communicates the operating model without fabricating a screen.
System model
Conceptual · not product UI
Opportunity
Facility or portfolio
Vetted access
Buyer permissions
Diligence
Documents · photography
Inquiry
Visible next action
Decision
Advisor and buyer
Close
One shared record
03 / Architecture
One late requirement could have broken the product.
Portfolio deals changed the relationship between facilities, documents, buyers, and inquiries. Treating that requirement as an extra screen would have created brittle exceptions. The underlying model was adjusted so single assets and portfolios could move through the same system.
04 / Intervention
One operating environment for both sides of the transaction.
Working with two UI designers and a distributed development team, the project delivered advisor and buyer experiences, listing management, document and photography workflows, permissions, and a visible deal pipeline over eight months.
05 / Impact
Deals moved faster.
The documented result was a 40% reduction in inquiry-to-close time. The gain came from putting the actual transaction model in one operational system, not from adding another layer to the generic CRM.
What this carries forward
Sometimes SaaS is the shortcut. Sometimes SaaS is the constraint.
Relevant services
More selected work
More systems built around how the business works.
Have a similar constraint?
Tell us how the work runs today.
We will help determine whether the answer is AI, automation, better software, a simpler process, or something else.