ROUNDTABLES 5 upvotes 2015

Ask HN: How do I present my side project to my current company?

5 pts
Hacker News Signal
2015 · Shared by @d--b
Ask HN: How do I present my side project to my current company? by @d--b

The Founder's Submission

Direct narrative and submission text authored by @d--b on Hacker News:

Hi HN,

I have been working on a side project for a while, and now I think I have a prototype that is not quite ready for beta, but almost. At the same time, a partner at my current job told me that they have a project they want to do, and they don't really know how to make it happen. What they don't know is that the side project I have been developing would be perfect for the task.

So I really want to take advantage of the situation by approaching the partner and telling him that I have been working on a tool on my own, and that it would make sense for them to use it for their project.

What I would like to do is:

1. Create a company (not yet created because I work in finance, and if I create a company I have to tell my boss for legal reasons...)

2. Make sure the company owns the IP of the tool I developed

3. Still work at my current job, part-time if possible, to keep the money coming and to integrate my tool into their infrastructure, and to have some time to work on the company (raising money, communicate, finding other clients)

4. In 6 months or so, leave my current job, and work full time on the company.

So, I am asking myself the following questions:

a. Is that a sound plan?

b. How do I present my plan to them?

c. This must happen all the time, are there any kind of templatized legal agreements for my point 2 and 3 above?

d. Are there any pitfalls? What are the ways I can get screwed?

Any help, past experiences to share, or good advice would be much appreciated! It is a rather exciting / stressful time!

Retrospective Overview & Key Insights

Distilled reflections, business mechanics, and tactical takeaways:

An open Ask HN community consultation from 2015 where @d--b convened hundreds of developers and bootstrappers to share real experiences, hard numbers, and tactics.

Core Principles for Independent Builders:
1
Participants share raw revenue figures, churn rates, and stack decisions that corporate PR never publishes.
2
Recurring answers reveal that distribution, not coding skill, is almost universally the rate-limiting step in developer businesses.
3
Practical recommendations on bookkeeping, payment gateways (Stripe vs Paddle), and freelance-to-product transitions.
Community Debate Themes:

Hundreds of active indie hackers contributed case studies, pricing heuristics, and pitfalls to avoid when moonlighting on side projects.

Community Discussions & Critical Reviews

Key perspectives, counter-arguments, and peer founder insights debated on Hacker News (8 total discussions):

CJ @cjslep Peer Contributor
DU @dudul Peer Contributor
JE @jeffmould Peer Contributor
IO @iolothebard Peer Contributor

Why do you need to tell your current company anything?

Just work your normal job until it becomes too inconvenient to keep working there, give 2 weeks notice and be on your way.

HISTORICAL ERA Cloud & Mobile Era (2014–2019)
COMMUNITY SCORE 5 points
TOTAL DISCUSSIONS 8 comments
TOPICS & TECH STACK: