Climate co-founder matching: a 30-day trial plan

In ClimateTech, the exposure is higher because the company usually cannot reach a meaningful commercial test in a few weeks.

Hardware manufacturing can take 18–24 months. Field testing can take 12 months or more. Regulatory approval can take 6–12 months. If two founders discover incompatible decision rules after six months, the company has already spent capital, customer trust, and execution time.

A climate startup co-founder trial plan reduces that risk before equity is issued and roles become difficult to unwind. The plan is not a compatibility exercise. It is a controlled operating test.

The target is 30 days and at least 120 hours of shared work. The output is not certainty. The output is evidence.

The 65% failure risk: why ClimateTech needs a harder test

A general software startup can test a co-founder through customer interviews, product changes, and a short sprint. The feedback loop is fast. A founder can make a poor decision on Monday and correct it by Friday.

ClimateTech has slower feedback loops and more dependencies. A product may require:

• Laboratory validation before customer trials.
• Supplier qualification before manufacturing.
• Site access before field deployment.
• Safety review before installation.
• Regulatory approval before revenue.
• Public or enterprise procurement before scale.

This changes the co-founder requirement. You are not only selecting someone who can generate ideas or build a prototype. You are selecting someone who can operate through long periods where the company has high burn rate and limited external validation.

The trial must therefore test four operating variables:

1. Throughput. Can the person produce useful work at the agreed pace?

2. Decision quality. Can the person make decisions with incomplete data?

3. Conflict handling. Can disagreement produce a better decision instead of a stalled one?

4. Commitment under delay. Does the person continue operating when deployment moves by a quarter?

If the answer to any of these is unknown, the partnership is not ready for an equity agreement.

A co-founder trial is not a month of collaboration. It is a month of evidence about how the company will behave under load.

The trial does not guarantee a successful partnership. It does something narrower and more useful: it exposes operating incompatibility while the cost of exit is still low.

Set the trial parameters before the first task

The trial should be written down before work begins. A shared document is sufficient for the operating plan. Legal protection requires a separate agreement.

Use the structure applied in the Y Combinator Startup School co-founder trial framework: names and intentions, timelines and accountability, and project details. Keep the language direct. Avoid statements that cannot be measured.

1. Names and intentions

Record:

• The names of both participants.
• The working name of the company or project.
• The problem being investigated.
• The reason each person is considering the partnership.
• The expected role of each person during the trial.
• The conditions under which either person can stop.

Do not write “we want to build a major climate company.” That is not an operating intention. Write: “We will test whether industrial heat customers will pay for a monitoring and control product that reduces gas consumption without requiring a full equipment replacement.”

The second version creates a test boundary. It also prevents scope expansion.

2. Timeline and workload

A 30-day trial requires a fixed start date, end date, and workload. A practical minimum is approximately 120 hours of shared work. That does not mean both founders work 120 hours exclusively on the trial. It means the partnership generates enough joint exposure to reveal work habits, response time, and decision patterns.

Define:

• Weekly hours available from each founder.
• The days and times reserved for joint work.
• The response-time expectation for urgent decisions.
• The weekly review time.
• The deadline for the final decision.
• The process for pausing the trial.

If one founder can contribute 35 hours per week and the other can contribute 8, the mismatch must be visible before the company starts. It may still be workable. It is not a detail.

3. Project details

The project needs one primary outcome and no more than three supporting outputs.

For example:

Primary outcome: Secure five qualified interviews with operators of commercial refrigeration sites.

Supporting outputs:

• A customer problem map based on interviews.
• A first-pass estimate of savings and implementation cost.
• A decision memo stating whether to continue, narrow, or stop.

The project must be difficult enough to create pressure and narrow enough to finish. If it cannot be completed within one to four weeks, it is not a trial project. It is an early company.

The 30-day operating plan

A 30-day plan should create a sequence of commitments. Each week has a different test. The objective is not to simulate every founder responsibility. The objective is to increase exposure without increasing irreversible cost.

Days 1–3: define the system

The first three days establish the operating rules.

Agree on:

• The customer segment.
• The problem statement.
• The trial hypothesis.
• The work split.
• The meeting cadence.
• The decision owner for each workstream.
• The evidence required to change direction.
• The definition of completion.

Assign decision ownership even if the partnership is intended to be equal. Equal equity does not require equal authority over every decision. A trial without ownership creates silent duplication and later blame.

Use a simple decision log. Each entry should contain:

• Decision.
• Owner.
• Evidence available.
• Reversible or irreversible status.
• Date for review.

A reversible decision can be made quickly. An irreversible decision requires more evidence and, if possible, joint approval. This distinction prevents a common failure mode: treating a slide layout and a regulatory claim as if they carry the same risk.

Days 4–10: run customer and technical discovery

The first work cycle should connect the commercial problem to technical reality.

A climate entrepreneur co-founder matching process often fails because candidates discuss mission alignment before testing how they reason about constraints. Discovery work corrects this. One founder can lead customer interviews. The other can map system requirements, costs, and deployment barriers. Both must review the evidence.

A useful discovery package includes:

