Exhibit C (Developer Materials)

This exhibit organizes all pre-existing materials used in a project into two groups: those owned by the developer and those owned by third parties. Its purpose is to make ownership and usage rights clear so the team can build in accordance with the main agreement and the project specifications. It is typically executed with the master contract for the engagement and helps prevent disputes over prior work, license scope, or later improvements created during the project.

Each listed item should include a concise written description, links or references to documentation, and the intended use within the product or site. Identify the owner, the contact person, and any required approvals. Note whether use is limited to the project or broader, and whether attribution or other statements are required.

When third parties are involved, include license terms, expense responsibilities, and any processing steps to obtain permissions. Every asset must be clearly identified and associated with a deliverable so the team can carry the correct rights forward.

Operationally, complete this schedule prior to proceeding with build work. The developer and client should confirm who is responsible for approvals, how to request additions or substitutions, and how changes will be reported. If questions arise, the developer can provide assistance to gather missing information. Good practice includes documenting design concepts, code libraries, media, fonts, data sets, and tools, and recording any constraints that affect deployment or integration.

Typical use cases include a website build that relies on a developer's framework plus third-party libraries and stock images; a mobile app that incorporates prior modules for authentication and mapping; or a data-processing solution that uses pre-existing connectors and licensed datasets. In each scenario, the exhibit presents what comes from the developer, what comes from others, and who bears the expense and risk for approvals, ensuring the project proceeds in an orderly manner and in accordance with the specifications.

The Proposal Kit can help teams prepare this schedule and related documents. Its document assembly streamlines creation of exhibits and attachments, automated line-item quoting supports budget clarity, the AI Writer can write supporting documentation, and the extensive template library makes it easy to tailor clear, professional materials for your next engagement.

Beyond listing assets, this exhibit functions as a governance tool for risk, cost, and compliance. Treated as a living inventory, it helps teams present a single source of truth at kickoff and during reviews. Product owners and procurement can quickly see the association between each component and its deliverables, licenses, and approvals, which reduces rework and delays.

Finance gains clearer forecasting because third-party licenses, attribution duties, and limits are visible before the build begins. Legal and IT can standardize due diligence for audits, vendor onboarding, and M&A evaluations using the same structured schedule.

Project managers can set a cadence to produce a brief report that highlights new items, changes to scope, and pending approvals. This keeps stakeholders aligned without diving into technical repositories. The approach scales from startups reusing code libraries to enterprises coordinating multiple vendors across regions, and it benefits nonprofits and associations that rely on grant-funded software where license terms and attribution must be tightly controlled.

Proposal Kit adds practical support for assembling this material list and keeping it consistent with the statement of work. Teams can generate exhibits that link items to requirements and line-item budgets, use the AI Writer to write concise descriptions and requests for approvals, and draw from templates for schedules, change requests, and supporting documentation. The result is a clear package you can present to executives, with content tailored to the engagement and easy to maintain as the project evolves.

To strengthen execution, treat the schedule as a controlled artifact with versioning and sign-offs. At project kickoff, record each item with a written description, version, owner, and link to documentation. Note whether the right to use is limited, the exact scope in accordance with specifications, and any attribution statements.

Include the contact person for licenses, the approval path, and who is responsible for the ongoing expense. As new components are identified during the proceeding work, submit a request, route it for approvals, and log the decision so the team can carry the correct rights forward after the schedule is executed.

Define inclusion criteria that are simple and auditable: any prior asset or third-party component used in the build or deployed on the site belongs on the list. Capture whether the asset enables concepts or features, whether it restricts future improvements, and any processing steps required before release, such as security scans or procurement checks. Establish a monthly report to highlight pending approvals, budget impact, and items needing assistance. This reduces surprises late in the engagement and helps leadership allocate resources.

Consider lifecycle value beyond launch. The exhibit supports onboarding of new developers, vendor transitions, audits, and end-of-life decisions. It helps product teams plan upgrades when a library sunsets, and it clarifies who to contact if a license changes.

Typical additional use cases include re-platforming a legacy site that reuses prior modules, OEM bundles that embed a developer framework with third-party codecs, and analytics projects that incorporate pre-existing data connectors. In each case, clear ownership records accelerate compliance reviews and cut lead time to deployment.

Proposal Kit can streamline this workflow. Teams can assemble consistent schedules and related statements, tie items to requirements and budgets with automated line-item quoting, and use the AI Writer to write descriptions, requests, and change notes. Its template library makes it easier to present a coherent package aligned to your specifications and keep it current throughout the project.

Writing the Exhibit C (Developer Materials) document - The Narrative

How to Build a Legal Contract with Proposal Kit

This video illustrates how to create a legal contract using the Proposal Pack Wizard software. It also shows how to create a proposal with an invoice and contract at the same time.