Should I give the project to a freelance tech person or hire my own tech person? Costs are very different

we went the freelance route, regretted it. Guy left in 3 months, code was copy-pasted rewriting was very expensive. After hiring our own tech person issues decreased a lot. tbh of course he wasnt very productive in the first few months but he was trained

Best practice: freelance for MVP (3 months, 9000), then hire your own tech person (8-10k/month). Tech person follows up on MVP, scales it. Risk is high for freelancers, or they're very expensive (good freelancer). This combined path is good.

Question for me: can you find a reliable freelancer? Because reliable PHP/React freelancers for 3000 lira are rare. They usually start from 8000+. In that case, the price difference for hiring your own remains small.

freelancer for building MVP, employee for after-sales. businesses often do the opposite then :) If possible, finish MVP quickly, then hire a quality employee.

Are you worried about the code quality of a 3000 lira freelancer, as if asking me? It's very low, either it'll be bad, or the guy is working 10 jobs. Hiring your own employee is safer.

Long-term view, if you plan to scale, hire your own tech person. One person sets up code architecture, code review, best practices. Freelancer starts fresh with every project, there's no integrity.

Edit: asked below, I wrote the answer in the second message.

let me write how its done in practice but when making decisions, write down the worst-case scenario too, not just the best.

processes without records never improve becase you don't know what to fix. tbh if I were you, I'd go this route.

i think differently and everrything goes well for the first three months; problems arise in the fourth.

people defend habits, not processes. resistance comes from there. if you have questions, write them; Ill answer as best I can.

I've been dealing with this for a long time. When listing, put proof that the product actually works at the very top.

That's all, sorry if I went on too long.

The answer above hits the nail on the head. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Of course, it varies if your situation is different.

Following.

We experienced almost the exact same thing last year. When we decide without measuring, we always end up in the same place.

This is my opinion, I'm not claiming it's absolute truth.

Ive been dealing with this for a long time. When we decide without measuring, we always end up in the same place.

Processes without records never improve because you dont know what to fix. If you post the result here it will help others too.

I'll try it.

Let me summarize what's been said so far. A partnership without a payment schedule locks up at the first split.

If IP assignment to the company isn't written from the start, it can't be collected later. If you have questions write them; I'll answer as best I can.

i agree.

Could you elaborate on that? If you get three different answers on a topic, the question was asked wrong.

Just leaving this note, it might be useful.

The discussion got scattered, let me summarize. Taking notes for two weeks yields better results than a six-month estimate.

If you're offering equity instead of salary, also state what you're offering in return.