Client operations
Partners keep freelance accounts, messages, and payouts in their own name while the studio stays behind the work.
Delivery studio
A small team for freelance work.
Codepilot is a two-role studio. Client partners own the relationship and the freelance account. Engineering owns planning, build, and delivery. Project fees are shared 20% / 80%. No coding required to join the client side.
The studio
Built like an agency. Sized like a focused team.
Product engineering
The delivery team handles planning, development, testing, and launch support for each engagement.
Accountable delivery
Deadlines and quality sit with engineering, so client partners can focus on communication — not the build.
The team
Two seats. One studio.
Codepilot is built as an agency, not a one-person pitch. Client partners hold the relationship. Engineering holds the build.
Client operations · 20%
Client partners
- Work from a legitimate freelance account in their own name (Upwork, Fiverr, Freelancer, LinkedIn, and similar)
- Handle day-to-day client communication — relaying messages and sharing updates
- Receive drafted technical replies from the delivery team whenever needed
- Collect payment on the account, then share project fees with the studio
Engineering · 80%
Delivery team
- Source suitable projects and handle bidding
- Own technical planning, development, testing, and delivery support
- Keep work on schedule and up to the studio standard
- Stay accountable for quality so partners are not guessing at the build
How we work
How a project moves
Strong technical work and freelance experience mean jobs are secured and delivered quickly. For client partners, that turns into income on their own account — a few hours a week of messages and coordination, not a full-time job, and not coding.
Fast job securing
Engineering sources work and writes the technical bids. Freelance experience is what gets suitable projects locked in sooner. Partners do not hunt for work.
Fast delivery
Planning, development, and testing stay with the studio, so the job ships on schedule.
Quick income
When the client pays, the fee lands on the partner’s account. Partners keep 20% and send 80% for the build.
01
The studio finds and bids
Engineering sources suitable projects and handles bidding from freelance experience, so work gets locked in sooner. Partners do not need to hunt for work or write technical proposals.
02
Partners talk to the client
Messages come through the partner’s freelance account. They relay updates. When a reply needs technical detail, delivery drafts it.
03
Engineering builds and tests
Planning, development, testing, and delivery stay with the studio. Technical depth is what keeps the job on schedule and up to standard.
04
The client pays. Fees are shared.
Payment lands on the partner’s account — the quick-income moment. Partners keep 20% and send 80% for the build — always through their own payouts.
Project fees
How the studio shares work.
Fees follow the work. Engineering, planning, testing, and delivery take the larger share. Client partners are paid for the account, communication, and collecting payment.
20% partners
80% delivery
The client pays the partner
Invoices and platform payouts stay in the partner’s name, on their account.
Delivery receives the build share
After the client pays, 80% covers planning, development, and delivery.
Partners keep the client share
20% stays with the partner for communication, coordination, and the relationship.
Who we’re hiring
Client partners, not engineers.
- A computer and reliable internet
- A legitimate freelance account in their own name — no fake identities, no bought accounts
- A few hours a week for communication and coordination
- Comfort with basic client chat; the delivery team drafts technical replies
Not required
- Coding skills
- Finding or bidding on projects
- Doing the actual development, testing, or delivery
The studio is looking for people who already have — or can open — a freelance account, and who can commit a few hours a week. That’s enough to start a conversation.
FAQ
Before joining
Does a client partner need to code?+
No. Communication and coordination sit with client partners. Planning, development, testing, and delivery stay with engineering.
Who talks to the client?+
Client partners do, through their own freelance account. They relay messages and share updates. The delivery team drafts technical replies whenever needed.
How do payments work?+
The client pays the partner. Partners keep 20% and send 80% for the build. Payouts stay on the partner’s freelance account.
Can someone use a bought or shared account?+
No. The account has to be legitimate and in the partner’s own name. Fake identities and purchased accounts are out.
How much time is this?+
A few hours a week for messages and coordination. It is not a full-time role and it is not development work.
Who finds the projects?+
The studio does. Engineering looks for suitable work and handles bidding so partners are not writing technical proposals.
Partner feedback
How client partners worked with the studio
Nikhil V.
USA · Upwork
“I relayed client messages on a few projects while engineering owned the build. Kept the relationship moving — without coding.”
Nguyên N.
Vietnam · Fiverr
“I handed off what the client needed, used delivery’s drafted technical replies when it mattered, and saw the projects ship.”
Amalia G.
Spain · Upwork, Freelancer
“The client paid on my account. I kept my share and sent the build share — the split stayed clear and legitimate.”
Guillermo R.
Mexico · Upwork
“The studio found and built the work. I stayed on the client side and kept communication moving through delivery.”
Bohdan Z.
Ukraine · Upwork, Fiverr
“Ran from a legitimate account with engineering behind each delivery. A few hours a week was enough for the engagements.”
Andersen L.
USA · Upwork, LinkedIn
“I kept the client conversation on my accounts while the studio took the technical load. After payout, the split stayed straightforward.”
Nikhil V.
USA · Upwork
“I relayed client messages on a few projects while engineering owned the build. Kept the relationship moving — without coding.”
Nguyên N.
Vietnam · Fiverr
“I handed off what the client needed, used delivery’s drafted technical replies when it mattered, and saw the projects ship.”
Amalia G.
Spain · Upwork, Freelancer
“The client paid on my account. I kept my share and sent the build share — the split stayed clear and legitimate.”
Guillermo R.
Mexico · Upwork
“The studio found and built the work. I stayed on the client side and kept communication moving through delivery.”
Bohdan Z.
Ukraine · Upwork, Fiverr
“Ran from a legitimate account with engineering behind each delivery. A few hours a week was enough for the engagements.”
Andersen L.
USA · Upwork, LinkedIn
“I kept the client conversation on my accounts while the studio took the technical load. After payout, the split stayed straightforward.”
Nikhil V.
USA · Upwork
“I relayed client messages on a few projects while engineering owned the build. Kept the relationship moving — without coding.”
Nguyên N.
Vietnam · Fiverr
“I handed off what the client needed, used delivery’s drafted technical replies when it mattered, and saw the projects ship.”
Amalia G.
Spain · Upwork, Freelancer
“The client paid on my account. I kept my share and sent the build share — the split stayed clear and legitimate.”
Guillermo R.
Mexico · Upwork
“The studio found and built the work. I stayed on the client side and kept communication moving through delivery.”
Bohdan Z.
Ukraine · Upwork, Fiverr
“Ran from a legitimate account with engineering behind each delivery. A few hours a week was enough for the engagements.”
Andersen L.
USA · Upwork, LinkedIn
“I kept the client conversation on my accounts while the studio took the technical load. After payout, the split stayed straightforward.”
Join the team
Apply as a client partner
Share the freelance account you already use, and how many hours a week you can commit. The studio will take it from there.