Last updated: June 2024
This document serves as a repository for Blueprint's general terms of work with its nonprofit partners. It should set the expectations for Blueprint's specialization of work, development cycle, and work contract, so you can see if your organization is a good fit for Blueprint's services. Once an organization is selected to work with Blueprint, a customized version of this contract, along with all details of the project deliverables, will be signed by both parties.
Our projects require a large time investment for our developers and designers (see the next section, "Timeline"), showcasing our equally as great commitment towards your organization's success. The type of project that we look for is one that will enable your organization to scale and achieve a level of operation otherwise unreachable without the assistance of our technology. It does not matter how big or small you are already--if you believe that we can help you create meaningful change, pitch us your idea.
- A web portal for Black, LGBTQ+/SGL, and other marginalized communities to find and connect with organizations nationwide. See the demo, or see National Black Justice Coalition’s project recap →
- A progressive web application with offline capability to help electricians maintain solar powered grids. This app was handed off for internal use, but check out our custom documentation for users and developers! See Mee Panyar Project Recap →
- A customer rewards program and store locator mobile app (see it on the App Store) aimed at increasing accessibility to affordable healthy food in DC's food deserts through DC Central Kitchen's Healthy Corners stores. See DC Central Kitchen Case Study →
- And more of our past projects on our website or more detailed recaps on our Medium →
Examples of projects that will NOT be accepted: Redesigning a static website, refactoring old codebases to use newer technology, creating a mobile app "version" of already existing technology that is already effectively solving the problem.
Blueprint's developers have created many kinds of software. We specialize in web application and mobile application development, but these are by no means strict limitations. We are eager to hear your proposals.
For the tech savvy, our projects usually run on a React or React Native frontend. Recently, we've also started to use Typescript syntax and Firebase as a backend for some of our web and mobile apps. We strive to use the latest and most accessible technology, and this past year, we've had success building web apps using a combination of NextJS and Retool.
We are based at the University of California, Berkeley, and our developers are all students attending the university. We ask you to be cognizant of our development cycle, which is closely tied to our semesterly system of recruitment and breaks.
Exact dates may vary slightly.
Week 1 — September 7th
We have recruited all designers and developers for the semester. They are introduced to their respective project teams.
Week 4 — September 30th
Developers, designers and the project lead (which make up the project team) finalize project scoping and create the final contract of work between Blueprint and the nonprofit which is then signed by both parties. By this time, a digital prototype will have been designed and approved, and feature development is underway.
Note: When both parties agree to this project proposal, it should be agreed upon and set unless in otherwise unforeseen circumstances. There may be pivots or revalued features, but not a revamp that fundamentally changes the purpose and/or mission of what we are trying to achieve.
Week 8 — October 28th
First-quarter check-in. Project team and the nonprofit meet (either in-person or remotely) to check in and relay updates regarding design and development progress.
Week 14 — November 28th
Midpoint check-in. Project team and the nonprofit meet to check in. The minimum testable product (MTP) should be mostly complete at this time.
Week 16-21 — December 16th - January 17th
Project team remains on university break during this period.
Week 23 — February 7th
Blueprint recruits new members to fill in project team members that have graduated. Design and development resume.
Week 30 — March 24th
Third-quarter check-in. Project team and the nonprofit meet to check in. Any final feature adjustments and refinements should be made at this point.
Week 38 — May 5th - 19th
Project team meets at the NPO's office to give a live presentation and hand off final product. If this is not possible it will be held remotely.
Project teams and their nonprofits will try to meet every other week to give brief status updates regarding the project and answer any questions. More in-depth check-ins will be held quarterly over the entire development cycle. We want to have as open of a communication channel as possible, so we will always be open via email or phone to answer any questions or concerns.
Blueprint's services are offered completely pro bono. Our developers and designers are highly-skilled individuals who have had experience working at Silicon Valley's leading tech companies, but we're also students who share a concern for improving our community. We choose to donate our free time towards these humanitarian causes because we are confident that we can build the technology to help you realize your goals. All we ask is your continued commitment towards us throughout the year we work together.
Looking forward to working with you,
