Database Developer

Seeking Request for Proposals for Database Developer(s) -Contract Position- 1. Project Introduction: The Latino Community Foundation of Colorado (LCFC) seeks proposals from qualified database and analytics consultants to design and implement a centralized, cloud-based SQL database environment hosted in Microsoft Azure. The database will support internal reporting, data consolidation, and analytics through Tableau Cloud. The objective of this project is to create a centralized data layer that consolidates key operational information and supports reporting through Tableau Cloud. This project does not require the development of a custom web application. LCFC prefers consultants with experience supporting nonprofit organizations or organizations of a similar size, staffing, and data maturity. LCFC currently uses the following systems: • C-Suite by Foundant – primary system for CRM, grant management, donor, donation, and organization records. Historical donation records from prior platforms may be provided through exports where needed, but C-Suite is expected to serve as the primary donation system going forward. • Monday.com - Project management, expected to be treated as archival/export based unless a future reporting need is identified. • Mailchimp - Email communications platform, expected to be treated as archival/export based unless a future reporting need is identified. • SurveyMonkey - Survey collection platform, expected to be treated as archival/export based unless a future reporting need is identified. LCFC will retain full ownership of the database schema, dashboards, SQL code, data pipelines, tableau workbooks, and all data assets created as part of this project. 2. Project Objectives: • Design and implement a scalable, Azure-hosted SQL database environment. • Create a centralized organization table to serve as the primary organization reference point across systems where applicable. • Establish a single LCFC organization identifier that can map records from source systems where applicable. • Support LCFC managed organization record alignment by providing the necessary table structure, templates, and validation views. • Integrate, ingest, or archive data from LCFC systems based on business value, reporting need, and return on investment. • Centralize core transformation and business logic within SQL views wherever practical. • Develop Tableau Cloud data sources and foundational dashboards that allow staff to: o Filter by organization. o Apply keyword-based filters. o View defined reporting queries. • Configure role-based access controls within Tableau Cloud. • Deliver documentation sufficient for LCFC to maintain the system internally after project completion. 3. System Architecture Requirements: The proposed solution must: • Use Microsoft Azure as the cloud environment for the centralized SQL database. • Use Tableau Cloud as the analytics and dashboard platform. • Use a centralized SQL database as the authoritative data layer for modeled warehouse data. • Use the centralized organization table as the primary reference point for organization level reporting across integrated tables where applicable. • Store transformation and business logic within SQL views wherever possible. • Support Tableau Cloud reporting through published data sources or SQL views. • Prioritize standard SQL and Tableau Cloud functionality. Respondents must provide a proposed system architecture diagram showing: • Source systems. • Data ingestion or archival process. • Azure database environment. • Data pipeline or ETL process. • Tableau Cloud connection. • Security and access model. • Backup and recovery approach. Proposals must include a written rationale explaining the recommended architecture, including considerations for cost, maintainability, security, performance, scalability and long term support. 4. User Roles and Access Levels: The system must support two primary access levels: Administration User Level • Limited to designated LCFC staff. • Ability to: o Create and maintain SQL queries and views. o Publish and manage Tableau dashboards. o Manage refresh schedules. o Configure Tableau permissions. • Access granted only upon written supervisor approval and authorization by the CEO or Vice President. Staff User Level • Read only access within Tableau Cloud. • Ability to: o View dashboards. o Filter by organization. o Apply keyword-based filters. • Staff users will not write SQL or modify underlying data structures. 5. Scope of Work A. Discovery and Requirements • Review LCFC’s current systems, data structures, exports, and reporting workflows. • Conduct stakeholder sessions to define reporting and filtering requirements. • Document data sources, access methods, and integration constraints. • Identify which data sources should be fully integrated, lightly structured, or archival only. • Confirm Phase 1 versus future-phase requirements. Refresh cadence will be determined during discovery based on reporting needs, source system capabilities, and implementation cost. LCFC does not require real time data synchronization. B. Database Design and Integration • Design an Azure-hosted SQL database structure appropriate to LCFC’s size, data volume, and reporting needs. • Establish a centralized organization table. • Create source system mapping fields or tables that allow LCFC to align organization records across systems. • Document schema, field definitions, and transformation logic. • Provide templates or validation views to support LCFC managed organization matching. • Build reusable SQL views for Tableau reporting. The Consultant is not expected to perform fuzzy matching or deduplication of organization records. Due to LCFC’s record volume and internal knowledge of organizational relationships, LCFC will complete and validate organization matching internally. The consultant should provide the necessary table structure, templates, and validation views to support this process. C. Source System Classification During discovery, the consultant will work with LCFC to classify each data source as one of the following: • Fully integrated reporting source. • Limited export based ingestion source. • Archival source for historical reference. • Future phase source. Not all listed systems are expected to require full API integration. Systems with limited reporting value, sufficient native dashboards, or primarily ad hoc usage may be handled through scheduled exports or archival storage rather than automated API pipelines. Expected initial classification: Core Modeled Source: C-Suite by Foundant • Expected to serve as the primary operational source for donor, donation, grant, organization, and CRM related records. Archival / Export Based Unless Otherwise Justified: Monday.com • Project management data is expected to be treated as archival/export based unless LCFC identifies a compelling cross system reporting use case. Mailchimp • Campaign and email engagement data may be retained through exports or archival storage unless LCFC identifies a recurring reporting use case requiring modeled integration. SurveyMonkey • Survey exports may be retained for archival reference unless a recurring structured reporting need is identified. D. Data Integration, Validation, and Lineage The proposed solution must include a clear methodology for validating data accuracy across all integrated or ingested systems. The consultant must describe how they will: • Verify that data is being correctly retrieved from each source system. • Test API based or export based integrations for completeness and consistency. • Identify and handle discrepancies between source systems and the warehouse. • Validate selected warehouse outputs against source system data. • Document data lineage, including where data originated and how it is transformed. • Provide visibility into pipeline success, failure, and refresh status. Because integration across multiple systems is a primary project risk, proposals must describe how the vendor will mitigate data inconsistency, access limitation, API failure, and validation risks. E. Tableau Data Sources and Foundational Dashboards • Develop and publish centralized Tableau Cloud data sources connected to the Azure SQL database. • Configure role-based permissions within Tableau Cloud. • Create a limited set of foundational dashboards sufficient to: o Validate organizational level filtering. o Demonstrate keyword-based filtering. o Confirm that defined SQL driven queries surface correctly. o Demonstrate that Tableau can reliably consume the curated SQL views. Final executive and strategic dashboards may be developed and maintained by LCFC staff following project completion. F. Iterative Development • Follow structured development cycles. • Conduct demonstrations with LCFC at the conclusion of each development cycle. • Incorporate structured feedback during development phases to refine functionality and usability. • Provide progress updates sufficient for LCFC to understand what has been completed, what remains, and where risks exist. • Identify project risks, blockers, or decisions needed from LCFC in a timely manner. 6. Data Privacy, Security, and Recovery: The selected consultant will be required to maintain the confidentiality of all LCFC data accessed during the engagement. This includes donor data, grantee data, survey responses, internal operational data, and any other sensitive organizational information. Consultants may be required to execute a confidentiality or non-disclosure agreement prior to accessing production systems. Proposals must describe the vendor’s approach to: • Data security and access controls. • Protection of sensitive organizational data. • Role based access management. • Credential and secret management. • Backup and recovery strategy. • Disaster recovery considerations. • Mitigation of potential vulnerabilities within the data pipeline and storage environment. LCFC must retain administrative ownership of the Azure environment, database, Tableau Cloud assets, and all related configuration where applicable. 7. LCFC Responsibilities: LCFC will support the project by: • Providing access to required systems and data sources. • Designating a product owner to provide direction and approve deliverables. • Making staff available for requirements discussions, feedback sessions, validation, and training. • Providing timely feedback during development cycles. • Reviewing and approving organization matching decisions. • Validating selected datasets against source systems where internal business knowledge is required. 8. Project Timeline: LCFC anticipates a project duration of approximately 3-6 months, to be finalized collaboratively with the selected consultant. Work is expected to be delivered in structured phases, including: • Discovery and requirements validation. • Architecture design and approval. • Data model design and approval. • Source system classification. • Integration, ingestion, and archival process implementation. • Tableau data source configuration. • Foundational dashboard development. • Testing, validation, and lineage documentation. • Staff feedback and refinement. • Documentation and training. • Go-live and transition. The selected consultant will propose a detailed project timeline and milestone plan as part of their submission. LCFC expects regular progress updates and demonstrations throughout the project to ensure alignment and timely course correction. 9. Deliverables: The consultant(s) will deliver: • An Azure hosted SQL database fully accessible to LCFC. • Proposed architecture diagram and technical rationale. • Database schema and source system mapping structure. • Centralized organization table structure. • Organization mapping table or template for LCFC managed record alignment. • Documented SQL views and transformation logic. • Data classification recommendation for each source system. • Automated data pipelines where approved and justified. • Export based ingestion or archival process where appropriate. • Data validation and lineage documentation. • Demonstration of data accuracy through validation of selected datasets against source systems. • Published Tableau Cloud data sources. • Foundational Tableau dashboards validating system functionality. • Configured role based access within Tableau Cloud. • A staff user guide. • Administrator system and maintenance manual. • Recorded demo videos reflecting the final production configuration. • Training sessions for administrators and staff. All database schemas, SQL code, integration scripts, Tableau workbooks, documentation, and related configuration assets must be transferred to LCFC upon project completion. Documentation must be sufficient to allow LCFC staff to independently maintain, modify, and extend the system without ongoing vendor dependency. 10. Acceptance Criteria: The system will be considered complete when the following conditions are met: • Azure SQL database environment is implemented and accessible to LCFC administrators. • Approved source systems are integrated, ingested, or archived according to the agreed source classification. • Data refresh, ingestion, or archival processes function as documented. • Centralized organization table structure and mapping approach are implemented. • Database structure supports LCFC managed organization matching across source systems. • Data outputs have been validated against selected source systems for accuracy. • Data lineage and transformation documentation has been delivered. • Tableau Cloud data sources successfully connect to the curated SQL views or approved data tables. • Organization level filtering and defined reporting queries function correctly within Tableau Cloud where applicable. • Staff are able to independently navigate and use foundational dashboards. • LCFC administrators are able to manage SQL views, refresh processes and Tableau updates without vendor assistance. • All required documentation has been delivered and approved by LCFC leadership. Final project acceptance will occur upon formal review and approval by LCFC’s designated Product Owner. 11. Change Management: This RFP defines the expected scope of work for the project. Any material changes to scope, deliverables, timeline, or budget must be documented and approved in writing by LCFC prior to implementation and execution. During the project, additional feature requests or enhancements may be identified. Such requests will be evaluated collaboratively and, if approved, may be incorporated into future phases or handled through a formal change order process. The selected consultant will provide a detailed project plan at initiation, including milestones and dependencies, to support alignment and minimize scope drift. 12. Proposal Submission: Proposals will be reviewed on a rolling basis. Complete proposals must be submitted by Wednesday, July 8, 2026 at 11:59 pm Mountain Time. Proposals that do not address the required submission elements outlined in this RFP may be considered non-responsive and may not be evaluated. Submissions must include: • Proposed total project cost, with a breakdown by major phase or workstream. • Estimated project timeline and milestone structure. • Proposed Azure architecture and rationale. • Proposed approach to Tableau Cloud integration. • Proposed approach to source system classification. • Description of relevant experience designing SQL data models and implementing Tableau Cloud environments. • Experience with Azure hosted SQL database environments. • Experience integrating CRM, grant management, or similar operational systems. • Experience working with nonprofit organizations or organizations of a similar size, staffing, and data maturity. • Description of proposed approach to data validation, lineage, and quality assurance. • Description of security, access control, backup, and recovery approach. • Identification of project team members, their technical background and their roles. • At least one example of a comparable project, including references. Selected finalists may be asked to: • Demonstrate a similar completed project. • Walk through their proposed technical architecture. • Explain data integration and validation methods. • Provide clarification on assumptions included in their proposed cost. About the Latino Community Foundation of Colorado: The Latino Community Foundation of Colorado (LCFC) is a state-based 501(c)3 philanthropic foundation. We invest in nonprofit organizations, grassroots leaders, and bold ideas that spark systemic change and create pathways for community wellbeing. The Latino Community Foundation of Colorado is not an endowed foundation.