Start with a conversation
Everything starts with contact and discussion so the website can be shaped around the real business need before anything else happens.
How It Works
A clear path from first conversation to ongoing support.
This page explains what the process looks like so you know what to expect before you move forward. It covers the demo stage, when payment begins, what portal access includes, and how ongoing support is handled.
Gather the right information
I look at the pages, features, assets, and business requirements needed to build the right site for you.
Build a fully functional demo
The site is built on one of my demo domains and remains fully functional there, so you can explore the real experience before payment begins.
Review and refine
You review the demo, give feedback, and I make revisions. Payment does not begin until the site is approved.
Move into the live service
After first payment, I launch the site in the managed live setup and create your portal access.
Continue with monthly support
Support, invoices, receipts, and service requests continue month to month under the subscription.
What I'll need from you
- Business information and what the site needs to achieve
- The pages, features, and workflows you want the site to support
- Contact details, business details, and service information
- Logo, images, copy, and brand assets if you want custom ones used
- Guidance on where assets should come from if you want me to source them from a specific place
- Any example sites, references, or feature expectations that help define the build
My focus is the programming side of the website. Custom logos, copy, branding, and other site assets are best provided by the client or clearly directed by the client. If I need to design or source those separately, that becomes additional work outside the standard service.
What you can expect
- The demo site is fully functional, not a restricted preview or mockup.
- You review the site before subscription billing begins.
- After approval, the same work moves into the live managed service.
- Portal access begins after first payment.
Portal access
- A portal account is created only after first payment.
- Every login uses an 8-character one-time password sent by email.
- The first login requires acceptance of the current legal documents.
- The dashboard shows your active websites, invoices, receipts, payment instructions, support requests, and cancellation requests.
Portal limits
- Plan changes are handled directly with me rather than through self-service controls.
- Infrastructure and hosting changes are managed directly with me.
- Ownership transfer or moving the site elsewhere is not part of the standard portal flow.
- Receipts appear after payment has been reviewed and confirmed.
Support expectations
- Support requests should be submitted through the internal portal.
- Phone is for discussion and direct conversation.
- Email is best for non-urgent contact.
- Guaranteed hours reserve time for your account, but they do not mean unlimited instant changes at once.
- Support priority runs Dynamic Pro first, then Dynamic Basic, then Static.
- If several requests come in at once and only part of them are handled in the guaranteed time, the remaining work continues through the queue.
Billing and payment details
- Payment starts only after the demo site is reviewed, revised, and approved.
- Invoices for the next month are sent on the last Monday of the current month.
- That timing gives clients the remaining days of that week to pay for the next month.
- Payments are made by cash or bank transfer.
- Each invoice includes a 6-character payment reference for bank transfer.
- No prorated launch dates are used. If payment happens in the middle of a month, launch begins at the start of the next month.
- Receipts are issued after payment has been confirmed.
- No refunds are given once a paid month has started.
Ownership and cancellation
- The standard service is for use of the website service rather than automatic ownership of the full site system or infrastructure.
- The hosting setup, managed service environment, and operating stack remain under my management.
- If a client wants to host the website elsewhere, the website code can be purchased separately.
- If a client cancels, service continues until the end of the paid month and then stops for the next unpaid month.
- Clients may request a database copy or database deletion when ending the service.
Taking over an existing website
- If a business already has a website, I rebuild it in my own stack before taking over long-term management.
- That keeps the service on technology I know well and can support properly over time.
Website timelines depend on the size of the site, the required features, and how ready the client is with assets and decisions. The timeline is discussed after I assess the actual requirements.
Next step