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.
Limited availability
PROGRAMMING / SMALL SCOPE / DIRECT
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.
SCENE 02 / SCOPE
SMALL DOES NOT MEAN VAGUE.
THE BOUNDARY IS THE BRIEF.
SCENE 03 / PROTOCOL
Eight checkpoints. Every accepted job gets a clear scope, an individual EUR quote, and an agreed delivery path before work begins.
You send a detailed request through the form or message me privately.
I check the scope, fit, and current availability. Requests can be declined here.
We define exactly what gets built, the EUR quote, and included revisions.
We agree on payment before work starts. PayPal is currently the only method.
I build to the agreed scope. Dates remain estimates unless explicitly agreed.
You inspect the work, report issues, and use the revision rounds in the quote.
After approval and full payment, you receive the agreed files and access.
I fix reproducible bugs in the agreed scope for seven days after delivery.
PAYMENT MODEL / 01
No upfront payment.
PAYMENT MODEL / 02
50 / 50 split.
REVISION CONTROL
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
Source files, ZIP archive, GitHub access or ownership transfer, deployment handoff, and setup documentation when agreed.
FULL CONDITIONS
SCENE 04 / PRIVATE INTAKE
Describe the outcome, constraints, and what already exists. I’ll reply privately on Telegram if the request is a possible fit.
Your submission is sent privately to my Telegram chat and is not intentionally stored in a website database.