The offer

Start a brief

Send me a short written brief. If the job fits, I reply within 2 to 3 business days with a written plan. The price is USD 175 to 275 per hour, set by scope and agreed in writing before any paid hour. After both sides sign the agreement, the first week of 40 hours is free.

Write your briefPriority, USD 4,999

[1]Brief

Your brief

Fields marked optional can stay empty.

Your full name.

I reply here, in writing, within 2 to 3 business days.

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.

What’s wrong or missing, who it affects, and any deadline. Links to docs, tickets or a short recording help a lot. Ten characters at least.

Or write to michael@axdale.com.

[2]Priority

Two ways to start

Most briefs take the standard path, and it costs nothing. Priority is for a production failure that cannot wait.

Standard

Free

A written plan within 2 to 3 business days

  • ReplyWithin 2 to 3 business days
  • CostFree
  • ThenFirst week of 40 hours free after signing

Priority

USD 4,999

My full attention, from the same working day

  • ReplySame working day, by 19:00 CET
  • ThenYour project comes first, with days of up to 16 hours
  • CostOne time, credited in full to your first paid invoice
  • PaymentGitHub Sponsors
Start a priority engagement (opens GitHub Sponsors in a new tab)

Payment sends an alert to my phone the moment it lands.

Pay by 17:00 CET on a working day and my written reply reaches you by 19:00 CET. From then on your project comes first. I work days of up to 16 hours, agreed in writing, with AI coding agents where you approve them, and I keep up with the newest models and current security issues. Paid later, or at a weekend, the reply arrives the next working morning. Send the brief through the form above as well, so I can start the moment the payment lands.

[3]Steps

Three steps

  1. [1]

    Send a written brief

    A few lines are enough to start, and more context helps. Links to the repo, docs or tickets are welcome. 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.

[+]Context

The more context, the better the work

Written context does the job a meeting would do. The more I can read before I plan, the sharper the plan and the faster week 1 gets going.

All of it is optional. Send what you already have, in any form.

  • The repo or the key files, and any architecture notes
  • Tickets, bug reports and past incident write-ups
  • For agent work, examples of good and bad output
  • Limits I should know about, such as data that must stay private
  • A short screen recording you make yourself, if that’s quicker than writing

[4]After week 1

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 hours are USD 175 to 275 each, set by scope and agreed in writing before any paid hour. Invoices go out one week at a time.

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.

[5]Fair use

How the free week stays fair

One free week per company. It’s the first slice of a job that needs at least two paid weeks, with criteria fixed in writing before day 1. It runs on a branch with test keys, never in production. If I hear nothing for three working days it pauses, and after five it ends. The full rules are in the agreement.

Read the agreement

[6]Questions

Questions

  1. Why is the first week free

    A week of work on your code 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 priority include

    A written reply the same working day with the scope, the risks and a first estimate. Then your project comes first, with days of up to 16 hours agreed in writing. The USD 4,999 is credited in full against your first paid invoice.

  3. What do paid hours cost

    USD 175 to 275 per hour, set by scope and agreed in writing before any paid hour. Invoices go out one week at a time. Extra hours need your written approval first.

  4. 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.

  5. 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.

  6. What if my team goes quiet during week 1

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

  7. What if I have questions before I sign

    Send them by email. I answer in writing within 2 to 3 business days, in full, 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 and goes nowhere else. Write to michael@axdale.com to have it deleted.

Analytics on this site

I use Google Analytics 4 to see which pages people read. It records the pages viewed, the device type and an approximate location, such as the country and city. It does not receive your name, your email or the text of a brief. Plan pages all report as one shared address, so no company name reaches Google.

Advertising features are off. I do not use the data for ads and I do not sell it. Google keeps it for 14 months and then deletes it.

Visitors from the EU, the UK and Switzerland see a short choice at the bottom of the page. Until you allow analytics, no analytics cookie is set on your device, and the page sends Google only a basic signal with no identifier in it.

You can change your choice at any time with Analytics choices in the footer. A browser blocker that stops Google Analytics works too, and the site works the same without it.

Last reviewed