Imagine that student engineering teams frequently need a torque wrench, sensor, or specialized tool for a short-lived design project. They may be able to buy what they need, but the equipment can be expensive and hard to find. CampusKit proposes a simple system for reserving and borrowing or renting shared project tools.
The important question is not “Could we build a website?” It is “Are enough people having this problem, and will they use and pay for this approach?”
| Canvas square | CampusKit’s first-draft answer |
|---|---|
| 1. Problem | Teams need specialty tools briefly; buying is costly; searching wastes time. Alternatives: friends, campus labs, buying tools. |
| 2. Customer Segments | University engineering design teams. Early adopters: teams nearing a prototype deadline without convenient access. |
| 3. Unique Value Proposition | “The tools your project team needs this week—without buying equipment you’ll use only once.” Concept: short-term project-tool library. |
| 4. Solution | Browse a simple inventory, reserve a tool kit, pick it up, and return it. |
| 5. Channels | Instructor referrals, engineering clubs, a reservation webpage, and campus pickup. |
| 6. Revenue Streams | Hypothetical $18 per weekly kit rental; potential department packages. |
| 7. Cost Structure | Tools, replacement and repair, insurance, storage, staffing, transaction fees. |
| 8. Key Metrics | Paid rentals, completed pickups, repeat rentals, contribution per rental. |
| 9. Unfair Advantage | None yet established. Potential future strength: trusted campus partnerships and reliable shared inventory. |
Open the one-page editor and select Load example. The nine boxes will fill with the CampusKit model, ready to examine or print. Export your own work first—loading the example replaces the active draft.
Open the editable example →Suppose a team pays $18 per rental week. If a completed rental costs $5 in cleaning, transaction fees, and average maintenance, the illustrative contribution is $13 per completed rental.
\[ \text{Contribution per rental}=\$18-\$5=\$13 \]
If the business incurs $520 in monthly fixed costs, it would need 40 completed rentals per month to cover those simplified fixed costs at that contribution rate:
\[ \frac{\$520}{\$13\text{ per rental}}=40\text{ rentals} \]
That calculation does not establish demand, and it omits other potential costs such as taxes, major equipment replacement, or financing. It simply exposes a testable business question: Can CampusKit attract roughly 40 paid rentals per month at that price and margin?
Imagine building the inventory before learning that students already get equipment for free. A practical test plan might look like this:
| Assumption | Low-cost test | What would count as useful evidence? |
|---|---|---|
| Students frequently struggle to access equipment. | Interview ten recent project teams. | Repeated, concrete examples from recent projects. |
| Teams will pay $18 for a rental week. | Offer an actual small paid pilot. | Completed payments rather than expressions of interest. |
| Instructor referrals can reach customers. | Ask two instructors to share a reservation link. | Reserving and paying customers traceable to referrals. |
| Equipment can be returned reliably. | Test a checkout-and-return process. | Most rentals completed without expensive losses. |
A canvas is not a sales pitch. A useful canvas clearly distinguishes what you think from what you have measured. If the evidence changes, update the square and test again.
Replace CampusKit with a business, nonprofit service, research application, or campus project of your own. Can you identify the single assumption that would cause the whole model to fail if it proved false?