Advisors & Portfolio Support

How to Run Portfolio Fundraising Office Hours

Design founder office hours around one prepared question, a useful working artifact and a clear follow-through record.

By Finta Editorial TeamPublished October 19, 2026

An emerald calendar arch frames a lilac document, an empty speech bubble and an amber next-step tile on a reflective surface.

What you will learn

  • Choose private or group office hours for the actual job
  • Prepare focused founder questions without unnecessary disclosure
  • Close each session with a useful return and accepted owner

Run portfolio fundraising office hours around one question a founder needs to resolve, not an unprepared pitch from every attendee. Ask for a short pre-read, choose a suitable private or group format and leave with a useful artifact or decision. The session should clarify the next step, not promise an investment or replace specialist advice.

Office hours can be a repeatable support route. Y Combinator describes both group and one-to-one office hours, including continuing access after its program. The format below is an original operating example for your team, not a claim about YC's exact process.

1. Match privacy and format to the job

Use a private session for sensitive company context, a specific investor conversation or a question that requires restricted materials. Use a small group when founders can learn from a shared operating problem without exposing confidential details. Do not make public pitching the price of receiving help.

State the facilitator's scope. General preparation and operating feedback are different from legal, tax, accounting or investment advice. When a question needs a specialist, capture the issue and route it rather than improvising a confident answer in front of the group.

Set a confidentiality expectation and decide whether any notes or recording are appropriate. Obtain specific permission before recording or reusing examples. A participant attending a session has not automatically agreed to public teaching use of their company information.

2. Ask for a short question packet

  • The exact question and why it matters now.
  • What the founder has already tried.
  • A minimal approved artifact, such as one slide or a small research sample.
  • The decision or useful return wanted from the session.
  • What must remain private and who may see the materials.

Return incomplete questions with a small preparation request. “Can you review our fundraise?” can become “Which part of this opening prevents a reader from understanding our buyer?” The latter can be addressed in a limited session.

3. Facilitate from question to return

Illustrative 30-minute private session

TimeFacilitator actionFounder return
0–5 minutesConfirm the question and boundariesOne agreed job
5–12 minutesInspect the source artifact and ask clarifying questionsShared understanding of the problem
12–22 minutesWork through one revision or decision frameworkMarked-up artifact or options
22–27 minutesAsk the founder to apply the recommendationEvidence that the idea is understood
27–30 minutesRead back action, owner and review triggerA short session receipt

In a group, state the time per founder and preserve room to synthesize shared lessons. Stop speculative advice cascades. Ask contributors what evidence or experience supports a suggestion and let the founder decide what applies.

4. Worked example: turn a vague pitch question into a useful revision

Illustrative example: Harbor Sensor books a private session because investors confuse its user with its buyer. The founder supplies two approved slides and a customer-definition note. The facilitator does not ask for a full financial model or confidential customer contracts.

The founder explains the product in two minutes. The facilitator asks who experiences the problem, who approves a purchase and how those roles differ. They mark the sentence where “customer” hides both roles. The founder rewrites it using accurate business language, then reads the opening aloud.

The return is a revised explanation and a test: ask two appropriate readers to describe the user and payer without prompting. That is a clarity exercise, not proof that the new wording will raise money.

Completed session receipt

Question: Who uses the product and who buys it?
Artifact: Approved opening slides plus customer-definition note.
Observed problem: One label was used for two different roles.
Return: Revised explanation and a two-reader clarity check.
Founder action: Test the wording and record misunderstandings.
Owner: Founder.
Facilitator follow-through: Review the next version if within agreed scope.
Sharing: Private, no recording or reuse approved.
Open specialist questions: None decided in this session.

5. Copy the office-hours packet

Session purpose and format:
Founder question:
Why now:
What has already been tried:
Smallest useful artifact:
Expected return:
Privacy / recording / note-sharing permissions:
Facilitator scope:
Key observation and evidence:
Advice or options, labeled as such:
Founder decision:
Action / accepted owner / due date:
Completion check and revisit trigger:
Specialist referral needed:

Improve the format after each session

  • Founders arrive without a question: Add a simple pre-read prompt and offer a short scoping step.
  • The session becomes a lecture: Return to the founder's artifact and let them apply the idea.
  • Confidential details enter a group: Stop and move the sensitive issue to an appropriate private route.
  • Everyone leaves with ten tasks: Choose the smallest meaningful next action.

Completion check: The founder can state what improved, what remains uncertain and what they will do next. Record that return separately from attendance or satisfaction with the conversation.