Founder Resources
A useful fundraising conversation starts with investor fit, evidence that matches your stage, and an honest account of what remains unproven.
TGN Ventures
·

Before improving a pitch deck, ask two questions: is this investor a plausible fit for the business, and what evidence would help them evaluate it now?
A founder with an early technical concept, a marketplace with providers but limited demand evidence, and a company choosing a development partner face different questions. A polished presentation helps an investor understand those questions. It cannot resolve them by itself.
In the November 13, 2026 TGN Investor Office Hours, Darrel Frater discussed these distinctions with Priyanka Desai of ADIN, an AI-assisted venture fund and scout network, and Andrew Chan, Founder and Managing Partner of Atas VC, whose stated focus includes technology serving energy, manufacturing and other traditional industries. Their feedback offers a practical way to prepare for the next investor conversation.
Start with the investor’s mandate
Researching an investor is part of the work. Priyanka encouraged founders to read a fund’s published materials and understand the future it wants to help build. Andrew repeatedly distinguished an interesting business from one that fits his particular fund.
That distinction became especially clear in the GridPay discussion. Founder Devan described a business around helping energy customers participate in grid-related rewards. Andrew said that the opportunity, as presented, did not fit his narrow technology thesis. His answer addressed fit with his strategy; it was not a verdict on whether the business could serve customers or attract a different investor.
Darrel reinforced the point: founders can lose time pursuing anyone with an investor title instead of finding alignment on stage, thesis and, sometimes, geography.
Before reaching out, write one sentence explaining the fit. Ground it in the fund’s actual mandate and your business as it exists. If the sentence only works after changing the substance of the company, investigate a different investor.
Explain the ambition without presenting it as evidence
Priyanka wanted founders to describe where an early idea could go over seven to ten years. A product that initially sounds like a feature may support a larger business, but the founder has to explain the customer, the market and why the timing matters.
This is a request for a coherent ambition. It does not make a forecast true. Keep the future you want to build separate from the progress you can demonstrate today.
A useful preparation exercise is to put three statements next to each other: the problem you can explain now, the evidence you have gathered, and the larger opportunity you intend to test. An investor should be able to see how those statements connect and where the uncertainty begins.
Match the proof to the stage and the business
Andrew described his own pre-seed approach as emphasizing thesis fit, differentiated technology and the team. In some hardware or deep technology situations, he said, there may be little traction or no finished product when he invests. That was an explanation of his approach, not a promise that every investor will fund an idea without customer evidence.
Elsewhere, Priyanka encouraged an early security founder to work toward a design partner or pilot. Those comments can coexist. The relevant question is what the next piece of evidence would show about this particular company.
For a technical product, that might be a demonstration of what it can do differently from existing tools. For a design partnership, it might be a clear account of the customer’s problem, the workflow being tested and the feedback that could change the product.
Describe each relationship accurately. A conversation, a prospective design partner, a pilot and a paying customer are different states. Use the state you can support.
Separate the two sides of a marketplace
Bookovia founder Ezra described a car ownership and services platform, reporting an established provider network and a vehicle-owner waitlist. Those were founder-reported figures, not independently verified results.
Priyanka recognized the work on the provider side while asking for a clearer picture of car owners, repeat use, margins and how the service works. Her questions did not establish that demand was absent. They showed that the supply-side numbers were more concrete in the pitch.
Andrew later asked what additional capital would unlock and encouraged demand validation. He expressly qualified that discussion: the company did not fit his fund’s thesis, and he did not have deep experience in that market.
For a marketplace pitch, keep separate evidence for supply, customer acquisition and completed activity. A provider count is not a customer count. A waitlist is not a completed transaction. A cost measured while acquiring providers should not be presented as the cost of acquiring buyers.
Use AI review to find questions, not guarantee a decision
Priyanka described ADIN’s process as combining AI-generated research with human judgment. After the system’s review, the human partners speak with the team and decide whether to invest.
Her later answer about scoring was equally important. Asked what causes founders to receive lower scores, she said she had not found a reliable pattern. More information could help produce a more detailed report, but the system could miss information, leave gaps or behave inconsistently. Market clarity was one issue she had noticed; she did not offer a dependable formula for optimizing a score.
A founder can use an automated review to examine unclear explanations or missing information. The output still needs scrutiny. A higher score is not proof of business quality, a prediction of returns or a commitment from an investor.
Andrew raised a related concern about pitch materials: AI can help with design and save time, but a generic deck without the company’s actual context can undermine the conversation. The founder remains responsible for the facts and the explanation.
Make the partnership and ownership story understandable
A founder considering a technology development partner asked how giving that partner equity might affect investor interest. Andrew focused on founder incentives, room to incentivize employees and whether an outside partner could control decisions.
His answer was conditional on the ownership structure. He also offered a small advisor-equity example in that context; it was not a universal allocation rule or a conclusion about the founder’s proposed arrangement. The discussion did not settle legal or tax questions about a specific company.
The preparation task is to explain the arrangement clearly: what each party contributes, what they own, who makes decisions, and what happens if the relationship changes. Keep unresolved terms visible rather than letting the pitch imply that they are already settled.
Bring a specific question to the next conversation
Prepare a short evidence note before the next pitch:
Fit: why this investor’s stage, sector and geographic focus match the company.
Progress: what exists today, with interest, pilots, customers and transactions distinguished.
Next test: the uncertainty a prototype, customer conversation or pilot could help resolve.
Ambition: how the initial product could connect to a larger opportunity.
Request: the specific feedback or next step you want from this meeting.
This note is an editorial exercise drawn from the discussion, not an investor’s approval checklist. Its purpose is to make the conversation more useful: give the investor enough context to respond, then learn from the questions that remain.