AYON1XW COMMISSION INTAKE

Limited availability

PROGRAMMING / SMALL SCOPE / DIRECT

SelectedCommissions

I take on a limited number of small, clearly scoped programming projects. Send what you need; I’ll check the fit before discussing scope and price.

A request is not an acceptance.

RESPONSE USUALLY < 24H
PAYMENT EUR / PAYPAL
Open request protocol

SCENE 02 / SCOPE

Know the
boundary.

01

Good fit

ACCEPT
  • Small websites and landing pages
  • Portfolio pages
  • Small scripts and tools
  • Bug fixes
  • UI cleanup
  • Discord or Telegram bot features
  • README / GitHub setup
  • Small automation
  • Focused edits to existing code
02

Not a fit

DECLINE
  • Full SaaS or startup builds
  • Large or long-term projects
  • Payment systems
  • Crypto, gambling, banking, or similarly risky projects
  • Malware, spam tools, account bots, or private-data scraping
  • Vague requests without a clear scope

SMALL DOES NOT MEAN VAGUE.
THE BOUNDARY IS THE BRIEF.

SCENE 03 / PROTOCOL

Request to
handoff.

Eight checkpoints. Every accepted job gets a clear scope, an individual EUR quote, and an agreed delivery path before work begins.

  1. 01

    Request

    You send a detailed request through the form or message me privately.

  2. 02

    Fit check

    I check the scope, fit, and current availability. Requests can be declined here.

  3. 03

    Scope & quote

    We define exactly what gets built, the EUR quote, and included revisions.

  4. 04

    Agreement

    We agree on payment before work starts. PayPal is currently the only method.

  5. 05

    Development

    I build to the agreed scope. Dates remain estimates unless explicitly agreed.

  6. 06

    Preview

    You inspect the work, report issues, and use the revision rounds in the quote.

  7. 07

    Payment & delivery

    After approval and full payment, you receive the agreed files and access.

  8. 08

    7-day support

    I fix reproducible bugs in the agreed scope for seven days after delivery.

PAYMENT MODEL / 01

Small project

No upfront payment.

  • I build and show a preview.
  • You pay in full when happy with the preview.
  • Files, source, repository access, or ownership follow full payment.

PAYMENT MODEL / 02

Larger project

50 / 50 split.

  • 50% before work begins.
  • Preview when the work is ready.
  • Remaining 50% before final delivery and handoff.

REVISION CONTROL

Two rounds by default.

The exact allowance is always stated in the quote. Extra revisions may cost more; new features or changes beyond the agreed scope require a separate quote.

DELIVERY OPTIONS

Agreed per project.

Source files, ZIP archive, GitHub access or ownership transfer, deployment handoff, and setup documentation when agreed.

SCENE 04 / PRIVATE INTAKE

Send the
brief.

Describe the outcome, constraints, and what already exists. I’ll reply privately on Telegram if the request is a possible fit.

CHANNEL
TELEGRAM
STORAGE
NO SITE DATABASE
STATUS
Limited availability

With or without the @. This is where I’ll reply.

What should be built, what it’s for, and anything already decided. At least 50 characters.

0 / 3000 characters

Free text. This is preferred, not guaranteed.

Confirm before transmission

Your submission is sent privately to my Telegram chat and is not intentionally stored in a website database.