The challenge.
What changed with Conductor.
The outcomes.
This is a HUGE step forward for MSHDA. Very different than our old days of huge three-ring binders.
Michigan State Housing Development Authority, May 2026Overall, this system is fantastic. It was pretty easy to follow, it is visually well designed and was fairly intuitive to follow. I am really looking forward to seeing how the implementation of this continues to improve workflow and communication. This is a HUGE step forward for MSHDA. Very different than our old days of huge three-ring binders.
Administrators define Notice of Funding Availability rounds with question sets that change based on the project type. Configured by program staff in the admin interface, not coded.
A fully digital intake process where developers submit initial data. Logic-driven forms ensure only relevant questions and document requirements surface. The same developer record carries through every subsequent stage.
Spreadsheet sovereignty meets database intelligence. Teams continue using familiar Excel models for complex what-if scenarios while high-value data (unit counts, rental prices, cash flow projections) is automatically extracted into the central database. Every iteration versioned for audit.
External developers see only their cases. Housing development officers manage the pipeline. Certifiers (legal, marketing, environmental) are auto-assigned tasks based on workflow triggers. In-app communication replaces email chains.
Underwriting Committee kills unviable projects early, saving downstream resources. Loan Committee and Board approvals tracked with strict version control on post-approval revisions. Automated staff report generation aggregates certifier inputs into the board package.
After closing, the same record carries through 20 to 30 years of compliance monitoring. Asset management runs from the same platform that ran underwriting. OData feed surfaces live data for Capital Needs Assessments and federal reporting.
Every document a deal needs to close, tracked to one record: status, version, and who's holding it up. Redlines move from email into the system, with every pass logged. E-signature and wet-sign documents both tracked to completion and compiled into the closing binder when the deal is done.
Video walkthroughs of each surface are in production and will be added here once cut.
This is a HUGE step forward for MSHDA. Very different than our old days of huge three-ring binders.
Michigan State Housing Development Authority, May 2026Four audiences. Four different problems. One record.
Need a program template that isn't on this list? New templates can be configured in your own tenant and added to the library for other agencies that need them. Talk to us.
A deep dive into the housing development lifecycle on Conductor: the configurable NOFA architecture, the hybrid proforma engine, multi-party role-based access, certifier workflows, committee gate approvals, automated staff report generation, document-tracked closings, board docketing, and long-term compliance monitoring. Plus the MSHDA deployment, compliance posture, and what an implementation looks like.
Something went wrong sending the form. Your details are still here; please try again, or email us directly.
Administrators define Notice of Funding Availability rounds with question sets that change based on project type. New rounds stand up from templates without engineering. Scoring criteria configured in admin UI, versioned for audit.
Keep your Excel models; the numbers flow into the database. Teams keep complex modeling in familiar spreadsheets while high-value data feeds cross-deal analysis. Every iteration version-controlled.
External developers, their counsel, and their lenders see only their own cases, admitted by invitation. Housing development officers manage the pipeline. Certifiers (legal, marketing, environmental) are auto-assigned tasks via workflow triggers. In-app communication replaces email chains.
Marketing, legal, and environmental reviews run in parallel rather than blocking each other. The next decision surfaces the moment its dependencies are ready. Sequential bottlenecks eliminated.
Every document a deal needs to close gets its own status, its own version history, and its own review record. Redlines that used to run over email happen in the system instead. When the deal closes, the documents compile into the closing binder.
Staff compile board packets from live case data, route them through manager and legal-director review, and track the docket through approval, conditions, or a send-back. Loan Committee and Board approvals carry strict version control on post-approval revisions.
Aggregates data and narratives from all certifiers to auto-generate the staff report required for board review. Weeks of manual compilation reduced to platform output.
After closing, the same record carries through 20 to 30 years of compliance monitoring. Asset management workflows run from the same platform. Federal compliance reporting from live data.
Configurable dashboards show pipeline health, allocation efficiency, and where a deal is sitting, and with whom. OData feed surfaces live data for Excel, Power BI, and Tableau. Asset management runs Capital Needs Assessments from the same record that ran underwriting.
Conductor is available through established purchasing vehicles: TXShare Cooperative MSA (#2025-018), Texas DIR-CPO-5958 (DBITS Software Services), GSA Multiple Award Schedule (GS-35F-160CA), and TIPS Contract (#220105). When the fit is clear, the right vehicle gets the work started without a full solicitation cycle.
SOC 2 Type II · ISO 27001, 27017, 27018 · NIST SP 800-53 · HIPAA-ready · WCAG 2.1 AA and Section 508. Built on a FedRAMP Moderate authorized platform. Applications can be deployed into FedRAMP Moderate or High environments where a contract requires it; commercial cloud as standard. Your agency retains exclusive ownership of all data, documents, configuration, and audit logs, with real-time access through an OData connector for Power BI or Tableau, and structured exports plus a Certificate of Data Destruction on exit.
SOC 2 Type II, ISO 27001, ISO 27017, and ISO 27018. Reports are available on request to support agency vendor risk assessments.
Built on a FedRAMP Moderate authorized platform. Applications can be deployed into FedRAMP Moderate or High environments where a contract requires it; commercial cloud as standard for programs without a federal authorization requirement.
Applications inherit platform-level control implementation and add engagement-specific controls. Delivery aligns with StateRAMP Moderate where required by state contract.
Business Associate Agreements are supported. Encryption, access controls, audit logging, and breach notification align with the HIPAA Security and Privacy Rules where an application processes protected health information.
Accessibility is designed in from the first sprint, not audited at the end. Automated scanning runs every sprint, and screen reader testing with NVDA, JAWS, and VoiceOver covers critical workflows before release. An Accessibility Conformance Report in VPAT format is produced as a delivery artifact.
TLS 1.2 or 1.3 in transit and AES-256 at rest. Every environment uses an isolated database instance. Permissions are enforced at the data model, so a restricted user cannot reach protected data even through an API.
Cloud agnostic. Deploy on the cloud you choose. Azure, Google Cloud, and agency-controlled environments are supported alongside AWS.
We'll walk you through a working Conductor deployment with real developer portals, real certifier workflows, the proforma engine in production, and an honest conversation about how Conductor would fit your housing finance operations.
Already know it fits? Conductor is available through GSA (GS-35F-160CA), Texas DIR (DIR-CPO-5958), TXShare (#2025-018), and TIPS (#220105), so we can start without a full solicitation cycle.
Craig Smith, Partner, Kinetech PSN craig.smith@kinetechcloud.com 773-230-5157