Payment FAQ: Scope, Pricing, Timeline, Refunds

No. Please share the project details first. Payment should only happen after the scope, package, price, and next step are clearly confirmed.

Because every website issue is different. A small bug, a broken form, a slow website, and a full rebuild do not require the same amount of work. Reviewing the scope helps avoid the wrong package being chosen.

It is better not to. Payment links are available for convenience, but the safest flow is to confirm the scope first so both sides understand what is included.

Your submitted details are reviewed first. If the request is clear, I can recommend the most suitable next step, package, or payment option. If the request needs clarification, I may ask follow-up questions before payment.

Start with the Free Quick Check or send the project details first. I can help you understand whether the website needs a small fix, deeper cleanup, a new website, or monthly website care.

Package prices are fixed for the listed scope. If the request goes beyond the package, I will explain the difference before asking for any extra payment.

A fix package is for improving or repairing an existing website. A new website package is for building a fresh page, multi-page website, or website with a small system.

If the payment was made before scope confirmation, the work may need to be reviewed first. If the package is clearly not suitable, I will suggest the correct option and discuss the safest next step.

Yes. Monthly website care is for monitoring, small edits, priority fixes, or ongoing support depending on the selected plan.

Yes. If your request does not fit the listed package, I can review the details and prepare a custom quote based on the actual scope.

The timeline starts after the scope is confirmed, payment is completed where required, and all important content or access details are ready.

Timeline can change if required content is missing, feedback is delayed, extra requests are added, the website has hidden technical issues, or third-party services take longer than expected.

Sometimes, yes. Urgent work depends on the current workload, the size of the issue, and whether the required access or information is ready.

Yes. For normal project work, I will give updates when there is progress, when feedback is needed, or when something important changes.

If feedback, files, or access details are delayed, the project timeline may also move. This helps keep the workflow fair and realistic.

Small revisions are usually included when they are part of the confirmed scope. Large changes, new sections, new features, or a different direction may require a new quote.

A small revision may include text changes, spacing adjustments, small layout polish, replacing an image, or improving a section that was already part of the confirmed work.

A new request may include a new page, new feature, new form logic, payment flow, admin function, automation, extra integration, or a redesign direction that was not part of the original scope.

Yes, but it should be reviewed separately. If the extra work affects cost or timeline, I will explain it before continuing.

Scope control keeps the work clear, prevents confusion, protects both sides, and helps the project finish without becoming messy.

Refunds depend on the situation, how much work has already started, and whether the issue is caused by unclear scope, duplicate payment, technical failure, or cancellation. Each case needs to be reviewed fairly.

Contact me as soon as possible with the payment details. If no work has started and the payment was clearly accidental, the situation can be reviewed.

If the payment fails, no project is confirmed yet. You can try again, use another available payment option, or contact me before proceeding.

If you want to cancel, contact me as early as possible. Cancellation is easier to handle before work has started or before major project time has been used.

No. Stripe and PayPal checkout pages are handled by those payment providers. This website only links to the payment options where relevant.

After payment, keep the payment confirmation and make sure your project details, files, links, and access requirements are ready. I will use the confirmed scope as the guide for the work.

Payment helps confirm the next step, but the project still follows the agreed scope. For safety, scope and payment should be clearly matched before work begins.

Submitted details may be sent to business email notifications and may be reviewed in an admin or dashboard system for tracking. Please avoid sending passwords, payment card details, or private customer data through public forms.

Yes. Asking before payment is recommended, especially if you are unsure whether your request is a small fix, cleanup, new website, or monthly care plan.

The safest way is to send your details first, wait for scope confirmation, then use the correct payment link only when the package and next step are clear.