How to order

This is the whole thing, screen by screen, from the security audit packages to the receipt. The screenshots below are the real pages, not mock-ups. Start to finish it takes a few minutes and you never speak to anyone unless you want to.

1. Pick the package and read what it covers

   Every package page ends with the price and a plain list of what is included and what is not. Nothing is added to that number later, and there is no monthly tie-in on the audit packages.

   
   1. AThe whole price, once
   2. BWhat is included, in writing
   3. CTwo fields, then payment

2. Answer the few things I need before I can start

   Two questions on the Basic audit, five on the Deep one. I only ask what I genuinely cannot start without, and the box at the end is free text if you want to tell me more. The authorisation question is not a formality — I do not test a site without written permission.

   
   1. AOnly what I need to start
   2. BI never test a site without this
   3. CEverything else is optional

3. Check the amount on the payment page

   One screen. The package, the amount, the currency and the delivery time in the summary box, and the cards and wallets I accept under Payment method. The button stays switched off until you accept the terms, and it only opens the card box. Nothing is charged at this step.

   
   1. AAmount and currency, no surprises
   2. BOpens the card box, does not charge yet
   3. CThe cards and wallets I accept

4. Pay in the box that opens over the page

   The box is served by Stripe inside their own frame, so your card number never reaches this website and is never stored here. Pay by card, or with Link if you already use it. The Pay button inside that box is the one that charges, and it is the only one that does.

   

5. You get the confirmation straight away

   The page confirms what you bought and what you paid, with the order reference. The receipt is available on the spot, not only by email.

   

6. Receipt in your inbox and on the screen

   A numbered receipt is issued the moment the payment clears and emailed to you. You can also open it here and download it as a receipt or as an invoice, whichever your accounts department wants.

   

Prefer to pay against an invoice by bank transfer? That is still available, and the terms are on the payment and handover page.

If the job is not one of the fixed packages, it starts with the form instead. I check the scope before anything is invoiced, rather than taking your money first and finding out afterwards.

1. You send me the details

   Write it the way you would explain it to a friend. No technical words needed, and you do not need to know what should be built. What the business does, what happens now, and which part wastes the most time is enough for me to work from.

2. I ask about whatever is missing

   A few questions by email, usually the same day I read it. This is also where I tell you if the job is smaller than you think, or if it is not one I should be taking.

3. One document, within 1 to 2 business days

   Scope, the full price, delivery dates, any monthly running cost, and a plain list of what is not included. The whole number goes in front of you once. Nothing gets added to it later.

4. You decide, and changes are free at this point

   Cut something, add something, or ask why a line costs what it costs. Nothing is committed and nothing is charged while the scope is still moving.

5. Contract in English

   Scope, delivery dates, who owns the code, refund terms, and the hours I answer in, converted to your time zone. My national ID number is on it, so you can check that the person signing is the person doing the work. I am a registered sole trader, not a limited company, so the contract is with me by name. My commercial registration number is 1719900398604, issued by the Thai Ministry of Commerce.

6. Invoice, then work starts

   Once the scope is agreed I send the invoice with the payment instructions on it. Terms are usually half up front, and larger builds are split into stages you pay against work you have already seen and accepted.

7. You see it running before it is finished

   I put the work on a test link while it is being built, not at the end. If something feels wrong in week two, week two is when it is cheap to change.

8. You check it, then handover and 60 days of support

   You use the finished system on my server first and tell me what needs changing. Once the final instalment clears, the source code goes into your own repository and the deployment to your domain follows straight after, with documentation in English. I stay available for 60 days from handover. What that covers and what it does not is written out on the support and refunds page.

For custom work, or if you are not sure which package fits. If you already know which package you want, the buy button on the package page is faster.