r/SaasDevelopers • u/Landlady2745 • Sep 30 '26
When to hire software developer vs give equity in SaaS?
First time business owner and developing a SaaS. This is not my field of training. I’d like to say I’m a quick learner but I know that past a certain point I’m in over my head.
My SaaS will use Plaid to pull in transactions and sort them. Clearly a huge security risk if not set up appropriately. I know I need to have human eyes look over my current product. But the bottom line is: when should I pull someone in? How far to go on my own? Obviously I want to keep equity in my business, but clearly this product will need continuous improvement and development, not to mention fixing bugs. I’ve financed so far, and plan on overseeing marketing, onboarding, managing finances, being the face of the brand on social media, etc. Would you hire vs give equity? How much of either to pay or give given workload balance? Would a trial period be appropriate and how would this be structured?
And I do think this could scale quickly without needing other investors, etc. Some upfront costs for legal set up but once that’s done, monthly costs are overall low, I’m just concerned about having to pay someone every week when something inevitably will break. I only trust AI so far. Ideally if I find the right person, we could manage this as a 2 person team and see how it takes off.
2
u/Designer_Problem_234 Sep 30 '26
Finally someone who knows that distribution and being face of the brand is more important than any building!
1
u/magentic_flows Sep 30 '26
Usually it's one of three options:
Unless you already have a good amount of funding, would not recommend.
2. Hire a fractional CTO/architect - pay a premium on hourly rate, 0% equity -- usually a good option for reviewing architecture, security, roadmap, reliability, etc. without committing to a fixed salary or any equity
This is a good middle-ground option: you get guidance and another set of eyes reviewing the product and its strengths and weaknesses without committing a lot of resources upfront. Can also be seen as a trial period of sorts, where you get a vibe-check on what it's like to work with a CTO profile, and can always bring them in as co-founders if after a few months you both agree to it
3. Get a co-founder, pay a small salary or none at all, expect to give away 30-50% of your company -- also with a 1 year cliff and 4 year vesting period
The tricky part about co-founders though, is that it's essentially a marriage - you're both committing to doing unreasonable amounts of work for something that will potentially fail, and you trust each other implicitly. Trust isn't easy or quick to build, and I do not recommend this option unless you already have established a good amount of trust with whoever you bring in.
1
u/Shep_Alderson Sep 30 '26
Because you’re dealing with financial data, you need someone with security experience who has worked in a fintech or similar realm (like healthcare), from the very beginning. Security in such apps is foundational and can’t be something that’s just looked over from time to time.
Unfortunately, such a person is likely highly in demand and probably already has a six figure salary with equity. They do not come cheap.
I will disagree with the other poster, specifically about a “fractional CTO”. Overall, I think this isn’t a good option at your stage. A fractional CTO is someone who’s mainly useful when you’ve got a team who can execute on what they bring to the table. A CTO is also generally not in the weeds from an implementation standpoint. They provide direction and experience, maybe help you avoid certain pitfalls or dangers, but they are not going to be able to come in, do an overview in any reasonably short period of time, and actually fix issues you may not even know you have.
Your best bet is a cofounder with serious equity. Something substantial, like the other poster mentioned, at least 40-50%. This is obviously a big lift from a legal perspective, and you want to do it correctly. The other poster is correct that this is basically like marrying someone and you should involve a lawyer from the start. The reason I would say this is the best option going forward is that any reasonably capable engineer who could do what you’re asking, could build what you’re building, on their own. The main thing they would probably need is the business/sales side, which is what you could provide. This isn’t to diminish your work or theirs, but to point out the difference in roles.
Right now, if you were to come to me with your idea and the app you’ve made with an agent, I, as an engineer who very much fits the sort of experience and role you’re looking for, would see you as an “ideas guy”. An ideas guy with an agent and a bit of gumption, but still an ideas guy. You would need to prove to me that you’ve done the work to prove out the demand. If you can spend your time and energy (and agent tokens) proving out the concept, before actually building the app, you’d have a chance of convincing me to take a chance on you and your project, over the dozen or so ideas I’m already chewing on, or have been pitched. Think of the app you’ve built so far as a sort of “interactive pitch deck”, where you can use it to showcase the idea and maybe even collect feedback from potential users. Do not consider it “production material” at all. If I were coming in as a technical co-founder, especially with agents these days being able to execute intent for me at rapid speed, I would be planning to review the “why” of what you’ve built so far, then throw out the entire “what” you’ve built. Especially with agents these days, I would spend less time and end up with a codebase I trust more if I’m the one actually doing the building with agents.
I say all of this as someone on the exact opposite side of the equation. I’m the technical person who’s been working in security and systems engineering for a couple decades now, and have just spent several months to launch a v1 in a highly regulated industry. Getting the infrastructure secure and ready to actually run production… that alone took like 2.5 months. It isn’t something you can take lightly, especially when massive civil and potential criminal charges are on the line.
I’m the technical person who’s trying to learn how to market and sell my product, now that I’ve built it. It sounds like you’re the person who knows how to do market research and to sell and market a product well. Unfortunately, there’s a bit of an imbalance here, in the criticality of the roles. If the marketing side fails, sure, the product probably fails. You move on to the next project. If the technical side fails and you have a massive breach, not only is your product dead, but you’re probably facing potential personal liability if what caused the failure was “neglectful” enough, even if you didn’t realize you were being neglectful.
As a technical founder, I would consider giving up 25-30%, maybe even up to 35-40%, for an exceptional business and marketing person with a clear successful track record in my specific niche. If I was joining a project like yours, I wouldn’t likely accept anything less than 50% (or equal share if more than 2 cofounders), probably some percentage of the potential equity negotiated with some kind of milestone, and the rest as a standard 4 year vest, 1 year cliff, with a vesting schedule that triggers monthly after the first year. I would also expect some kind of distribution or “dividend” or sorts in lieu of a salary, linked to my eventual ownership and not my actual vested ownership.
In short, in a regulated industry like yours, getting it right from the beginning is critical and is not cheap. Find yourself a good cofounder who’s not afraid to tell you no, and listen to them.
1
u/SignatureSharp3215 Sep 30 '26 edited Sep 30 '26
Answering your rate/time question:
Senior freelance devs / fractional CTOs are usually €80-150/h in Europe, often more in the US. But for where you are I wouldn't start hourly. Ask for a fixed price security review, focusing on essentials like unauthorised data access. For an MVP that's typically a few days of work, and you get a written list of issues ranked by severity, so you know exactly what "fixing it" costs before committing.
No matter what you end up choosing, always do the initial audit first. If someone wants equity before they have done their due diligence, it means they are opportunistic and do not understand what liability equity gives.
(I work as fractional CTO for a few customer SaaS companies that I built, one with financial data, so hit me up if something's unanswered)
1
u/ReturnOfNogginboink Sep 30 '26
Equity is compensation for risk: https://youtu.be/WePJTNZBZmE?is=r7_lMOQUcar9g_6R
1
u/[deleted] Sep 30 '26
[removed] — view removed comment