tl;dr: get a founding engineer’s tech plan for your early stage startup • takes 2 weeks • $350 • happens over email • written by
Kevin
Dear Early Stage Startup Founder,
I'm writing to tell you about Tech Plan Letters, a service I've created for pre-funding founders like yourself who want strategic guidance on the tech side of their startup. You need it early. You need it now. And, while you maybe didn’t realize it, you need it over email.
Why
I love helping people think through how to make the software side of their startup happen. What kind of budget might realistically get things moving, can we no-code it for a while, which technology professionals might be needed, and what kind of stack are we talking about.
The challenge with being pre-funding is exactly that — it's before there's any money for serious professional services or staff. You can't pay for fancy advisory packages, and finding the right technical co-founder often consumes months of precious time and energy.
But this kind of early advice is really important. It can mean differences in the outcomes around features, teams, cofounders, first hires, investors. Pursuing a startup or not.
Why email
I used to offer this guidance over video calls, but frankly, it became overwhelming. Too many calls, not enough advice.
Worse, when I considered scaling the meeting approach, it led me towards consulting strategies I don’t like — workshops, focus groups, webinars with high price tags and generic content.
Writing thoughts down and exchanging them via email can be an extraordinarily powerful medium for advice. It gives both of us time to think, reflect, and craft more thoughtful responses.
How
The entire process happens over email. No virtual classrooms, no weird Notion databases, no Zoom workshops or “in depth group sessions”.
By the end of our correspondence, you'll have what I call the "TechPlan.md" -- a structured text file written in markdown, a format great to keep going with in emails, LLM chats, vibe-coding tools, wire-framing, etc.
We work through how a variety of components might impact the tech -- ideal client profile, their "jobs to be done", common problems, main feature solutions, competition -- and write up your tech stack, lightweight product requirements document, data model, high level roadmap, and contractor plan.
The types of questions we can answer:
- What kind of budget should you realistically expect to deliver a minimum viable product?
- What does your engineering plan look like if you haven't found a technical co-founder by the time funding arrives?
- How can you develop a smart no-code strategy to bridge the gap until you secure funding or find that technical co-founder?
- When investors inevitably ask about your plan for engineering resources, what will you tell them?
- Are there “killer” features or components in your startup's vision that might actually be more “killer” in the sense that they’re much more complicated than you realize?
The process is designed to give you more confidence as you move forward with all the next choices for your startup's life.
If this approach resonates with you, I’d be honored to enter into your correspondence.
Best regards,
Kevin