Technical co-founder, when it's right for both of us
Every engagement starts with me as your fractional CTO. Some become something more.
When you believe in where I can take the technology, I believe in your vision, and we both want to build it together for good, I become your technical co-founder.
Book a callIt isn't something you buy
It's something we both agree to.
I've come in as a contractor and stayed as a co-founder. More than once.
What changes
- I own part of the outcome, so the technology is mine to answer for
- I'm in it for the long run, through the hard years too
- Investors meet me as part of the founding team
What doesn't
- You own the code and every account
- Downshift's team keeps building, scaling up or down as needed
- No fixed contracts
Questions
Can I hire you as a technical co-founder from day one?
We start with me as your fractional CTO. Co-founder comes once we've worked together long enough that we both know.
Why would I still pay if you're a co-founder?
You pay for the team's work. The partnership is separate: it's about ownership and commitment, not the invoice.
Is equity part of it?
It isn't required to start. It's part of becoming co-founders, on terms that make sense for the company.
Who owns the code?
You do, from day one. It lives in your GitHub and your accounts.
What happens when we hire engineers in-house?
Sometimes it makes sense, sometimes it doesn't. Either way, I help you hire them and get them onboarded, with or without Downshift engineers alongside them.
Tell me what you're building.
A 30-minute call. Every partnership starts with one.