Web developer in Saint John

Businesses in Saint John usually come to me after a site has already been built once and disappointed. That is a useful starting point, because it means the requirements are no longer theoretical — you know exactly which parts failed. Rebuilding from a list of specific complaints produces a far better result than rebuilding from a mood board.

One thing worth knowing about building for Canada

Quebec Law 25 caught a lot of Canadian sites out: consent has to be explicit and granular, and the default cookie banner most agencies drop in does not meet it. I build the consent layer properly rather than bolting on a plugin.

How a Saint John build is scoped before anything is written

Scope is fixed in writing before development starts, and the number in that document is the number on the invoice. For Saint John projects that document lists every page, every form, every integration and every third-party account the site will touch — priced in CAD, not converted at the end from something else.

The reason this matters more than it sounds: almost every dispute in web development is a scope dispute wearing a different hat. "Can you just add" is how a three-day build becomes a three-week one. Fixing scope up front does not stop you changing your mind; it makes the cost of changing your mind visible before you commit to it, which is the only honest way to run a fixed price.

Professional services in Saint John

Accountants, solicitors, consultants and agencies sell judgement, which cannot be photographed. What converts instead is specificity: the sectors you actually work in, the size of client you actually serve, and named people with real biographies. A professional services site full of stock imagery and the word "bespoke" is indistinguishable from every competitor in Saint John.

Practically, the site's job is qualification rather than lead volume. Publishing your minimum engagement size loses you enquiries and saves you hours, and almost every practice I have built for concluded afterwards that it should have done it sooner.

Images shipped at ten times the size they display

A hero photograph exported at 4000 pixels wide and displayed at 400 is the most common single cause of a slow page. The browser downloads all of it and then discards most of it. On a phone over mobile data that is several seconds spent waiting for pixels nobody will ever see.

The fix is generating each image at the sizes actually used, serving AVIF or WebP with a fallback, and setting explicit width and height so the layout does not jump while they load. It is mechanical work with a directly measurable result, which makes it the first thing worth doing on almost any Saint John site.

Hiring a developer who is not in Saint John

Working across a border adds one genuine obligation most suppliers skip: your customers' personal data ends up being processed in a country their privacy notice probably does not mention. Under PIPEDA federally that is your liability, not mine. It is handled here before you ask — the mechanism is published, pre-signed and linked from every page on this site.

What I am not claiming about Saint John

A location page is the easiest place on a website to imply something untrue, so here is the other side of it plainly:

• I have no office, postal address or phone number in Saint John
• I cannot meet you in person, and if that is a requirement you should hire locally
• I am not claiming existing clients in Saint John specifically — my live work is listed on the work page and you can check it
• Nothing on this page is a guarantee of search rankings, which no developer can honestly offer

Saint John web development — common questions

How long does a Saint John project actually take?

Three days for a business site, seven for a store, ten for a custom application. That holds because the process is fixed rather than improvised and because your content exists on day one. What stretches a build is almost never the code — it is waiting for copy, logos and photographs, so those are requested before the clock starts.

What hours will you be available to us in Saint John?

Honestly: very little, by default. My standard day lands at 00:00–09:00 your time, which barely touches a Saint John working day. So Canada projects run on a deliberately shifted schedule — I commit in writing to a fixed daily window that falls inside your morning, plus asynchronous written updates you can read before you start. If a supplier in your own timezone is what you need, that is a legitimate reason to hire locally.

Can you fix my existing site rather than rebuild it?

Often, yes, and it is usually the cheaper answer. Speed problems, a broken mobile layout, a form that silently fails or missing structured data are all fixable on the site you already have. I will tell you which of the two you need after looking, and a rebuild only gets recommended when the fix would cost more than starting again.

Do you provide ongoing maintenance after launch?

Thirty days of snag fixes are included after launch at no extra cost — anything that does not work as specified gets fixed. Beyond that there are monthly plans for updates, backups, monitoring and small changes. They are optional and cancellable; a site handed over properly does not require a retainer to keep running.

What currency will I be invoiced in?

CAD. Quotes, milestones and the final invoice are all written in CAD so you are never comparing a converted figure against a local supplier's. Regarding tax: GST/HST at 5–15% depending on province — my invoices are zero-rated exports and carry no Canadian tax.

Who owns the website when it is finished?

You do, completely. The domain is registered in your name, hosting sits in your account, the code lives in a repository you control, and any payment provider account is opened in your business name. Credentials are handed to you as they are created rather than at the end, so you are never locked out of your own site.

How do you handle our customers' data under PIPEDA federally?

Your customer data is governed by PIPEDA federally, with Quebec Law 25 layered on top if you have Quebec customers, and sending it to a developer in Pakistan is a restricted transfer. That is resolved by a written DPA naming Pakistan as the processing location, which PIPEDA requires you to disclose to your own customers, published on this site and pre-signed before you send an enquiry — not drafted after you ask about it.

Where this page sits

This page covers Saint John. Every other town in Canada is listed on the Canada coverage page, and the full worldwide list is at all locations. The full commercial terms for this market — contracting, currency and the data-transfer mechanism in detail — are on the Canada market page.

Before you enquire: pricing is published rather than quoted on request, how I work covers the process end to end, the work page lists live client sites you can open, and vendor information answers the procurement questions.