• Five to ten customer or operator conversations.
• A list of current alternatives.
• The buyer, user, and approver for the proposed product.
• The operating environment where the product would be installed.
• The required data, hardware, permits, or integrations.
• The cost of a failed deployment.
• The expected payback period for the customer.

Do not count scheduled calls as throughput. Count completed conversations with decision-relevant information.

If customers describe the problem differently, record the variance. If the technical solution requires site modifications that customers reject, record that as a constraint. If the proposed carbon reduction depends on behavior that the user cannot control, remove it from the model.

Days 11–17: build one artifact together

The second work cycle should produce an artifact that forces trade-offs. Select one:

• A unit economics model.
• A deployment plan for one pilot site.
• A technical risk register.
• A prototype with a defined test.
• A regulatory pathway.
• A customer proposal with pricing.
• A supplier and manufacturing cost map.

The artifact must have a clear owner. The other founder must be able to challenge it.

For a hardware product, the unit economics model should separate:

Do not use a unit economics model to create a credible-looking spreadsheet. Use it to identify the bottleneck.

If installation capacity limits growth, manufacturing cost is not the first constraint. If regulatory review limits sales, customer acquisition is not the first constraint. If the product cannot generate verified savings, pricing is not the first constraint.

The co-founder should be able to identify the current bottleneck and state what evidence would remove it.

Days 18–24: operate under disagreement

The third work cycle should include a decision where reasonable people can disagree.

Examples:

• Sell a paid pilot or offer a free pilot.
• Narrow the customer segment or keep the market broad.
• Build the full product or test one component.
• Accept a slower deployment path with stronger validation.
• Use a channel partner or sell directly.
• Pursue a regulated market now or defer it.

Set a deadline. Require a written position from each founder. Then hold the decision meeting.

Evaluate the process, not only the outcome.

A functional disagreement has a sequence:

1. Each founder states the decision in one sentence.

2. Each founder states the evidence supporting their position.

3. Unknowns are separated from assumptions.

4. The downside of each option is quantified where possible.

5. One person owns the final decision.

6. The decision is logged.

7. New evidence triggers a review, not an argument about who was right.

A dysfunctional disagreement has a different sequence:

• The scope changes during the discussion.
• Personal commitment is used as evidence.
• The founder with the strongest status wins.
• The decision is deferred without a next test.
• The same issue returns in the next meeting.
• Silence is treated as agreement.

The point is not to eliminate conflict. That is impossible. The point is to keep conflict from reducing throughput.

Days 25–30: produce the decision package

The final week converts activity into a partnership decision.

The package should contain:

• What was tested.
• What evidence was collected.
• What remains unknown.
• The current customer hypothesis.
• The current technical hypothesis.
• The unit economics assumptions.
• The main bottleneck.
• The next 90-day operating plan.
• The capital required.
• The responsibilities of each founder.
• The unresolved risks.
• The proposed process for resolving those risks.

Then answer one question: would both founders choose to work together for the next 90 days if the project had no prestige and no immediate funding?

This is not a motivational question. It is a resource allocation decision. If the answer is no, stop before creating more burn.

Design the trial around ClimateTech constraints

A generic co-founder task does not test a ClimateTech partnership. Building a pitch deck can show writing speed. It does not show whether a candidate can manage a field test, document a safety issue, or revise a commercial model when the deployment schedule slips.

The trial project should resemble the operating environment of the proposed company.

If the company is hardware-led

The project should expose manufacturing and deployment constraints. Ask the team to produce a pilot plan for one real site.

The plan should include:

• Site requirements.
• Installation sequence.
• Safety risks.
• Supplier dependencies.
• Expected lead times.
• Test instrumentation.
• Data collection method.
• Maintenance process.
• Failure response.
• Removal or replacement plan.

The test is not whether the plan looks complete. The test is whether the founders notice the dependencies before committing to a customer date.

If the company is software-led

The project should connect product scope to measurable climate or operational outcomes. Build a narrow workflow around one user and one data source.

The founders should define:

• Who supplies the data.
• How data quality will be measured.
• Which output changes a customer decision.
• What the product does when data is missing.
• How savings or emissions impact will be calculated.
• What the customer pays for.
• What part of the workflow remains manual.

A software product with no credible measurement model can create attractive activity without climate impact. That is a throughput problem disguised as progress.

If the company depends on regulation

The project should map the approval path. Include the relevant authority, required tests, documentation, sequence, and expected review points.

Do not pretend to know an approval timeline that has not been confirmed. Mark assumptions as assumptions. A founder who hides uncertainty inside a calendar is creating risk, not reducing it.

If the company depends on project finance

The trial should produce a capital stack and cash-flow model. Include customer payment timing, grants, debt, equity, deposits, and working capital.

Project finance can create a low-burn appearance while increasing cash exposure. If the company pays for deployment before receiving customer revenue, the model must show the gap. A positive gross margin does not solve a negative cash conversion cycle.

Protect IP before the trial starts

The trial creates assets. Those assets need defined treatment whether the founders continue or separate.

Before work begins, sign a Memorandum of Understanding or trial-period agreement. The document should address:

