How we work
Our Process
Most web projects fail quietly. Not because the code was wrong, but because nobody agreed who owned which decision, and the silence between updates grew until one side assumed the worst.
So we publish the whole process. Every step below names who owns it and roughly when it happens. You will receive this same document as a PDF the moment your payment clears, and you may hold us to every line of it.
One line matters more than the rest: sending us content and access on time is the single largest cause of delay on every project we have ever run, and it is the part only you can do.
-
01
Payment clears and your slot is reserved
Your receipt arrives immediately, along with this document and your proposal. Your place in the build queue is held from this moment, not from when we next speak.
Owner: Automatic Typically: Within minutes
-
02
We make contact
A real person texts you, then emails, within one business day. Not a sequence, not a bot. We confirm what you bought and ask for what we need to start.
Owner: Megaone Typically: One business day
-
03
Kickoff call
Forty-five minutes. We agree the single outcome the project must produce, who approves work, and the dates that actually matter to your business. Bring the decision-maker.
Owner: Both Typically: Within the first week
-
04
You send content and access
Logo files, brand colours, copy, product data, hosting credentials. This is the single most common cause of delay on every project we have ever run, and it is the part only you can do.
Owner: You Typically: Within one week of kickoff
-
05
Structure before design
We map every page and every content type before a pixel is drawn. You approve the skeleton. Changes here cost minutes; the same change after design costs days.
Owner: Megaone, you approve Typically: Week one to two
-
06
Design, in the browser
We show you the real thing on your own phone, not a flat image that behaves differently once built. Feedback is consolidated into rounds rather than trickling in.
Owner: Megaone, you review Typically: Week two to four
-
07
Build and integration
Bespoke code, no page builders. Payments, SMS and analytics are wired and tested end to end with real transactions before anyone calls it finished.
Owner: Megaone Typically: Week three onward
-
08
You test on staging
A full copy of the site, on a private URL. Click everything. Break it deliberately. Nothing reaches production until you have tried to.
Owner: You Typically: One week before launch
-
09
Training and handover
A recorded session teaching your team to run the site. You receive the repository, the documentation and every credential. There is no licence to renew.
Owner: Megaone Typically: Launch week
-
10
Launch, then watch
We deploy, verify every form and payment path against production, and watch the first day of real traffic with you. Then your support window begins.
Owner: Megaone Typically: Launch day
That is the whole process.
No mystery, no silence, no invoice you did not expect. Start whenever you are ready.