close

Taking new briefsFull-stack engineering, for funded US product teams

Send me your project. I take it from brief to shipped.

BERJAYAMichael Lip
Agentic full-stack developer, freelance since 2015, Warsaw, Poland (CET)

I’ve shipped more than 50 client projects since 2015, and that experience decides what I build and what I leave out. Go, TypeScript and Python, React, Django, Postgres and AWS. I pick what fits your product and own all of it, from the database to the screen. One client has kept me for 14.5 months, sprint after sprint.

Send me your projectSee the price

Within one working day of a complete brief you get a written plan, free. The first milestone is up to 20 hours at USD 65 per hour, and you pay for it only if you accept it.

Code merged by maintainers at Dagu, Vendure, CISO Assistant, Appium, Sympozium and Google Chrome samples.

Client projects shipped since 2015
50+
One client since August 2025, hourly then in sprints
14.5 months
Merged pull requests in other people’s repositories
300+
Price, one rate for all work
USD 65 an hour
A whole project, from your brief to shipped codeSix stages from left to right. One, your brief with the scope, the files and the deadline. Two, a written plan with milestones, risks and an estimate, free within one working day. Three, many thin lines fan out, the agent lanes that read code, reproduce bugs and draft changes in parallel, only where you approve it in writing. Four, every line meets one review node, where I reproduce, test and review each change. Five, a few small pull requests with tests leave the node. Six, they merge into your main branch only on your approval. Along the bottom, a week axis with one written report at the end of each week. Counts of lines and pull requests are schematic.[1] Briefscope and files[2] Planfree, in 1 day[3] Agent lanesread, reproduce, draft[4] Reviewevery change[5] Pull requestssmall, tested[6] Shippedyour approvalscopemilestonesrisksestimateaccessreproduce, test, reviewmainweek 1week 2week 3week 4week 5week 6Paid work, one written report at the end of every week, 18:00 CETA whole project, from your brief to shipped codeSix stages from left to right. One, your brief with the scope, the files and the deadline. Two, a written plan with milestones, risks and an estimate, free within one working day. Three, many thin lines fan out, the agent lanes that read code, reproduce bugs and draft changes in parallel, only where you approve it in writing. Four, every line meets one review node, where I reproduce, test and review each change. Five, a few small pull requests with tests leave the node. Six, they merge into your main branch only on your approval. Along the bottom, a week axis with one written report at the end of each week. Counts of lines and pull requests are schematic.[1] Briefscope, files, deadline[2] Planfree, one working day[3] Agent lanesread, reproduce, draft[4] Reviewone engineer, every change[5] Pull requestssmall, with tests[6] Shippedon your approvalscopemilestonesrisksestimate
A whole project, from your brief to shipped code. The agent lanes do the legwork in parallel, and every change passes one review before it becomes a pull request. Lines and pull requests are schematic.

[1]Proof

What the maintainer wrote when he merged the fix

github.com/dagucloud/dagu/pull/3035

Merged dagucloud/dagu · Go · 4.5k stars · merged 7 Oct 2026

Stop gracefully on SIGINT and SIGTERM fix(worker)

+ stop the pollers first, then drain running tasks
+ forward SIGTERM to each running task
+ tests in signal_unix_test.go and lifecycle_test.go

All checks passed

“The drain design is the right one, and the writeup made it easy to verify”

This is the shape of what you get back. One cause, one small pull request with a test, and a write-up a reviewer can check. Open it on GitHub

[2]Price

One rate, three steps, and a first milestone you pay for only if you accept it

[1]

A free project plan within one working day

Send the brief, the repo and the files. I read them and send back a written plan with the scope, the milestones, the risks, an estimate and what I need from you. A single bug works too, and then the plan is a diagnosis. When the repo is public and you say yes, a draft pull request comes with it.

[2]

A first milestone with an acceptance guarantee

Up to 20 hours at USD 65 per hour. The acceptance criteria are agreed in writing first, and if the result doesn’t meet them, you don’t pay for it.

[3]

Then USD 65 per hour, milestone by milestone

Invoiced weekly for the hours worked, with one written report each week. No retainer, no minimum, and the code is yours once each invoice is paid.

One rate covers the whole stack, because the agent lanes do the legwork in parallel and I bill only my own hours. No retainer, no minimum, and the only paid step before you’ve seen the work is a first milestone you can reject.

See sample diagnoses of merged fixes

[3]Sizes

What a whole project usually costs

[1]

Fix and harden a product

About 40 to 80 hours over 2 to 4 weeks, so USD 2,600 to 5,200. Failing jobs, slow pages, security gaps and missing tests, each closed with a written before and after.

[2]

A feature, end to end

About 80 to 160 hours over 3 to 6 weeks, so USD 5,200 to 10,400. The database change, the API, the screens, the tests and the release, delivered in milestones you accept one by one.

[3]

A product, first release

About 200 to 400 hours over 2 to 4 months, so USD 13,000 to 26,000. Scope, architecture, build, deploy and handover, with a working release at the end of every milestone.

[4]

A product team’s backlog

About 400 to 750 hours over 3 to 6 months, so USD 26,000 to 48,750. A standing lane next to your team, planned in milestones you accept one by one, with a written report every week.

For scale, sprints 13 to 18 for my long-term client came to 316 billed hours. Your written plan names the real number for your project before any paid hour, and you can stop after any milestone.

[4]Direct

Why I work directly with clients

[1]

Work first, payment after

You see working, tested code before you pay. The first milestone is billed only if you accept it, and every milestone after it works the same way.

