7 Steps to Starting a Direct Contract Project: Please Read Before Sending a DM
Hello, I'm Masu.
I work as a freelance engineer, primarily taking on projects through direct contracts with companies.
This article summarizes only the order in which things proceed when I take on a direct contract project and bring on an engineer as a contractor to work with me.the sequence of stepsis all that is covered here.
In my project introduction, I wrote about the actual direct contract projects I have taken on.
However, even if you are interested in a project, I think it can be unsettling not to know the process when you are about to join as a contractor.
What happens next after I send a DM?
Will I be introduced to a company right away?
Will things move forward without me realizing it?
If I feel it's not a good fit, at what point can I back out?
Therefore, I have written down the sequence of steps here, from the initial DM to starting the project and continuing thereafter.
Details regarding conditions such as compensation and scope of responsibility are summarized in the contract article, and what to send in a DM is summarized in a separate consultation article. This article is only about the 'flow'.
1. Starting with a DM or referral
It often starts with a DM on X or a referral through an acquaintance.
I do not introduce you to a company or throw you into a project right away.
We start by just talking.
Your DM doesn't need to be perfectly polished.
A casual sentiment like 'I'd like to get involved in development on a small scale as a contractor' is enough.
If you are not comfortable with a 1-on-1 right away, I host study sessions in Tokyo and Osaka, so please feel free to join from there!
▼ IT Engineer Study Session Recruitment Site on connpass
Organizer of 'IT Engineer One Up Study Session'
▼ Note summarizing the study sessions
2. Asking about your experience and future direction
Next, I will ask about the environments you have worked in, the technologies you have used, what kind of projects you want to be involved in, and your availability.
What I want to hear here is not a perfect resume, but your current experience and the direction you want to head in next.
3. Sharing direct contract projects that seem like a good fit
Among the direct contract projects that come to me, I will share those that seem to be a good fit in terms of content, technology, workload, and timing.
Just because you hear about one doesn't mean you are obligated to join.
It is perfectly fine to decline if it doesn't fit (my thoughts on this are summarized in my article on contracts).
4. Aligning Conditions and Roles
If it seems like a good fit, we will align on conditions and roles in advance.
Compensation, workload, deadlines, scope of responsibility, and methods for communication and review. I make it a priority not to leave these ambiguous from the start.
Sometimes I act as the point of contact for the company and outsource the development to you, and other times I connect you directly with the company.
We will decide which approach to take at this stage.
I have written in detail about how I determine the content of these conditions in my article on contracts.
5. Contract and Start Small
Once you are satisfied with the conditions, we will sign a contract and start small.
Rather than handing over everything at once, I believe it is safer for both parties to break the work down into smaller pieces, check the compatibility of our working styles and communication, and gradually expand the scope of work.
6. Development, Review, and Reflection
During development, it helps if you can share any roadblocks early on. It is ultimately smoother than proceeding while unsure.
At key milestones, we will have a brief reflection to see what we can apply to the next stage and how we can organize the experience to be included in your skill sheet.
I want to ensure that the work doesn't just end with the delivery, but is preserved as an experience that leads to the next opportunity.
7. Leading to the Next Direct Contract or Continued Work
Once we have successfully worked together, it becomes easier for me to reach out to you when the next consultation comes in.
Some projects are ongoing, while others are one-offs. It doesn't always lead to the next project immediately, but once we have worked together, it creates a sense of security for both sides, and a good flow gradually develops.
Conclusion
The process is not exactly the same every time. It changes depending on the project content and the situation of both the company and the engineer.
However, what I consistently value is not rushing into things, not leaving conditions or roles ambiguous, and ensuring it is okay to decline if it is not a good fit.
If you are interested, please first read the article on individual consultations.