Our process
What happens between “yes” and “live”.
Most people buying a website have never bought one before. Here is the whole thing, in order, including the parts that are your job rather than ours.
In one paragraph
A Latx Technologies project runs in five stages: discussion, design, implementation, testing and delivery. Each stage ends in a written approval, so no work continues on an assumption nobody confirmed. During implementation you get regular progress and review calls, and after delivery you get two months of maintenance covering content changes and bug fixes.
-
5 Stages
-
5 Approval gates
-
2 rounds design revisions included
-
2 months maintenance after delivery
The stages
Five stages, five approvals.
Each stage lists what we do, what you do, and what you sign off before the next one starts.
-
Stage 01
Discussion
We go through your pages, your goals and your requirements. Out of that comes a written scope: what is included, what is excluded, and the assumptions behind the figure. The quote is fixed, and the scope document is yours to keep whether or not you proceed.
This is also where we look at your current site if there is one, at what competitors are doing, and at what people actually search for, so that the structure is decided deliberately rather than copied. It is the stage that decides whether the site works, and it is the one most often skipped.
- We do
- The call, the research, the scope, the quote
- You do
- Describe the business honestly
- You approve
- The scope and the quote
-
Stage 02
Design
We design the look and the structure. The homepage comes first, because it sets the direction for everything else, and once you are happy with it the remaining templates follow quickly. Two rounds of revisions are included, and what counts as a revision is written into the scope so nobody has to argue about it later.
- We do
- Homepage, then templates
- You do
- Consolidated feedback, once per round
- You approve
- The designs
-
Stage 03
Implementation
We build it, with regular progress and review calls so you are never in the dark. The theme is written from scratch, content goes in, forms and integrations are wired up. You get a link on the first day of this stage and can look at it whenever you like.
Responsive behaviour, accessibility and performance are checked as the build progresses, not bolted on at the end where they are always the first things cut.
- We do
- Build, content, integrations, weekly calls
- You do
- Supply remaining content and review as we go
- You approve
- The build
-
Stage 04
Testing
Ours first: cross-browser and device testing, an accessibility pass, a performance pass, schema and analytics verification, and redirects if we are replacing an existing site.
Then yours. You get real time to test everything thoroughly rather than a two-day window before a date we picked. Anything you find in this stage is fixed before launch, not after it.
- We do
- Our test passes, then fix what you find
- You do
- Test it properly, on your own devices
- You approve
- That it is ready
-
Stage 05
Delivery
Launch in an agreed window, a recorded walkthrough on your actual site, and handover of every credential and every file: admin, hosting, domain, the theme, any custom plugin code, and a full content export.
Then two months of maintenance, included. Content changes and bug fixes are covered for eight weeks after delivery, so you are supported once you go live rather than handed a login and wished luck.
- We do
- Launch, train, hand over, then maintain for 2 months
- You do
- Attend the walkthrough
- You approve
- Go-live
Your side
What we need from you.
This is the most useful list on the page. Projects that have these ready run smoothly; projects that do not, do not.
-
Logo and brand files in the highest quality you have, ideally vector.
-
Photographs of the real business, the real team, the real product.
-
Page content, or approval for us to write it as a quoted addition.
-
Product or service details — names, descriptions, and any regulated wording.
-
Domain and hosting access, or permission for us to arrange them.
-
One named decision-maker. Feedback from five people who disagree is the single most expensive thing in a project.
What actually slows projects down
In our experience it is almost never the development. It is one of these four:
-
Content arriving late. The design is ready and the pages are empty. This is the number one cause of a delayed launch, by a wide margin.
-
Feedback by committee. Contradictory notes from several people, with nobody empowered to settle them.
-
Changes after an approval gate. Reopening a signed-off design is a new design stage, and it is quoted as one.
-
Third-party access delays. Waiting on a hosting password, a payment gateway account, or a previous developer who has stopped replying.
Working together
How we communicate.
Predictable, written, and from the people doing the work.
-
One named contact
A named designer and a named developer are introduced at kickoff and stay with the project. You talk to them directly, not through an account manager relaying messages.
-
A written update every week
On a fixed day: what moved, what is next, and anything we are waiting on from you. Written, so there is a record you can look back at.
-
A reply within one business day
To any question, during the project and for the support window afterwards. If the answer needs research, you get an acknowledgement in that time and the answer after.
-
A staging link from the build stage
Open any time. Nothing is hidden until it is finished, and there is no dramatic reveal at the end that you either love or have to live with.
-
Everything in writing
Scope, quote, approvals and change requests. Verbal agreements get written up and confirmed, because memory is not a project management tool.
-
We say when something is a bad idea
Including when the cheaper option is the right one, or when what you have asked for will not do what you want it to do. Before you pay, not after.
Common questions
About how projects run.
What are the stages of a website project?
Discussion, design, implementation, testing and delivery. Each stage produces a specific deliverable: a written scope and fixed quote, approved designs, a built site you can review with regular progress calls, a testing window that is genuinely yours, and a live site handed over with every credential plus two months of maintenance.
What do I need to provide?
Logo and brand files, photographs, page content or approval for us to write it, product or service details, access to your domain and hosting, one named decision-maker, and feedback within the agreed window at each approval gate.
How many rounds of revisions are included?
Two rounds at the design stage. A revision is a consolidated set of changes to an existing direction. A request to start a new direction after approval is a new design stage and is quoted separately — and this is written into the scope before work begins, so it is never a surprise.
What happens after my website goes live?
Two months of maintenance are included, covering content changes and bug fixes at no extra cost, plus a recorded training session and full handover of credentials and files. After those two months you either self-manage the site, which most clients can because they already edit their own content, or move to a monthly care plan covering updates, backups, security and support.
What if I do not like the design?
Say so early and specifically. That is exactly why the homepage is designed first and why revisions are built into the stage — it is far cheaper to change direction on one page than on eight. If the direction is genuinely wrong we would rather redo it than build a site you do not want to show anyone.
Start here
Ready to start at stage zero?
Send a few lines about the project. A developer reads it and replies within one business day, and you get a written scope before anyone asks you for money.