[2]

Pay the way you prefer

Bank wire, PayPal, GitHub Sponsors or crypto, invoiced in USD. If you want the money held until you accept the work, I use an escrow service you are happy with.

[3]

No platform in the middle

For years my client work ran through freelance platforms. A platform can close an account overnight, even mid-project, so I left to work directly. You deal with the engineer doing the work, and nobody else holds the relationship.

[4]

My full-time work

Client engineering is my living, so every relationship matters. I reply within one working day, keep your code and data private, and treat your decision to hire me with the respect it deserves.

[5]Why me

Why hire a contractor, and why this one

This is business to business. You buy finished, accepted work from my company, not a seat on your payroll. You carry no benefits, no payroll taxes, no recruiting and no promise of permanent work. A project runs for as many sprints as it needs, then it closes with a handover, a pause and a handshake, and you can come back any time.

What you pay forTwo bars. An employee costs wages, about 70 percent, plus benefits, about 30 percent, plus hiring and idle weeks. A contractor costs only the milestones you accept. Three accepted milestones are solid, and a rejected milestone is dashed and costs nothing.What you carryEmployeeWages 70%BenefitsHiringContractor, meAccepted milestonesRejected, USD 0US private employers, BLS2025

[1] You pay for results

A US employer spends about 30 percent of each hour’s cost on benefits, before hiring and idle weeks. With me you pay for accepted milestones, and nothing else.

A project with an endA timeline. Sign, plan, fifteen sprint dots, handover, then a handshake. The project starts when you sign and ends with a handover.One project, start to endSignPlanSprints 1 to 15HandoverHandshakeA written report every weekStarts at signingEnds handed over

[2] A project with an end

No payroll, no notice period, no promise of permanent work. A project runs for the sprints it needs, then closes with a handover note and a handshake.

Four clients at mostFour client slots side by side. Each slot shows a range from 10 to 40 hours a week. When all four are taken, new briefs get the next quarter with an open slot.Clients at one time123440h10hAll four taken, the auto-replynames the next open quarter

[3] Four clients at most

I keep three to four clients at a time, 10 to 40 hours a week each. That limit is why each one gets my full attention.

No hand-holdingA short brief becomes a full written report within one working day of access, with no check-ins in between.From brief to full reportno check-insReportAccessone working dayReportBrief onceFindings, plan, risks

[4] No hand-holding

You write the brief once. Within one working day of access you get a full written report, with what I found, what I will do and the risks.

Why work with me. Benefit share from the US Bureau of Labor Statistics, 2025. Capacity and hours as I run my practice today.

What you get is an engineer with more than 50 client projects shipped since 2015, who also builds and runs live products that real people use and pay for. I choose my clients and how I solve their problems, so the price is a rate for results, ready from the day you sign the contract.

Source for the 30 percent, BLS Employer Costs for Employee Compensation.

[6]Case studies

Shipped work, with the numbers

A clinical platform built over 11 months, fixes inside two AI agent platforms, and production bugs in workflow and messaging systems. Private clients are anonymized. Open source work links to the merged pull request.

Products I design, build and run

Every screen, diagram and line of code below is mine, from the first sketch to the store release.

All work

[7]How it works

Your night is my working day

I work 09:00 to 18:00 in Warsaw, which is 03:00 to 12:00 in New York, so most of the work is done before your team starts. AI coding agents help with the legwork, on private code only where you approve it in writing, and every change is reproduced, tested and reviewed by me before it becomes a pull request. I bill only my own hours.

How I work, step by step

[8]Your risks

What goes wrong with contractors, and what I do about it

[1]

You won’t have to hand-hold me

I write the plan, the weekly report and every question, each with a default answer. I need one person who decides.

[2]

Nothing reaches production unapproved

I never push to your main branch. Work runs on a branch with test keys, and the NDA and DPA are ready to sign, and the security pack comes on request.

[3]

You pay for accepted work

The first milestone is paid only if it meets the agreed criteria. After that, if an accepted criterion fails, tell me within 10 working days and I fix it at no charge.

[9]Questions

Four questions every CTO asks before the first paid hour

[1]

Who your finance team pays

I invoice in USD through AUTOM8 LLC, my registered company. Your finance team gets a W-8BEN-E and the signed agreement before the first paid hour.

[2]

If I am ever unavailable

You already hold the code, every weekly report and a handover note another engineer can continue from. Nothing lives only in my head or in my accounts.

[3]

Private code and the NDA

I sign your NDA before I read a line of private code. Access is the minimum the work needs, and it ends with the project.

[4]

Who this is not for

If you need daily video meetings, someone in your time zone all day, or a fixed price without a written scope, I am not the right fit. Everything here runs in writing, with a report every week.

[10]About

About

Michael Lip, portrait in black and white

Michael Lip

Agentic full-stack developer

Warsaw, Poland (CET)

I’m Michael Lip, an agentic full-stack developer in Warsaw, Poland (CET), freelance since 2015. Since March 2023 I’ve logged more than 7,300 engineering hours for 27 engineering clients, and five of them kept me for more than 600 hours each.

GitHub credits me as the reporter on 4 published security advisories, including a High 8.7 CVE in NLTK, the Python language toolkit.

Security advisories

How I work

Next step

Send me your project, or the part your team can’t get to.

Send me your project

My last client result, a reports page cut from 3,800 requests per load to 3. The brief and the repo are enough to start.

How it starts

  1. [1]Send your project
  2. [2]Get a free plan
  3. [3]Approve the first milestone