Eliminating "That's not what I heard." Things I decide before starting freelance outsourcing.

Hello, this is Masu.

I am a freelance engineer who usually works under direct contracts with companies.

In this article, I will write about how I decide on money, scope of responsibility, and handling of information when I outsource projects I have received through direct contracts to other engineers.

Since the order of the process is summarized in another article, I will focus here on the content of the terms.

Just one thing first.
This is not legal advice.
It is a prerequisite to check with a professional if you need contract content or legal judgment.
With that in mind, I will talk about "what not to leave ambiguous so that people can accept outsourcing with peace of mind."

Contract types vary by project

The way we work together changes depending on the content of the direct contract project.

For small developments, I sometimes ask for deliverables-based work, and for continuous development or operations, I sometimes ask for work based on hours worked.

There are cases where I act as the company's point of contact and outsource development, and cases where I connect the company and the engineer directly.

Which is better depends on the project.
The important thing is not to leave that ambiguous from the start.

Things to check in advance

Before starting a project, I check at least these points.

How much is the compensation and when will it be paid? How much work is expected?
When is the deadline?
What is the communication method? What is the scope of responsibility, and what is out of scope?
How will reviews and delivery confirmation proceed?

It may seem detailed, but if you proceed with this remaining ambiguous, it will be difficult for both parties.

"That's not what I heard."
"There was more work than I thought."
"I don't know when it will be finished."
"I don't know if this is an additional request or within the original scope."

I want to eliminate these situations in advance.

Deciding roles and scope of responsibility

When outsourcing, I decide "who holds what" first.

When I act as the company's point of contact, I often handle requirement alignment, condition adjustment, and process organization.
I want to make it a form where those who join can focus on development and implementation as much as possible.

If you would like to gain experience in upstream communication or meetings with companies, we can discuss that arrangement as well.

Who will handle communication with the company?
Who will organize the requirements?
Who will be in charge of design and implementation?
How will testing and delivery verification be handled?
Sorting these out beforehand makes the work much easier to proceed with.

It is okay to decline if it is not a good fit

Just because you have heard about an opportunity does not mean you are obligated to take it.

The workload does not match.
You have technical concerns.
It is difficult at this time.
The terms do not align.

These things happen normally.

If you force yourself to join, it will not be a good situation for either party.
I, for one, do not want to push projects that are not a good fit.
I value creating a situation that both the company and the engineer can sustain without strain.

Handling of information

During introductions and consultations, I may ask to see your skill sheet or resume.

However, I will never share them with a company without your explicit consent.

Regarding client information, I am naturally careful with anything that must not be disclosed. I may also sign an NDA if necessary.

Even if you were introduced through an acquaintance, I will not suddenly push hard for sales or force projects on you.
I value maintaining the trust of the person who introduced us just as much.

Finally

Talks about contracts and freelance work might seem a bit stiff.

However, proceeding without knowing the compensation or scope of responsibility is far more unsettling. That is precisely why I want to discuss what we can beforehand and work together to create a sustainable arrangement.

It is okay if you have concerns about the terms. Please consult with me first.

You can find information on what direct contract projects are available here.