T3NK
WE FUND. WE BUILD.
The engineering-first VC
We invest in early-stage software companies. Then our engineers join the repo and help you ship.
Capital gets you started. Code gets you to revenue.
Pre-seed to Series A. Software only.
If the hard part is technical, we should talk.
THE STACK
The tools we use to build and run what we back.
LESS NARRATIVE.
MORE SOFTWARE.
Venture rewards the story more often than the system. We do the opposite: we invest in teams that ship, then work with them to ship better.
We are engineers before we are investors. That shapes who we back and how we spend our time.
01.Revenue > Valuation
We optimize for customers and cash flow, not the next round.
02.Shipping > Slides
Progress is a working product in front of real users, not a roadmap.
03.Durability > Burn
We build systems a small team can run. Technology should be an asset, not a liability.
WHAT WE BUILD
We work inside your team on the parts that decide whether the product ships.
PRODUCT ENGINEERING
Web and mobile products, from first prototype to production.
AI SYSTEMS
LLM applications, agents, and evaluation pipelines that hold up in production.
INFRASTRUCTURE
Deployment, observability, and cost control for systems that have to stay up.
SECURITY
Threat modeling, code review, and penetration testing before launch.
DATA
Pipelines, analytics, and the data model behind the product.
TECHNICAL HIRING
We define roles and interview the first engineers with you.
FROM ZERO TO
REVENUE.
We are engineers before we are investors. The process is built around getting software into users' hands.
Thesis
We pressure-test the problem, the market, and the technical approach before we invest.
Prototype
We build a working MVP with your team. The goal is a product early users can try, not a deck.
Harden
We put the fundamentals in place: tests, CI/CD, observability, security, and documentation.
Scale
We stay involved through hiring, fundraising, and the first scaling problems.
We build what
we back.
Our engineers work in the same repository as your team. That changes what gets built and how.
We review architecture before it hardens, review code before it ships, and leave documentation your team can use.
No handoff. No black box.
- Architecture review
- Code review
- CI/CD and environments
- Observability and alerts
- Threat modeling
- Documentation
- Ship a prototype and disappear.
- Sell an audit we should have done during the build.
- Guarantee outcomes we do not control.
Code you can own
Your team gets the architecture, documentation, and context to maintain the system without us.
Security from day one
Threat modeling and code review are part of the build, not a post-launch audit.
We stay involved
We work through the first scaling problems, not just the first release.
Latest from the partners.
Decisions, engineering logs and signals. Not a blog.
Capital, then code
What the T3NK writing bit is for — the segment between investing and shipping, straight from the partners' desk.
Why we passed on the AI meeting-notes SaaS
A decision note on the most common pitch of 2026 — and the four questions that killed it.
Shipping a fix to someone else's repo
A short log of what porting a portfolio app from serial webhooks to event streams actually took.
BUILDING
SOMETHING BIG?
⚡ PITCH US/pitch// We respond to every founder. No deck required for first contact.
Prefer email? in@t3nk.com