Use this free Markdown template to give ChatGPT a clear starting point for your company. It works without 1PC: copy it, fill in the facts you know, and provide it with the next task. You can start without a clear idea: write down your experience, the people you can reach and a question to investigate.

Copy or download the founder context template

Download the Markdown template ↓

# Founder and product context

Last reviewed: [date]
Current decision: [one question to answer]

## Starting point
Experience or strengths I can build on:
People or customer groups I can reach:
Problems or directions to investigate:
What is still unclear:

## Product or working direction
Name (a working name is enough):
Stage:
Problem:
Intended customer:
Useful outcome:
Current alternative:

## Founder facts
Team and roles:
Strong skills:
Skills to learn:
Available hours per week:
Budget and period:
Reachable audience or distribution assets:

## Constraints
Non-negotiables:
Work excluded for now:

## Evidence
- Observation:
  Source and date:
  Segment and sample:
  What this does and does not establish:

## Hypotheses to test
- Hypothesis:
  Evidence needed:
  Result that would change our direction:

## Accepted decisions
- Investment considered:
  Decision (go / pivot / no-go, if applicable):
  Reason or supporting evidence:
  Accepted by and date:
  Review trigger:
  Decision record reference:

## Current checkpoint
Completed work and evidence:
Unfinished work or blocker:
Next action:
Source document and revision, if available:

## Next experiment
Cohort:
Action or offer:
Time and budget:
Observable decision criterion:
Next review:

## Working rules
Use relevant facts and constraints before proposing a plan.
Separate evidence, hypotheses, and unknowns.
If no idea is clear, compare directions before creating a build plan.
Apply go / pivot / no-go to a specific investment, not to certainty of success.
Surface conflicting or outdated information.
Keep one current copy and provide it explicitly in each client's supported way.
Confirm accepted choices and remaining work before continuing a new session.
Save accepted summaries rather than a raw conversation.
Do not include credentials or unnecessary personal/customer data.

Fill it with constraints that change the recommendation

Be specific about time and budget. “Bootstrapped” gives less guidance than “15 hours each week and $200 a month, with no hiring.” Name the period for any budget figure.

Write customer claims as hypotheses until you have evidence. Unknown customers, an unsettled direction and an empty evidence section are acceptable. Include sources and dates when you have them, and explain what a small sample cannot establish.

For the hypothetical AgentCRM example, the product hypothesis is “help independent agents choose their next follow-up.” A useful current decision is “should I run a manual pilot before writing software?” That is enough to start a focused task.

Use the file in your next chat

Use the attached founder context to help with [current decision].
Start by confirming my current direction, evidence and constraints.
If I have no clear idea, compare feasible directions before making a build plan.
List gaps or conflicts that would materially change your answer.
Propose one next action that fits my available resources.
Keep facts and assumptions separate.

Attach or provide the file using the tools available in your client. Read the startup context guide for an annotated example and maintenance rules.

Update after a material decision

When research changes the buyer, scope, or experiment, update the relevant section. Keep still-valid facts and remove outdated decisions from the current brief. Maintain your own version history if you need to recover earlier edits.

This page does not submit your template or store the information you enter in a downloaded file. If you choose to put it into a client or 1PC workspace, that is a separate action. Use only information needed for the task.

Continue with the validation checklist or return to ChatGPT for founders to pick the next decision.

Reuse the file across AI tools

Keep one current copy and provide it through the attachment or project mechanism your next client supports. The file format is portable; uploading it to one application does not automatically update another. The cross-tool context guide explains how to review and resume it.

Add a short checkpoint with completed work, blockers and the next action. Use the decision log template when a choice needs its own evidence, acceptance and replacement history.

Shape and test a direction.

1PC connects founder context with Idea Intake and Validation on Free. Save the reviewed brief and use it to choose your next step.

Start free ↗