Purpose: Centralized, reusable documentation system for grant applications, accelerator programs, investor outreach, and fundraising activities
New to Fundraising?
Read [[investors/HOW-TO-USE]] - Complete guide to investor research
Review [[investors/founder-friendly-funds-research]] - 40 VCs researched, top 15 prioritized
Apply directly: [[investors/100x-vc]] and [[investors/pioneer-fund]]
Ready to Reach Out?
VCs: See [[investors/founder-friendly-funds-research#Top 15 Actionable Funds]]
Angels: See [[investors/operator-angels-detailed]]
Grants: See [[grants/README]]
📊 Current Status (Updated: Feb 4, 2026)
Institutional Investors (VCs)
✅ 40/40 funds researched (100% complete)
🎯 15 actionable funds identified
💬 In conversation: Eximius Ventures
📝 Direct applications ready: 100X.VC, Pioneer Fund
Angel Investors
✅ 80+ operator angels researched
📧 Multiple inbounds via LinkedIn
🎯 Strategy: Feedback → Networks → Big names
Grants (Non-Dilutive)
🎯 ₹9-100Cr opportunities identified
📝 Active applications in progress
✅ Cloud credits: AWS Activate received, NVIDIA Inception member
💰 AWS Credits: $942 remaining (via NVIDIA Inception pathway)
See [[investors/README]] for complete investor strategy See [[grants/README]] for grant opportunities See [[tracking]] for application status
🔴 Recent Updates (2025-12-30)
Accelerator Rejections:
❌ Y Combinator W2026 - Rejected
New Strategy:
🎯 Focus: Build traction before reapplying to top-tier accelerators
🎯 Priority: Non-dilutive funding (grants, cloud credits)
🎯 Goal: Get first 10 paying customers, demonstrate PMF
See:
[[applications/REJECTIONS|Rejections & Learnings]] - What we learned and next steps
[[tracking#Recent Rejections|Funding Tracker]] - Updated application status
📁 Directory Structure
For a New Application
Create application directory
Copy YC template as starting point
Customize for specific program
Keep the ![[template#^block]] references
Add program-specific sections
Adjust word limits and format
Update tracking dashboard
Add to [[tracking]] with deadline and status
📝 How to Use Templates
Understanding Block References
Templates use Obsidian's block reference syntax: ![[file-name#^block-id]]
Example:
Available Templates
Template
What It Contains
When to Use
[[templates/company-overview]]
Company descriptions (5 variants: one-liner, elevator pitch, extended, etc.)
Any "describe your company" question
[[templates/problem-statement]]
Problem description (investor angle, user pain, market gap)
"What problem are you solving?"
Product features, differentiation, roadmap
"What does your product do?"
[[templates/market-analysis]]
Market size, trends, TAM/SAM/SOM
[[templates/business-model]]
Revenue model, pricing, projections, unit economics
"How will you make money?"
Founder backgrounds, expertise, relationship
"Tell us about your team"
[[templates/traction-metrics]]
Progress, milestones, validation
[[templates/technical-architecture]]
Tech stack, architecture, security
"What's your tech stack?"
Using Block References
Each template has multiple named blocks for different contexts:
Example from company-overview.md:
^one-liner - 50 character description
^elevator-pitch - 280 character (tweet length)
^short-description - 1 paragraph
^healthcare-pitch - Healthcare grant focus
^impact-pitch - Social impact focus
Usage:
🎯 Template Content Strategy
1. Atomic Content Blocks
Each template contains modular, reusable pieces that can be:
Combined for different audiences
Updated once, reflected everywhere
2. Multiple Variants by Audience
Templates include variants for:
Investors: Growth, market opportunity, returns
Accelerators: Traction, team, vision
Healthcare grants: Social impact, health outcomes
Philanthropic grants: Mission alignment, impact metrics
Technical audiences: Architecture, security, scalability
3. Version Control
Templates include:
Track when content was last updated and for whom.
📊 Application Workflow
Phase 1: Initial Setup (Done ✅)
Phase 2: Content Refinement
Phase 3: Reuse for Next Applications
Identify next program (Sequoia Surge, BIRAC, etc.)
Copy YC template structure
Adjust for program-specific requirements
Most content auto-populates via block references
Add/customize program-specific sections
Phase 4: Maintain & Improve
Update templates as traction grows
Version templates (v1.0 → v1.1 → v2.0)
Track which version used for each submission
Iterate based on what works
🔄 Content Reuse Examples
Example 1: From YC to Sequoia Surge
YC asks: "What does your company do?" Answer: ![[company-overview#^elevator-pitch]]
Sequoia asks: "Describe your company" Answer: Same block reference! Just transclude it.
Example 2: From Accelerator to Grant
YC asks: "How will you make money?" Answer: ![[business-model#^revenue-model]] (investor focus)
Gates Foundation asks: "How will you sustain the program?" Answer: ![[business-model#^social-sustainability]] (impact focus) → Add this new block to business-model.md
Example 3: Updating Once, Reflects Everywhere
You hit 1,000 users milestone. Update: traction-metrics.md → all applications auto-update! 🎉
✅ Best Practices
Update templates regularly as traction grows
Version templates when making significant changes
Create new blocks for new contexts/audiences
Link related templates for easy navigation
Use descriptive block IDs (^investor-angle, ^grant-focus)
Test block references in Obsidian preview
Don't duplicate content - reference templates instead
Don't skip frontmatter - version tracking is important
Don't write directly in applications - extract to templates
Don't forget to update tracking.md when submitting
Don't delete old block IDs - breaks existing references
📋 Common Application Types
Accelerators (YC, Sequoia, Accel)
Focus: Traction, team, growth potential Key sections:
Company description (short)
Templates to use:
company-overview (^elevator-pitch)
solution (^core-solution)
team-bios (^founder-history)
traction-metrics (^milestone-1, ^milestone-2)
Healthcare Grants (BIRAC, Gates Foundation)
Focus: Health outcomes, social impact, sustainability Key sections:
Solution (health outcomes)
Templates to use:
problem-statement (^healthcare-angle)
company-overview (^healthcare-pitch, ^impact-pitch)
solution (^preventive-care, ^democratizing)
market-analysis (^india-scale)
Cloud Credits (Google, AWS, NVIDIA)
Focus: Technical needs, infrastructure, scalability Key sections:
Templates to use:
technical-architecture (^tech-stack, ^cloud-infrastructure)
solution (^core-solution)
traction-metrics (^milestone-1)
📈 Tracking Progress
Use [[tracking]] Dashboard For:
✅ Application status tracking
Submitting application → Change status to ⏳ Submitted
Receiving response → Update with result
Major milestone → Update traction-metrics.md
Pivot/change → Update relevant templates
Short-Term (This Month)
Medium-Term (Next Quarter)
[[tracking]] - Application tracker dashboard
[[investors/README]] - Angel investor strategy
[[grants/README]] - All grant opportunities
[[memo]] - Product vision
[[competitors/strategic-insights]] - Market insights
[[product/feature-ideas]] - Detailed features
📞 Questions or Issues?
Template Not Working?
Check Obsidian preview mode (block references don't work in edit mode)
Verify block ID exists: ^block-id at end of paragraph
Ensure file path is correct: _templates/file-name.md
Need New Template Section?
Add content to relevant template file
Update this README with new block
Content Out of Date?
Update source template (e.g., traction-metrics.md)
Bump version number in frontmatter
Note update in tracking dashboard
Content auto-reflects in all applications! ✅
Tip 1: Use Graph View
Obsidian's graph view shows connections between applications and templates. Use it to:
See which templates are most used
Understand content relationships
Tip 2: Search for Block References
Search for ![[template-name to find all applications using a template
Tip 3: Version Templates When Pivoting
If you make significant changes (pivot, new positioning):
Save old template as company-overview-v1.md
Older applications reference v1, new ones reference v2
Tip 4: Create Application-Specific Addendums
For unique questions, create applications/[program]/custom-answers.md:
🎯 Success Metrics
Track how this system helps:
⏱️ Time saved: How long does next application take?
🎯 Acceptance rate: Do applications perform better?
🔄 Reuse: How many templates used per application?
✨ Quality: Feedback on applications
🙏 Acknowledgments
Inspired by:
YC application best practices
Obsidian Zettelkasten method
DRY (Don't Repeat Yourself) principle
System created: 2025-12-11 Last updated: 2025-12-11 Version: 1.0