• Confidentiality.
• Ownership of pre-existing IP.
• Ownership of work created during the trial.
• Access to shared files and systems.
• Use of customer information.
• Treatment of third-party materials.
• Return or deletion of confidential information.
• What happens if one founder exits.
• Whether either person can continue developing an unrelated idea.

A general startup agreement may be sufficient as a starting point, but ClimateTech adds specific asset classes: technical drawings, test data, field measurements, supplier terms, laboratory results, regulatory correspondence, and customer site information.

Do not place customer data in personal accounts that the company cannot access. Use a shared workspace with permission controls. Keep a dated record of technical work. Record who created what before and during the trial.

The agreement should not attempt to create a full founder relationship before the trial proves that one exists. It should protect the work and define the exit.

Discuss equity without pretending the answer is known

Equity is often delayed because founders want to avoid an uncomfortable conversation. That delay does not remove the issue. It increases its cost.

During the trial, discuss equity expectations at a high level:

• Is an equal split the default expectation?
• Does one founder expect a controlling position?
• Will prior work receive credit?
• How will future commitment affect ownership?
• Will vesting apply?
• What happens if one founder becomes part-time?
• Who has the authority to break a deadlock?
• What happens if one founder leaves?

Do not finalize the split merely because 30 days have passed. The trial is evidence about contribution and compatibility. It is not a valuation of the company or a legal substitute for a founder agreement.

A co-founder equity trial period should therefore have two separate decisions:

1. Relationship decision: continue working together or stop.

2. Ownership decision: define equity, vesting, authority, and exit terms in a formal agreement.

They are related. They are not identical.

A 50/50 split can work. It can also create a deadlock if no decision rule exists. A non-equal split can work. It can also damage trust if the basis is unclear. The relevant variable is not the visual symmetry of the cap table. It is whether both founders understand the logic and can operate under it.

Find candidates through evidence, not profile density

YC’s Co-Founder Matching platform, launched in 2021, reported more than 150,000 profiles by 2025. This increases access. It does not increase fit.

Finding a ClimateTech co-founder requires filtering for operating exposure. Review candidates against the actual bottlenecks of the company:

• Has the person shipped into a physical environment?
• Has the person sold to an enterprise or public-sector buyer?
• Has the person managed a long validation cycle?
• Can the person work with technical, commercial, and regulatory constraints?
• Has the person owned a budget or burn rate?
• Can the person explain a failure without changing the facts?
• Does the person have enough availability for the next 12 months?
• Is the person willing to perform a trial before discussing a final equity structure?

A candidate may be a strong engineer and a poor co-founder for a regulated hardware company. A candidate may be a strong sales operator and still lack the patience required for field validation. There is no universal founder profile. There is only fit against the company’s constraint set.

Use short conversations to screen. Use the trial to decide.

Evaluate resilience against the real deployment clock

ClimateTech founders must tolerate delay without losing operating discipline. The test is not whether a person claims to be patient. The test is how they react when the schedule changes.

During the trial, introduce realistic uncertainty:

• A customer postpones the interview.
• A supplier cannot meet the assumed lead time.
• A technical test produces inconclusive data.
• A cost estimate increases.
• A regulatory assumption requires confirmation.
• A pilot site adds a safety requirement.
• A customer asks for a feature outside the initial scope.

Observe the response.

If the founder updates the model, revises the plan, and preserves the decision trail, the system is functioning. If the founder hides the problem, blames the external party, or expands the scope to compensate, the company is accumulating future burn.

The long-term deployment cycle makes this non-negotiable. A 12-month field test will contain more ambiguity than a 30-day trial. An 18-month manufacturing path will contain more supplier failures than a customer discovery sprint. The trial must reveal whether both founders use evidence under pressure.

In ClimateTech, commitment is not measured by enthusiasm at launch. It is measured by decision quality after the launch date moves.

Close the trial with a binary decision

Do not end the 30 days with “let’s keep talking.” That creates an undefined partnership with undefined authority.

Choose one of three operational outcomes:

• Continue: sign the formal founder agreement and start the next 90-day plan.
• Pause: define the missing evidence, owner, and date for a second decision.
• Stop: transfer or delete assets according to the trial agreement and end the collaboration.

A pause is valid only when the uncertainty is specific. “We need more time” is not a decision. “We need three additional customer interviews with facility operators before selecting the segment” is a decision.

Use this final binary checklist:

• Did both founders complete the agreed workload?
• Did each founder deliver an owned workstream?
• Did the partnership maintain acceptable throughput?
• Were disagreements resolved through evidence and decision ownership?
• Is the current unit economics model understood by both founders?
• Is the primary bottleneck explicit?
• Can both founders accept the next 90-day plan?
• Are availability and burn-rate expectations aligned?
• Are confidentiality and IP terms signed?
• Can the equity discussion proceed without concealed assumptions?

If any answer is no, do not sign the final co-founder agreement yet.

A climate startup co-founder trial plan does not remove risk. It moves risk to the point where it is cheapest to manage. Thirty days of structured work, with a defined project and at least 120 hours of real collaboration, can expose more than months of networking conversations.

The operating rule is simple. If the partnership improves throughput under uncertainty, continue. If it creates a bottleneck before the company has customers, stop.