The offer

Start a brief

Send me a short written brief. If the job fits, I reply within one working day with a written plan. After both sides sign the agreement, the first week of 40 hours is free. After that you continue on paid weeks of USD 3,200 for up to 40 hours, or you stop.

[1]Three steps

Three steps

  1. [1]

    Send a written brief

    Under 300 words. A public repository link helps, but access to private code comes later.

  2. [2]

    Sign the agreement

    You approve the plan and its acceptance criteria in writing, and both sides sign.

  3. [3]

    Week 1 starts

    Forty hours over five working days, free of charge, within 10 working days of signing.

[2]Brief

Your brief

Fields marked optional can stay empty.

Your full name.

I reply here, in writing, within one working day.

The company the work is for. The free week is one per company.

A public link helps. For private code, leave this empty. I ask for access only after both sides sign.

Under 300 words. What should change for your users, how you will know it worked, the stack, and anything I must not touch.

Or write to michael@axdale.com.

[3]After week one

Paid weeks, or stop

You get a pull request with tests, a handover note and a written plan for the paid weeks. Then you choose.

To continue, approve the next week in writing. Paid weeks are USD 3,200 for up to 40 hours, invoiced one week at a time, in advance.

To stop, send a short written close-out within 10 working days, with two to four sentences of honest feedback. The week 1 work is then yours to keep. If neither happens, I close the pull request and delete my copies. The brief, the plan, the updates and the handover note stay with you in every case.

[4]Fair use

How the free week stays fair

A free week only works if it is fair to both sides. These are the rules, and the reason for each.

  • One free week per company. This includes related companies and email domains, and companies that have hired me before.
  • A real job. The free week is the first slice of a job that needs at least two paid weeks after it. A smaller job is a paid week.
  • Criteria fixed before day 1. One named person approves them in writing, so the week does not keep growing.
  • Forty hours or five days, whichever comes first. The box is fixed, so both sides know where it ends.
  • A branch or a fork, and test keys. There is no production access, data or deploy in the free week.
  • A pause on silence. If I hear nothing for 2 working days, the week pauses. After 5, it ends and counts as your free week.
  • A limited number at a time. I run only a few free weeks at once. I may put your start date on a dated waiting list, or decline in writing with the reason.

[5]Questions

Questions

  1. Why is the first week free

    A week of real work tells you more than a profile. I offer it only for jobs that need at least two paid weeks after it, so it stays fair to both sides.

  2. What does a paid week cost

    USD 3,200 for up to 40 hours over five working days, invoiced one week at a time, in advance. Extra hours need your written approval first.

  3. Do you need access to production

    No. Week 1 runs on a branch or a fork with test keys. In paid weeks, each production change needs written approval for that specific step.

  4. Will AI tools see my code

    Only the providers you approve in writing. I review every change an AI tool helped to write, and the pull request says so.

  5. What if my team goes quiet during week 1

    After 2 working days of silence the week pauses. After 5 it ends and counts as your free week.

  6. What if I have questions before I sign

    Send them by email. I answer in writing within one working day, and the answers stay in your inbox for your team.

Privacy

What happens to your brief

I use what you send only to reply to your brief. It is stored in a database on Cloudflare, with no cookies and no tracking. Write to michael@axdale.com to have it deleted.